May 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

format some partitions, don't format others
by John SJ Anderson 22 May '06

22 May '06

Hi -- I'm working on setting up an autoinstall infrastructure that will be used to convert around 750 machines from a customized Slackware distribution to SLES9SP3. Obviously, automation of as much as possible is key. We'd also like to borrow a page from the ROCKS folks and make re-installs as painless as possible, because it's something that comes up in our environment a fair bit. The general idea is to have two "standard" partitions, / and /var, on /dev/md0 (sd[ab]1) and /dev/md1 (sd[ab]2), respectively, and then have some more specific RAID partitions on the remaining parts of the disk (with different sorts of machines having different sorts of partitioning schemes). During an initial install (which can be assumed to mean "an install onto disks that don't have a partition table yet"), all of these partitions would need to be created and initialized, the RAIDs set up, and the filesystems created. During a reinstall, we would only want to reformat '/' and '/var' -- any other partitions/RAID devices/filesystems should be left alone. The /etc/fstab file will be managed with our configuration management system, so having that maintained properly across reinstalls isn't a concern -- as long as the reinstall can get to the point where it will boot and mount / and /var, everything will converge to the desired state once the tool runs. The goal is to do this with only a single install.xml config file. It's not clear from the AutoYaST PDF whether or not this is possible -- can anybody here shed some light on whether this particular windmill is a good tilting target or not? thanks, john. -- It's easy to get the *wrong* answer in O(1) time. Mark Jason Dominus's Good Advice #11963

2 1

Configuring SLES 9 autoinstall with new RPMs
by Spangler, Tim 22 May '06

22 May '06

Hello, I've created a SUSE auto install server and have configured it to apply SP3 during the install process. Now I need to configure it to allow me to copy new and updated RPMs into a folder and apply them when necessary. For example, I want to deploy the newest version of Bastille to each new server I build and then create a post install script that runs Bastille to lockdown the server right during install. In a month I may decide I need to put the newest version of perl in the install directory and have it automatically deployed. In other words this needs to be a solution where I can just copy RPMs into the updates folder and have them be applied. So far I've created an updates directory in the root install directory and have configured the instorder and order files to look in the updates folder like follows: /updates /sles9sp3/cd1 /sles9/cd1 /core9/cd1 I've copied the newest Bastille rpm into the updates folder, but when the auto install runs I get an error that says "reading media description failed". Any ideas on where am I going wrong? Thanks, -Tim Spangler

2 1

Using GPT partitions with SLES9
by Jeremy Silver 18 May '06

18 May '06

All, I am trying to create an install profile for a system with >2TB disk (a raid array). Can anyone tell me how I can specify a disk be partitioned using GPT instead of the standard partitioning scheme? I have no problem setting up the disk using parted, but I have yet to see anything close to this in the documentation or list archives. Thanks in advance. -- Jeremy Silver Jeremy-list(a)broadware.com

2 4

Linking error with vsftpd
by naveen penumala 18 May '06

18 May '06

I'm trying to build vsftpd, and I have downloaded version 2.0.4 on SUSE linux 10.1. gcc -c access.c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIE -fstack-protector -idirafter dummyinc gcc -c features.c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIE -fstack-protector -idirafter dummyinc gcc -c readwrite.c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIE -fstack-protector -idirafter dummyinc gcc -c ssl.c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIE -fstack-protector -idirafter dummyinc gcc -c sysutil.c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIE -fstack-protector -idirafter dummyinc sysutil.c: In function âvsf_sysutil_connect_timeoutâ: sysutil.c:1744: warning: pointer targets in passing argument 5 of âgetsockoptâ differ in signedness gcc -c sysdeputil.c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fPIE -fstack-protector -idirafter dummyinc gcc -o vsftpd main.o utility.o prelogin.o ftpcmdio.o postlogin.o privsock.o tunables.o ftpdataio.o secbuf.o ls.o postprivparent.o logging.o str.o netstr.o sysstr.o strlist.o banner.o filestr.o parseconf.o secutil.o ascii.o oneprocess.o twoprocess.o privops.o standalone.o hash.o tcpwrap.o ipaddrparse.o access.o features.o readwrite.o ssl.o sysutil.o sysdeputil.o-Wl,-s `./vsf_findlibs.sh` -pie /lib/libpam.so.0: could not read symbols: File in wrong format collect2: ld returned 1 exit status make: *** [vsftpd] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.97854 (%build) It seems to me that there is some trouble reading symbols defined in libpam - but why? thnaks Naveen.P

2 1

RE: [suse-autoinstall] SLES 9 SP3 Network Install Issue
by warren＠leetnet.com 17 May '06

17 May '06

Installing with a 100MB boot partition worked. Thanks for your help figuring this out. Now on to actually doing the autoyast stuff along with some post-install scripts. Thanks! Warren Quoting anoop kundathil <anoopbharathan(a)yahoo.com>: > Warren, > > It is clear that your installation setup has no issues now. Things can be > suspected is > 1.Your partitoning scheme > 2. additional hardware which is connected to your system ( any usb cd/key > etc ) > also try to install with 100MB boot partition as i suggested earlier > > thanks > Anoop > > warren(a)leetnet.com wrote: > Thanks for the reply. See below: > > Quoting Hans-Joachim Ehlers : > > > Some thoughts about the SLES reposirtoy > > 1) If you create a SLES9 SP3 repository for the installation server - > > actually the machine from where you create the repository - should be > > forhand updated to SP3 > > This is exactly what was done. > > > 2) use the yast installation server menues to create the repository > > Again, this is what was done. (I actually did it manually before realizing > that > I could do it through YaST - once I realized it I started from scratch and > did > it through YaST) > > > 3) The most important thing is that you use at least the SP3 boot CD. In > our > > current enviroment we build the boot CD from the fresh created repository. > > I've tried booting from SP3 and I've tried the regular SLES boot CD as well > with > the same results. This disk was created prior to me coming to this company, > however it installs SP3 just fine and was added to the repository through > YaST > with no issues. > > > Regarding dell > > Nowaday DELL machine have SATA drives. The SLES GM release does not supoort > > SATA afaik but at least SP2 does. > > To install from a SLES GM release you can switch in the DELL bios the SATA > > mode to combined meaning that ATA will be used. > > Problem with that: > > SLES GM will see hdX device but after installation you might have sdX > > devices. In this case grub will fail. > > So you are might back to point 3) above ;-) > > I'm using GX260's for testing purposes initially, which are IDE. The > bootloader > is trying to load from /dev/hdax as well. > > This morning I am going to do as suggested before and try another network > install and create a 100MB boot partition instead of letting the boot > directory > sit on the / partition. I'll post back the results. > > Anymore insight into this issue would be greatly appreciated. > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > --------------------------------- > How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0

RE: [suse-autoinstall] SLES 9 SP3 Network Install Issue
by warren＠leetnet.com 17 May '06

17 May '06

Thanks for the reply. See below: Quoting Hans-Joachim Ehlers <HansJoachim.Ehlers(a)eumetsat.int>: > Some thoughts about the SLES reposirtoy > 1) If you create a SLES9 SP3 repository for the installation server - > actually the machine from where you create the repository - should be > forhand updated to SP3 This is exactly what was done. > 2) use the yast installation server menues to create the repository Again, this is what was done. (I actually did it manually before realizing that I could do it through YaST - once I realized it I started from scratch and did it through YaST) > 3) The most important thing is that you use at least the SP3 boot CD. In our > current enviroment we build the boot CD from the fresh created repository. I've tried booting from SP3 and I've tried the regular SLES boot CD as well with the same results. This disk was created prior to me coming to this company, however it installs SP3 just fine and was added to the repository through YaST with no issues. > Regarding dell > Nowaday DELL machine have SATA drives. The SLES GM release does not supoort > SATA afaik but at least SP2 does. > To install from a SLES GM release you can switch in the DELL bios the SATA > mode to combined meaning that ATA will be used. > Problem with that: > SLES GM will see hdX device but after installation you might have sdX > devices. In this case grub will fail. > So you are might back to point 3) above ;-) I'm using GX260's for testing purposes initially, which are IDE. The bootloader is trying to load from /dev/hdax as well. This morning I am going to do as suggested before and try another network install and create a 100MB boot partition instead of letting the boot directory sit on the / partition. I'll post back the results. Anymore insight into this issue would be greatly appreciated. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0

RE: [suse-autoinstall] SLES 9 SP3 Network Install Issue
by Hans-Joachim Ehlers 17 May '06

17 May '06

Some thoughts about the SLES reposirtoy 1) If you create a SLES9 SP3 repository for the installation server - actually the machine from where you create the repository - should be forhand updated to SP3 2) use the yast installation server menues to create the repository 3) The most important thing is that you use at least the SP3 boot CD. In our current enviroment we build the boot CD from the fresh created repository. Regarding dell Nowaday DELL machine have SATA drives. The SLES GM release does not supoort SATA afaik but at least SP2 does. To install from a SLES GM release you can switch in the DELL bios the SATA mode to combined meaning that ATA will be used. Problem with that: SLES GM will see hdX device but after installation you might have sdX devices. In this case grub will fail. So you are might back to point 3) above ;-) This way you will not have the trouble to boot from GM release but installing SP3 hth Hajo >>> "Warren Crigger" <warren(a)leetnet.com> 17/05/2006 06:11:00 >>> Thanks for the reply. The hardware I'm installing on initially for test are Dell desktops: P4 ~2.4Ghz, 1 GB RAM, single 40GB drive. The 'repository' server is a PowerEdge 2650, 2 x ~3.2 Xeon, 8 GB, 4x73gb running Raid 5. I'll be asking for a second PowerEdge as a client for testing once I get this working a little better. When I install SLES from CD media everything is fine, however, now we want to do this automated over the network. I used Yast-> Misc-> Installation Server to set up the repository of SLES inclusive of SP3 with no errors whatsoever. When I'm back at the office tomorrow I'll try to run the install again with a 100mb boot partition and see what happens. It's the better way to go, I agree, but that shouldn't really be the issue. Thanks for your help. _____ From: anoop kundathil [mailto:anoopbharathan@yahoo.com] Sent: Tuesday, May 16, 2006 11:41 PM To: warren(a)leetnet.com Subject: Re: [suse-autoinstall] SLES 9 SP3 Network Install Issue Hi, If the machine is hanging at GRUB stage2, then the system is not able to locate the GRUB stage2 loader which may be on your boot/root partition. Grub loads in two stages, stgae 1 and stage2. Stage1 is hardly 446 bytes and it is a pointer to the stage2 program.Stage2 is the actual boot loader and the size of the program is more than the size of an MBR (512 bytes) This is the reason why the program is loaded in two stages. You can create a seperate boot partition of ~100MB and try the installation. In most of the cases it is advisable to have a /boot partition for easy maintenance and sysadmin work. Also if you can provide more information of the hadware it will help. I have installed and tested Dell Poweredge systems with SLES9 SP3 and works fine for me Thanks Anoop warren(a)leetnet.com wrote: Firstly, sorry for the long email, I'd rather put more info than not enough ;-) I've been tasked with setting up Autoyast for my company's SLES 9.1 installs. I used yast2 to create the media directories (SLES & SP3) and decided to run some network (http) install tests first before doing the xml Autoyast stuff. I've tested this on two Dell desktops for test with the same result. Ultimately we will be installing on PowerEdges but I haven't been able to test that hardware yet and I doubt it will make a difference. What I'm doing: Booting to CD, choosing http silent install along with selecting local, packages, partitioning scheme (a temp partition with tmpfs and the remaining on / as reiserfs). I choose to let grub load from the MBR. The install over the network runs fine. However, when it completes and reboots the problem comes in: "GRUB Loading stage2.. GRUB Loading stage2.." And hangs. I've booted into rescue mode and viewed the Yast logs but nothing is sticking out at me: -in y2logRPM.log packages including kernel shows installed ok -in y2log there are a few errors, but i wouldn't consider any critical -y2loggrub: --------------------------------------- GNU GRUB version 0.94 (640K lower / 3072K upper memory) grub> root (hd0,1) Filesystem type is reiserfs, partition type 0x83 grub> install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0) /boot/grub/stage2 0x8000 (hd0,1)/boot/grub/menu.lst grub> quit Root device: /dev/hda2 (mounted on / as reiserfs) Module list: reiserfs ---------------------------------------- -y2logmkinitrd: ---------------------------------------- Kernel image: /boot/vmlinuz-2.6.5-7.244-default Initrd image: /boot/initrd-2.6.5-7.244-default Shared libs: lib/ld-2.3.3.so lib/libblkid.so.1.0 lib/libc.so.6 lib/libselinux.so.1 lib/libuuid.so.1.2 Modules: kernel/fs/reiserfs/reiserfs.ko Including: udev You may now have to update your boot loader configuration. ------------------------------------------ The /boot/ directory seems normal to me: ------------------------------------------ -rw-r--r-- 1 root root 119140 Dec 12 19:58 Kerntypes-2.6.5-7.244-default -rw-r--r-- 1 root root 774348 Dec 12 19:44 System.map-2.6.5-7.244-default -rw-r--r-- 1 root root 512 May 12 11:56 backup_mbr lrwxrwxrwx 1 root root 1 May 16 14:21 boot -> . -rw-r--r-- 1 root root 5969920 May 16 14:03 boot.tar -rw-r--r-- 1 root root 57001 Dec 12 19:58 config-2.6.5-7.244-default drwxr-xr-x 2 root root 416 May 12 11:56 grub lrwxrwxrwx 1 root root 26 May 16 14:21 initrd -> initrd-2.6.5-7.244-default -rw-r--r-- 1 root root 1264374 May 12 11:56 initrd-2.6.5-7.244-default -rw-r--r-- 1 root root 82944 May 12 11:56 message -rw-r--r-- 1 root root 108897 Dec 12 20:02 symvers-2.6.5-7.244-i386-default.gz -rw-r--r-- 1 root root 1827091 Dec 12 19:58 vmlinux-2.6.5-7.244-default.gz lrwxrwxrwx 1 root root 27 May 16 14:21 vmlinuz -> vmlinuz-2.6.5-7.244-default -rw-r--r-- 1 root root 1544369 Dec 12 19:44 vmlinuz-2.6.5-7.244-default ---------------------------------------------- Any help would be greatly appreciated. Maybe it's something simple here, I am new to using SuSE distrubutions. Regards, Warren ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com _____ Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great <http://us.rd.yahoo.com/mail_us/taglines/postman7/*http://us.rd.yahoo.com/ev t=39666/*http://messenger.yahoo.com> rates starting at 1¢/min.

1 0

RE: [suse-autoinstall] SLES 9 SP3 Network Install Issue
by Warren Crigger 17 May '06

17 May '06

Thanks for the reply. The hardware I'm installing on initially for test are Dell desktops: P4 ~2.4Ghz, 1 GB RAM, single 40GB drive. The 'repository' server is a PowerEdge 2650, 2 x ~3.2 Xeon, 8 GB, 4x73gb running Raid 5. I'll be asking for a second PowerEdge as a client for testing once I get this working a little better. When I install SLES from CD media everything is fine, however, now we want to do this automated over the network. I used Yast-> Misc-> Installation Server to set up the repository of SLES inclusive of SP3 with no errors whatsoever. When I'm back at the office tomorrow I'll try to run the install again with a 100mb boot partition and see what happens. It's the better way to go, I agree, but that shouldn't really be the issue. Thanks for your help. _____ From: anoop kundathil [mailto:anoopbharathan@yahoo.com] Sent: Tuesday, May 16, 2006 11:41 PM To: warren(a)leetnet.com Subject: Re: [suse-autoinstall] SLES 9 SP3 Network Install Issue Hi, If the machine is hanging at GRUB stage2, then the system is not able to locate the GRUB stage2 loader which may be on your boot/root partition. Grub loads in two stages, stgae 1 and stage2. Stage1 is hardly 446 bytes and it is a pointer to the stage2 program.Stage2 is the actual boot loader and the size of the program is more than the size of an MBR (512 bytes) This is the reason why the program is loaded in two stages. You can create a seperate boot partition of ~100MB and try the installation. In most of the cases it is advisable to have a /boot partition for easy maintenance and sysadmin work. Also if you can provide more information of the hadware it will help. I have installed and tested Dell Poweredge systems with SLES9 SP3 and works fine for me Thanks Anoop warren(a)leetnet.com wrote: Firstly, sorry for the long email, I'd rather put more info than not enough ;-) I've been tasked with setting up Autoyast for my company's SLES 9.1 installs. I used yast2 to create the media directories (SLES & SP3) and decided to run some network (http) install tests first before doing the xml Autoyast stuff. I've tested this on two Dell desktops for test with the same result. Ultimately we will be installing on PowerEdges but I haven't been able to test that hardware yet and I doubt it will make a difference. What I'm doing: Booting to CD, choosing http silent install along with selecting local, packages, partitioning scheme (a temp partition with tmpfs and the remaining on / as reiserfs). I choose to let grub load from the MBR. The install over the network runs fine. However, when it completes and reboots the problem comes in: "GRUB Loading stage2.. GRUB Loading stage2.." And hangs. I've booted into rescue mode and viewed the Yast logs but nothing is sticking out at me: -in y2logRPM.log packages including kernel shows installed ok -in y2log there are a few errors, but i wouldn't consider any critical -y2loggrub: --------------------------------------- GNU GRUB version 0.94 (640K lower / 3072K upper memory) grub> root (hd0,1) Filesystem type is reiserfs, partition type 0x83 grub> install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0) /boot/grub/stage2 0x8000 (hd0,1)/boot/grub/menu.lst grub> quit Root device: /dev/hda2 (mounted on / as reiserfs) Module list: reiserfs ---------------------------------------- -y2logmkinitrd: ---------------------------------------- Kernel image: /boot/vmlinuz-2.6.5-7.244-default Initrd image: /boot/initrd-2.6.5-7.244-default Shared libs: lib/ld-2.3.3.so lib/libblkid.so.1.0 lib/libc.so.6 lib/libselinux.so.1 lib/libuuid.so.1.2 Modules: kernel/fs/reiserfs/reiserfs.ko Including: udev You may now have to update your boot loader configuration. ------------------------------------------ The /boot/ directory seems normal to me: ------------------------------------------ -rw-r--r-- 1 root root 119140 Dec 12 19:58 Kerntypes-2.6.5-7.244-default -rw-r--r-- 1 root root 774348 Dec 12 19:44 System.map-2.6.5-7.244-default -rw-r--r-- 1 root root 512 May 12 11:56 backup_mbr lrwxrwxrwx 1 root root 1 May 16 14:21 boot -> . -rw-r--r-- 1 root root 5969920 May 16 14:03 boot.tar -rw-r--r-- 1 root root 57001 Dec 12 19:58 config-2.6.5-7.244-default drwxr-xr-x 2 root root 416 May 12 11:56 grub lrwxrwxrwx 1 root root 26 May 16 14:21 initrd -> initrd-2.6.5-7.244-default -rw-r--r-- 1 root root 1264374 May 12 11:56 initrd-2.6.5-7.244-default -rw-r--r-- 1 root root 82944 May 12 11:56 message -rw-r--r-- 1 root root 108897 Dec 12 20:02 symvers-2.6.5-7.244-i386-default.gz -rw-r--r-- 1 root root 1827091 Dec 12 19:58 vmlinux-2.6.5-7.244-default.gz lrwxrwxrwx 1 root root 27 May 16 14:21 vmlinuz -> vmlinuz-2.6.5-7.244-default -rw-r--r-- 1 root root 1544369 Dec 12 19:44 vmlinuz-2.6.5-7.244-default ---------------------------------------------- Any help would be greatly appreciated. Maybe it's something simple here, I am new to using SuSE distrubutions. Regards, Warren ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com _____ Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great <http://us.rd.yahoo.com/mail_us/taglines/postman7/*http://us.rd.yahoo.com/ev t=39666/*http://messenger.yahoo.com> rates starting at 1¢/min.

1 0

SLES 9 SP3 Network Install Issue
by warren＠leetnet.com 16 May '06

16 May '06

Firstly, sorry for the long email, I'd rather put more info than not enough ;-) I've been tasked with setting up Autoyast for my company's SLES 9.1 installs. I used yast2 to create the media directories (SLES & SP3) and decided to run some network (http) install tests first before doing the xml Autoyast stuff. I've tested this on two Dell desktops for test with the same result. Ultimately we will be installing on PowerEdges but I haven't been able to test that hardware yet and I doubt it will make a difference. What I'm doing: Booting to CD, choosing http silent install along with selecting local, packages, partitioning scheme (a temp partition with tmpfs and the remaining on / as reiserfs). I choose to let grub load from the MBR. The install over the network runs fine. However, when it completes and reboots the problem comes in: "GRUB Loading stage2.. GRUB Loading stage2.." And hangs. I've booted into rescue mode and viewed the Yast logs but nothing is sticking out at me: -in y2logRPM.log packages including kernel shows installed ok -in y2log there are a few errors, but i wouldn't consider any critical -y2loggrub: --------------------------------------- GNU GRUB version 0.94 (640K lower / 3072K upper memory) <snip> grub> root (hd0,1) Filesystem type is reiserfs, partition type 0x83 grub> install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0) /boot/grub/stage2 0x8000 (hd0,1)/boot/grub/menu.lst grub> quit Root device: /dev/hda2 (mounted on / as reiserfs) Module list: reiserfs ---------------------------------------- -y2logmkinitrd: ---------------------------------------- Kernel image: /boot/vmlinuz-2.6.5-7.244-default Initrd image: /boot/initrd-2.6.5-7.244-default Shared libs: lib/ld-2.3.3.so lib/libblkid.so.1.0 lib/libc.so.6 lib/libselinux.so.1 lib/libuuid.so.1.2 Modules: kernel/fs/reiserfs/reiserfs.ko Including: udev You may now have to update your boot loader configuration. ------------------------------------------ The /boot/ directory seems normal to me: ------------------------------------------ -rw-r--r-- 1 root root 119140 Dec 12 19:58 Kerntypes-2.6.5-7.244-default -rw-r--r-- 1 root root 774348 Dec 12 19:44 System.map-2.6.5-7.244-default -rw-r--r-- 1 root root 512 May 12 11:56 backup_mbr lrwxrwxrwx 1 root root 1 May 16 14:21 boot -> . -rw-r--r-- 1 root root 5969920 May 16 14:03 boot.tar -rw-r--r-- 1 root root 57001 Dec 12 19:58 config-2.6.5-7.244-default drwxr-xr-x 2 root root 416 May 12 11:56 grub lrwxrwxrwx 1 root root 26 May 16 14:21 initrd -> initrd-2.6.5-7.244-default -rw-r--r-- 1 root root 1264374 May 12 11:56 initrd-2.6.5-7.244-default -rw-r--r-- 1 root root 82944 May 12 11:56 message -rw-r--r-- 1 root root 108897 Dec 12 20:02 symvers-2.6.5-7.244-i386-default.gz -rw-r--r-- 1 root root 1827091 Dec 12 19:58 vmlinux-2.6.5-7.244-default.gz lrwxrwxrwx 1 root root 27 May 16 14:21 vmlinuz -> vmlinuz-2.6.5-7.244-default -rw-r--r-- 1 root root 1544369 Dec 12 19:44 vmlinuz-2.6.5-7.244-default ---------------------------------------------- Any help would be greatly appreciated. Maybe it's something simple here, I am new to using SuSE distrubutions. Regards, Warren ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0

SLES 9 SP2 smp kernel is runing but cat /proc/version shows default
by Hans-Joachim Ehlers 12 May '06

12 May '06

Hi , right i try to install SLES9 incl SP2 ( Using the 32 bit version on 64 smp hardware( intel) ) The autoyast installation went fine but afterwards the system has a smp-kernel runing ( That ok ) but the cat /proc/version and uname -a saying that i am using the default kernel. Thus i am not able to build the propertary ATI driver because the ati installer says that i have a mistmach between runing and configured kernel. Does anybody run into the same problem and could provide a fix ? Selectiong the default kernel in the autoinstall.xml is not an option because the network does not work afterwards. Example: <base>Minimal+X11</base> <kernel>kernel-smp</kernel> tia Hajo

1 0

Re: [suse-autoinstall] Hard drive detection order during autoinstall
by Hans-Joachim Ehlers 12 May '06

12 May '06

Hi Ian, have you tried the insmod command line option insmod=ModuleOne insmod=ModulTwo eitherway on the command line or put it into the info file. hth Hajo >>> "Marlier, Ian" <ian.marlier(a)studentuniverse.com> 12/05/2006 17:28 >>> Hey, there -- This is an old issue, one that I've never managed to solve once and for all... I've got a set of machines with 2 SATA RAID controllers: an onboard that uses the sata_sil module; and a PCI controller that uses the 3w-9xxx driver. The BIOS detects the sata_sil drives first, and uses the MBR on the first of them. It then detects the RAID 5 exported from the 3ware card. SuSE detects the 3ware card first, and calls its RAID 5 /dev/sda; then it loads the sata_sil driver and calls the two drives on it /dev/sdb and /dev/sdc As the system needs to go onto the sata_sil drives, this ends up causing problems when doing an autoinstall. Ideally, I'd like to be able to force the installation system to load the sata_sil driver _before_ the 3w-9xxx driver. Is there a way to do this, maybe in the "append=" section of my pxelinux configuration? As an alternative, I can modify the initrd (taken from the SuSE 10.0 DVD /boot directory). There isn't an /etc/modules.conf file on there, though, and linuxrc.config doesn't have anything about modules. If there isn't a boot parameter that can be passed, anyone know what I would need to change/add to the initrd to force the sata_sil module to load before 3w-9xxx? Thanks! - Ian -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Hard drive detection order during autoinstall
by Marlier, Ian 12 May '06

12 May '06

Hey, there -- This is an old issue, one that I've never managed to solve once and for all... I've got a set of machines with 2 SATA RAID controllers: an onboard that uses the sata_sil module; and a PCI controller that uses the 3w-9xxx driver. The BIOS detects the sata_sil drives first, and uses the MBR on the first of them. It then detects the RAID 5 exported from the 3ware card. SuSE detects the 3ware card first, and calls its RAID 5 /dev/sda; then it loads the sata_sil driver and calls the two drives on it /dev/sdb and /dev/sdc As the system needs to go onto the sata_sil drives, this ends up causing problems when doing an autoinstall. Ideally, I'd like to be able to force the installation system to load the sata_sil driver _before_ the 3w-9xxx driver. Is there a way to do this, maybe in the "append=" section of my pxelinux configuration? As an alternative, I can modify the initrd (taken from the SuSE 10.0 DVD /boot directory). There isn't an /etc/modules.conf file on there, though, and linuxrc.config doesn't have anything about modules. If there isn't a boot parameter that can be passed, anyone know what I would need to change/add to the initrd to force the sata_sil module to load before 3w-9xxx? Thanks! - Ian

1 0

How to efficiently figure out categories for autoyast in SLED 10.
by Hans Deragon 12 May '06

12 May '06

Greetings. Did: # ls SLED10/i386/suse/setup/descr apparmor-10-12.i586.pat laptop-10-12.i586.pat base-10-12.i586.pat MD5SUMS basis-devel-10-12.i586.pat mono-10-12.i586.pat ccb-10-12.i586.pat network-10-12.i586.pat common.war Novell-software-10-12.i586.pat default-10-12.i586.pat packages directory.yast packages.cs documentation-10-12.i586.pat packages.de EXTRA_PROV packages.DU gnome-10-12.i586.pat packages.en gnome-devel-10-12.i586.pat packages.es gnome-laptop-10-12.i586.pat packages.fr kde-10-12.i586.pat packages.hu kde-devel-10-12.i586.pat packages.sk kde-laptop-10-12.i586.pat patterns kernel-devel-10-12.i586.pat x11-10-12.i586.pat Now, is there an efficient and official way to get all the categories? The only way I found to find the categories is: # fgrep "=Cat.en" * | cut -d: -f3 | sort -u Additional Software Base Technologies Desktops Development Aren't these not stored in some other file I could parse more easily? Best regards, Hans Deragon -- Consultant en informatique/Software Consultant Deragon Informatique inc. http://www.deragon.biz Open source (contribution): mailto://hans@deragon.biz http://autopoweroff.deragon.biz

1 0

autoinstall onto a raid controller
by bryant 10 May '06

10 May '06

I'm trying to do an autoinstallation onto clients systems with raid controllers. the os will be installed onto the raid controller on the clietns using a sles9 server with autoyast. How do I install the raid controller driver onto the client systems before the autoinstallation process? --------------------------------- Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2¢/min with Yahoo! Messenger with Voice.

2 1

"unsubscribe"
by george morrow 04 May '06

04 May '06

"unsubscribe" --------------------------------- Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2¢/min with Yahoo! Messenger with Voice.

1 0

RE: [suse-autoinstall] How to unsubscribe
by Schumacher, Gordon 03 May '06

03 May '06

# From: Lamont R. Peterson [mailto:lrp@xmission.com] # Sent: Wednesday, May 03, 2006 9:00 AM # To: suse-autoinstall(a)suse.com # Subject: Re: [suse-autoinstall] How to unsubscribe # # On Wednesday 03 May 2006 04:44am, Niels Hohn wrote: <snip> # > with the word "unsubscribe" in the subject line. I always get an email # > back telling me that I have succesfully unsubscribed, but still the # > emails from this mailing list comes pooring in. # # Have you tried putting "unsubscribe" in the body of the message? Presumably the system recognized it or he would not have gotten a response back, no?

2 1

How to unsubscribe
by Niels Hohn 03 May '06

03 May '06

Hi all Does anyone know how to unsubscribe from this suse-autoinstall mailing list. I have tried possibly 40 or 50 times to unsubscribe from this mailing list, using the"unsubscribe" link at the bottom of the emails without any luck. I have both sent it with a empty subject line, and with the word "unsubscribe" in the subject line. I always get an email back telling me that I have succesfully unsubscribed, but still the emails from this mailing list comes pooring in. So if anyone know the magic of how to unsubscribe from this mailing list, I would be most appreciative if you could share that knowledge with my. Thank you very much Niels

3 2

Command-line options for "yast2 autoyast"
by Michael T.Halligan 02 May '06

02 May '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to automate the generation of profiles for new servers. I can't seem to find much documentation on if there are, or aren't any command line options I can use with `yast2 autoyast` that would help facilitate this process. Does anybody know if there are? Michael T. Halligan - ------------------------------------- BitPusher, LLC http://www.bitpusher.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEVu/4wjCqooJyNAMRAmtyAJ0fd48xl+AQ4PukNWrlgrxDF2kyywCeIogu 2A6HlWoI13KsNpysrZuI8No= =FnLJ -----END PGP SIGNATURE-----

3 3