May 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Minor problem w/ info file and custom kernel package
by Nicoya Helm 08 May '04

08 May '04

I'm just in the beginning stages of understanding SuSE's autoinstall process, which I'm implementing for an OpenMosix cluster. The scenario is that I have a server w/ the appropriate media directories, a standard SuSE boot CD, and a floppy w/ a custom autoinst.xml and info file at the root. And using SuSE 9.0 Yast 2. Problem 1: Info file not working. Because this is on a cluster, and for various reasons we don't want to run DHCP on the control node, I would like to use an info file to statically assign IP info and have the YaST look for the nfs install directory. Here's the contents of my info file: netdevice: eth0 ip: 192.168.1.200 netmask: 255.255.255.0 gateway: 192.168.1.200 install: nfs://192.168.1.1/usr/local/SuSE/current autoyast: floppy During the boot process the system searches for the info file, loads usb drivers, etc., searches for autoinstall file, then says "Sending DHCP request to eth0". I've watched, and the system reads the floppy drive both times. If I use this info file and autoinst.xml file on a network that has a DHCP server available, the network card grabs an IP, finds the nfs share, and proceeds to install according to my autoinst settings. But it fails if I use it on the cluster segment where no DHCP is available. I can do a manual installation, load the card drivers and manually enter all the IP and NFS info, and the autoinstallation proceed wonderfully. So my question is - what's wrong w/ my info file that the systems keep trying to use DHCP instead of the static info? Clearly they're getting at least some of the info from the file since the install finds the NFS shared okay. Problem 2: Not so much a problem as looking for additional tips/docu resources for how to make a custom kernel as part of the autoinstall process. I need to have the openmosix kernel installed, and am looking for the best way to accomplish this automatically. I tried to have it install as an addon package like any other RPM (like section 4.5.3 of the documentation says for general RPMS) - the install completes partially, then fails. However, I'm thinking I may be confused and should be adding it as a kernel package (is this any different than a standard RPM?) per section 4.5.4 of the documentation. If so, other than specifying the "kernel" property, is there anything different I will need to do to get the custom kernel to install automatically? Any suggestions very much appreciated! Nicoya Helm University of Kansas Medical Center nhelm2(a)kumc.edu

2 1

dhcpd.leases and SLES8 autoinstall
by Frank Samuel 07 May '04

07 May '04

Hi, I have a question regarding to autoinstall for SLES8. During the autoinstall of a node. The following two new leases are noticed in the dhcp.leases file. I feel surprised when I read the latter lease. Could someone explain what is the meaning of uid "\001\000PE\000\244\022"; Thanks a lot. lease 192.168.0.19 { starts 5 2004/05/07 10:35:48; ends 6 2004/05/08 10:35:48; binding state active; next binding state free; hardware ethernet 00:50:45:00:a4:12; } lease 192.168.0.19 { starts 5 2004/05/07 10:36:11; ends 6 2004/05/08 10:36:11; binding state active; next binding state free; hardware ethernet 00:50:45:00:a4:12; uid "\001\000PE\000\244\022"; } __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover

1 0

Re: [suse-autoinstall] Upgrade 9.0 -> 9.1 went totally wrong
by Wolfgang.Bauer＠schoellerbank.at 07 May '04

07 May '04

Hi Roy, no, my specs are: Athlon XP 1600, 768 MB RAM, 80 GB IDE (ATA-100), Geforce 440 MX, SB live, 2x ethernet, 1 firewire-card The funny thing was, that I was always told that the upgrade-program could not mount my root-partition but when I chose "reset options" (by not changing any options before) it recognised the root-partition... I guess, there could be a bug somewhere in the upgrade-program... I would love to track this problem down, but I fear that all logs were deleted. Yours, Gery ------------------------------------------------------------------- Dipl.-Ing. Wolfgang Gernot Bauer, Leiter Internet Schoellerbank AG, Sterneckstrasse 5, 5024 Salzburg, Austria/Europe Tel.: ++43-662-8684-364, Fax.: ++43-662-8684-44364 Email: mailto:wolfgang.bauer@schoellerbank.at, WWW: http://www.schoellerbank.at Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur für den Gebrauch des Empfängers bestimmt. This message is only for informational purposes and is intended solely for the use of the addressee. Roy Butler <roy.butler@jpl. nasa.gov> An suse-autoinstall(a)suse.com 06.05.2004 22:27 Kopie Thema Re: [suse-autoinstall] Upgrade 9.0 -> 9.1 went totally wrong Gery, Is your root-partition on an SATA drive? If so, maybe the upgrade feature isn't accomodating the device file change between the 2.4 and 2.6 kernels. Roy Wolfgang.Bauer(a)schoellerbank.at wrote: > > > > > Hello everybody, > > I tried to install SuSE 9.1 yesterday by trying to Upgrade my > 9.0-installation. The nightmare was as follows: > > The first problem I encountered was that yast was not able to mount my > root-partition (reiserfs) although my 9.0-installation worked properly... > > After a few tries, I used the "Auto-Repair Installed System"-feature (if > you still use 9.0 - DONT USE THIS FEATURE!!!). First it worked very nicely > until it got to the point where it checked the installation. The > repair-function noticed that the 9.1-installation was faulty (right, as it > was a 9.0-installation) and upgraded some packages. After a reboot the > system did not come up (could not find kernel). Well, yast-installation > again - could not mount root-filesystem. Damn. > > I tried many things but when I used "Reset Options" from the menu on the > bottom YAST COULD MOUNT MY PARTITION - there were no other settings but (by > magic) now it worked (could this be a bug?!). But as the repair-system > changed my old 9.0-installation "There was an error upgrading your system". > > After I copied all my /home-data to my windowspartition via text-console > and freshly installed 9.1, I had a running linux-system again. But I really > have to say: poor upgrade-system. It used to work better with older > Suse-distributions... > > Btw. I'm not a Linux novice (I use Linux since 1994) but it seems that you > must not rely on "automatic upgrade functionalities"... > > Sad, sad. > > Gery > ------------------------------------------------------------------- > Dipl.-Ing. Wolfgang Gernot Bauer, Leiter Internet > Schoellerbank AG, Sterneckstrasse 5, 5024 Salzburg, Austria/Europe > Tel.: ++43-662-8684-364, Fax.: ++43-662-8684-44364 > Email: mailto:wolfgang.bauer@schoellerbank.at, WWW: > http://www.schoellerbank.at > > Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur für > den Gebrauch des Empfängers bestimmt. > This message is only for informational purposes and is intended solely for > the use of the addressee. > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

SuSE SLES 8 and United Linux 1.0 autoinstall
by Frank Samuel 07 May '04

07 May '04

I have a question regarding to SLES8 autoinstall. I've done some experiments for SLES8 autoinstall without SP3. One experiment I did is copying the CDs to a dir of /usr/local/SLES8 in the order of UnitedLinux 3,2,1 and SLES8 and then removed some packages not used. After installation, Welcome to SuSE SLES8 ... will be in the file of /etc/issue. I didn't notice any problem happen during the installation. So is it a valid method? Another issue is how can I possibly install UnitedLinuxinstead of SLES8 using autoinstall? Copying three CDs of United Linux seems won't work. Thanks. __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover

2 2

Upgrade 9.0 -> 9.1 went totally wrong
by Wolfgang.Bauer＠schoellerbank.at 06 May '04

06 May '04

Hello everybody, I tried to install SuSE 9.1 yesterday by trying to Upgrade my 9.0-installation. The nightmare was as follows: The first problem I encountered was that yast was not able to mount my root-partition (reiserfs) although my 9.0-installation worked properly... After a few tries, I used the "Auto-Repair Installed System"-feature (if you still use 9.0 - DONT USE THIS FEATURE!!!). First it worked very nicely until it got to the point where it checked the installation. The repair-function noticed that the 9.1-installation was faulty (right, as it was a 9.0-installation) and upgraded some packages. After a reboot the system did not come up (could not find kernel). Well, yast-installation again - could not mount root-filesystem. Damn. I tried many things but when I used "Reset Options" from the menu on the bottom YAST COULD MOUNT MY PARTITION - there were no other settings but (by magic) now it worked (could this be a bug?!). But as the repair-system changed my old 9.0-installation "There was an error upgrading your system". After I copied all my /home-data to my windowspartition via text-console and freshly installed 9.1, I had a running linux-system again. But I really have to say: poor upgrade-system. It used to work better with older Suse-distributions... Btw. I'm not a Linux novice (I use Linux since 1994) but it seems that you must not rely on "automatic upgrade functionalities"... Sad, sad. Gery ------------------------------------------------------------------- Dipl.-Ing. Wolfgang Gernot Bauer, Leiter Internet Schoellerbank AG, Sterneckstrasse 5, 5024 Salzburg, Austria/Europe Tel.: ++43-662-8684-364, Fax.: ++43-662-8684-44364 Email: mailto:wolfgang.bauer@schoellerbank.at, WWW: http://www.schoellerbank.at Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur für den Gebrauch des Empfängers bestimmt. This message is only for informational purposes and is intended solely for the use of the addressee.

2 1

Re: [suse-autoinstall] Upgrade 9.0 -> 9.1 went totally wrong
by Ryan Partridge 06 May '04

06 May '04

Just wanted to show the other side of the coin. Two days ago I upgraded my development workstation from 9.0 to 9.1 and the process couldn't have been smoother. I'm sorry that you had trouble, Gery. I would imagine that the majority of users will not experience the same problems you did. Just the same, if anybody else has bad experiences, please publish them so the underlying issues can be addressed. Cheers! >>> <Wolfgang.Bauer(a)schoellerbank.at> 5/6/2004 1:26:18 AM >>> Hello everybody, I tried to install SuSE 9.1 yesterday by trying to Upgrade my 9.0-installation. The nightmare was as follows: The first problem I encountered was that yast was not able to mount my root-partition (reiserfs) although my 9.0-installation worked properly... After a few tries, I used the "Auto-Repair Installed System"-feature (if you still use 9.0 - DONT USE THIS FEATURE!!!). First it worked very nicely until it got to the point where it checked the installation. The repair-function noticed that the 9.1-installation was faulty (right, as it was a 9.0-installation) and upgraded some packages. After a reboot the system did not come up (could not find kernel). Well, yast-installation again - could not mount root-filesystem. Damn. I tried many things but when I used "Reset Options" from the menu on the bottom YAST COULD MOUNT MY PARTITION - there were no other settings but (by magic) now it worked (could this be a bug?!). But as the repair-system changed my old 9.0-installation "There was an error upgrading your system". After I copied all my /home-data to my windowspartition via text-console and freshly installed 9.1, I had a running linux-system again. But I really have to say: poor upgrade-system. It used to work better with older Suse-distributions... Btw. I'm not a Linux novice (I use Linux since 1994) but it seems that you must not rely on "automatic upgrade functionalities"... Sad, sad. Gery ------------------------------------------------------------------- Dipl.-Ing. Wolfgang Gernot Bauer, Leiter Internet Schoellerbank AG, Sterneckstrasse 5, 5024 Salzburg, Austria/Europe Tel.: ++43-662-8684-364, Fax.: ++43-662-8684-44364 Email: mailto:wolfgang.bauer@schoellerbank.at, WWW: http://www.schoellerbank.at Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur für den Gebrauch des Empfängers bestimmt. This message is only for informational purposes and is intended solely for the use of the addressee. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

differences / description / experiences autoyast with suse9.1 ?
by Hella Breitkopf 06 May '04

06 May '04

Hi List, Before I dip my toes into automatic installation with suse9.1, is there a description on the way? Are there many differences from 9.0 to 9.1? Has anybody tried it, yet? With what results? (Btw: It would be nice to see a page "things what changed from version x to version x+1" in the description - and if the description is updated, date + version number would come in handy.) thanks for any information, Hella -- Top 100 things you don't want the sysadmin to say: 60. We're standardizing on AIX.

4 6

Secure Network-Based Install for SuSE 9.0...
by Roy Butler 06 May '04

06 May '04

Hi, I'd like to create a secure network-based install for SuSE 9.0 with AutoYaST using iptables. Currently, I have the following working quite well on a private network: - Server at 192.168.1.1 with SuSE 9.0 DVD contents NFS-exported and AutoYast XML control file served via TFTP. - Client connected through switch and booted from SuSE 9.0 CD1 with the following arguments: hostip=192.168.1.2 netmask=255.255.255.0 gateway=192.168.1.1 install=nfs://192.168.1.1/export/i386/SuSE/9.0/DVD autoyast=tftp://192.168.1.1/test-1.xml My goal is to move the server to a semi-public network and install clients in a manner similar to the above, but prohibit any network traffic to the client from anywhere but the server during the process. I've read (most of) Anas' fine AutoYaST documentation, the Linux Bootdisk HOWTO, and the kernel's initrd.txt file, as well as some of the messages on this list. I've missed it if anyone has described how to do this before, but here is my plan of attack: - Copy SuSE 9.0 CD1 to hard drive. - Gunzip and mount the CD's /boot/loader/initrd. - Copy iptables.o to initrd's /modules directory and add an entry to the [autoload] section of initrd's /modules/module.config file. - Unmount and gzip the initrd image. - Create a template entry for the long-winded boot arguments above in the CD's /boot/loader/isolinux.cfg. - Burn a custom SuSE 9.0 CD1 from the hard drive. - Create a pre-script in my test-1.xml file which runs "iptables <some rule>". Has anyone done something similar who can offer advice/comments? I like the extended boot arguments, because I can't rely on PXE or DHCP everywhere. I'm not stuck on iptables, if there's a similar way to do it otherwise. I have the sense that I may be working with the wrong ramdisk (/boot/loader/initrd) since I found no /lib directory and an incredibly sparse /bin directory there... Much appreciated, Roy

1 0

[suse linux 9.1 prof x86] autoinstall over network failed: yast: not enough memory !!!
by Maurer, Hermann 05 May '04

05 May '04

Hello folks, I have a trouble to start the autoinstall process of SuSE Linux 9.1 over the LAN. In my grub.conf on the boot floppy I have the following entries: title SuSE Linux 9.1 Installation kernel (nd)/boot/suse-linux-9.1 insmod=e100 install=ftp://10.73.59.88/pub/suse/i386/9.1 initrd (nd)/boot/suse-linux-9.1.initrd title SuSE Linux 9.0 Installation kernel (nd)/boot/suse-linux-9.0 insmod=e100 install=ftp://10.73.59.88/pub/suse/i386/9.0 initrd (nd)/boot/suse-linux-9.0.initrd The installation comes up to the point, where the installation process loads some data (53308 kb) onto the ram disk. It draws dots and switches then in the ncurses mode with the following error: "Your computer doesn't have enough memory to run YaST. To continue, activate some swap space" Some last lines on the tty3: ... going for automatic install Loading image "/pub/suse/i386/9.1/boot/root"... cramfs "root 53308" image size: 53308 kB mount: /dev/ram2: we need a loop device mount: using /dev/loop0 Loading image "/pub/suse/i386/9.1/driverupdate"... ramdisk /dev/ram3 freed Ther is not the file driverupdate in the root dir and in the subdirecories of the distribution ! The installation over pxe + grub over the LAN failes with the same error. Here is a section of my grub.conf for pxe-boots: # SuSE Linux 9.1 Installation title SuSE Linux 9.1 Installation root (nd) kernel /boot/suse-linux-9.1 ramdisk_size=65536 insmod=e100 install=ftp://10.73.59.88/pub/suse/i386/9.1 initrd /boot/suse-linux-9.1.initrd # SuSE Linux 9.0 Installation title SuSE Linux 9.0 Installation root (nd) kernel /boot/suse-linux-9.0 ramdisk_size=65536 insmod=e100 install=ftp://10.73.59.88/pub/suse/i386/9.0 initrd /boot/suse-linux-9.0.initrd The installation of SuSE 9.0 works fine, it doesn't matter, whether over pxe + grub or with grub boot floppy. My PC has the following hardware configuration: - Intel P-III 550 MHz - 128 MB RAM - 9 GB SCSI HDD - Matrox G400 AGP card - Intel EtherExpress 10/100 NIC Any help will be appreciated ! Thank you very much ! Regards, Hermann Maurer

3 2

Full automatic installation of SLES8 with update
by Nicolas Marciniak 05 May '04

05 May '04

Here some tips to help you to install a sles8 with update. I think it will be usefull for many people. ========================================================= == 1 == Setting up install directory ========================================================= Use the script in section 6.1.3 of the autoyast documentation for sles8 You have now a repository with SLES CD and UL CD 1,2,3 I have setup my repository in /suse/install I have used UL/CD{1,2,3} and SLES/ instead of unitedlinux-i386/CD{1,2,3} and sles8-i386/CD1 directory ========================================================= == 2 == Download update ========================================================= Go to http://sdb.suse.de/download/i386/update/SuSE-SLES/8/rpm/ Download all rpms like this : foo-x.xx-xx.rpm Do NOT download foo.patch.rpm and foo.rpm files Save files in directory like this /suse/update/update/i586 /suse/update/update/i686 /suse/update/update/noarch Download SP3 CD1 iso to get driverupdate file You must have it later. ========================================================= == 3 == Creating package description for update ========================================================= Install autoyast2 rpm ### script ### cd /suse/update/update/ /usr/local/YaST2/bin/create_package_descr -d /suse/update/update -l english -l german -l french cd /suse/update mkdir media.1 touch content touch media.1/media ############### ### file : content ### PRODUCT SuSE SLES VERSION update DISTPRODUCT SuSE-Linux-SLES-i386 DISTVERSION 8.1-0 BASEPRODUCT UnitedLinux BASEVERSION 1.0 YOUTYPE business YOUPATH i386/update/SuSE-SLES/8 YOUURL http://www.suse.de/cgi-bin/suseservers.cgi VENDOR SuSE Linux AG ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i386 REQUIRES distribution-release LINGUAS de en LABEL SuSE SLES Update LABEL.de SuSE SLES Update DESCRDIR update/setup/descr DATADIR update LANGUAGE en_US TIMEZONE America/Los_Angeles ############### ### file : media.1/media ### SuSE Linux AG 20021022191434 1 ############### You must have this in your /suse/update /suse/update |-- content |-- media.1 | `-- media `-- update |-- i586 -- *.rpm |-- i686 -- *.rpm |-- noarch -- *.rpm `-- setup `-- descr |-- packages |-- packages.DU |-- packages.en `-- packages.fr ========================================================= == 5 == setting up the final repository with update rpms ========================================================= #### script ################ mv /suse/update /suse/install/ cd /suse/install mkdir -p yast/update/update/setup/descr mkdir -p yast/update/media.1 cp -a update/content yast/update/ cp -a update/media.1/media yast/update/media.1/ cp -a update/update/setup/descr/*.* yast/update/update/setup/descr/ ############################ Your /suse/install/yast must look like this : |-- TRANS.TBL |-- order |-- sles8 | |-- content | |-- media.1 | | |-- TRANS.TBL | | |-- info.txt | | |-- media | | `-- products | `-- suse | `-- setup | `-- descr | |-- Minimal+X11.sel | |-- Minimal.sel | |-- X11.sel | |-- packages | |-- packages.DU | |-- .... |-- ul | |-- TRANS.TBL | |-- UnitedLinux | | |-- TRANS.TBL | | `-- setup | | |-- TRANS.TBL | | `-- descr | | |-- Minimal+X11.sel | | |-- Minimal.sel | | |-- X11.sel | | |-- packages | | |-- packages.DU | | |-- packages.cs | | |-- ..... | |-- content | `-- media.1 | |-- TRANS.TBL | |-- info.txt | |-- media | `-- products `-- update |-- content |-- media.1 | `-- media `-- update `-- setup `-- descr |-- packages |-- packages.DU |-- packages.en `-- packages.fr ---- /!\ Don't forget to put the driverupdate file of SP3 CD1 in /suse/install ========================================================= == 6 == Important files ========================================================= /suse/install/yast/order : -------------------------- /yast/update /update /yast/ul /UL/CD1 /yast/sles8 /SLES ========================================================= == 7 == Make a custom boot cd ========================================================= Mount and copy your SLES8 CD1 to /iso/cdboot/ You can delete all rpm in /iso/cdboot/ to reduce the size of the final cd Mount the SP3 CD to /mnt/sp3 ### script ### cp /mnt/sp3/boot/loader/linux /iso/cdboot/boot/loader/ cp /mnt/sp3/boot/loader/initrd /iso/cdboot/boot/loader/ cp /mnt/sp3/boot/loader/initrd /iso/ touch /iso/info ############### the file info is used to setup network and connect to the nfs repository to install the system ### file : /iso/info ### install: nfs://128.1.217.166/suse/install/ netdevice: eth0 hostip: 128.1.33.60 gateway: 128.1.6.23 nameserver: 128.1.6.228 netmask: 255.255.0.0 textmode: 1 forceinsmod: 1 nopcmcia: 1 ############### I have tweak the isolinux.cfg to get different autoyast control file ### file /iso/cdboot/boot/loader/isolinux.cfg #### default harddisk # hard disk label harddisk kernel linux append SLX=0x202 # ide label ide kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/ide.xml # scsi label scsi kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/scsi.xml # custom1 label custom1 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/custom1.xml # custom2 label custom2 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/custom2.xml # custom3 label custom3 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/custom3.xml failsafe label failsafe kernel linux append initrd=initrd ramdisk_size=65536 ide=nodma apm=off acpi=off # apic #label apic # kernel linux # append initrd=initrd ramdisk_size=65536 apic # manual #label manual # kernel linux # append initrd=initrd ramdisk_size=65536 manual=1 memory test label memtest kernel memtest implicit 0 gfxboot bootlogo display message prompt 1 timeout 100 readinfo 2 framebuffer 1 ####################### Here my script to create a cdboot with sp3 kernel and info file ##### script makeiso.sh ####### #!/bin/bash INITRD=/iso/initrd INITRD_GUNZIP=/iso/initrd_gunzip INITRD_MOUNT=/iso/temp/initrd INFO=$1 CDBOOT=/iso/cdboot ISO=$2 INITRD_FINAL=$CDBOOT/boot/loader/initrd if [ "$#" -lt 2 ] then echo "Usage: makeiso file_info image.iso" exit 1 fi mkdir -p $INITRD_MOUNT gunzip -q < $INITRD > $INITRD_GUNZIP mount -o loop -t minix $INITRD_GUNZIP $INITRD_MOUNT cp $INFO $INITRD_MOUNT umount $INITRD_MOUNT gzip < $INITRD_GUNZIP > $INITRD_FINAL mkisofs -R -l -J -o $ISO -b boot/loader/isolinux.bin -c boot.catalog \ -no-emul-boot -boot-load-size 4 -boot-info-table \ $CDBOOT rm -f $INITRD_GUNZIP ############################### in /iso simply use : ./makeiso.sh info slescustom.iso :) ========================================================= == 7 == Creating a good control file with nfs postinstall script and LVM stuff :) ========================================================= Here my ide.xml control file --------------------- <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <scripts> <chroot-scripts config:type="list"/> <post-scripts config:type="list" > <script> <filename>postinstall.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh UPDATE_SRV=128.1.217.166 UPDATE_DIR=/suse/postinstall eject echo "Mounting update server" mkdir -p /tmp/postinstall mount -t nfs $UPDATE_SRV:$UPDATE_DIR /tmp/postinstall sh /tmp/postinstall/update_rpm.sh ]]> </source> </script> </post-scripts> <pre-scripts config:type="list"/> </scripts> </configure> <install> <bootloader> <location>mbr</location> </bootloader> <report> <messages> <show>false</show> <timeout>5</timeout> <log>true</log> </messages> <errors> <show>true</show> <timeout>5</timeout> <log>true</log> </errors> <warnings> <show>true</show> <timeout>5</timeout> <log>true</log> </warnings> </report> <general> <clock> <hwclock>GMT</hwclock> <timezone>Europe/Paris</timezone> </clock> <keyboard> <keymap>french</keymap> </keyboard> <language>fr_FR</language> <mouse> <id>20_imps2</id> </mouse> </general> <lvm config:type="list"> <lvm_group> <logical_volumes config:type="list"> <lv> <lv_fs config:type="symbol">reiser</lv_fs> <lv_mount>/</lv_mount> <lv_name>lvroot</lv_name> <lv_size>2147483648</lv_size> </lv> <lv> <lv_fs config:type="symbol">reiser</lv_fs> <lv_mount>/tmp</lv_mount> <lv_name>lvtmp</lv_name> <lv_size>536870912</lv_size> </lv> <lv> <lv_fs config:type="symbol">reiser</lv_fs> <lv_mount>/var</lv_mount> <lv_name>lvvar</lv_name> <lv_size>536870912</lv_size> </lv> </logical_volumes> <lvm_name>vgroot</lvm_name> <pesize>8M</pesize> </lvm_group> </lvm> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext2</filesystem> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>49348609</size> </partition> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>1069219841</size> </partition> <partition> <lvm_group>vgroot</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>auto</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <software> <base>Minimal+X11</base> </software> </install> </profile> -------------- Note : report directive doesn't work, whatever the timeout value , it's always 10s and is always show A Postinstall script on the nfs repository is executed. ========================================================= == 8 == postinstall script and nfs setting ========================================================= My setup is like this /suse/install : repository used to install /suse/autoyast : store .xml control file /suse/update : store homemade and update rpms which are not in /suse/install /suse/postinstall : store postinstall scripts ### file : /suse/postinstall/update_rpm.sh #### #!/bin/sh SERV_UPDATE=128.1.217.166 PATH_UPDATE=/suse/update PATH_SLES=/suse/install mkdir -p /tmp/nfs mount -t nfs $SERV_UPDATE:$PATH_UPDATE /tmp/nfs ### useless since update rpms are in install repository #rpm -Fvh /tmp/nfs/update/i686/*.rpm #rpm -Fvh /tmp/nfs/update/i586/*.rpm #rpm -Fvh /tmp/nfs/update/noarch/*.rpm ### ###### Install homemade rpms (cfengine etc...) ######### rpm -Uvh --nodeps /tmp/nfs/update/add/*.rpm umount /tmp/nfs ##### install sles8 banner ###### mount -t nfs $SERV_UPDATE:$PATH_SLES /tmp/nfs rpm -e --nodeps unitedlinux-release rpm -Uvh /tmp/nfs/SLES/suse/i586/sles-release*.rpm rpm -e --nodeps yast2-theme-UnitedLinux rpm -Uvh /tmp/nfs/SLES/suse/noarch/yast2-theme-SuSE*.rpm umount /tmp/nfs ######## SOURCE UPDATE ########### PATH_UPDATE=/suse/install/update PATH_SLES=/suse/install/SLES PATH_UL=/suse/install/UL/CD1 echo "Deleting old sources" rm -rf /var/adm/YaST/InstSrcManager/* echo "Adding new sources" installation_sources -ea nfs://$SERV_UPDATE:$PATH_UPDATE installation_sources -ea nfs://$SERV_UPDATE:$PATH_SLES installation_sources -ea nfs://$SERV_UPDATE:$PATH_UL #################################### --------------------------------------------------------- ### file : /etc/exports #### /suse/autoyast *(sync,ro) /suse/update *(sync,ro) /suse/install *(sync,ro) /suse/postinstall *(sync,ro) ################# ========================================================= == 9 == Conclusion ========================================================= A sles8 installation is made within 5-10 minutes depending the install machine. No human intervention is needed after the boot (all you must do is to choose the right .xml at the lilo cd screen) After installation the machine reboots on harddrive (in fact it reboot on cd but the cd boots by default on harddrive :p) Update is done at install time : you can say goodbye to smp/bcm5700 driver bug in kernel 2.4.19 Postinstall script on nfs provide easy way to install homemade rpms I hope this set of tips will be on Anas Nashif autoyast Homepage :) Regards, Nicolas Marciniak

1 0

Full automatic installation of SLES8 with update
by Nicolas Marciniak 05 May '04

05 May '04

Here some tips to help you to install a sles8 with update. I think it will be usefull for many people. ========================================================= == 1 == Setting up install directory ========================================================= Use the script in section 6.1.3 of the autoyast documentation for sles8 You have now a repository with SLES CD and UL CD 1,2,3 I have setup my repository in /suse/install I have used UL/CD{1,2,3} and SLES/ instead of unitedlinux-i386/CD{1,2,3} and sles8-i386/CD1 directory ========================================================= == 2 == Download update ========================================================= Go to http://sdb.suse.de/download/i386/update/SuSE-SLES/8/rpm/ Download all rpms like this : foo-x.xx-xx.rpm Do NOT download foo.patch.rpm and foo.rpm files Save files in directory like this /suse/update/update/i586 /suse/update/update/i686 /suse/update/update/noarch Download SP3 CD1 iso to get driverupdate file You must have it later. ========================================================= == 3 == Creating package description for update ========================================================= Install autoyast2 rpm ### script ### cd /suse/update/update/ /usr/local/YaST2/bin/create_package_descr -d /suse/update/update -l english -l german -l french cd /suse/update mkdir media.1 touch content touch media.1/media ############### ### file : content ### PRODUCT SuSE SLES VERSION update DISTPRODUCT SuSE-Linux-SLES-i386 DISTVERSION 8.1-0 BASEPRODUCT UnitedLinux BASEVERSION 1.0 YOUTYPE business YOUPATH i386/update/SuSE-SLES/8 YOUURL http://www.suse.de/cgi-bin/suseservers.cgi VENDOR SuSE Linux AG ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i386 REQUIRES distribution-release LINGUAS de en LABEL SuSE SLES Update LABEL.de SuSE SLES Update DESCRDIR update/setup/descr DATADIR update LANGUAGE en_US TIMEZONE America/Los_Angeles ############### ### file : media.1/media ### SuSE Linux AG 20021022191434 1 ############### You must have this in your /suse/update /suse/update |-- content |-- media.1 | `-- media `-- update |-- i586 -- *.rpm |-- i686 -- *.rpm |-- noarch -- *.rpm `-- setup `-- descr |-- packages |-- packages.DU |-- packages.en `-- packages.fr ========================================================= == 5 == setting up the final repository with update rpms ========================================================= #### script ################ mv /suse/update /suse/install/ cd /suse/install mkdir -p yast/update/update/setup/descr mkdir -p yast/update/media.1 cp -a update/content yast/update/ cp -a update/media.1/media yast/update/media.1/ cp -a update/update/setup/descr/*.* yast/update/update/setup/descr/ ############################ Your /suse/install/yast must look like this : |-- TRANS.TBL |-- order |-- sles8 | |-- content | |-- media.1 | | |-- TRANS.TBL | | |-- info.txt | | |-- media | | `-- products | `-- suse | `-- setup | `-- descr | |-- Minimal+X11.sel | |-- Minimal.sel | |-- X11.sel | |-- packages | |-- packages.DU | |-- .... |-- ul | |-- TRANS.TBL | |-- UnitedLinux | | |-- TRANS.TBL | | `-- setup | | |-- TRANS.TBL | | `-- descr | | |-- Minimal+X11.sel | | |-- Minimal.sel | | |-- X11.sel | | |-- packages | | |-- packages.DU | | |-- packages.cs | | |-- ..... | |-- content | `-- media.1 | |-- TRANS.TBL | |-- info.txt | |-- media | `-- products `-- update |-- content |-- media.1 | `-- media `-- update `-- setup `-- descr |-- packages |-- packages.DU |-- packages.en `-- packages.fr ---- /!\ Don't forget to put the driverupdate file of SP3 CD1 in /suse/install ========================================================= == 6 == Important files ========================================================= /suse/install/yast/order : -------------------------- /yast/update /update /yast/ul /UL/CD1 /yast/sles8 /SLES ========================================================= == 7 == Make a custom boot cd ========================================================= Mount and copy your SLES8 CD1 to /iso/cdboot/ You can delete all rpm in /iso/cdboot/ to reduce the size of the final cd Mount the SP3 CD to /mnt/sp3 ### script ### cp /mnt/sp3/boot/loader/linux /iso/cdboot/boot/loader/ cp /mnt/sp3/boot/loader/initrd /iso/cdboot/boot/loader/ cp /mnt/sp3/boot/loader/initrd /iso/ touch /iso/info ############### the file info is used to setup network and connect to the nfs repository to install the system ### file : /iso/info ### install: nfs://128.1.217.166/suse/install/ netdevice: eth0 hostip: 128.1.33.60 gateway: 128.1.6.23 nameserver: 128.1.6.228 netmask: 255.255.0.0 textmode: 1 forceinsmod: 1 nopcmcia: 1 ############### I have tweak the isolinux.cfg to get different autoyast control file ### file /iso/cdboot/boot/loader/isolinux.cfg #### default harddisk # hard disk label harddisk kernel linux append SLX=0x202 # ide label ide kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/ide.xml # scsi label scsi kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/scsi.xml # custom1 label custom1 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/custom1.xml # custom2 label custom2 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/custom2.xml # custom3 label custom3 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/custom3.xml failsafe label failsafe kernel linux append initrd=initrd ramdisk_size=65536 ide=nodma apm=off acpi=off # apic #label apic # kernel linux # append initrd=initrd ramdisk_size=65536 apic # manual #label manual # kernel linux # append initrd=initrd ramdisk_size=65536 manual=1 memory test label memtest kernel memtest implicit 0 gfxboot bootlogo display message prompt 1 timeout 100 readinfo 2 framebuffer 1 ####################### Here my script to create a cdboot with sp3 kernel and info file ##### script makeiso.sh ####### #!/bin/bash INITRD=/iso/initrd INITRD_GUNZIP=/iso/initrd_gunzip INITRD_MOUNT=/iso/temp/initrd INFO=$1 CDBOOT=/iso/cdboot ISO=$2 INITRD_FINAL=$CDBOOT/boot/loader/initrd if [ "$#" -lt 2 ] then echo "Usage: makeiso file_info image.iso" exit 1 fi mkdir -p $INITRD_MOUNT gunzip -q < $INITRD > $INITRD_GUNZIP mount -o loop -t minix $INITRD_GUNZIP $INITRD_MOUNT cp $INFO $INITRD_MOUNT umount $INITRD_MOUNT gzip < $INITRD_GUNZIP > $INITRD_FINAL mkisofs -R -l -J -o $ISO -b boot/loader/isolinux.bin -c boot.catalog \ -no-emul-boot -boot-load-size 4 -boot-info-table \ $CDBOOT rm -f $INITRD_GUNZIP ############################### in /iso simply use : ./makeiso.sh info slescustom.iso :) ========================================================= == 7 == Creating a good control file with nfs postinstall script and LVM stuff :) ========================================================= Here my ide.xml control file --------------------- <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <scripts> <chroot-scripts config:type="list"/> <post-scripts config:type="list" > <script> <filename>postinstall.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh UPDATE_SRV=128.1.217.166 UPDATE_DIR=/suse/postinstall eject echo "Mounting update server" mkdir -p /tmp/postinstall mount -t nfs $UPDATE_SRV:$UPDATE_DIR /tmp/postinstall sh /tmp/postinstall/update_rpm.sh ]]> </source> </script> </post-scripts> <pre-scripts config:type="list"/> </scripts> </configure> <install> <bootloader> <location>mbr</location> </bootloader> <report> <messages> <show>false</show> <timeout>5</timeout> <log>true</log> </messages> <errors> <show>true</show> <timeout>5</timeout> <log>true</log> </errors> <warnings> <show>true</show> <timeout>5</timeout> <log>true</log> </warnings> </report> <general> <clock> <hwclock>GMT</hwclock> <timezone>Europe/Paris</timezone> </clock> <keyboard> <keymap>french</keymap> </keyboard> <language>fr_FR</language> <mouse> <id>20_imps2</id> </mouse> </general> <lvm config:type="list"> <lvm_group> <logical_volumes config:type="list"> <lv> <lv_fs config:type="symbol">reiser</lv_fs> <lv_mount>/</lv_mount> <lv_name>lvroot</lv_name> <lv_size>2147483648</lv_size> </lv> <lv> <lv_fs config:type="symbol">reiser</lv_fs> <lv_mount>/tmp</lv_mount> <lv_name>lvtmp</lv_name> <lv_size>536870912</lv_size> </lv> <lv> <lv_fs config:type="symbol">reiser</lv_fs> <lv_mount>/var</lv_mount> <lv_name>lvvar</lv_name> <lv_size>536870912</lv_size> </lv> </logical_volumes> <lvm_name>vgroot</lvm_name> <pesize>8M</pesize> </lvm_group> </lvm> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext2</filesystem> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>49348609</size> </partition> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>1069219841</size> </partition> <partition> <lvm_group>vgroot</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>auto</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <software> <base>Minimal+X11</base> </software> </install> </profile> -------------- Note : report directive doesn't work, whatever the timeout value , it's always 10s and is always show A Postinstall script on the nfs repository is executed. ========================================================= == 8 == postinstall script and nfs setting ========================================================= My setup is like this /suse/install : repository used to install /suse/autoyast : store .xml control file /suse/update : store homemade and update rpms which are not in /suse/install /suse/postinstall : store postinstall scripts ### file : /suse/postinstall/update_rpm.sh #### #!/bin/sh SERV_UPDATE=128.1.217.166 PATH_UPDATE=/suse/update PATH_SLES=/suse/install mkdir -p /tmp/nfs mount -t nfs $SERV_UPDATE:$PATH_UPDATE /tmp/nfs ### useless since update rpms are in install repository #rpm -Fvh /tmp/nfs/update/i686/*.rpm #rpm -Fvh /tmp/nfs/update/i586/*.rpm #rpm -Fvh /tmp/nfs/update/noarch/*.rpm ### ###### Install homemade rpms (cfengine etc...) ######### rpm -Uvh --nodeps /tmp/nfs/update/add/*.rpm umount /tmp/nfs ##### install sles8 banner ###### mount -t nfs $SERV_UPDATE:$PATH_SLES /tmp/nfs rpm -e --nodeps unitedlinux-release rpm -Uvh /tmp/nfs/SLES/suse/i586/sles-release*.rpm rpm -e --nodeps yast2-theme-UnitedLinux rpm -Uvh /tmp/nfs/SLES/suse/noarch/yast2-theme-SuSE*.rpm umount /tmp/nfs ######## SOURCE UPDATE ########### PATH_UPDATE=/suse/install/update PATH_SLES=/suse/install/SLES PATH_UL=/suse/install/UL/CD1 echo "Deleting old sources" rm -rf /var/adm/YaST/InstSrcManager/* echo "Adding new sources" installation_sources -ea nfs://$SERV_UPDATE:$PATH_UPDATE installation_sources -ea nfs://$SERV_UPDATE:$PATH_SLES installation_sources -ea nfs://$SERV_UPDATE:$PATH_UL #################################### --------------------------------------------------------- ### file : /etc/exports #### /suse/autoyast *(sync,ro) /suse/update *(sync,ro) /suse/install *(sync,ro) /suse/postinstall *(sync,ro) ################# ========================================================= == 9 == Conclusion ========================================================= A sles8 installation is made within 5-10 minutes depending the install machine. No human intervention is needed after the boot (all you must do is to choose the right .xml at the lilo cd screen) After installation the machine reboots on harddrive (in fact it reboot on cd but the cd boots by default on harddrive :p) Update is done at install time : you can say goodbye to smp/bcm5700 driver bug in kernel 2.4.19 Postinstall script on nfs provide easy way to install homemade rpms I hope this set of tips will be on Anas Nashif autoyast Homepage :) Regards, Nicolas Marciniak

1 0

SMB parameters for username, password, & workgroup?
by Kohrs, Steven 04 May '04

04 May '04

Where can I find a definition for the "init" element under "install"? I'm trying to include a username, password, & workgroup for a SMB share. I tried the following with no success: ... <init> <domain></domain> <gateway></gateway> <info_file> <![CDATA[ # # Don't remove the following line: # start_linuxrc_conf # install: smb://192.168.0.23/suse8 workdomain: WORKGROUP username: skohrs password: passw0rd Usedhcp: 1 Textmode: 1 # end_linuxrc_conf # Do not remove the above comment #]]> </init> ... Can I place these values in-line, like with FTP? smb://WORKGROUP\skohrs:passw0rd@192.168.0.23/suse8

1 0