openSUSE Autoinstall February 2006

autoinstall@lists.opensuse.org

37 participants
52 discussions

Scripting dirinstall?
by Teun 25 Feb '07

25 Feb '07

Does anyone know if it is possible to use the 'dirinstall' from the command line? For instance i would like to be able to do something like: # yast dirinstall -d /someroot -s mypackages.sel If i do yast -h it says: "Usage: /sbin/yast [OPTIONS] [MODULE] [module specific parameters]" But is there a way to find out what 'module specific parameters' are available for a specific module? Thanks, Teun

3 2

Problem with AutoInstallRules.ycp and merge.xslt
by Luzian Scherrer 16 Mar '06

16 Mar '06

Hello, I think there is a typo in AutoInstallRules.ycp (version 1.34.4.9 that comes with SLES9 SP2): the xsltproc to merge classes is called with the following param there (line 733): --param dontmerge \"'package, addon'\" and I'm quite sure that it sould be: --param dontmerge \"'package'\" --param dontmerge2 \"'addon'\" The result of this typo is that neither <package> nor <addon> are correctly aggregated, which is the desired effect I believe and I also hope. Quick demonstration: idhpb02:/ # cat /tmp/a.xml <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http:// www.suse.com/1.0/configns"> <install> <software> <addons config:type="list"> <addon>addon-A</addon> </addons> <packages config:type="list"> <package>package-A</package> </packages> </software> </install> </profile> idhpb02:/ # cat /tmp/b.xml <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http:// www.suse.com/1.0/configns"> <install> <software> <addons config:type="list"> <addon>addon-B</addon> </addons> <packages config:type="list"> <package>package-B</package> </packages> </software> </install> </profile> Calling it the wrong way: idhpb02:/ # xsltproc --novalid --param replace "'false'" --param dontmerge "'package, addon'" --param with "'/tmp/b.xml'" /usr/share/ autoinstall/xslt/merge.xslt /tmp/a.xml <?xml version="1.0"?> <ns1:profile xmlns:ns1="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns="http:// www.suse.com/1.0/yast2ns"> <ns1:install> <ns1:software> <ns1:addons config:type="list"> <ns1:addon>addon-B</ns1:addon> </ns1:addons> <ns1:packages config:type="list"> <ns1:package>package-B</ns1:package> </ns1:packages> </ns1:software> </ns1:install> </ns1:profile> Calling it the (as I think) right way: idhpb02:/ # xsltproc --novalid --param replace "'false'" --param dontmerge "'package'" --param dontmerge2 "'addon'" --param with "'/ tmp/b.xml'" /usr/share/autoinstall/xslt/merge.xslt /tmp/a.xml <?xml version="1.0"?> <ns1:profile xmlns:ns1="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns="http:// www.suse.com/1.0/yast2ns"> <ns1:install> <ns1:software> <ns1:addons config:type="list"> <ns1:addon>addon-A</ns1:addon><ns1:addon>addon-B</ns1:addon> </ns1:addons> <ns1:packages config:type="list"> <ns1:package>package-A</ns1:package><ns1:package>package-B</ ns1:package> </ns1:packages> </ns1:software> </ns1:install> </ns1:profile> Could this be fixed? Or is it already known and possibly a workaround in existance? Thanks in advance, -Luzian

4 6

Changing Kernel in pxe install
by Reeves, Matthew J. 01 Mar '06

01 Mar '06

Classification: UNCLASSIFIED I'm trying to set up a pxe environment to install SuSE 9.0 on some Dell Poweredge 1850s. The kernel that comes with 9.0 doesn't support the raid controllers. I want to change the installing kernel to 2.4.32 so that the raid works. I can get the systems booting and linuxrc runs but it asks for a module disk then goes into manual mode. In the manual mode I can kick off a ftp install but after root is downloaded the system just goes back to the linuxrc menu. Is there an easy way to change the kernel? Thanks, Matt

3 2

Standard software installation using autoyast.xml
by Trey Sizemore 28 Feb '06

28 Feb '06

I'm wondering if an autoyast.xml file could be used solely for designating software packages to be installed. In other words, for a minimal server install, I want the same packages installed on those servers regardless of the hardware present (one may be a Proliant server and another an Optiplex). But I *do* want packages X, Y, and Z installed on both. Is this possible? Partitioning wouldn't appear to work because the disk sizes might be different in the machines, but I want to update the process a much as possible. -- Cheers, Trey ---- Help fight continental drift. Linux chameleon 2.6.13-15-default i686 GNU/Linux 12:30pm up 4 days 18:39, 7 users, load average: 0.02, 0.35, 0.45

2 1

SuSE 10.0 yast2 Autoinstall Modul
by Folkhard Mueller 28 Feb '06

28 Feb '06

Dear Listmembers, Has anybody out there used the builtin autoinstall tool in yast2 SuSE Professional Vers. 10.0, unpatched, and created some useful operable control Files with it? I did it under Suse Version 9.1 successfully (after some hacking), but under Suse 10.0 all xmls created are garbage more or less! Especially for Package Selection nothing works really! Any comments are welcome! Beste Regards F.Mueller -- |\ _,,,---,,_ ZZZzz /,`.-'`' -. ;-;;,_ _______|,4- ) )-,_. ,\ (____-'_________________________________________ '---''(_/--' `-'\_) Dipl. Phys. F.Mueller EPCOS AG Surface Acoustic Wave Components Division SAW RD CAD P.O. Box 80 17 09 Phone: ++49 89 636 23316 D-81617 Munich Fax: ++49 89 636 27304 Germany mailto: Folkhard.Mueller(a)epcos.com Web: http://www.epcos.com

2 1

AW: [suse-autoinstall] SuSE 10.0 yast2 Autoinstall Modul
by KOEHLER, SVEN - PFHO 28 Feb '06

28 Feb '06

hi folkhard, > [...]and created some useful operable control Files with it? i did so. at least during my first tries. i had to edit the control file as there were some inconviniences regarding my actual tasks but i think the software selection was one of the few corners, i never had problems with. if you need help from this list you may wan't to concretize your problems greetz sven

1 0

forcing reboot after autoyast installation stage 1
by Kai Dusek 27 Feb '06

27 Feb '06

Dear all, I want to install a SLES9 SP2 or SP3 Linux with autoyast on a z/VM guest without any manual intervention. Unfortunately the installation is always stopping after stage 1 (package installation, preparing bootloader, ...) with an unclear error message on my 3270. I have to re-IPL my system manually to continue with stage 2 (post installation, suse-config etc.). That's output to 3270: [...] umount: /y2update: not mounted umount: /var/adm/mount: not mounted Feb 15 19:48:19 suse sshd¬322|: Received signal 15; terminating. [...] bash: no job control in this shell SuSE Instsys boeid120:/ # [...] My parmfile looks like: ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc dasd=150,151 TERM=dumb AUTOYAST=http://<IP>/autoinst.xml AUTOINSTALL=yes IP_INTERFACE=qeth IP_HOST=<hostname> IP_ADDR=x.x.x.x IP_NETMASK=x.x.x.x IP_BROADCAST=x.x.x.x IP_GATEWAY=x.x.x.x IP_DNS=x.x.x.x IP_SEARCH=x.x.x.x READ_DEVNO=7000 WRITE_DEVNO=7001 DATA_DEVNO=7002 PORTNAME=xxxxxx INST_INFO=ftp INST_IP_ADDR=x.x.x.x INST_IP_DIR=/SLES/sles9_s390_sp3 FTPUSER=<user> FTPPASSWORD=<pw> INST_SCREEN=VNC VNC_PASSWORD=<pw> IP_MTU=1492 INST_PASSWORD=<pw> The forceboot option is set to true. Kind regards Kai Dusek

1 0

RE: [suse-autoinstall] suse 10.0 nfs install
by Gunreben, Peter (Peter) 27 Feb '06

27 Feb '06

Roger, Roger Oberholtzer wrote: > On Wed, 2006-02-22 at 17:51 +0100, Gunreben, Peter (Peter) wrote: > > Roger, > > > > Roger Oberholtzer wrote: > > > > > > The install kernel boots. At some point it wants to get a > DHCP address > > > for the ethernet card. This 'should' be working as it got > an address > > > when it first booted. I see this in the server's > > > /var/log/messages. But > > > this seems to timeout. My dhcp entry is: > > > > > > host jboc1 { > > > > > > filename "/suseInstall/pxelinux.0"; > > > fixed-address 192.30.105.204; > > > hardware ethernet 00:30:48:56:38:B2; > > > next-server 192.30.105.201; > > > option host-name "jboc1"; > > > } > > > > > > 192.30.105.201 is the server for everything (dhcp, pxe, > suse install) > > > > > > After this, I get a message that the SUSE installation source > > > cannot be > > > found. When trying to set it up by hand (nice it does that), > > > I see that > > > the default values it offers are the ones I expect (despite > > > the probable > > > DHCP oddness). But when it tries to mount the nfs install > source, it > > > fails with 'unknown error -1'. > > > > Have you checked whether the nfs-export works properly, e.g. > > by mounting it manually? I had a similar problem, where > > I tried to export a loop-mounted directory tree. Only, > > a userspace-nfsserver can do that. > > I can mount it from other systems. Using > > mount -t nfs source:/vol1/distro/OpenSUSE10.0/suse10.0 /tmp/vv > > I can read files and go into directories. It just got back to my mind that I had an additional problem. For any reason I still do not know, I had to add insmod=<my_NIC_kernelmodule> to the kernel parameters in order to get everything work. Of course, you need to replace <my_NIC_kernelmodule> with the one you need. May be it's worth to give it a try. Peter.

6 17

how to autoinstall RAID spares disks ?
by rejaine＠bhz.jamef.com.br 24 Feb '06

24 Feb '06

Hi list, I need to install 4 RAID disks and 1 SPARE disk (backup disk) using autoinstall, but I don't know how ... My /etc/raidtab wil have to be like this: raiddev /dev/md0 raid-level 5 nr-raid-disks 4 ----> nr-spare-disks 1 persistent-superblock 1 parity-algorithm left-asymmetric chunk-size 128 device /dev/sda5 raid-disk 0 device /dev/sdb5 raid-disk 1 device /dev/sdc5 raid-disk 2 device /dev/sdd5 raid-disk 3 ---> device /dev/sde5 ---> spare-disk 0 raiddev /dev/md1 raid-level 5 nr-raid-disks 4 ----> nr-spare-disks 1 persistent-superblock 1 parity-algorithm left-asymmetric chunk-size 128 device /dev/sda5 raid-disk 0 device /dev/sdb5 raid-disk 1 device /dev/sdc5 raid-disk 2 device /dev/sdd5 raid-disk 3 ---> device /dev/sde5 ---> spare-disk 1 etc... I try to modify <raid_type>spare</raid_type) instead of <raid_type>raid</raid_type> like this: <drive> <device>/dev/sde</device> ... snip... <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">5</partition_nr> -----> <raid_name>/dev/md0</raid_name> -----> <raid_type>spare</raid_type> <size>30G</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">6</partition_nr> ----> <raid_name>/dev/md1</raid_name> ----> <raid_type>spare</raid_type> <size>21G</size> </partition> etc.. But don't work... I'm using SLES9 (whith service pack2) and Suse Linux 10 How can I configure this??? (sorry by bad english)

1 0

How to make blocking init-scripts?
by T. Ribbrock 23 Feb '06

23 Feb '06

Hi all, I just ran into some annoyance with the initial scripts that the autoinstall can perform: One of the tasks I do via such a script is the installation of all current updates and of some additional packages from an additional source. This does take a good while (depending on the machine I'm installing on - we still have some PIIIs running here...). However, I noticed that the machine will happily display the login screen even though this task has not finished yet. I find this undesirable, as i want the updates and installations to be finished before anything is started by a user (or root). Is it possible to write an init-script in a way that will make the machine wait for the script to finish before displaying the login screen? Cheerio, Thomas

4 6

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall February 2006