March 2008 - openSUSE Autoinstall - openSUSE Mailing Lists

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

[opensuse-autoinstall] Custom autoInstall boot CD for multiple distributions (SLES 9 & SLES10)
by Adam Hawks 05 May '08

05 May '08

Is it possible with AutoYast and CD install source to have different options in the isolinux.cfg that will autoinstall DIFFERENT releases. I have a product that installs on top of SLES and supports both SLES 9 and SLES 10. My customer base is mostly hardware maintenance folks not computer users so automation in necessary I'm trying to make my software install using autoinstall with a custom boot CD. I plan to have the "isolinux.cfg" present a list of machine hardware models and SLES version combination for them to select from and the rest be automated. I'm having trouble getting my custom boot CD to boot and start yast and then ask for the CD1 of SLES 9 or SLES 10 depending on which "isolinux.cfg" option was selected. It correctly boots and starts yast with the correct config file but then fails when it reaches "Configure Software Selections" and pops up the "Initializing catalogs" window. The error window contains: Error occurred while creating the catalog. cd:///?devices=/dev/hdc Source rejected by the user Retry Abort I was expecting it to ask for the SLES 9 CD #1 at this point but it does not. I have tried various combinations of options in the "content" files and in the "yast/order" and "yast/instorder" files to no avail. At this point I'm in need of help on how or IF this is even possible. My CD layout is as follows with some contents specific to the SLES 9 selection /media.1/media products /XPONSLES10/content 686850U.xml 68685AU.xml 8639PTW.xml /XPONSLES9/content 686850U.xml 68685AU.xml 8639PTW.xml /SLES9/yast/order instorder /boot/i386/root.fonts root loader/linux text4c.pcx 16001200.spl isolinux.bin isolinux.cfg initrd 16x16.fnt text2b.pcx text4a.pcx back.jpg text1.pcx bootlogo kroete.dat text3.pcx message text2c.pcx text4b.pcx memtest welcome.jpg en.tr 10240768.spl directory.yast timer_a.jpg text2a.pcx en.hlp 12801024.spl 14001050.spl 08000600.spl The files in the boot/i386/ folders are from SLES 10 SP1 CD #1 except for isolinux.cfg which contains default Install_3890XP_on_6868_50U_with_SLES9 # install label Install_3890XP_on_6868_50U_with_SLES9 kernel linux append initrd=initrd splash=verbose install=cd autoyast=file:///XPONSLES9/686850U.xml showopts # install label Install_3890XP_on_6868_50U_with_SLES10 kernel linux append initrd=initrd splash=verbose install=cd autoyast=file:///XPONSLES10/686850U.xml showopts ... ... ... The media.1/media file contains IBM 3890XP Control Program 20080317141526 1 The media.1/product file contains /XPONSLES9 IBM-3890XP-SLES9 2.0-21 /XPONSLES10 IBM-3890XP-SLES10 2.0-21 The SLES9/yast/order file contains / /SLES9/ /XPONSLES9 /XPONSLES9/ The SLES9/yast/instorder file contains /SLES9 /XPONSLES9 Thanks Adam W. Hawks T/L: 794-4033 Office: 704 594-4033 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 3

[opensuse-autoinstall] dns resolution during install
by Michael Welle 02 Apr '08

02 Apr '08

Hi, is there a way to use server names instead of the ip addresses for the installation source? Snipset from linuxrc.conf: #Nameserver: 192.168.198.100 #Gateway: 192.168.198.100 #Netmask: 255.255.255.0 #Broadcast: 192.168.198.255 Install: smb://DEMOSRV.demo.dom/share/foo AutoYaST: file:///autoyast.xml This results in the message 'dns: what is demosrv.demo.dom'. Even pinging the server doesn't work. If I exchange the server name with its ip address everything works as expected. The client gets its network parameters via dhcp. /etc/resolv.conf etc. seems to be properly filled. Next I added some network parameters to linuxrc.conf. Doesn't change the behaviour. Even worse in the summary printed on the console the broadcast address is now noted as 0.0.0.255. Any hints? Michael -- biff4emacsen - A biff-like tool for (X)Emacs http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html Drop spots? http://dropspots.org/spot/1812 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

Re: [opensuse-autoinstall] Custom autoInstall boot CD for multiple distributions (SLES 9 & SLES10)
by Adam Hawks 28 Mar '08

28 Mar '08

Michel-André Thanks for you help. What ended up working was to use the SLES 9 kernel,inird and root image with grub for the booting of the CD. Then I backported the SLES 10 autoinst.xml to the SLES 9 format and removed the paterns and replaced them with the individual packages. The SLES 9 yast installer with /yast/order was able to install the SLES 10 Now the only thing left is can I get it to work on one CD. But that is not a issue, if it becomes too complicated we can just have a SLES 9 CD and a SLES 10 CD version. Again thanks. Michel-André <michelandre(a)micronator.org> 03/27/2008 07:13 PM To Adam Hawks/Charlotte/IBM@IBMUS cc Subject Re: [opensuse-autoinstall] Custom autoInstall boot CD for multiple distributions (SLES 9 & SLES10) Hi Adam! In around 2003 I was working for a telecom company and using RedHat 6.9 & 7.3. We had exactly the same problem: install RedHat then install the company software. I did 2 CDs. The first one containing the OS and the second one the software. I was using kickstart to do the job. I modified the kickstart then redo the iso to contain the new kickstart. Kickstart is the same as autoyast. In SLES10-SP1 & SP2-beta, you can use a kickstart file and convert it to autoyast. I beleive then that it is possible to do the exact same thing with SLES-10 as I did with RedHat. It was just a matter of calling a script file at the end of the kickstart. Does the installation of your software done with one script file of some kind? I will have a look in my backup stuff and come back to you. Michel-André ********************************************* Adam Hawks a écrit : > Michel-André > > Sorry if my post was confusing. > > Here is my situation. > 1) I'm the OEM vendor of a piece of software that controls a specific > piece of hardware we sell. (i.e 3890XP Control Program) > 2) We had to move from one OS to another ( i.e OS/2 => Linux, we chose > SuSE's SLES 9 and now SLES 10) > 3) Our customers buy SLES from Novell and the 3890XP software and HW from > us. > 4) The install method MUST be CD. > a) Machines do not support DVD's > b) We can't require the customer to setup an install server to do the > install's > 5) The installer's are hardware maintenance guys and do not have much > knowledge of OS's or Linux. > > What I'm trying to achieve > 1) A bootable CD that will start the install and contain our profiles > 2) A grub menu that will automatically select the right profile based on > the menu selection. > 3) The booted CD to then ask for SLES 10 CD's as needed and our CD when > our software is able to install. > 4) After initial install of SLES and our software, on first boot kick off > a configuration to finalize the hardware settings. (this one will happen > if our software gets installed and SLES was configured properly). > 5) Get both SLES 9 and SLES 10 automation from one CD. > > For SLES 9 I'm able to accomplish parts 1-4 with our CD being bootable > with a profile.xml and grub. > > For SLES 10 I can't seem to figure out how to get our CD to boot and then > request SLES 10 CD's when needed. > If I let SLES 10 boot then I don't get a grub menu with autoyast > pre-confgured, and the profiles have to be on floppy. > > Getting our profiles on a CD that is bootable with grub and starts the > autoyast process is my problem. > The one solution at the moment I see is remastering the SLES 10 CD #1 with > my profiles and a new grub menu. > My problem with this is a matter of support. > If I understand Novell's support policy, then this is now my distribution > and I have to support it. > We need a solution that keeps Novell supporting the Linux and us > supporting the 3890XP Control program. > > Sorry to be so wordy. > I hope the details of my problem are more clear now. > I didn't see anything in your reply that would solve my problem. > It may be that there is no solution. > > > Thanks > > Adam W. Hawks > T/L: 794-4033 > Office: 704 594-4033 > > > > > Michel-André <michelandre(a)micronator.org> > 03/27/2008 04:43 PM > > To > Adam Hawks/Charlotte/IBM@IBMUS > cc > opensuse-autoinstall(a)opensuse.org > Subject > Re: [opensuse-autoinstall] Custom autoInstall boot CD for multiple > distributions (SLES 9 & SLES10) > > > > > > > For sure the solution is here: > > I did a document on how to setup an installation server in french but with > lot of screen shots. > http://www.micronator.org/PDF/PXE-installation-de-SLES10-SP1.pdf > > It is based in english on: > http://www.novell.com/connectionmagazine/2007/q3/tech_talk_6.html > > This will show you how to create the installation server. > You will save a little the planet by not using CD or DVD and it is much > faster that way. > > The first document, the one I did, also describe how to use menu.c32 and > the default file. > I did installed an installation server on both SLES-10sp1 and > OpenSuse-10.3. > On OpenSuSE-10.3, you have to install: yast2-instserver > Even if it is in french, as I wrote above there is a lot of screen shots > so it should be understandable. > > On both of them, syslinux is outdated and give a cosmetical error but it > still work. > If you want to get rid of the error, remove the original syslinux but > leave the mtools. > Then download the latest sysliux ans install it on the server to get the > pxelinux.0. > Put that file in the tftp/pxelinux.cfg. > The error only shows up if you use TEXT HELP...ENDTEXT. > If you don't use it then forget about the new syslinux and use the one > that is installed. > Anyway the error is cosmetical only. > ******************* > > ADD-ON > > then go to: > http://developer.novell.com/wiki/index.php/Creating_Add-On_Media_with_YaST > to understand the ADD-ON. Same URL as below. > > Don't forget to sign the add-on. I think your error is from signing the > iso. > Then put the add-on iso on the installation server. > > I did an installation that uses add-on for OES2. > It produced an autoinstall.xml. > The section below is what it add for the add-on. > <add-on> > <add_on_products config:type="list"> > <listentry> > <media_url>http://192.168.1.149/install/OES/CD1</media_url> > <product>OPEN_ENTERPRISE_SERVER</product> > <product_dir>/</product_dir> > </listentry> > </add_on_products> > </add-on> > ******************* > AUTOINSTALL.XML > The best way to produce a good autoinstall.xml is to use VMware. > It works on M$ and on Linux. > For M$, see: > http://www.micronator.org/PDF/InstallationDeVMwareServeur_WINDOWS.pdf > For Linux, see: > http://www.micronator.org/PDF/InstallationDeVMwareServeur_LINUX.pdf > Ask a few licenses, it is free and they don't check the email address. > > For linux, the best way is to get the RPM file. > Install it then run vmware-pl to configure it. Take all the defaults. > You need gcc installed so to be able to compile modules when you run > vmware-pl. > At some point it will ask the license, just copy & paste it when you run > vmware-pl. > > Then create a virtual machine and installed your SLES-10. > At the end, when it ask to clone the system, click yes. > It will put the autoinstall.xml in /root. > Copy and save the file, you will see how it did for the ADD-ON etc. > Modify it for each different machine you want to install. > Easier but longer way is to use the MAC adddress for the file name, > or add a line in menu.c32 for each different machine you want to install. > ******************* > AUTOYAST > autoyast=tftp://IP-Address-Of-TFTP/pxelinux.cfg/myprofile.xml > ******************* > VNC > > I tried it and it realy installed hand-free. > I was watching the installation with vncviewer. > vnc=1 vncpassword=your-password > ******************* > > Voilà, that should work. > > If it doesn't work then send me an email and we can connect together to > show you how to do it. > > Good luck > > Michel-André > ************************************************ > Adam Hawks a écrit : > Ok. I'm making progress with the add-on media for SLES 10. > But I'm still stuck on how do I create my own add-on media with my > autoyast profile.xml on it and get SLES 10 to use it. > My whole goal is to fully automate the system and add-on install in grub > menu selection. > > If I put autoyast=cd:///myprofile.xml I get a message from SLES 10 that it > > can't find/read my profile since the SLES 10 CD #1 is what has booted. > > If I copy the /boot folder from SLES 10 to my add-on CD and put > autoyast=file:///myprofile.xml in the isolinux.cfg file the YaST install > system finds my profile but then can't instialize the software catalogs > since it doesn't know about the SLES 10 media yet. > > Is there a solution to this delima or am I forced into the creation of a > floppy with the profile.xml on it and manually typing the "autoyast=floppy > > install=cd" on the grub boot line? > > > > > Try this. It works > > http://developer.novell.com/wiki/index.php/Creating_Add-On_Media_with_YaST > > Michel-André > ****************************** > > Steffen Winterfeldt a écrit : > On Tue, 25 Mar 2008, Adam Hawks wrote: > > > I changed the boot CD to have a SLES 9 and a SLES 10 kernel and initrd. > And since root is in different locations on SLES 9 vs SLES 10 then > linuxrc loads the corresponding install system. > YaST is correctly starting with the install system for the correct SLES > and reads the profiles without failing. > > I STILL have the problem that my CD doesn't request the SLES 9 or SLES > 10's CD #1 when initializing the software catalogs. > > With SLES 8 you had the SLES 8 CD #1 and the United Linux CD #1 and you > could boot from either one to install depending on whether you wanted SLES > > > or United Linux. > My situation is like the SLES 8 model where I have my RPM's that need to > be installed on top of SLES 9, SLES 10 during the install. > The only difference is I need to support both SLES 9 and SLES 10 as the > base product. > > So I guess my basic problem is two fold. > 1) How do you correctly layout a CD distribution with multiple products > (mine on top of SLES 9 and mine on top of SLES 10)? > 2) How do you create a boot CD that is an add-on to the existing SLES CD's > > > without remastering CD #1 of SLES? > > > Hm, I can't comment on the required layout for add-on CDs but if you > remove the 'root' images from your CD, linuxrc assumes you have a special > boot CD and will ask for CD1. Maybe that helps. > > > Steffen > > > > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Re: [opensuse-autoinstall] Custom autoInstall boot CD for multiple distributions (SLES 9 & SLES10)
by Adam Hawks 27 Mar '08

27 Mar '08

Ok. I'm making progress with the add-on media for SLES 10. But I'm still stuck on how do I create my own add-on media with my autoyast profile.xml on it and get SLES 10 to use it. My whole goal is to fully automate the system and add-on install in grub menu selection. If I put autoyast=cd:///myprofile.xml I get a message from SLES 10 that it can't find/read my profile since the SLES 10 CD #1 is what has booted. If I copy the /boot folder from SLES 10 to my add-on CD and put autoyast=file:///myprofile.xml in the isolinux.cfg file the YaST install system finds my profile but then can't instialize the software catalogs since it doesn't know about the SLES 10 media yet. Is there a solution to this delima or am I forced into the creation of a floppy with the profile.xml on it and manually typing the "autoyast=floppy install=cd" on the grub boot line? Try this. It works http://developer.novell.com/wiki/index.php/Creating_Add-On_Media_with_YaST Michel-André ****************************** Steffen Winterfeldt a écrit : On Tue, 25 Mar 2008, Adam Hawks wrote: I changed the boot CD to have a SLES 9 and a SLES 10 kernel and initrd. And since root is in different locations on SLES 9 vs SLES 10 then linuxrc loads the corresponding install system. YaST is correctly starting with the install system for the correct SLES and reads the profiles without failing. I STILL have the problem that my CD doesn't request the SLES 9 or SLES 10's CD #1 when initializing the software catalogs. With SLES 8 you had the SLES 8 CD #1 and the United Linux CD #1 and you could boot from either one to install depending on whether you wanted SLES or United Linux. My situation is like the SLES 8 model where I have my RPM's that need to be installed on top of SLES 9, SLES 10 during the install. The only difference is I need to support both SLES 9 and SLES 10 as the base product. So I guess my basic problem is two fold. 1) How do you correctly layout a CD distribution with multiple products (mine on top of SLES 9 and mine on top of SLES 10)? 2) How do you create a boot CD that is an add-on to the existing SLES CD's without remastering CD #1 of SLES? Hm, I can't comment on the required layout for add-on CDs but if you remove the 'root' images from your CD, linuxrc assumes you have a special boot CD and will ask for CD1. Maybe that helps. Steffen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] SOLVED : info file does not honor ethernet settings with SLES10SP1
by Guy Coste 26 Mar '08

26 Mar '08

Sorry for not quoting properly, I am replying using a webmail system. in short issue #2 is caused by issue #1 To fix the problem, here are the steps I have followed : added : autoyast=file:///autoinst.xml to append line in isolinux.cfg Looks the parameter's order is very important in the info file (install parameter seems to needs =, but didn't try with: ), here is the working one: Install=http://10.0.0.1/sles10sp1/base/ Server: 10.0.0.1 Textmode: 1 ##AutoYaST: file:///autoinst.xml BrokenModules: qla2400,qla2xxx HostIP: 10.0.0.12 Netmask: 255.0.0.0 Gateway: 10.0.0.254 Netdevice: eth2 Now I need to find the right place for the parameter BrokenModules which it not honored anymore ;-( Cheers, -Guy >>> "Guy Coste" <gcoste(a)novell.com> 26/03/08 18:20 >>> Hi all, I am trying to automatically install a HP blade with autoyast. The hardware is componend of 4 ethernet cards. I am creating a custom iso file that is booted by HP ILO. isolinux.cfg contains : label BLADE kernel linux append initrd=initrd ramdisk_size=65536 netsetup=-dhcp Here is the info file I'm using : InstMode: http ##Instsys: boot/x86_64/root ##Install: http://10.0.0.1/sles10sp1/base/ Textmode: 1 AutoYaST: file:///autoinst.xml BrokenModules: qla2400,qla2xxx Gateway: 10.0.0.254 HostIP: 10.0.0.12 Netmask: 255.0.0.0 Netdevice: eth2 Server: 10.0.0.1 Serverdir: /sles10sp1/base/ I've copied this info file into the initrd. (I know InstMode is deprecated but I didn't add any success with Install: and Instsys: parameters) 1 - When the system boots, the system prompts again for IP settings. What I've did wrong ? What parameters I am missing ? When I swith to "F3" I see many "SIOCSIF..." failed on interfaces eth0, eth1. The network settings are then correctly reported and eth2 activated Then the installation process reports the following error "http error: 404 not found" 2 - The installation tell it is loading the image from "/sles10sp1/base/boot/root" The reported path is wrong. it should be "/sles10sp1/base/boot/x86_64/root/" (note the arch between boot and root) Is this a kown issue ? Any clues how to fix/ workaround it ? Thanks in advance, Regards, -Guy -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Re: [opensuse-autoinstall] Custom autoInstall boot CD for multiple distributions (SLES 9 & SLES10)
by Steffen Winterfeldt 26 Mar '08

26 Mar '08

On Tue, 25 Mar 2008, Adam Hawks wrote: > I changed the boot CD to have a SLES 9 and a SLES 10 kernel and initrd. > And since root is in different locations on SLES 9 vs SLES 10 then > linuxrc loads the corresponding install system. > YaST is correctly starting with the install system for the correct SLES > and reads the profiles without failing. > > I STILL have the problem that my CD doesn't request the SLES 9 or SLES > 10's CD #1 when initializing the software catalogs. > > With SLES 8 you had the SLES 8 CD #1 and the United Linux CD #1 and you > could boot from either one to install depending on whether you wanted SLES > or United Linux. > My situation is like the SLES 8 model where I have my RPM's that need to > be installed on top of SLES 9, SLES 10 during the install. > The only difference is I need to support both SLES 9 and SLES 10 as the > base product. > > So I guess my basic problem is two fold. > 1) How do you correctly layout a CD distribution with multiple products > (mine on top of SLES 9 and mine on top of SLES 10)? > 2) How do you create a boot CD that is an add-on to the existing SLES CD's > without remastering CD #1 of SLES? Hm, I can't comment on the required layout for add-on CDs but if you remove the 'root' images from your CD, linuxrc assumes you have a special boot CD and will ask for CD1. Maybe that helps. Steffen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] info file does not honor ethernet settings with SLES10SP1
by Guy Coste 26 Mar '08

26 Mar '08

Hi all, I am trying to automatically install a HP blade with autoyast. The hardware is componend of 4 ethernet cards. I am creating a custom iso file that is booted by HP ILO. isolinux.cfg contains : label BLADE kernel linux append initrd=initrd ramdisk_size=65536 netsetup=-dhcp Here is the info file I'm using : InstMode: http ##Instsys: boot/x86_64/root ##Install: http://10.0.0.1/sles10sp1/base/ Textmode: 1 AutoYaST: file:///autoinst.xml BrokenModules: qla2400,qla2xxx Gateway: 10.0.0.254 HostIP: 10.0.0.12 Netmask: 255.0.0.0 Netdevice: eth2 Server: 10.0.0.1 Serverdir: /sles10sp1/base/ I've copied this info file into the initrd. (I know InstMode is deprecated but I didn't add any success with Install: and Instsys: parameters) 1 - When the system boots, the system prompts again for IP settings. What I've did wrong ? What parameters I am missing ? When I swith to "F3" I see many "SIOCSIF..." failed on interfaces eth0, eth1. The network settings are then correctly reported and eth2 activated Then the installation process reports the following error "http error: 404 not found" 2 - The installation tell it is loading the image from "/sles10sp1/base/boot/root" The reported path is wrong. it should be "/sles10sp1/base/boot/x86_64/root/" (note the arch between boot and root) Is this a kown issue ? Any clues how to fix/ workaround it ? Thanks in advance, Regards, -Guy -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] autoyast with openSUSE 10.3 doesn't work
by Ivan De Masi 26 Mar '08

26 Mar '08

Dear listmembers, I'm getting crazy trying to install openSUSE 10.3 from a created autoinst.xml profile file. I tried to tell autoyast to get the profile from usb-stickt, nfs-share and a webserver - no chance! I always get a message like that there was an error reading the profile. I only got it half way working using the option "vnc=1" . Than autoyast reads the profile (from the webserver), but stops with partitioning problems because of a factory partiton. I saw now thht this is a bug... But getting back to my first problem: What can I do? We want to set up some new clients with openSUSE 10.3 and I don't want to do that 50 times ... Thanks, Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] Software Installation Source
by LDB 21 Mar '08

21 Mar '08

Is there an easy way of adding installation sources during autoinstallation? Preferably within the XML directives, but within the post-installation script is sufficient as well. Thanks, LDB -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] Organizational software repository
by LDB 19 Mar '08

19 Mar '08

Sometimes some of my servers do not pick up all of the package contents in my local software repositories of SLES 9sp4 and 10sp1, while using "rug". I created the software repositories by copying the whole DVD ISOs under a directory within web root. Then I point the servers to the repositories via HTTP. Was this the correct protocol? Do I need to use Yast tool: Miscellaneous -> Installation Server to create the above? Is there an easy way to create an organization ONLY repository? I have done this in the past, but not sure of the current process. Thanks, LDB -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] root partition in LVM not mounting during 2nd phase of auto-installation process
by LDB 18 Mar '08

18 Mar '08

After the autoyast installation process and during the 1st boot, it stops and spews the the following ... Attempting manual resume Waiting for device /dev/rootvg/root to appear: .................. not found -- exiting to /bin/sh $ but then when I boot into rescue mode it mounts just fine ... <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">131</filesystem_id> <format config:type="boolean">true</format> <mount>/boot</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>534610432</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">swap</filesystem> <filesystem_id config:type="integer">130</filesystem_id> <format config:type="boolean">true</format> <mount>swap</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>2293595648</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem_id config:type="integer">142</filesystem_id> <lvm_group>rootvg</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions>  <use>all</use> </drive> <drive> <device>/dev/rootvg</device> <lvm2 config:type="boolean">true</lvm2> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>root</lv_name> <mount>/</mount> <mountby config:type="symbol">device</mountby> <size>5368709120</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>home</lv_name> <mount>/home</mount> <mountby config:type="symbol">device</mountby> <size>5368709120</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>tmp</lv_name> <mount>/tmp</mount> <mountby config:type="symbol">device</mountby> <size>4368709120</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>var</lv_name> <mount>/var</mount> <mountby config:type="symbol">device</mountby> <size>2368709120</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>var_log</lv_name> <mount>/var/log</mount> <mountby config:type="symbol">device</mountby> <size>5368709120</size> </partition> </partitions> <pesize>4M</pesize> <type config:type="symbol">CT_LVM</type> <use>all</use> </drive> </partitioning> Any ideas?? LDB -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 7

[opensuse-autoinstall] "info" file section
by LDB 18 Mar '08

18 Mar '08

I have this section in my autoinst.xml file and called it "info". It is called like the following: autoyast=http://192.168.101.66/profiles/booger/info ... <install> <init> <info_file> <![CDATA[ # # Don't remove the following line: # start_linuxrc_conf # autoyast: file:///info install: http://192.168.101.66/suse/x86/10sp1/base netdevice: eth0 hostip: 192.168.101.17 netmask: 255.255.255.0 gateway: 192.168.101.254 nameserver: 192.168.101.11 textmode: 1 vnc: 1 vncpassword: super # end_linuxrc_conf # Do not remove the above comment # ]]> </info_file> </init> </install> .... but it does not work as expected. Does anyone know what I am missing? Does this only work with PXE booting? http://www.novell.com/documentation/sles10/sles_admin/index.html?page=/docu… Thank you, LDB -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

5 30

[opensuse-autoinstall] <system_gid_min> applied too late
by Michael.Leu＠mgb.ch 17 Mar '08

17 Mar '08

Hello Using SLES10 SP1. I need to prevent the creation of UIDs and GIDs in the range of 100-149, so I added this to the profile. <security> <system_uid_min>150</system_uid_min> <system_gid_min>150</system_gid_min> </security> It gets added to /etc/login.defs but too late; some rpms have already added users and groups (hal, dbus and others). A pre-install script is too early as no filesystems have been created. Any ideas? Regards, Michael Leu -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] Autoyast cannot install rpm files - exit status 255
by Wayman Smith 12 Mar '08

12 Mar '08

Hello, I am attempting instal SLES-10 using autoyast. I generated my autoinst.xml file from a manual install on the same hardware. My installation is over the network using an NFS share. I am able to create my partitions correctly, however when the rpm installations begin, I receive the following error Subprocess failed. Error: RPM failed: error: %post (/rpm_name/) scriptlet failed exit status 255 Even when I hit ignore, the same message appears for the next rpm as well. I haven't changed any NFS information or modified any of the rpm files. I'm not sure what is causing this. Has anyone experienced this sort of error? Regards, Wayman Smith -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] Error in autoyast install process
by Wayman Smith 10 Mar '08

10 Mar '08

Hello, I am attempting to perform an autoinstall process with SuSE 10.1 sp1 using autoyast and a custom autoinst.xml file. The install process reads the autoinst.xml correctly, and performs all steps up until the Install boot manager process. Here, I receive the error /sbin/mkinitrd: line 3297: /etc/fstab: No such file or directory No '/' mountpoint spceified in /etc/fstab It should also be noted that my autoinst.xml file fails RNG validation (https://bugzilla.novell.com/show_bug.cgi?id=211014#c21) I have attached my autoinst.xml file also. Might these two problems be related? --W. Smith

8 11

[opensuse-autoinstall] Routes, openSUSE and SLES
by Dan Stromberg 07 Mar '08

07 Mar '08

We want to define a multicast route. I put it in ifroute-eth0, but that seemed to work on one of openSUSE or SLES but not the other - I don't recall which unfortunately. So I took the line that I thought should work in ifroute-eth0, and put it in /etc/sysconfig/network/routes, and that worked. Temporarily. On reboots, my routes file was getting renamed to routes.YaST2save and the prior content was stuffed back in (with just a default gateway). I'd prefer to be able to set the routes file content (or ifroute-eth*) via a shell script, but if I must use the .xml method, so be it. So I stuck the following into my autoyast.xml: <routing> <ip_forward config:type="boolean">false</ip_forward>   <routes config:type="list"> <route> <destination>228.0.0.0/8</destination> <gateway>0.0.0.0</gateway> <netmask>255.0.0.0</netmask> <device>eth0</device> <extrapara>multicast</extrapara> </route> </routes> </routing> ...and that seems to handle the multicast route pretty well. It even threw in the "multicast" part at the end of my routes line for the multicast route. But. Now all seems fine on openSUSE, but on SLES, I'm not getting a default route anymore, even when I set up both of a test machine's ethernet interfaces for DHCP. I'm thinking that if I try to stick a default route into the routes file, I'm going to run into the same problem - the content will disappear on reboots. What do I need to do to get good routing? I'd like the following: 1) A consistent method across openSUSE 10.3 and SLES 10.1 - this part isn't absolutely important though 2) A good default route on DHCP or static that survives reboots and can be changed in the field without reinstalling 3) A good multicast route that survives reboots and can be changed in the field without reinstalling Thanks! -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?
by Matt Gillard 05 Mar '08

05 Mar '08

I dont have kinternet installed. This is what doesnt seem to work: <software> <patterns config:type="list"> <pattern>default</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> <packages config:type="list"> <packages>perl-libwww-perl</packages> <packages>net-snmp</packages> <packages>kernel-source</packages> </packages> <remove-packages config:type="list"> <packages>pptp</packages> <packages>smpppd</packages> <packages>ppp</packages> <packages>wvdial</packages> <packages>mutt</packages> </remove-packages> </software> In y2log it mentions that those packages should be removed, but it goes ahead and installs them anyway. I can do it manually on the command line: # rpm -e pptp smpppd ppp wvdial mutt and that works fine so I know I have no dependency problems. matt > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Friday, 30 June 2006 12:50 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section? > > > On Thursday 29 June 2006 16:45, Manfred Hollstein wrote: > > > If that fails, you have kinternet installed; add that to > the list and it > > should work. > > good point. > <remove-packages> can not break dependencies and so it's very > likely that > there is still a package that needs those packages. > I did a very small installation with no X - so it worked for me. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug > now playing Covenant - Wasteland > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

4 6