January 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

<hwclock>localtime</hwclock> bug?
by Holger Hellmuth 19 Jan '04

19 Jan '04

Hi, after installing with the hardware clock set to localtime (because there might be a windows on a few machines, too) with <hwclock>localtime</hwclock> the machine still uses UTC, in /etc/sysconfig/clock there is still only the line HWCLOCK="-u" instead of HWCLOCK="--localtime" This is not the fault of YAST, with a manual install it works, only autoyast seems not to take the value. Here the relevant excerpts from y2log: 2003-12-22 17:56:30 <1> linux(1130) [YCP] modules/AutoInstall.ycp(Continue):147 Found and read saved autoinst data : <...> "general":$["clock":$["hwclock":"localtime", "timezo ne":"Europe/Berlin"], "keyboard":$["keymap":"german"], <...> and later: 2003-12-22 17:56:42 <1> linux(1130) [Interpreter] clients/installation.ycp:150 Loading YCP module Timezone 2003-12-22 17:56:42 <1> linux(1130) [YCP] modules/Misc.ycp(Misc::SysconfigRead):241 .sysconfig.clock.TIMEZONE: <Europe/Berlin> 2003-12-22 17:56:42 <1> linux(1130) [YCP] modules/Misc.ycp(Misc::SysconfigRead):241.sysconfig.clock.DEFAULT_TIMEZONE: <Europe/Berlin> 2003-12-22 17:56:42 <1> linux(1130) [YCP] modules/Misc.ycp(Misc::SysconfigRead):241 .sysconfig.clock.HWCLOCK: <-u> 2003-12-22 17:56:43 <1> linux(1130) [YCP] modules/Timezone.ycp(Timezone::Set):177 Set timezone:Europe/Berlin sel:0 name:Europa / Deutschland Holger.

1 0

Howto define IP ranges in rules?/script question
by Frank Steiner 19 Jan '04

19 Jan '04

Hi, I've installed dozens of computers with autoyast1 and SuSE 7.3 in the last years. Now I need to switch to SuSE 9.0 and try to learn the new autoyast2 interface. However, even after reading the complete html docu for 9.0 and browsing the mailing list archives, I still don't unterstand two things: 1) Is there any way to define IP ranges in rules? In autoyast1 I used to have lines like CLASS 141.84.1.210-240 k_smp in the main info file and info.k_smp would then contain a definition for using the k_smp kernel. In the rules.xml, I only see the hostaddress attribute which must match exactly. I tried a range there, but it did not work. How can I apply a rule to a set/range of ips without specifying each ip? 2) Do I really have to write all the scripts inside a profile? Is itnot possible to just call an external script file? Thanks a lot for any help (especially for the first question, the second is not really that important..) cu, Frank -- Dipl.-Inform. Frank Steiner Mail: fst_at_bio.informatik.uni-muenchen.de Lehrstuhl f. Bioinformatik Mail: frank_at_familiesteiner.de LMU, Amalienstr. 17 Phone: +49 89 2180-4049, Fax: -4054 80333 Muenchen, Germany http://www.informatik.uni-kiel.de/~fst/

2 2

Re: [suse-autoinstall] Autoinstallation and SuSE 8.2 Pro
by Mouncef_Belcaid＠blm.gov 19 Jan '04

19 Jan '04

Thank you for the suggestion. I copied all CDs to one directory using the following command for all CDs: mount /media/cdrom; cp -va /media/cdrom /repository/suse/8.2; eject Mouncef Anas Nashif <nashif(a)suse.de> To: suse-autoinstall(a)suse.com cc: 01/16/2004 07:02 Subject: Re: [suse-autoinstall] Autoinstallation and SuSE 8.2 Pro PM Patrick Greenwell wrote: > http://portal.suse.de/sdb/en/2003/03/rschmid_slesnfs.html > may help. > not reallly, this is more for sles configurations.. Mouncef, how did you copy the CDs, are all in the same directory or do you have seperate dirs for every CD? You have to copy them all into one directory if you wish to run the create_package_descr command, otherwise you dont need to run it, unless you change the packages. Anas > > On Jan 16, 2004 4:29 PM, Mouncef_Belcaid(a)blm.gov wrote: > > >> >> >> >> >>Hi everyone, >> >>I have been trying to install SuSE 8.2 using autoyast2 for the past couple >>of days. It worked with SuSE 9.0 but I'm having trouble with 8.2. >>I set up a repository from the 5 CDs provides with the SuSE distribution >>under /repository/suse/8.2, ran the following command: >>/usr/lib/YaST2/bin/create_package_descr -d /repository/suse/8.2/suse and >>shared it using nfs. This server is the pxe/tftp server as well as the nfs >>and dhcp server. >> >>I start the test machine, it goes through the configuration, formatting and >>installation process. Once it reboots the first time, it tries to install >>more packages and that is when it asks me to insert "CD 2". My question is, >>why doesn't it retrieve the rest of the packages from the nfs mount? This >>issue didn't happen with the SuSE 9.0 automated installation. >> >>Any help will be appreciated. >> >>Thanks in advance, >>Mouncef >> >> >>-- >>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

"searching /etc/fstab" functionality from ay1 lost?
by Frank Steiner 19 Jan '04

19 Jan '04

Hi, studying section 4.4 of the ay2-docu from SuSE 9.0, it seems that one great functionality from autoyast1 is los in autoyast2: In ay1 you could specify this: AUTO_FDISK_DISK /dev/hda FSTAB_SEARCH /dev/hda1 /dev/hda2 /dev/hda3 FSTAB_FORMAT / /boot Behaviour would be: On a unpartitioned disk /dev/hda, partition it according to the specification in some file (was in the descr directory). If the disk is already partitioned, search for /etc/fstab in partition 1, 2 and 3. If no fstab was found, partition the whole drive according to the specification. If fstab was found, just format the partitions that were mounted as /boot and / according to this fstab. Thus, for a partitioned drive, you could just let autoyast format some partitions, without any knowledge about number, id, size etc. of this partition, while a fresh hard disk would be partitionied automatically. In autoyast2, it seems that I have to know the partition numbers of /boot and /. This would make things very complicated for a large set of different hosts, because you would need a different partitions instruction for a lot of hosts. Also I don't see how I can perform a "if partitions exist, only format some, if partitions do not exist, create them" scenario in general, even if I would specify the partition numbers etc. Would a combination of "<use>free</use>" and "<create>no</create>" create any partitions on an empty hard disk..? I will try some things like that... Are there any known solutions to these problems? cu, Frank -- Dipl.-Inform. Frank Steiner Mail: fst_at_bio.informatik.uni-muenchen.de Lehrstuhl f. Bioinformatik Mail: frank_at_familiesteiner.de LMU, Amalienstr. 17 Phone: +49 89 2180-4049, Fax: -4054 80333 Muenchen, Germany http://www.informatik.uni-kiel.de/~fst/

1 0

Re: [suse-autoinstall] Need Help Creating a Network Boot Floppy
by Harald.Milz＠computacenter.com 19 Jan '04

19 Jan '04

There is no need to compile anything with Etherboot as long as you go to www.rom-o-matic.net. If you want/need to boot via PXE on a machine which doesn't support PXE, get the RBFG.exe file from a w2000 or w2003 server or from argontechnology. It does not support that many ethernet NICs, though, and it doesn't work too well within VMware. Mit freundlichen Gruessen - Best regards Harald Milz Senior Consultant CC CompuNet AG & Co. oHG A part of Computacenter plc Hoerselbergstrasse 7, 81677 Muenchen, Germany Phone: +49 (0)89 45712-161, Fax: -331, Mobile: +49 (0)173 3866604 E-Mail : Harald.Milz(a)computacenter.com Visit us on the Internet: http://www.computacenter.com Visit our Online-Shop: http://www.compunet.de/connect This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document. suse-autoinstall-return-1508-harald.milz=computacenter.com(a)suse.com on 16.01.2004 16:16:14 To: <suse-autoinstall(a)suse.com>, <marshall28(a)juno.com> cc: Subject: Re: [suse-autoinstall] Need Help Creating a Network Boot Floppy -------------------------------------------------------------------------- Note: http://www.tldp.org/HOWTO/NFS-Root.html may be your best source of information. "True" network boot: I did this years ago using Slackware, before SuSE was big. I used a package called "Boot-ROM" written by Gero Kuhlmann. It is really a package for writing Boot ROMs for putting into network cards if you have an EEPROM burner but you can use it just loaded onto a floppy too. It scans for an IP address then attempts to load a kernel over tftp using compiled in parameters. Also see http://www.etherboot.org/ as recommended on the PXE Linux homepage (http://syslinux.zytor.com/pxe.php) You'll need to do some compiling either way but etherboot looks like the most maintained. At the time I was doing it (6 years ago) etherboot was a bit basic as I remember. Possibly a simpler/better option: If you are sure that you won't ever want to distribute new kernels to your thin client PCs (i.e. they are not up the side of a mountain with no postal service! :) then you could just put a kernel directly onto a floppy disk for them. This is covered in the above HOWTO. Checking my SuSE 8.2 kernel I see it's got the relevant IP options discovery and NFS root code compiled in. To use this you'll need to pass the correct parameters to the kernel at boot time - see nfsroot.txt in /usr/src/linux (you have to have the kernel_source.rpm package installed). To go this route you'll also need to install LILO or GRUB on the floppy. If none of this works (one problem is that there may not be enough room on the floppy disk) you'll probably need to compile a kernel, which isn't all that hard really - there are many HOWTOs on how to do this. If you get nowhere finding stuff, I do have a disk image of a precompiled boot-rom for floppy disk if you want it, ask me and I'll email it directly to you but it will only work with NE2000 compatible NIC though which is probably little use. Regards, Carl Peto Linux Support Bookman Associates ----- Original Message ----- From: <marshall28(a)juno.com> To: <suse-autoinstall(a)suse.com> Sent: Thursday, January 15, 2004 6:29 PM Subject: [suse-autoinstall] Need Help Creating a Network Boot Floppy > I've got my tftp/dhcp server up and running but need help preparing a boot floppy which will start the install for me. I want to be able to just boot off the floppy, contact the tftp/dhcp servers and start the install. The attached document is very similiar to my configuration, except a few ip address differences. If someone knows how to create a network boot floppy using this configuration, please respond. > > thanks > marshall > ---------------------------------------------------------------------------- ---- > -- > 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

Rules example
by Frank Steiner 19 Jan '04

19 Jan '04

Hi, can someone provide some examples for rules using a) custom scripts b) the range match type? I haven't found any further explanations about those in the documentation. Thanks a lot! Best regards, Frank -- Dipl.-Inform. Frank Steiner Mail: fst_at_bio.informatik.uni-muenchen.de Lehrstuhl f. Bioinformatik Mail: frank_at_familiesteiner.de LMU, Amalienstr. 17 Phone: +49 89 2180-4049, Fax: -4054 80333 Muenchen, Germany http://www.informatik.uni-kiel.de/~fst/ * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

1 0

SLES vs UnitedLinux from NFS install
by Hal Wine 18 Jan '04

18 Jan '04

I'm a relative newbie to SuSE/yast, so first question is: what's the best way to search the list archive? Second question is on setting up an installation server. I used script in http://www.suse.de/~nashif/autoinstall/8.1/html/index.html and get an apparently good manual install. However, lsb-release thinks it's a UnitedLinux system, instead of a SLES8 system. When I install from the CD's, for lsb_release -a I get # lsb_release -a LSB Version: 1.2 Distributor ID: SuSE Description: SuSE SLES-8 (i386) Release: 8.1 Codename: n/a From the NFS install, I get: # lsb_release -a LSB Version: 1.2 Distributor ID: UnitedLinux Description: UnitedLinux 1.0 (i586) Release: 1.0 Codename: n/a This happens to be significant to us.... Any pointers to correcting this would be much appreciated.... --Hal

2 1

Autoinstallation and SuSE 8.2 Pro
by Mouncef_Belcaid＠blm.gov 17 Jan '04

17 Jan '04

Hi everyone, I have been trying to install SuSE 8.2 using autoyast2 for the past couple of days. It worked with SuSE 9.0 but I'm having trouble with 8.2. I set up a repository from the 5 CDs provides with the SuSE distribution under /repository/suse/8.2, ran the following command: /usr/lib/YaST2/bin/create_package_descr -d /repository/suse/8.2/suse and shared it using nfs. This server is the pxe/tftp server as well as the nfs and dhcp server. I start the test machine, it goes through the configuration, formatting and installation process. Once it reboots the first time, it tries to install more packages and that is when it asks me to insert "CD 2". My question is, why doesn't it retrieve the rest of the packages from the nfs mount? This issue didn't happen with the SuSE 9.0 automated installation. Any help will be appreciated. Thanks in advance, Mouncef

3 2

Re: [suse-autoinstall] Autoinstall+pxe+raid1
by Mouncef_Belcaid＠blm.gov 16 Jan '04

16 Jan '04

Hi Anas, Yes, I am using the original files that come with the SuSE 9.0 Pro. I tried SuSE 8.2 Pro and it worked. Thanks, Mouncef Anas Nashif <nashif(a)suse.de> To: Mouncef_Belcaid(a)blm.gov cc: suse-autoinstall(a)suse.com 01/15/2004 06:54 Subject: Re: [suse-autoinstall] Autoinstall+pxe+raid1 PM Hi, Are you using the original installation files, ie. kernel, initrd? This is probably due to version mismatch, the raid modules should be loaded automatically... Anas Mouncef_Belcaid(a)blm.gov wrote: > > > > Hi everyone! > > I have two 40GB drives that I want to mirror (hda and hdc). I am trying to > install SuSE 9.0 Pro using autoyast. I tried using software raid (raid1) > with no success. At the formatting stage of the auto installation I get the > following error: > "Error > Could not load module raid1" > > I would like to put /boot and / in /dev/md0 and /dev/md1. I also created > two swap partitions, one in each drive. Here is my raid config in the XML > control file: > ======================================================= > <partitioning config:type="list"> > <drive> > <device>/dev/hda</device> > <partitions config:type="list"> > <partition> > <format config:type="boolean">false</format> > <partition_id config:type="integer">253</partition_id> > <partition_type>primary</partition_type> > <raid_name>/dev/md0</raid_name> > <raid_type>raid</raid_type> > <size>100mb</size> > </partition> > <partition> > <format config:type="boolean">false</format> > <partition_id config:type="integer">253</partition_id> > <partition_type>primary</partition_type> > <raid_name>/dev/md1</raid_name> > <raid_type>raid</raid_type> > <size>36gb</size> > </partition> > <partition> > <filesystem config:type="symbol">swap</filesystem> > <format config:type="boolean">true</format> > <mount>swap</mount> > <partition_id config:type="integer">130</partition_id> > <partition_type>primary</partition_type> > <size>1gb</size> > </partition> > </partitions> > <use>all</use> > </drive> > <drive> > <device>/dev/hdc</device> > <partitions config:type="list"> > <partition> > <format config:type="boolean">false</format> > <partition_id config:type="integer">253</partition_id> > <partition_type>primary</partition_type> > <raid_name>/dev/md0</raid_name> > <raid_type>raid</raid_type> > <size>100mb</size> > </partition> > <partition> > <partition> > <format config:type="boolean">false</format> > <partition_id config:type="integer">253</partition_id> > <partition_type>primary</partition_type> > <raid_name>/dev/md1</raid_name> > <raid_type>raid</raid_type> > <size>36gb</size> > </partition> > <partition> > <filesystem config:type="symbol">swap</filesystem> > <format config:type="boolean">true</format> > <mount>swap</mount> > <partition_id config:type="integer">130</partition_id> > <partition_type>primary</partition_type> > <size>1gb</size> > </partition> > </partitions> > <use>all</use> > </drive> > <drive> > <device>/dev/md</device> > <partitions config:type="list"> > <partition> > <filesystem config:type="symbol">xfs</filesystem> > <format config:type="boolean">true</format> > <mount>/boot</mount> > <partition_id config:type="integer">131</partition_id> > <partition_nr config:type="integer">0</partition_nr> > <raid_options> > <chunk_size>4</chunk_size> > <parity_algorithm>left-asymmetric</parity_algorithm> > <raid_type>raid1</raid_type> > </raid_options> > </partition> > <partition> > <filesystem config:type="symbol">xfs</filesystem> > <format config:type="boolean">true</format> > <mount>/</mount> > <partition_id config:type="integer">131</partition_id> > <partition_nr config:type="integer">1</partition_nr> > <raid_options> > <chunk_size>4</chunk_size> > <parity_algorithm>left-asymmetric</parity_algorithm> > <raid_type>raid1</raid_type> > </raid_options> > </partition> > </partitions> > <use>all</use> > </drive> > </partitioning> > ========================================================= > > Any help will be greatly appreciated. > > Thanks, > mb > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Need Help Creating a Network Boot Floppy
by marshall28＠juno.com 16 Jan '04

16 Jan '04

I've got my tftp/dhcp server up and running but need help preparing a boot floppy which will start the install for me. I want to be able to just boot off the floppy, contact the tftp/dhcp servers and start the install. The attached document is very similiar to my configuration, except a few ip address differences. If someone knows how to create a network boot floppy using this configuration, please respond. thanks marshall

2 1