July 2010 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] general rules question
by dutchguy69 26 Jul '10

26 Jul '10

I have a working autoyast install for 11.1 without using rules. Right now I would like to introduce rules but I do not seem to understand exactly how to make this work. The current install is done by supplying information for a linuxrc info file on the kernel command line info=nfs://<ip-address>/<path>/1055_init.linuxrc The info file has several parameters defined for network access, the install and the autoyast variable autoyast: nfs://<ip-address>/<path>/1055_init.autoyast <- this is my autoinst profile below the path I have created the rules directory which includes a rules .xml file with following content <?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> # CPU_TYPE on vm's is giving same result for CPU as on real hardware we have to extend to video to understand the difference between virtual and real CPU_TYPE=`cat /proc/cpuinfo|grep 'model name'|uniq|awk 'BEGIN {FS=":"};{print $2}'` VIDEO_TYPE=`/sbin/lspci | grep "VGA compatible controller"|awk 'BEGIN {FS=":"};{print $3}'` if [ "$CPU_TYPE" == " AMD Athlon(tm) 64 X2 Dual Core Processor 4400+" ]; then if [ "$VIDEO_TYPE" == " nVidia Corporation G70 [GeForce 7300 GT] (rev a1)" ]; then echo -n "host1.xml" elif [ "$VIDEO_TYPE" == " InnoTek Systemberatung GmbH VirtualBox Graphics Adapter" ]; then echo -n "host1-virtualbox.xml" fi # information for scan64-3200 elif [ "$CPU_TYPE" == " AMD Athlon(tm) 64 Processor 3200+" ]; then if [ "$VIDEO_TYPE" == " nVidia Corporation G70 [GeForce 7300 GT] (rev a1)" ]; then echo -n "host2.xml" elif [ "$VIDEO_TYPE" == " InnoTek Systemberatung GmbH VirtualBox Graphics Adapter" ]; then echo -n "host2-virtualbox.xml" fi fi </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>@custom1@</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom> <script> </script> <match>*</match> <match_type>exact</match_type> </custom> <result> <profile>1055_init.autoyast</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> I have tried to change the autoyast parameter in the info file with the following values autoyast: nfs://<ip-address>/<path>/ <-- question about profile location autoyast: nfs://<ip-address>/<path>/rules/ <-- question about profile location autoyast: nfs://<ip-address>/<path>/rules/rules.xml Above direct reference to rules file seems to work but not as expected. When I check the box I can see that in /tmp/profile/autoinst.xml I find a copy of my rules.xml file where I'm expecting a merged profile from my 1055_init.autoyast and host2.xml information I'm not sure exactly what I'm doing wrong and even after extensive check via google haven't found the right references. I've used http://forgeftp.novell.com/yast/doc/SL11.1/autoinstall/ for documentation but it is not giving me enough detail to solve above issue. Any input would be welcomed. -- 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] Skip specific storage module during installation
by Ruediger Gunreben 23 Jul '10

23 Jul '10

Hi All, I have a system with a fibre channel attached. Is it possible to disable the qla2xxx module when installation starts. Because the ordering of the sda/sdb/sdc will be disturbed with it and a proper configuration of the devices is not possible anymore. Any suggestions are welcome Thanks in advance Regards Ruediger -- 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] performance question for add_on_products section
by Ruediger Gunreben 21 Jul '10

21 Jul '10

Hello, I've a performance question. I have several different add_on_products specified in the xml. The media_url ist <media_url>cd:///<path></media_url> always. When I start the installation I see in the log files that for all add_on_products a mechanism starts to detect the files. Now the Problem. I have 2 cd devices on the system wich will be probed. Unfortunately the device is /dev/sr1 and /dev/sr0 will always be probed first. So the detection of the path take ages. I've zipped the y2log: http://isarflow.de/~rgunreben/y2log_MediaProbing.zip Account: ay/ay Any advice is welcome to make this behaviour faster. Regards Ruediger -- 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] new 11.2 install problems with resolver
by Henrik Schmidt 19 Jul '10

19 Jul '10

I have a running install server with autoyast for 11.2 It seems repositories are shuffled around a bit due to 11.2 release. Now I get an error message in the badlist file during install : kalgrebra-4.4.4-3.2.i586 requires kdebase4-runtime >= 4.4.4, but this requirement cannot be provided I have included <listentry> <media_url>http://download.opensuse.org/repositories/KDE:/Distro:/Stable/openSUSE_11.2</media_url> <product>kde4 core</product> <product_dir>/</product_dir> <name>kde4 core</name> </listentry> This is the repo for both kalgebra and kdebase4-runtime. Whats up, can some enlighten me whats wrong ? It worked before. My complete addon list is : <add-on> <add_on_products config:type="list"> <listentry> <media_url>http://download.opensuse.org/update/11.2</media_url> <product>updates</product> <product_dir>/</product_dir> <name>updates</name> </listentry> <listentry> <media_url>http://download.opensuse.org/distribution/11.2/repo/oss</media_url> <product>oss</product> <product_dir>/</product_dir> <name>oss</name> </listentry> <listentry> <media_url>http://download.opensuse.org/distribution/11.2/repo/non-oss</media_url> <product>non-oss</product> <product_dir>/</product_dir> <name>non-oss</name> </listentry> <listentry> <media_url>http://ftp.gwdg.de/pub/linux/misc/packman/suse/11.2</media_url> <product>packman</product> <product_dir>/</product_dir> <name>packman</name> </listentry> <listentry> <media_url>ftp://download.nvidia.com/opensuse/11.2</media_url> <product>nvidia</product> <product_dir>/</product_dir> <name>nvidia</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/mozilla/openSUSE_11.2</media_url> <product>mozilla</product> <product_dir>/</product_dir> <name>mozilla</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_11.2</media_url> <product>wine</product> <product_dir>/</product_dir> <name>wine</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_11.2</media_url> <product>kde3 core</product> <product_dir>/</product_dir> <name>kde3 core</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/KDE:/Community/openSUSE_11.2</media_url> <product>kde3 community</product> <product_dir>/</product_dir> <name>kde3 community</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/KDE:/Backports/openSUSE_11.2</media_url> <product>kde backports</product> <product_dir>/</product_dir> <name>kde backports</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/KDE:/Distro:/Stable/openSUSE_11.2</media_url> <product>kde4 core</product> <product_dir>/</product_dir> <name>kde4 core</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/KDE:/KDE4:/Community/openSUSE_11.…</media_url> <product>kde4 community</product> <product_dir>/</product_dir> <name>kde4 community</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/KDE:/UpdatedApps/openSUSE_11.2</media_url> <product>kde4 updated apps</product> <product_dir>/</product_dir> <name>kde4 updated apps</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/KDE:/Qt:/STABLE/openSUSE_11.2</media_url> <product>qt</product> <product_dir>/</product_dir> <name>qt</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/GNOME:/STABLE:/2.28/openSUSE_11.2</media_url> <product>gnome stable</product> <product_dir>/</product_dir> <name>gnome stable</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/GNOME:/Contrib/openSUSE_11.2</media_url> <product>gnome contrib</product> <product_dir>/</product_dir> <name>gnome contrib</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/multimedia:/photo/openSUSE_11.2</media_url> <product>multimedia photo</product> <product_dir>/</product_dir> <name>multimedia photo</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/multimedia:/libs/openSUSE_11.2</media_url> <product>multimedia libs</product> <product_dir>/</product_dir> <name>multimedia libs</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/Java:/packages/openSUSE_11.2</media_url> <product>java</product> <product_dir>/</product_dir> <name>java</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/OpenOffice.org:/STABLE/openSUSE_1…</media_url> <product>openoffice stable</product> <product_dir>/</product_dir> <name>openoffice stable</name> </listentry> <listentry> <media_url>http://download.videolan.org/pub/vlc/SuSE/11.2</media_url> <product>videolan</product> <product_dir>/</product_dir> <name>videolan</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/Printing/openSUSE_11.2</media_url> <product>printing</product> <product_dir>/</product_dir> <name>printing</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/Printing:/ghostscript/openSUSE_11…</media_url> <product>ghostscript</product> <product_dir>/</product_dir> <name>ghostscript</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/Publishing/openSUSE_11.2</media_url> <product>publishing</product> <product_dir>/</product_dir> <name>publishing</name> </listentry> <listentry> <media_url>http://download.opensuse.org/repositories/hardware/openSUSE_11.2</media_url> <product>hardware</product> <product_dir>/</product_dir> <name>hardware</name> </listentry> </add_on_products> </add-on> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 5

[opensuse-autoinstall] How to select default entry for boot loader?
by Peter Pointner 19 Jul '10

19 Jul '10

Hello, I"m struggling with bootloader installation using opensuse-11.3. In order to solve a problem with the resume device I wanted to supply my own entry in grub's menu.lst (I will need that anyway). When I use the following: <bootloader> <loader_type>grub</loader_type> <global> <default>Linux</default> </global> <sections config:type="list"> <section> <append>noresume</append> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <name>Linux</name> <root>/dev/md0</root> <type>image</type> <vgamode>0x314</vgamode> </section> </sections> </bootloader> I do get an entry for "Linux" as expected, but additionally I get the standard entries, and the "default" points to the first of them. (Then it ends up waiting for the resume device to appear. The swap space is on a raid-1, which seems to cause this problem). So the question is: how can I get a boot loader installation preferably without the standard entries, or at least with the default pointing to my entry? -- 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] problem pxe booting opensuse 11.3 (bad kernel format, EFI?)
by Mike Coleman 15 Jul '10

15 Jul '10

I downloaded the opensuse 11.3 today hoping it'd be a quick upgrade from my existing opensuse 11.2 setup (gPXE to load the kernel and jump into autoyast). In the past, it's just been an easy matter of copying the kernel and initrd off of the DVD and away we go. But not in 11.3. Apparently the kernel format has changed, at least according to 'file'. It's no longer something recognized as a kernel, but instead is a gzip'ed ELF image. I gather by poking around on the disk that it's being loaded by efi, which I'm guessing is some sort of EFI loader. Whatever it is, gPXE doesn't recognize it, and I'm guessing PXELINUX won't either. The doc on the disk links to some sort of "remote install" document, but unfortunately that link is dead. I'm assuming it got lost in the wiki cutover. I know this is slightly off-topic, but does anyone know the trick to booting this kernel over pxe? Thanks, Mike -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

[opensuse-autoinstall] Problem with disk device names
by Peter Pointner 15 Jul '10

15 Jul '10

Hello, I am trying (on openSuse 11.2) to create a rules file and classes to create a software raid if the pc has 2 hard disks. My first try is to use disksize rules for /dev/sda and /dev/sdb. This failed, because I booted from USB stick, and the first SATA disk became /dev/sda, the USB stick became /dev/sdb, and the second SATA disk became /dev/sdc. Probably I will find a way to find out if there are 2 disks, but what to use for the "device" attribute of the "partitioning" section? Is there a generic way to specify the first, second, ... harddisk without getting disturbed by USB sticks? Peter -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

5 12

[opensuse-autoinstall] xsltproc parameters
by Jochen Schaefer 13 Jul '10

13 Jul '10

Hi list, I'm trying to use xsltproc for merging some autoyast snippets in stage 1. Since I'm not familar with xslt so may be someone can answer my question. I would like to replace a tag and its whole content from modified.xml e.g. partitioning by a partitioning tag from a second xml.file. I don't want to merge it - it should be simple replaced. I tried xsltproc with several parameters but it didn't work like I need it. I started with below line and played with replace, dontmerge parameters and changed the with file and the modified.xml. But still not successful. xsltproc --novalid --param with "'snippet.xml'" --param replace "'false'" --param dontmerge "'partitioning'" --output out.xml /usr/share/autoinstall/xslt/merge.xslt modified.xml Has Anyone an idea? Thanks, Jochen Mit freundlichen Grüßen Novell GmbH, Jochen Schaefer Senior Consultant - Novell Services - Mobile: +49 (0)173 5876 969 Fax.: +49 (0)211 - 5631 3769 e-mail: jschaef(a)novell.com Location: Düsseldorf, Deutschland Novell GmbH, Düsseldorf; GF: Dr. Jürgen Müller, Sylvia Geil, Felix Imendörffer; HRB 21108 (AG Düsseldorf) Ready for enterprise-class consulting www.novell.de/consulting -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

Re: [opensuse-autoinstall] xsltproc parameters
by Jochen Schaefer 13 Jul '10

13 Jul '10

Thanks Uwe, I will try it this way. Jochen >>> Uwe Gansert 07/13/10 1:25 PM >>> on Tuesday 13 July 2010 Jochen Schaefer wrote: > I would like to replace a tag and its whole content from modified.xml e.g. > partitioning by a partitioning tag from a second xml.file. > I don't want to merge it - it should be simple replaced. > > I tried xsltproc with several parameters but it didn't work like I need it. > > I started with below line and played with replace, dontmerge parameters and > changed the with file and the modified.xml. But still not successful. > xsltproc --novalid --param with "'snippet.xml'" --param replace "'false'" > --param dontmerge "'partitioning'" --output out.xml > /usr/share/autoinstall/xslt/merge.xslt modified.xml I don't think merge.xslt can handle that. You'd have to write your own xslt file but because you say you don't know anything about xslt, you should split it into 3 xml files. 2 times partitioning and one all_the_rest.xml Then merge the correct partitioning into the all_the_rest.xml with merge.xslt -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "New World Order" by The Retrosic -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org -- 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] Not Creating /dev/md
by Bart Wahlgren 07 Jul '10

07 Jul '10

I'm having trouble with getting autoyast to create software RAID devices. The partitions get created on the devices but the /dev/md devices fail to get created. This is for SLED 11.0. The partition setup I'd like is the following. /sd*1 md0 /boot /sd*2 swap /sd*3 md1 /var /sd*4 md2 / This is the partition section of the autoinst.xml, I've compared it with the autoyast documentation and it looks like it should work. Thank you in advance for any assistance. <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">253</filesystem_id> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <resize config:type="boolean">false</resize> <raid_name>/dev/md0</raid_name> <size>123379200</size> </partition> <partition> <create config:type="boolean">true</create> <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> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <resize config:type="boolean">false</resize> <size>2138572288</size> </partition> <partition> <create config:type="boolean">true</create> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">253</filesystem_id> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <resize config:type="boolean">false</resize> <raid_name>/dev/md1</raid_name> <size>32201971200</size> </partition> <partition> <create config:type="boolean">true</create> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">253</filesystem_id> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">4</partition_nr> <resize config:type="boolean">false</resize> <raid_name>/dev/md2</raid_name> <size>165541984768</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">253</filesystem_id> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <resize config:type="boolean">false</resize> <raid_name>/dev/md0</raid_name> <size>123379200</size> </partition> <partition> <create config:type="boolean">true</create> <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> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <resize config:type="boolean">false</resize> <size>2138572288</size> </partition> <partition> <create config:type="boolean">true</create> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">253</filesystem_id> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <resize config:type="boolean">false</resize> <raid_name>/dev/md1</raid_name> <size>32201971200</size> </partition> <partition> <create config:type="boolean">true</create> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">253</filesystem_id> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">4</partition_nr> <raid_name>/dev/md2</raid_name> <resize config:type="boolean">false</resize> <size>165541984768</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> <drive> <device>/dev/md</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <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> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <resize config:type="boolean">false</resize> </partition> <partition> <create config:type="boolean">true</create> <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> <loop_fs config:type="boolean">false</loop_fs> <mount>/var</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <resize config:type="boolean">false</resize> </partition> <partition> <create config:type="boolean">true</create> <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> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <resize config:type="boolean">false</resize> </partition> </partitions> <type config:type="symbol">CT_MD</type> <use>1,3,4</use> </drive> </partitioning> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1