February 2007 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] Including other files in an XML rules file
by Liam MacKenzie 22 Feb '07

22 Feb '07

Hi all! I'm working on an autoyast system for my company and was wondering if there's a better way than to have one whole file per server. I've got quite a lot of standardisation across the machines yet each are slightly different. Is there a way to 'include' files in a build script? For instance, you can write a bash script and use `source` to have it source and run different scripts elsewhere on the filesystem. I'd like to do something similar with autoyast. I notice there's a "classes" directory in my build space, but I can't find any documentation on it. Is this relevant? Thanks in advance! Liam -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] YaST CD Creator
by Shah Chowdhury 20 Feb '07

20 Feb '07

I'm having some difficulty trying to create install CDs with YaST CD creator. I'm planning on using it to create ISO images for auto-install CDs with my AutoYaST control file. This works fine except it create an ISO image that's too big to fit on one CD (bigger than 700mb). Burning DVDs is not an option for me. I was wondering how I could have the utitily span my install image over multiple CDs. Also, if that's (spanning the image to multiple CDs) not possible, is there a work around that I could use to accomplish the same result. I believe all I need is to be able to burn the Autoyast control file to the first CD image. Can I take an existing live CD's ISO image and somehow include my control file (autoinst.xml) the first bootable CD? My understanding is that SLES installer looks for a 'autoinst.xml' file and if found uses it. I tried "editing" CD1 of the install source to add my autoinst.xml file and got an 'Image checksum error'. How do I update the implanted image checksum once I've inserted my autoinst.xml and rebuilt the ISO? Thanks in advance. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] How to change the root disk in grub?
by GUNREBEN, PETER (Peter) 20 Feb '07

20 Feb '07

Hi, I'm using a bootable USB-Stick to boot the computer for autoinstallation. Everything works fine, but the grub boot-loader installation just before the first reboot is selecting the wrong harddisk as root device. I.e. it should be "root (hd0,1)", but actually it is set to "root (hd1,1)". Background: At inital boot, the USB-Stick is /dev/sda and the HDD is /dev/sdb. After kernel and initrd have been loaded from the USB-Stick, I'm removing the stick and the autoinstall continues. After 1st reboot, the HDD is /dev/sda and grub fails, because (hd1,1) is not present. How can I force autoyast to tell grub to use (hd0,0) as root? In SUSE 10.1 this problem did not exist. System: openSUSE-10.2 (final) on ASUS K8N-DER (Dual Opteron 275) Thanks, Peter. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 6

[opensuse-autoinstall] additional inst sources
by Lars Stavholm 19 Feb '07

19 Feb '07

Hi List, is there a way to add installation sources in the autoyast.xml? I already have three local installation sources and in addition I would like to specify a couple from opensuse.org (oss and non-oss). The local installation sources are already in place after installation. But how do I add some external installation sources in autoyast.xml? Do I have to use some post script trick or is there an easier way? Thanks /Lars -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 18

Re: [opensuse-autoinstall] range-type in scripts is faulty
by Frank Steiner 16 Feb '07

16 Feb '07

Uwe Gansert wrote >> I wouldn't reject a driverupdate if you find the time to create >> one (actually, a compiled ybc module would suffice since I build my >> own driverupdate already). > > I have attached a ybc file. Hmm, ain't that easy it seems... Including this file into the driverupdate makes the install process hang when reading rules and profiles. Even on hosts that don't fall into that rule. The y2log ends with: 2007-02-14 16:00:58 <1> 141.84.1.23(3696) [YCP] /tmp/AutoInstallRules.ycp:485 Writing rule script into /tmp/YaST2-03696-AYG3gG/rule_custom2 2007-02-14 16:00:58 <1> 141.84.1.23(3696) [YCP] /tmp/AutoInstallRules.ycp:390 Bash return: if ( [ "$custom2" -ge "211" -a "$custom2" -le "239" ] ) ; then exit 0; else exit 1; fi ($["exit":1, "stderr":"", "stdout":""]) ($["arch":"i386", "custom1":"riemann", "custom2":"23", "custom3":"23", "custom4":"23", "installed_product":"SUSE Linux 10.1", "karch":"kernel-default"]) 2007-02-14 16:00:58 <1> 141.84.1.23(3696) [YCP] /tmp/AutoInstallRules.ycp:625 Getting Rules: ["profiles/lmu.xml", "profiles/10.1.xml", "profiles/k_deflt.xml", "profiles/part_riemann_keep.xml"] 2007-02-14 16:00:58 <1> 141.84.1.23(3696) [agent-system] SystemAgent.cc(Execute):1097 mkdir /tmp/YaST2-03696-AYG3gG/rules/profiles/ 2007-02-14 16:00:58 <1> 141.84.1.23(3696) [agent-system] SystemAgent.cc(Execute):1097 mkdir /tmp/YaST2-03696-0mQDoc/tmp_mount 2007-02-14 16:00:58 <1> 141.84.1.23(3696) [YCP] autoinstall/io.ycp:180 Copy Command: /bin/cp /tmp/YaST2-03696-0mQDoc/tmp_mount/lmu.xml /tmp/YaST2-03696-AYG3gG/rules/profiles/lmu.xml Removing the ybc file again solves the problem. I put the file into driverupdate created from ftp://ftp.suse.com/pub/people/ug/autoyast/sles10_root_fix_v0.4 Anything else I can try? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] Autoinstall Partitioning Question
by David Mackintosh 15 Feb '07

15 Feb '07

Hi folks, I'm trying to get started with autoYaST and have a question. When I set up the AutoYaST file to repartition the hard disk, the process stops at the "Installation Settings" screen with red "Set disk label of /dev/hda to msdos". If I hit "Accept" at this window, it pops up a "Confirm Installation" window which goes away when I hit "Install". Everything else works in a hands-off manner the way I want. So my question is: what magic do I have to include in my autoYaST file to make it accept both of these without promting the user? Thanks. The relevant part of the autoYaST file reads: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">swap</filesystem> <filesystem_id config:type="integer">130</filesystem_id> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>1024M</size> </partition> <partition> <crypt>twofish256</crypt> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">131</filesystem_id> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> </partitioning> -- /\oo/\ / /()\ \ David Mackintosh | dave(a)xdroop.com | http://www.xdroop.com

2 1

Re: [opensuse-autoinstall] range-type in scripts is faulty
by Frank Steiner 13 Feb '07

13 Feb '07

Uwe Gansert wrote > okay but it would be just including the border via "or" or using a custom > script that does the -gt -lt correctly. Well, I didn't think about fixing it in rules.xml :-( You are right, that would have beena lot easier. >> Is there an announcement date for SP1? If it's far in the future, > > it's May I think > >> I wouldn't reject a driverupdate if you find the time to create >> one (actually, a compiled ybc module would suffice since I build my >> own driverupdate already). > > I have attached a ybc file. Many thanks! -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] range-type in scripts is faulty
by Frank Steiner 13 Feb '07

13 Feb '07

Hi Uwe, in AY for SLES10 I'm using a script like this: <rule> <custom3> <script> <![CDATA[ #!/bin/sh ip=$(/sbin/ifconfig eth0 | sed -n "s/$inet\ addr:$$[0-9.]*$.*/\2/p" | cut -d'.' -f 4) echo -n $ip ]]> </script> <match>171-204</match> <match_type>range</match_type> </custom3> <result> ... (whatever) My understanding is that a host with ip x.x.x.171 should match that rule. However, y2log show the following: AutoInstallRules.ycp:390 Bash return: if ( [ "$custom3" -gt "171" -a "$custom3" -lt "204" ] ) ; then exit 0; else exit 1; fi I feel this is wrong and must be "-ge" and "-le" instead of "-gt" and "-lt" because I expect a closed range, not an open one. I really do need a fix for that, because we generate those rules from host config files automatically :-( cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 5

[opensuse-autoinstall] JFYI: YaST IRC-Meeting
by Uwe Gansert 13 Feb '07

13 Feb '07

---------- Forwarded Message ---------- Subject: YaST IRC-Meeting Date: Friday 09 February 2007 16:18 From: Edith Parzefall <emap(a)suse.de> To: opensuse-announce(a)opensuse.org Hiho! On request by the openSUSE community, we invite everyone interested in YaST development to chat with the YaST teams on IRC next Wednesday. We want to hear your ideas on how you'd like to contribute to YaST. When: Wednesday, Feb. 14, 5pm CET Where: #opensuse-project on irc.Freenode.net Feel free to add topics to http://en.opensuse.org/Meetings/YaST_Meeting_2007-02-14 Thanks for your interest, Edith -- Edith Parzefall Teamleader YaST, SUSE Linux Products GmbH - a Novell Business Maxfeldstr. 5, 90409 Nürnberg, Germany. Phone +49-911-74053-156 ------------------------------------------------------- -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug now playing Colony 5 - Stay young -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] insmod-Parameters not transferred to INITRD_MODULES anymore?
by Frank Steiner 13 Feb '07

13 Feb '07

Hi, with SLES 9, modules loaded with "insmod bla" in the info file, made it to the INITRD_MODULES line in /etc/sysconfig/kernel automatically. This was neat for e.g. fixing the order of scsi controllers or which network card to initialize as eth0 etc. It was also nice that only those modules for existing cards/controllers were added to INITRD_MODULES. So you could specify e.g. 5 different network modules to load but on every host only those came into INITRD_MODULES that matched a card on that host. In SLES 10 this feature is gone! None of the insmod-modules is listed in INITRD_MODULES anymore, just stuff that yast considered useful. As a consequence, e.g. the order of scsi controllers often differs from the order used during the installation, the same for network cards (and that idiotic udev "persistent nework device names" feature isn't able to recognize which card I used as eth0 during installation). Was that feature dropped or is it a bug? If it was dropped, how can I transfer the order of loading modules that I use during installation into the installed system? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 5