September 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] PXE install fails with SCSI disks
by Anas Nashif 23 Sep '04

23 Sep '04

Steve, I asked you for more information but I got no answer to the questions below. Could you provide some more information about where it hangs? Anas Anas Nashif wrote: > This is indeed strange. Where does the installation exactly stop. In > YaST? In linuxrc? If in YaST, can you send me the log files from > /var/log/YaST2/ > > There should be no difference when installaing over network, same files > are used so I do not see why this is failing. > > Anas > > Steve Glines wrote: > >> suse.root is the initrd file talen from boot/loader on CD1. >> >> SG >> >> Anas Nashif wrote: >> >> >>> >>> Steve Glines wrote: >>> >>> >>>> I’m building a PXE install lab for SUSE and other flavors of Linux. >>>> >>>> The DHCP and tftp servers are working. Note: I can fully install Red >>>> Hat >>>> from this lab but SUSE (SLES9 rc5) shows the following symptoms: >>>> >>>> 1. a cdrom install on the target system runs to completion in >>>> graphics >>>> mode. System is an HP PC with SCSI disk. >>>> 2. PXE install runs in non X-window mode (text) and fails to load >>>> scsi >>>> controllers – cannot find any disks. Fails even when modules are >>>> manually added. >>>> >>>> Here is the content of /tftpboot/pxelinux.cfg/default: >>>> >>>> default suse >>>> prompt 1 >>>> display boot.msg >>>> timeout 200 >>>> >>>> label redhat >>>> kernel redhat.kernel >>>> append initrd=redhat.root ramdisk_size=65536 >>>> >>>> label suse >>>> kernel suse.kernel >>>> append initrd=suse.root ramdisk_size=65536\ >>>> install=http://10.0.3.11/suse/CD1/ >>> >>> >>> >>> What is suse.root exactly? >>> >>> Btw, To get graphical installer, you need to add vga=791 or something >>> similar. >>> >>> Anas >>> >> >>

2 2

RE: [suse-autoinstall] What tools are available to help with remo te installs of headless machines.
by Connector Email 23 Sep '04

23 Sep '04

Ssh ;) -----Original Message----- From: Leendert Meyer [mailto:leen.meyer@home.nl] Sent: Thursday, September 23, 2004 1:49 PM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] What tools are available to help with remote installs of headless machines. On Thursday 23 September 2004 21:13, Colin Murphy wrote: > This is purely from the point of view of wanting to 'play' with some of the > machines I get given. All the machines will be different, different > hardware, different resources, different needs. > > I want to do remote installs, using vnc, on headless machines. I have tried > this feature out a little on machines that have keyboard and display using > local and network installation media and being able to control an install > from the comfort of my own desk was a great boon. I would now like to be > able to do installs on machines where I just plug in a power and network > cable and floppy of CD. > > What I really want is a way to start an installation with the further > option 'vnc=1 vncpassword=whatever' passed as the default install option, > using either a floppy or CD. > > Are there any tools to help me build such boot installation media? Install the package 'autoyast2'. Docs are in /usr/share/docs/packages/autoyast2 Run YaST from 'yast autoyast'. Here's a (partial but working) GRUB menu.lst that I used to install SuSE Linux 9.1: #dhcp bootp gfxmenu (nd)/9.1/message color white/blue black/light-gray default 2 timeout 8 title Installation - Automatic with SSH kernel (nd)/9.1/linux insmod=tulip UseSSH=1 SSHPassword=123 autoyast=http://10.0.0.1/pub/suse/profiles/ install=http://10.0.0.1/pub/suse/i386/9.1 vga=0x31A splash=silent showopts initrd (nd)/9.1/initrd (Kmail wrapped the long line starting with 'kernel (nd)/... into 3 lines). You need to install tftpboot on the server, copy boot/loader/{linux,initrd} to tftpboot/9.1/. Boot the client via GRUB with previous menu.lst or with a GRUB boot floppy with prior menu.lst on it. See http://www.suse.de/~nashif/autoinstall/ for a GRUB bootfloppy and instructions. BTW, installing remotely can be a tricky task if the boot process fails. Unless there is someone on the other side in case of boot failure, or you have physical access to the 'remote' client, you're pretty much lost in such a case (I was). Cheers, Leen -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

What tools are available to help with remote installs of headless machines.
by Colin Murphy 23 Sep '04

23 Sep '04

This is purely from the point of view of wanting to 'play' with some of the machines I get given. All the machines will be different, different hardware, different resources, different needs. I want to do remote installs, using vnc, on headless machines. I have tried this feature out a little on machines that have keyboard and display using local and network installation media and being able to control an install from the comfort of my own desk was a great boon. I would now like to be able to do installs on machines where I just plug in a power and network cable and floppy of CD. What I really want is a way to start an installation with the further option 'vnc=1 vncpassword=whatever' passed as the default install option, using either a floppy or CD. Are there any tools to help me build such boot installation media? Thanks on advance. -- Colin Murphy - A man for all seasons but I especially like pepper.

2 1

Installation Server and CD Creation
by Morten K. Poulsen 23 Sep '04

23 Sep '04

Hi list, I am not sure this is the list to rant about the "Installation Server" YaST module, but here goes: I have installed SLES 9 (RC5 - I was told that it was the GM) on a host and want to make a CD for auto-installation. I did that with SLES 8 and it was a mess because of "multiple installation sources." With SLES 8 i ended up dropping SLES and just using UnitedLinux plus my own packages. OK, now on to the problems I have with SLES 9. a) I have tried different combinations of packages (CDs) in a single or different repositories. You can see the directory listings at the bottom of this mail (appendix A). 1) Both SLES and CORE - one package repository First I tried making one (Installation Server -> Change -> Add -> Source Name: "all9" -> [X] Use ISO Images Instead of CDs -> select each of the six ISOs) with both SLES 9 and CORE 9. I am able to select this in Software Source Media (it identifies itself as "SUSE SLES Version 9"), but I am unable to install any packages from it. Only the installed packaged are shown in Install and Remove Software. 2) Only SLES Then I tried making a repository with only the SLES CD (#1). I used the same procedure as above, but called it "sles9" and only selected the first ISO. When I select it in Software Source Media (it also identifies itself as "SUSE SLES Version 9"), I get the exact same result as before: No installable packages. 3) Only CORE Then I tried making a repository with only the CORE CDs (#2-6). I used the same procedure again, and called it "core9". When I select it in Software Source Media (it identifies itself as "SUSE CORE Version 9"), I am able to install packages from it. But - obviously - I can only install the CORE packages. 4) Both SLES and CORE - two different package repositories If I select both the package repository that I named "sles9" and the one I named "core9", I am still able to install the CORE packages, but still not the SLES packages. The result is the same, no matter which is first in the Software Source Media list. b) When I use the CD Creator YaST module, I get an "Error while writing settings" at "Saving CD Creator Configuration," no files are copied to the selected directory and no ISO file is created. This is the same, no matter if I select Packages by "Package Manager" or "AutoYaST Control File," and no matter if I select CORE, SLES or both as package source. I have tried to locate online documentation about this, but so far I haven't found any. Am I looking in the wrong places? I hope someone can help, or tell me where to go looking for help about this, as I would like to get started with using SLES 9 in our production environment. Best regards, Morten Appendix (I guess this mail is getting long) A) 1) mopo@flimmer-new:~> find all9/ -type d all9/ all9/yast all9/SUSE-CORE-Version-9 all9/SUSE-CORE-Version-9/CD1 all9/SUSE-CORE-Version-9/CD1/suse all9/SUSE-CORE-Version-9/CD1/suse/i586 all9/SUSE-CORE-Version-9/CD1/suse/i686 all9/SUSE-CORE-Version-9/CD1/suse/setup all9/SUSE-CORE-Version-9/CD1/suse/setup/descr all9/SUSE-CORE-Version-9/CD1/suse/noarch all9/SUSE-CORE-Version-9/CD1/media.1 all9/SUSE-CORE-Version-9/CD2 all9/SUSE-CORE-Version-9/CD2/suse all9/SUSE-CORE-Version-9/CD2/suse/i586 all9/SUSE-CORE-Version-9/CD2/suse/i686 all9/SUSE-CORE-Version-9/CD2/suse/noarch all9/SUSE-CORE-Version-9/CD2/media.2 all9/SUSE-CORE-Version-9/CD3 all9/SUSE-CORE-Version-9/CD3/suse all9/SUSE-CORE-Version-9/CD3/suse/src all9/SUSE-CORE-Version-9/CD3/suse/i586 all9/SUSE-CORE-Version-9/CD3/suse/i686 all9/SUSE-CORE-Version-9/CD3/suse/noarch all9/SUSE-CORE-Version-9/CD3/media.3 all9/SUSE-CORE-Version-9/CD4 all9/SUSE-CORE-Version-9/CD4/suse all9/SUSE-CORE-Version-9/CD4/suse/src all9/SUSE-CORE-Version-9/CD4/suse/nosrc all9/SUSE-CORE-Version-9/CD4/media.4 all9/SUSE-CORE-Version-9/CD5 all9/SUSE-CORE-Version-9/CD5/suse all9/SUSE-CORE-Version-9/CD5/suse/src all9/SUSE-CORE-Version-9/CD5/suse/nosrc all9/SUSE-CORE-Version-9/CD5/media.5 all9/SUSE-SLES-Version-9 all9/SUSE-SLES-Version-9/CD1 all9/SUSE-SLES-Version-9/CD1/boot all9/SUSE-SLES-Version-9/CD1/boot/loader all9/SUSE-SLES-Version-9/CD1/docu all9/SUSE-SLES-Version-9/CD1/docu/de all9/SUSE-SLES-Version-9/CD1/docu/en all9/SUSE-SLES-Version-9/CD1/docu/es all9/SUSE-SLES-Version-9/CD1/docu/fr all9/SUSE-SLES-Version-9/CD1/docu/ja all9/SUSE-SLES-Version-9/CD1/docu/it all9/SUSE-SLES-Version-9/CD1/docu/ko all9/SUSE-SLES-Version-9/CD1/docu/HOWTOs all9/SUSE-SLES-Version-9/CD1/docu/pt_BR all9/SUSE-SLES-Version-9/CD1/docu/zh_CN all9/SUSE-SLES-Version-9/CD1/suse all9/SUSE-SLES-Version-9/CD1/suse/src all9/SUSE-SLES-Version-9/CD1/suse/i586 all9/SUSE-SLES-Version-9/CD1/suse/nosrc all9/SUSE-SLES-Version-9/CD1/suse/setup all9/SUSE-SLES-Version-9/CD1/suse/setup/descr all9/SUSE-SLES-Version-9/CD1/suse/noarch all9/SUSE-SLES-Version-9/CD1/yast all9/SUSE-SLES-Version-9/CD1/yast/core9 all9/SUSE-SLES-Version-9/CD1/yast/core9/suse all9/SUSE-SLES-Version-9/CD1/yast/core9/suse/setup all9/SUSE-SLES-Version-9/CD1/yast/core9/suse/setup/descr all9/SUSE-SLES-Version-9/CD1/yast/core9/media.1 all9/SUSE-SLES-Version-9/CD1/dosutils all9/SUSE-SLES-Version-9/CD1/dosutils/lfn all9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool all9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/src all9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/sys all9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/linux all9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/ext2fs all9/SUSE-SLES-Version-9/CD1/dosutils/fips all9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips15 all9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips15/restorrb all9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips15/source all9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips20 all9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips20/restorrb all9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips20/source all9/SUSE-SLES-Version-9/CD1/dosutils/gzip all9/SUSE-SLES-Version-9/CD1/dosutils/rawrite all9/SUSE-SLES-Version-9/CD1/dosutils/putty all9/SUSE-SLES-Version-9/CD1/dosutils/untgz all9/SUSE-SLES-Version-9/CD1/dosutils/loadlin all9/SUSE-SLES-Version-9/CD1/dosutils/loadlin/doc all9/SUSE-SLES-Version-9/CD1/dosutils/loadlin/src all9/SUSE-SLES-Version-9/CD1/dosutils/dparam all9/SUSE-SLES-Version-9/CD1/dosutils/zipzp715 all9/SUSE-SLES-Version-9/CD1/dosutils/ltools all9/SUSE-SLES-Version-9/CD1/dosutils/gtar109 all9/SUSE-SLES-Version-9/CD1/dosutils/weirdx all9/SUSE-SLES-Version-9/CD1/dosutils/weirdx/config all9/SUSE-SLES-Version-9/CD1/dosutils/xfs186 all9/SUSE-SLES-Version-9/CD1/dosutils/tightvnc all9/SUSE-SLES-Version-9/CD1/dosutils/xfs32-11 all9/SUSE-SLES-Version-9/CD1/dosutils/pkunzip all9/SUSE-SLES-Version-9/CD1/dosutils/rawwritewin all9/SUSE-SLES-Version-9/CD1/dosutils/install all9/SUSE-SLES-Version-9/CD1/media.1 all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/de all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/cz all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/es all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/fr all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/it all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/nl all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/pl all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/en_US all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/pt_BR mopo@flimmer-new:~> ls -l all9/ |cut -b 24- 28 2004-09-20 13:08 boot -> SUSE-SLES-Version-9/CD1/boot 31 2004-09-20 13:08 content -> SUSE-SLES-Version-9/CD1/content 35 2004-09-20 13:08 control.xml -> SUSE-SLES-Version-9/CD1/control.xml 31 2004-09-20 13:08 media.1 -> SUSE-SLES-Version-9/CD1/media.1 168 2004-09-20 13:19 SUSE-CORE-Version-9 72 2004-09-20 13:08 SUSE-SLES-Version-9 104 2004-09-20 13:23 yast 2) mopo@flimmer-new:~> find sles9/ -type d sles9/ sles9/yast sles9/SUSE-SLES-Version-9 sles9/SUSE-SLES-Version-9/CD1 sles9/SUSE-SLES-Version-9/CD1/boot sles9/SUSE-SLES-Version-9/CD1/boot/loader sles9/SUSE-SLES-Version-9/CD1/docu sles9/SUSE-SLES-Version-9/CD1/docu/de sles9/SUSE-SLES-Version-9/CD1/docu/en sles9/SUSE-SLES-Version-9/CD1/docu/es sles9/SUSE-SLES-Version-9/CD1/docu/fr sles9/SUSE-SLES-Version-9/CD1/docu/ja sles9/SUSE-SLES-Version-9/CD1/docu/it sles9/SUSE-SLES-Version-9/CD1/docu/ko sles9/SUSE-SLES-Version-9/CD1/docu/HOWTOs sles9/SUSE-SLES-Version-9/CD1/docu/pt_BR sles9/SUSE-SLES-Version-9/CD1/docu/zh_CN sles9/SUSE-SLES-Version-9/CD1/suse sles9/SUSE-SLES-Version-9/CD1/suse/src sles9/SUSE-SLES-Version-9/CD1/suse/i586 sles9/SUSE-SLES-Version-9/CD1/suse/nosrc sles9/SUSE-SLES-Version-9/CD1/suse/setup sles9/SUSE-SLES-Version-9/CD1/suse/setup/descr sles9/SUSE-SLES-Version-9/CD1/suse/noarch sles9/SUSE-SLES-Version-9/CD1/yast sles9/SUSE-SLES-Version-9/CD1/yast/core9 sles9/SUSE-SLES-Version-9/CD1/yast/core9/suse sles9/SUSE-SLES-Version-9/CD1/yast/core9/suse/setup sles9/SUSE-SLES-Version-9/CD1/yast/core9/suse/setup/descr sles9/SUSE-SLES-Version-9/CD1/yast/core9/media.1 sles9/SUSE-SLES-Version-9/CD1/dosutils sles9/SUSE-SLES-Version-9/CD1/dosutils/lfn sles9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool sles9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/src sles9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/sys sles9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/linux sles9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/ext2fs sles9/SUSE-SLES-Version-9/CD1/dosutils/fips sles9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips15 sles9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips15/restorrb sles9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips15/source sles9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips20 sles9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips20/restorrb sles9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips20/source sles9/SUSE-SLES-Version-9/CD1/dosutils/gzip sles9/SUSE-SLES-Version-9/CD1/dosutils/rawrite sles9/SUSE-SLES-Version-9/CD1/dosutils/putty sles9/SUSE-SLES-Version-9/CD1/dosutils/untgz sles9/SUSE-SLES-Version-9/CD1/dosutils/loadlin sles9/SUSE-SLES-Version-9/CD1/dosutils/loadlin/doc sles9/SUSE-SLES-Version-9/CD1/dosutils/loadlin/src sles9/SUSE-SLES-Version-9/CD1/dosutils/dparam sles9/SUSE-SLES-Version-9/CD1/dosutils/zipzp715 sles9/SUSE-SLES-Version-9/CD1/dosutils/ltools sles9/SUSE-SLES-Version-9/CD1/dosutils/gtar109 sles9/SUSE-SLES-Version-9/CD1/dosutils/weirdx sles9/SUSE-SLES-Version-9/CD1/dosutils/weirdx/config sles9/SUSE-SLES-Version-9/CD1/dosutils/xfs186 sles9/SUSE-SLES-Version-9/CD1/dosutils/tightvnc sles9/SUSE-SLES-Version-9/CD1/dosutils/xfs32-11 sles9/SUSE-SLES-Version-9/CD1/dosutils/pkunzip sles9/SUSE-SLES-Version-9/CD1/dosutils/rawwritewin sles9/SUSE-SLES-Version-9/CD1/dosutils/install sles9/SUSE-SLES-Version-9/CD1/media.1 sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/de sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/cz sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/es sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/fr sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/it sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/nl sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/pl sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/en_US sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/pt_BR mopo@flimmer-new:~> ls -l sles9/ |cut -b 24- 28 2004-09-20 13:34 boot -> SUSE-SLES-Version-9/CD1/boot 31 2004-09-20 13:34 content -> SUSE-SLES-Version-9/CD1/content 35 2004-09-20 13:34 control.xml -> SUSE-SLES-Version-9/CD1/control.xml 31 2004-09-20 13:34 media.1 -> SUSE-SLES-Version-9/CD1/media.1 72 2004-09-20 13:34 SUSE-SLES-Version-9 48 2004-09-20 13:34 yast 3) mopo@flimmer-new:~> find core9/ -type d core9/ core9/suse core9/suse/src core9/suse/i586 core9/suse/i686 core9/suse/nosrc core9/suse/setup core9/suse/setup/descr core9/suse/noarch core9/media.1 core9/media.2 core9/media.3 core9/media.4 core9/media.5 mopo@flimmer-new:~> ls -l core9/ |cut -b 24- 3906522 2004-07-02 20:19 ARCHIVES.gz 3734181 2004-07-02 20:17 ChangeLog 604 2004-07-02 20:15 content 31 2004-07-02 20:18 directory.yast 23022 2004-07-02 20:21 INDEX.gz 42719 2004-07-02 20:19 ls-lR.gz 128 2004-07-02 20:18 media.1 96 2004-07-02 20:19 media.2 96 2004-07-02 20:19 media.3 96 2004-07-02 20:19 media.4 96 2004-07-02 20:19 media.5 192 2004-07-02 20:15 suse -- Morten K. Poulsen <lists.suse.com(a)afdelingp.dk> http://www.afdelingp.dk/

2 2

Re: Re: [suse-autoinstall] Controlfile + Rules doesn't work
by Kai Moeller 23 Sep '04

23 Sep '04

Hi there, Here a supplement to my privious Mail in the morning: I'm sure that the MAC Address of my Ethernet Adapter is the right on and It is only 1 Ethernet Adapter in this Machine! But it didn't work anymore :( Is it possible do define a default rule/profile for a machine where no rules defined? Another question (presupposed the rules.xml is running soon :-) Howto do a based config combined with a Machine cut preconfig for every machine with another hardware and another Hostnames and so on... I'm sorry, but theres not enough documentation about the rules and classes, the section is very short. best regards Kai Möller

1 0

SLES8: No reboot after autoyast
by Oliver Schwabedissen 23 Sep '04

23 Sep '04

Hi, I'm also having a reboot problem, this one is with SLES8. Up to now all installations went fine: after autoyast completes the system does a reboot and executes my own startup scripts in rc3.d to finish the installation. Yesterday I installed a similar machine (HP DL380 G3, other machines were IBM x235, x360 and HP ML370/570), but after autoyast finished the server didn't reboot but entered runlevel 5. This is due to a bug in autoyast. We specify runlevel 3 in autoyast.xml and then configure X11, but this sets the runlevel to 5 in /etc/inittab. So as a workaround (suggested by SuSE support) we added the "3" as a kernel parameter for the bootloader to force the machine to runlevel 3 (and then execute the startup script). All the other machines did a reboot after autoyast installation finished, this one doesn't... What can be the reason? Only differences between installations are in network configuration (ip address, nic modules etc.) and partitioning (1 or 2 RAIDs). All machines are configured with forceboot=false and reboot=false in the general section. AFAIK the reboot parameter is only for a reboot before the first initial reboot takes place (and doesn't work at all) and forceboot is documented nowhere... Oliver -- +++ GMX DSL Premiumtarife 3 Monate gratis* + WLAN-Router 0,- EUR* +++ Clevere DSL-Nutzer wechseln jetzt zu GMX: http://www.gmx.net/de/go/dsl

2 6

Antwort: Re: [suse-autoinstall] Controlfile + Rules doesn't work
by Kai Moeller 23 Sep '04

23 Sep '04

>Hi, > >In the rules you have to use lower case mac address. > >Anas Hi, in your documentatin you wrote in an example to use it uppercase! (ie. rules and classes > system attributes) But I've tried it upper and lowercase but it still doesn't work! Same failure... same message to me... I should enter the full path to my profile! Greetings Kai Moeller

1 0

Controlfile + Rules doesn't work
by Kai Moeller 23 Sep '04

23 Sep '04

Hi there, after working without any rules or templates, I would create some rules to merge my autoyast profile for different workstations. My Profile directory is: '/pub/suse/9.1/autoyast/' ... I starts the autoyast routine on the commandline without a speficy profile (Autoyast=nfs://10.xxx.xxx.62/pub/suse/9.1/autoyast/) my rules.xml is in '/pub/suse/9.1/autoyast/rules/rules.xml' and contains following lines: <CTYPE 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> <mac> <match>00B0D0E25C86</match> <match_type>exact</match_type> </mac> <result> <profile>km2.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> the needed profile is in '/pub/suse/9.1/autoyast/' and is should be accessable to any user! Before AutoYast starts parsing my Controlfile, it receive the rules.xml and want to receive my controlfile to merge it. There's my problem, at this stage autoyast tells me, it couldn't find my profile and i should enter the fullpath to the controlfile. But I'm sure, the controlfile is in '/pub/suse/9.1/autoyast/' with filename "km2.xml" if I symlink my HexIP to my controlfile it works fine! Any Solutions? Best regards Kai Moeller

2 1

sles9 and autoyast boot disks
by Brad Hudson 23 Sep '04

23 Sep '04

does anyone have any step through procedures on creating a boot disk & info file on a floppy in order to perform an autoyast installation via an nfs server (install=nfs://<server>/sles9 autoyast=nfs://<server>/sles9/profiles/<profile>)? i have not found this info in the autoyast.pdf or the html docs. i have a need to perform repetitive manufacturing of a standard config. any info would be of value. bh

2 1

SLES9 hangs at Creating initrd
by Aaron McSorley 23 Sep '04

23 Sep '04

SLES9 AMD64 manual network PXE install hangs at "Finishing Basic Installation" => "Install boot manager" -> "Creating initrd ..." Does this ring any bells? If not let me know and I'll provide more information. This is short because I'm out of time Thanks -Aaron

2 1