February 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

FTP installation from diskettes
by Manuel Balderrábano 10 Feb '04

10 Feb '04

Hi to all. I am trying to install SuSE 9.0 from the suse ftp server. 1.- I created the boot, modules1 and modules3 diskettes. 2.- Booted from first diskette, selected install-manually. 3.- Loaded network card's module(Realtek 8139) from modules3. 4.- Configured network IP, gateway and DNS (ping to the new PC from other PC in the network responds ok) 5.- Tried to install from FTP 195.135.221.130, but after a while I get: Failed to connect to FTP server What am I doing wrong? Thanks in advance.

1 0

various problems with SLSS
by Tom Davidson 10 Feb '04

10 Feb '04

I've got a number of problems with SLSS autoinstall, ranging from minor to serious: 1) *minor* Somewhere, somehow, the initial part of the textmode (and prolly X) installer runs in German. It switched to English as configured once it has the autoinstall XML file. But it hald reverts to German when installing the RPMs, as the descriptions are in German. The resulting box is installed in English OK however. I'm installing via PXE, and I haven't specified anything on the append line for language, but even if I specify on it, I still get the same. 2) *serious* I'm installing on servers ranging from HP DL360 G2/G3s up to possible DL580s (developing on a DL360 G2). The raid controller is detected and the module loaded fine, but when it comes to allocating the partitioning, it fails saying "no free space available on /dev/cciss/c0d0". There will be partitions on there as I've constantly rebuilding testing, but it shouldn't care as I've specified <use>all</use> for the disk /dev/cciss/c0d0 (configured in RAID 1 obviously). This is a pretty unhelpful error message for debugging purposes - where can I suitable logging to tell me why this fails? I've looked in /var/adm/autoinstall, /var/log/YaST2, /tmp/YaST2-####/pre-scripts. Where else does stuff get logged? I've tried a pre-install script hack of dd if=/dev/zero of=/dev/cciss/c0d0 bs=1024 count=1, and it doesn't work when booting with a system that already has partitions - presumably these must get cached earlier on somewhere (a bad practice IMHO). But if I abort the installation, or reboot and try again, nothing is there to get cached, and it half works, which brings me on to the third problem. 3) *serious* I've got a number of partitions configured, including a fixed size of swap (I've included my autoinstall file at the end - apologies for the length). / gets configures as a primary, and I let YaST sort out the rest, which numbers swap c0d0p9. So from issue 3 above, when it installs over a blank disk, it successfully creates all the filesystem partitions, but moans about being unable to create swap with another very unhelpful error message: "could not set up swap partition /dev/cciss/c0d0p9". Why should it successfully create everything but swap? It's not a space issue (they have 18Gb disks), because the "max" setting for /usr/local gobbles up the space that swap should have taken. 4) *concerning* I install SP3 via a finish script that is called from the finish script in the autoinstall file as below. However, when I install it, the kernel it installs hangs on reading the partition table for /dev/cciss/c0d0. I've narrowed this down to acpi, so I've put acpi=off into the kernel parameters section on the autoinstall file, but I'm certain that it shouldn't do that! Please can anyone help with these, especially the serious ones. I'm sure I have more, but I can't think of them right now... Cheers, Tom <?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> <users config:type="list"> <user> <encrypted config:type="boolean">false</encrypted> <user_password>foo</user_password> <username>root</username> </user> </users> <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>localnet</domain> <hostname>susedev-lin-01</hostname> </dns> <interfaces config:type="list"> <interface> <device>eth0</device> <bootproto>dhcp</bootproto> <startmode>onboot</startmode> </interface> <interface> <device>eth1</device> <bootproto>static</bootproto> <broadcast>10.10.10.255</broadcast> <ipaddr>10.10.10.10</ipaddr> <netmask>255.255.255.0</netmask> <network>10.10.10.0</network> <startmode>onboot</startmode> </interface> </interfaces> <routing> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>10.144.128.1</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> <scripts> <chroot-scripts config:type="list"> <script> <filename>chroot.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[#this is chroot #!/bin/sh # Functions die() { echo "$@";exit 1; } # Global Variables NFS_SERVER=foo NFS_PATH=/img NFS_MOUNT_POINT=/a export NFS_SERVER NFS_PATH NFS_MOUNT_POINT # Local Variables BASE=${BASE:-"/mnt"} # mount up the finish scripts test -d $NFS_MOUNT_POINT || mkdir $NFS_MOUNT_POINT test -d $NFS_MOUNT_POINT/suse || \ mount $NFS_SERVER:$NFS_PATH $NFS_MOUNT_POINT || die "couldn't perform NFS mount" fin=$NFS_MOUNT_POINT/suse/scripts # copy the finish scripts test -d $BASE/fin || mkdir $BASE/fin cd $BASE/fin && rm * cp -p $fin/* . 2> /dev/null # unmount the finish scripts cd / umount $NFS_MOUNT_POINT #end chroot]]> </source> </script> </chroot-scripts> <post-scripts config:type="list"> <script> <filename>postinst.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[#this is postinst #!/bin/sh #FAKE=echo # Functions die() { echo "$@";exit 1; } # Global Variables NFS_SERVER=foo NFS_PATH=/img NFS_MOUNT_POINT=/mnt export NFS_SERVER NFS_PATH NFS_MOUNT_POINT # Local Variables # run the finish scripts cd /fin echo "params: 1=$1 2=$2 3=$3 4=$4 5=$5" script_list=${@:-"F*"} script_list="F*" for i in $script_list do test -x $i || interpreter="sh" echo "### executing $i" $FAKE $interpreter ./$i if [ $? = 10 ]; then die "argh! cannot continue. see /var/adm/autoinstall/logs/" fi unset interpreter done cd / #$FAKE rm -rf /fin #end postinst]]> </source> </script> <script> <filename>setrootpw</filename> <interpreter>shell</interpreter> <source> <![CDATA[/usr/bin/perl -pi -e 's#^root::.*$#root:<MDD5Encryption>:::::::\n#' /etc/shadow exit 0]]> </source> </script> </post-scripts> <pre-scripts config:type="list"> <script> <filename>preinst.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[#this is preinst dd if=/dev/zero of=/dev/cciss/c0d0 bs=1024 count=1 #end preinst]]> </source> </script> </pre-scripts> </scripts> </configure> <install> <bootloader> <location>mbr</location> <loader_type>grub</loader_type> <loader_device>/dev/cciss/c0d0</loader_device>   <kernel_parameters>acpi=off</kernel_parameters> </bootloader> <general> <clock> <hwclock>UTC</hwclock> <timezone>Europe/London</timezone> </clock> <keyboard> <keymap>english-uk</keymap> </keyboard> <language>en_GB</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <reboot config:type="boolean">true</reboot> </mode> <mouse> <id>00_ps2</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <use>all</use> <partitions config:type="list">  <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/</mount> <size>1g</size> <partition_type>primary</partition_type> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/usr</mount> <size>1g</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/var</mount> <size>4g</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/home</mount> <size>2g</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/usr/local</mount>  <size>max</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>swap</mount>  <size>2g</size> </partition> </partitions> </drive> </partitioning> <software> <base>Minimal</base> <packages config:type="list"> <package>xntp</package> <package>rcs</package> <package>cvs</package> <package>xinetd</package> <package>tcpdump</package> <package>tcpd</package> <package>screen</package> </packages> </software> </install> </profile> -- Dr. Tom Davidson RHCE Unix Engineer Energis (http://www.energis.com)

2 1

VS: DASD_Parameter, linuxrc, does not recognzie
by Steen Bank Johnsen 10 Feb '04

10 Feb '04

> I have tried to use parmfile to setup the DASD specification for > autoinstall. But no matter how I put it in the parmfile linuxrc does not > recognize it. I have tried mixed case,upper case and lower case. But > nothing helps, has any actually succeded in this ? I'm using SLES8 64 bit > for s390. > > Regards, > > Steen

1 0

Typo on loop mounting instructions?
by Jeff Crow 10 Feb '04

10 Feb '04

I was just wondering if there was a typo error on the instructions for "creating an installation source by loop mounting ISO images instead of copying them to the local disk". The instructions can be found here: http://www.suse.de/~nashif/autoinstall/faq.html#id2459380 The second to last instruction says to do the following: printf "/SLES/CD1\t/SLES/CD1" >> yast/instorder However, there is no CD1 under the SLES directory because there is only one CD for this. Is this a mistake?? Thanks, Jeff

2 1

nfs-Verzeichnisse werden nicht gemountet
by Stefan Preihs 09 Feb '04

09 Feb '04

Hallo ! Ich habe ein privates kleines Computernetz mit 3 Computern. Ich verwende Suse 9.0. 1. Frage: Bei Comp. A habe ich als nfs-server Verzeichnise freigegeben. Comp. B kann diese als nfs-client aber nicht mounten. Es kommt die Fehlermeldung: "Die nfs-Verzeichnisse, die in der Datei etc/fstab eingetragen sind, konnten nicht gemountet werden." Das jeweilige anpingen funktioniert. Die Comp. haben eine statische IP-Adresse (10.100.0.1/3) mit Subnet mask 255.255.255.0. Gleichzeitig verwende ich sie auch als Samba-Netz, d.h. Comp. A ist der Samba Server und Comp. B und C sind Windows Computer. Nur bei Comp. B habe ich Linux und Windows installiert. Ich möchte also bei Comp. B, wenn er in linux arbeitet, auch auf Comp. A mit nfs zugreifen. Ich habe Comp B auch als Samba-client mit YaST2 konfiguriert. Was könnte der Fehler sein? Hängt das mit Samba zusammen? 2. Frage: Wenn Comp. B als linux gestartet ist, kann er auch nicht mittels Samba auf A zugreifen. A ist Samba-server und B ist als Samba-client konfiguriert. Es funktioniert nur wenn ich in den browser (netzwerkumgebung) die IP von A eingebe. Den Namen von A findet er nicht. Ich habe versucht bei den DNS Einstellungen einiges zu verändern und auszuprobieren. Es geht aber nicht. Stefan Mit schönen Grüßen von Yahoo! Mail - http://mail.yahoo.de

1 0

How to create a single CD for SLES (+ SP3) installation?
by Robert Pollak 09 Feb '04

09 Feb '04

Hi, to install a SLES "Minimum system" with SP3, normally three CDs are needed: - UnitedLinux 1.0 SP3 CD1 (to boot with) - SLES8 Installation CD - UnitedLinux 1.0 CD1. I want to create a single CD that combines the necessary data s.t. installing only from this CD gives the same "Minimum system" of SLES-SP3. (Adding autoinst.xml would then yield an install process without any necessary interaction, without the need of a network connection (as with nfs install).) Can this be done with AutoYaST2's "Create ISO Image", or do i have to collect the data and call mkisofs manually (as sketched in http://lists.suse.com/archive/suse-autoinstall/2003-Apr/0047.html "Self made CD-ROMS")? Anas Nashif wrote in "Re: No Kernel SLES8 SP3 autoinstallation", 2004-01-16: > The autoyast2 interface does not support creating CD for SLES8 > installation or in general terms, a CD from multiple sources. So therefore i tried to combine the three CDs' contents into one source (similar to "Create a Packagedatabase", http://lists.suse.com/archive/suse-autoinstall/2003-Oct/0067.html ): Working on a SLES-SP3 minimum system as described at the beginning, I created suse/{i586,i686,noarch} and filled it by copying the contents of - UL CD1: UnitedLinux/{i586,i686,noarch} - SLES CD: suse/{i586, noarch}, - UL SP3 CD1: UnitedLinux/{i586, i686, noarch} . Then i called cd suse; /usr/lib/YaST2/bin/create_package_descr -d . This gives me "processed 1069 packages", and the setup/descr/packages file. Next step would be to add the suse directory as Software Source to yast2, but this only gives me: ERROR(InstSrc:E_no_instsrc_on_media). How do i have to prepare the directory for use as software source? -Robert P.S.: Or should i forget about SP3 and try to manually extend the SLES8 installation CD contents by data from UL-CD1 to get a self-contained CD? (This would give me a single installation interaction: accepting the license.)

2 1

Network Card autoinstall problem
by Bernhard Nöggerath 07 Feb '04

07 Feb '04

Hi, I use SuSE Linux9 AutoYast for installation systems from my own created CD. The destination systems have different network cards, graphic cards, etc. Installation and configuration of the new system works fine incl. Graphic card, X11 etc. During the configuration also the network card is found, configured and useable. But after rebooting the system, the network is not useable since the module was not loaded. It seems to me that just the /etc/modules.conf was not setup right during the autoinstallation. Is there something wrong, or is there a way that I can do "repair" this with one of my post(chroot)-install scripts ? Regards, Bernhard -- | SAM Electronics GmbH | Dipl.-Ing. Bernhard Nöggerath | Software Navigation Systems, Dept. MST 21 | Kurfürstenallee 130 | D-28211 Bremen, Germany | | Phone: +49 421 1784 3513 | Fax: +49 421 1784 2026 | mailto:Bernhard.Noeggerath@sam-electronics.de

2 1

Driver update media problems with SLES 8 SP3
by Andrew Wray 07 Feb '04

07 Feb '04

All, I've been trying to setup a network install (over NFS) for SLES 8 with service pack 3 integrated. I've updated the boot directory with the SP3 files in the root of the install source, and also put the linux directory from SP3 CD1 into an 02/linux directory in the root of the install source. The driverupdates file is there as well. The driver that I need is megaide.o, for an LSI IDE RAID adapter. I've taken the package that LSI provides for SP2a, recompiled the drivers against SP3, repackaged the update.tar.gz file, and then placed it under the 01/linux directory (the BootGRUB.ycp and inst_finish.ycp files were included in the megaide driver update media package, so I thought I should install the SP3 linux directory updates after, so its BootGRUB.ycp and inst_finish.ycp files would overwrite the older ones from the megaide package). The install goes OK, the megaide.o driver is loaded, and the RAID device is seen and installed to, and the SP3 files are installed as well, however, when the system reboots, the megaide module is not on the initrd, so it fails to mount root. I checked the output from mk_initrd during the install, and it reports "Cannot determine dependencies of module megaide\Is modules.dep up to date?". I checked into this further, and it looks like the mk_initrd from SP3 looks at /lib/modules/<kernel-version>/modules.dep, which is not setup by the update.pre script (which is basically just a copy from the example given in the driver update howto), or the update.post script. It is setup in the /etc/modules.dep file though. I modified the update.post script to append the right dependency line in the /lib/modules/<kernel-version>/modules.dep file, and then the install completed OK. However, my question is, does the driver update howto need to be updated to explain how to do this for SP3, or is this a mk_initrd bug? It seems that the way I've set this up, just outputting to the specific kernel that I know will wind up on the system, post-install, is not very portable either--it would fail if a different kernel was installed (on a different system perhaps). Thanks, Andy Wray

1 0

Re: [suse-autoinstall] Cannot mount NFS repository automatically ? SOLVED (maybe)
by francois.blaes＠eu.effem.com 05 Feb '04

05 Feb '04

The problem has just been solved, apparently The server is fitted with a bcm5700 card, which takes a lot of time to come up (more than 40 seconds) probably because of un-optimized switch settings. That timeout is too long for linuxrc to get the network and map the NFS server. However, after a while when the network finally comes up, the NFS volume *can* be mounted and the manual install proceed, as long as one answers "no" when prompted to reconfigure the NIC by linuxrc ("Your network is already configured. Do you want to change this ?") Otherwise, should one answer "yes I want to change my settings" , it looks like linuxrc would switch down and reconfig the NIC, thereby inducing another delay and screw up the NFS mount again. Francois BLAES ? Global Unix Team ? Mars ISI DDI *170 1639 ? Tel +33 (0) 3 88 05 16 39 ? Fax +33 (0) 3 88 05 16 79

2 1

slec8 & xd2
by Grant Williamson 05 Feb '04

05 Feb '04

Hi, I am wondering if anyone has a autoyast config to install a base slec8 & xd2 system. -- Grant Williamson <traxtopel(a)fastmail.fm>

1 0

does yast/instorder matter? Syntax errors in examples.
by Hal Wine 04 Feb '04

04 Feb '04

In some recent verification tests of my http installation server for SLES8 with Service Pack (both 2a & 3), it appears that the contents of the yast/instorder file do not affect the resulting system image. NOTE: this file is documented as having only one field. Many of the examples show 2 tab delimited fields. When you use a tab delimited file, the yast/instorder file appears to be ignored, and the displayed order of sources is as described in the yast/order file. While the listing of source order, as displayed during installation, does differ between a valid yast/instorder and an invalid one, there are no differences in the resulting systems (as measured by comparing 'rpm -qa' output from both variations). As I had read the documentation's description of the purpose of the yast/instorder file, I did expect some differences w.r.t. the yast2 packages. --Hal

3 2

rules.xml and merging
by Voss Stefan 04 Feb '04

04 Feb '04

Hi, at the moment our auto installation does read a non-machine specific generic xml file (via autoyast=...) and a machine specific xml file determined by the following rules.xml: <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script> <![CDATA[ #!/bin/sh # Try to determine value of boot parameter "sysname" sysname=$(cat /proc/cmdline | perl -ne 'print /sysname=(\w+)/') echo -n $sysname ]]> </script> <match>machine1</match> <match_type>exact</match_type> </custom1> <result> <profile>machine1.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> Without rules.xml (i.e. with the generic xml file alone) the installation works ok. With rules.xml (and thus with the machine specific machine1.xml) autoyast2 suddenly complains about wrong partition plans though there is no partition plan in the machine specific xml file. The partition plans are only in the generic xml file. Here's the machine specific xml file: <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <dns> <hostname>machine1</hostname> </dns> </networking> </configure> </profile> So the merge of the generic xml file and the machine specific xml file is somehow wrong. How can the result of the merge be checked? Where is the result of the merge stored? Regards, Stefan Voss

1 0

SLES8 (with SP3), /boot on /dev/md0 with grub
by Andreas Kurz 04 Feb '04

04 Feb '04

Hello all! I´m having some problems installing the grub-bootmanager on my boot-device (is a software-raid1). /boot is also missing in the /etc/fstab once the installation is complete but the raid1 is correctly configured and formated. Does someone know how I can get the 'chroot-scripts' working? I also found no way to prevent the reboot at the end of the installation .... very strange Here are some parts of my xml file: ...... <chroot-scripts config:type="list"> <script> <filename>/tmp/grub.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh mkinitrd -m "raid1 lvm-mod xfs" -d /dev/rootvg/rootlv -b /boot / cat << MENU > /boot/grub/menu.lst color white/blue black/light-gray default 0 timeout 10 title linux kernel (hd0,0)/vmlinuz root=/dev/rootvg/root_lv acpi=oldboot initrd (hd0,0)/initrd title failsafe kernel (hd0,0)/vmlinuz.shipped root=/dev/rootvg/root_lv ide=nodma apm=off acpi=off vga=normal nosmp noapic maxcpus=0 3 initrd (hd0,0)/initrd.shipped MENU cat << GRUB > /etc/grub.conf root (hd0,0) setup (hd0) root (hd1,0) setup (hd1) quit GRUB grub --batch < /etc/grub.conf exit 0 ]]> </source> </script> </chroot-scripts> ...... <install> <bootloader> <write_bootloader config:type="boolean">false</write_bootloader> </bootloader> .... <mode> <confirm config:type="boolean">false</confirm> <reboot config:type="boolean">false</reboot> <forceboot config:type="boolean">false</forceboot> <interactive_boot config:type="boolean">false</interactive_boot> </mode> Regards, Andreas Kurz -- Andreas Kurz | BearingPoint INFONOVA GmbH | Systems Engineer, Systemintegration | Seering 6, 8141 Unterpremstaetten/Graz, Austria Phone +43 316 8003 2933 | Fax +43 316 8003 1080 mailto:andreas.kurz@bearingpoint.com | www.bearingpoint.com | www.infonova.com --- BearingPoint INFONOVA GmbH is a subsidiary of BearingPoint GmbH, Frankfurt (formerly KPMG Consulting AG). The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.

1 0

Install program exit code is 134
by Wallace, Andrew 04 Feb '04

04 Feb '04

Hi, I'm trying to get autoyast working on suse-8.2, using DHCP/PXELinux/NFS, and I'm having problems. The PXE boot works OK, the NFS mount works, I assume the autoinst.xml is valid as I wrote it using Yast2... Following the progress on tty3, I see it loading up a load of modules, then it gets this far (see below) and stops. OK, going to mount 192.168.0.1:/builds/suse... NFS mount ok Setting up localhost...done going for automatic install mount: /var/adm/mount/boot/root: we need a loop device mount: using /dev/loop0 rmmod usb-storage starting /mounts/instsys/sbin/inst_setup yast [pauses for a minute or 2] install program exit code is 134 sync...ok That's it - installer dies, no idea why. Anyone here know? Cheers, Andy Wallace

1 0

Cannot mount NFS repository automatically ?
by francois.blaes＠eu.effem.com 04 Feb '04

04 Feb '04

Hi all I am facing a fairly weird issue with autoyast and its NFS repository ... any help appreciated I use a custom boot CD, mostly based on the SLES8 one, just a few pre-configured isolinux options to specify the NFS repository location : autoyast=nfs://<ip address of the repository server>/<full path to directory holding the XML configuration files> install=nfs://<ip address of the repository server>/<full path to packages repository> At the prompt, I add the following ad-hoc parameters : hostip=<ip address of the server to be installed> netmask=<netmask of the server to be installed> gateway=<gateway of the server to be installed> The boot process goes well, and linuxrc starts, but fails after a few seconds with "an error occured while trying to mount the nfs directory : reason given by server unknown error -1" I retried multiple times using the manual install mode, but unsuccesssfully However, when I switch to the console with Alt F9, I can ping the NFS server I can even **manually** mount anything from the NFS server using mount -t nfs /<ip address of the repository server>/<full path> /mnt which assumingly proves that all network and NFS server settings are correct ? On other hosts, the same install runs smoothly without any problem So it can't be a question of permission, can it ? How can linuxrc not succeed to mount the NFS volume whilst I can ? What would linuxrc use as mount point to mount the NFS volumes passed as parameters ? Francois BLAES ? Global Unix Team ? Mars ISI DDI *170 1639 ? Tel +33 (0) 3 88 05 16 39 ? Fax +33 (0) 3 88 05 16 79

1 0

rules.xml example using custom rules?
by Voss Stefan 04 Feb '04

04 Feb '04

Hi, has anybody an examples rules.xml that uses custom1-5 rules? We want to determine the machine specific configuration (hostname, IP address settings) via rules. According to rules.dtd such a rule could look like this <rule> <custom1> <script>/path/to/some/script.sh</script> <match>machine1</match> <match_type>equal</match_type> </custom> <result> <profile>machine1.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> Is it correct that <script> contains a script path or does it contain the script body like the following? <rule> <custom1> <script> <![CDATA[ #!/bin/sh # Try to determine value of boot parameter $machine=$(cat /proc/cmdline | grep "name=") echo $machine ]]> </script> <match>machine1</match> <match_type>equal</match_type> </custom> <result> <profile>machine1.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> Regards, Stefan Voss

1 0

WG: [suse-autoinstall] Problems customizing an install CD
by Lenz, Fabian 04 Feb '04

04 Feb '04

Your first problem: on the first cd, in the directory /boot/loader/ is the isolinux.cfg (SuSE 9.0). default linux # hard disk label harddisk kernel linux append SLX=0x202 showopts # install label linux kernel linux append initrd=initrd ramdisk_size=65536 splash=silent showopts acpi=off <----------- add this! Your third problem: in /suse/setup/descr/ is the file packages! =Ver: 2.0 ##---------------------------------------- =Pkg: 3ddiag 0.703 159 i586 +Req: /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 /bin/sh ld-linux.so.2 libc.so.6 libc.so.6(GLIBC_2.0) libhd.so.7 rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Req: +Prq: /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Prq: +Prv: 3ddiag = 0.703-159 -Prv: =Grp: System/Base =Lic: GPL =Src: 3ddiag 0.703 159 src =Tim: 1064411185 =Loc: 1 3ddiag-0.703-159.i586.rpm <---------------------- Loc: 1 means the package is on CD 1! =Siz: 27266 50861 change all Loc : X to Loc: 1 if you have all +Aut: packages on one cd! Stefan Dirsch <sndirsch(a)suse.de> -Aut: ##---------------------------------------- =Pkg: BASS 20030801 50 i586 +Req: scummvm timidity ... ... ... ... -----Ursprüngliche Nachricht----- Von: steven.cardinal(a)adheris.com [mailto:steven.cardinal@adheris.com] Gesendet: Donnerstag, 29. Januar 2004 16:10 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] Problems customizing an install CD I'm new to both SuSE and Autoyast. I've read through the autoinstall docs on the Suse site and find that I don't seem to know enough about autoyast in the first place to figure out what they are telling me. Here's what I've done and the problems I am having: I created a directory /SUSE9 and copied (cp -a /mnt/* /SUSE9/) all 5 CDs into this directory. I setup Yast to use this as a repository (I already used Yast update to patch this machine, so my yast utilities should be the latest available). I found that, using the GUI to select my source directory, if it appends a trailing / to the path (/SUSE9/) - it is not seen as a valid source. Finally figured that out and got autoyast to see the directory as well. I created a config for a server I am building. I used the Minimal+X11 selection plus added dhcp and bind. I setup some user accounts, etc. Everything seemed fine (the disks on this compaq dl360 show as /dev/ida/c0d0 so I had to hand-edit my config file afterwards). I then chose to build an ISO based on this config. It said it found all the necessary files and created an iso file, which I burned to media. First problem I had was that the compaq seems to have acpi issues, so I had to boot the cd with "linux acpi=off". Is there a way to configure autoyast to add those parameters by default? This CD will be used to rebuild the system should it die for some reason (hard drive crash or something) - it would be easier to hand off to my support people if they had very few ways of generating problems ;-) Second, I had an error installing grub (in the config file I told it to use the MBR and to replace what is there) The error was 'File not found'. I chose to reconfigure and retry and it worked ok - not sure if this is a problem with this particular machine or in my config. Any ideas? Next, it rebooted and went to install packages, but it suddenly couldn't find most of my packages and started prompting me for CD2. Shouldn't the 'Create ISO' setup the necessary paths in the iso image so that it works? Is there something I have to configure elsewhere? Once I get past this I'll hack away at adding extra packages (samba3, etc). I haven't had any luck getting autoyast to recognize my custom .sel file (it can't open any of my CD-provided .sel files either, so I don't understand how it works) Also, autoupdate pulls down patch.rpm files. Is there a way to apply these to my source directory so that my final build cd is patched already? Thanks Steve Oh, is there any plan to make the mailing list archives searchable? -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

typos in autoinstall FAQ
by Hal Wine 03 Feb '04

03 Feb '04

Anas, Thanks for the FAQ -- it's helping me move forward on SLES installation server setup... There are some typos in the example code for 2.5 (HTTP loopback mount of ISO images): printf "/SP3\t/SP3" > yast/order printf "/SLES\t/SLES" > yast/order printf "/UL/CD1\t/UL/CD1" >> yast/order printf "/unitedlinux-i386/CD1\t/unitedlinux-i386/CD1" > yast/instorder printf "/sles8-i386/CD1\t/sles8-i386/CD1" >> yast/instorder printf "/SP3\t/SP3" > yast/instorder first, there is a missing '>' in the second and the last line. second, either the command needs be changed to 'echo -e', or '\n' needs to be added to the end of the strings. third, I'm not sure that the sets of data match. This is the only place I've seen different naming conventions used in the same pair of order/instorder files. The 'order' file refers to '/SLES', and the 'instorder' file refers to '/sles8-i386/CD1' finally, I _think_ to match the directory structure earlier in the example, the correct refernce to SP3 should be '/SP3/CD1' I'm not sure about the last two, as even with with (and without) those changes, I still can't get sles8 sp3 to install via HTTP. --Hal

1 1

Re: [suse-autoinstall] example for sles8 + sp3 install server setup?
by Joachim Jordan 02 Feb '04

02 Feb '04

Hi everyone, it works for me to it that way. I added the SP3 just as another source to the installation tree. Here is my script i'm using to setup the distribution: ------------------------------------------------------- #!/bin/sh # Script to setup SLES netinstall source if [ $# -lt 1 ] then echo "Please provide the path of the new driver as parameter!" exit 1 fi cd $1 # check if in correct directory! if [ ! -f suse/CD1/content ] then echo "Error: Looks like wrong directory!" exit 1 fi # remove previous configurations if [ -d yast ] then rm -r yast fi if [ -d boot ] then rm -r boot fi if [ -d media.1 ] then rm -r media.1 fi if [ -f content ] then rm content fi if [ -f driverupdate ] then rm driverupdate fi # Now we have to move some data around to make this # a multiple source directory # # first we copy the order directory described above. mkdir yast cp suse/CD1/content yast/ cp suse/CD1/content . # Then the boot directory with the installation image cp -a suse/CD1/boot . # The content file and the media directory cp -a suse/CD1/media.1 . if [ -f media.1/info.txt ] then rm media.1/info.txt fi # Now we copy the description files from SLES to the order directory as # described earlier. mkdir -p yast/suse/suse/setup/descr cp -a suse/CD1/suse/setup/descr yast/suse/suse/setup cp suse/CD1/content yast/suse/ cp -a suse/CD1/media.1 yast/suse/ cp -a suse/CD2/media.2 yast/suse/ cp -a suse/CD3/media.3 yast/suse/ # Same applies for supplementary mkdir -p yast/sup/suse/setup/descr cp -a supplementary/CD1/suse/setup/descr yast/sup/suse/setup cp supplementary/CD1/content yast/sup/ cp -a supplementary/CD1/media.1 yast/sup/ cp -a supplementary/CD2/media.2 yast/sup/ # Do the same for Service Pack 3 mkdir -p yast/sp3/suse/setup/descr cp -LRp sp3/CD1/suse/setup/descr yast/sp3/suse/setup cp sp3/CD1/content yast/sp3/ cp -a sp3/CD1/media.1 yast/sp3/ cp -a sp3/CD2/media.2 yast/sp3/ # overwrite the old file in the boot directory with new ones cp -a sp3/CD1/boot . # copy driverupdate file cp sp3/CD1/driverupdate . # Do the same for Addons mkdir -p yast/ad/addons/setup/descr cp -a Addons/addons/setup/descr yast/ad/addons/setup cp Addons/content yast/ad/ cp -a Addons/media.1 yast/ad/ # We are almost done.. # Now we'll adapt the order files. # Fields of the order files are TAB delimited cat << EOF > yast/order /yast/ad Addons /yast/sp3 sp3/CD1 /yast/suse suse/CD1 /yast/sup supplementary/CD1 EOF cat << EOF > yast/instorder /yast/sup /yast/suse /yast/sp3 /yast/ad EOF # final stuff #cp ../Code/root/root.neu boot/root chown -R wwwrun:nogroup . # End ------------------------------------------------------------------- I even added another source for my own packages. For that i reused the content and media.1 files from the SLES distribution and changed them. I'm using HTTP as installation protocol and this is for an Power PC based installation for JS20 blades. But it is more or less the same for Intel. Just one thing about the SP3, to get all the Yast fixes included in the installation process( for example necessary for HTTP support, HTTP is broken in the SLES8 and fixed with the code in the SP3), you have to copy the driverupdate file to the root of your new multi source distribution(or if you use NFS, you can also copy the subdirectory containing all from the CD to the root). For me, the driverupdate file does not work. If i use it, yast dies in the middle of the installation with an segfault. If i copy all files from the driverupdate file into the root file manually, it works. Best regards, Joachim Jordan Linux IT Architect, EMEA Linux Center of Competence IBM Laboratories, Dept.3300, Schoenaicherstr.220, D 71032 Boeblingen, Germany Sametime/e-mail: jordanj(a)de.ibm.com, Phone: +49-7031-16-4407; Fax: +49-7031-16-3232 Hal Wine <hal(a)reactivity.c To: suse-autoinstall(a)suse.com om> cc: Subject: [suse-autoinstall] example for sles8 + sp3 install server setup? 13.01.2004 18:32 Can anyone point me to an example install server layout for autoyast installations of sles 8 + service pack 3? I followed Anas' example laytout for my original installation server setup. I'ts unclear to me if I should: 1) replace the sles8 cd content with the content from sp3 cd's, or 2) add sp3 content as another source. If #2, I think I would place it at the end of the order file, and the beginning of the instorder. Is that correct? Finally, what do folks typically do to handle maintenance updates? I.e. where do they place the RPMs. Thanks, --Hal -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 2

Install Problem
by Ryan Simmons 02 Feb '04

02 Feb '04

I have SuSE Linux 8.2 Professional that I have installed before on this computer. However, I was redoing my harddrive and repartioning it more to my liking, so I wiped it clean and began to reinstall various OS's on my comp. When I boot up from the SuSE CD OR DVD I can only get as far as selecting which install to do. Such as Installation, Installation-Safe Settings, Installation- ACPI Enabled, Manual Installation, etc., etc. After I select which one(I've tried each one) all I get is a blue line on the left of my screen and a mashed up, mostly grayish lines at the top of my screen. If I start hitting enter or other buttons, I can see the gray lines switch around like it is going through options, it's just not displayed where a human can tell what is going on. I have not changed my display card or drivers or anything really, exept upgrading my RAM a little. But the memory test says that all my RAM is fine. Since I have installed this before on my computer without this problem, I've been trying to figure out what is different now than before. But I can't think of anything. Has anyone had this problem? Or any ideas on what's wrong? Ryan Dell Dimension 8200 Pentium 4 2.4GHz 1 GB RDRAM 128MB NVIDIA GeForce4 Ti 4600 Tv out _________________________________________________________________ Let the new MSN Premium Internet Software make the most of your high-speed experience. http://join.msn.com/?pgmarket=en-us&page=byoa/prem&ST=1

2 1

Next Bug with autoyast and SP3?
by Hans Kamm 01 Feb '04

01 Feb '04

Hi, how many bugs have autoyast? over 100?. Situation. Booting from SP3-CD with control-file and install-files on nfs. lilo wouldn't install (I' see noting interesting in the log. I think the new kernel is missing.) With SP 2a-CD it works! Hans _________________________________________________________________ Schützen Sie Ihren Posteingang vor unerwünschten E-Mails. http://www.msn.de/antispam/prevention/junkmailfilter Jetzt Hotmail-Junk-Filter aktivieren!

1 0