- openSUSE Autoinstall

[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

[opensuse-autoinstall] boot device in stage 1?
by Jochen Schaefer 07 Jul '10

07 Jul '10

Hi, can anybody tell me please how to invoke a reboot from an autoyast script in stage 1? reboot, init 1, init 6, shutdown are not working. 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

2 1

[opensuse-autoinstall] create_package_descr EXTRA_PROV SLE-11
by Jochen Schaefer 01 Jul '10

01 Jul '10

Hi list, does anybody know where to find the EXTRA_PROV file within SLE11 distribution? It was located in setupu/descr at code 10 installation media or is it not needed for SLE11? 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

2 1

[opensuse-autoinstall] ssh based installation for phase 1 only?
by Jochen Schaefer 29 Jun '10

29 Jun '10

Hi list, is there any way to perform an autoyast installation via ssh for phase 1 only and let the second stage run automatically without ssh? 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

2 2

[opensuse-autoinstall] sles11 sp1 problem on add_on section in xml file
by Ruediger Gunreben 29 Jun '10

29 Jun '10

Hello, I've a Problem with the SP1 on SLES11. I have the following xml file sniplet which will be merged by the rules.xml file during autoyast installation Condition: ================================================ <?xml version="1.0"?> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <add-on> <add_on_products config:type="list"> <listentry> <media_url>cd:///?devices=/dev/sr0,/dev/sr1</media_url> <product>IsarFlowAddons</product> <product_dir>/addons/isarflow</product_dir> <ask_on_error config:type="boolean">true</ask_on_error> <name>IsarFlowAddons</name> </listentry> ... ================================================ When I've a look at the processed /tmp/profile/autoinst.xml file after the merging during the installation process the media_url entry looks like this: Problem: ================================================ <media_url><![CDATA[cd:///?devices=/dev/sr0,/dev/sr1]]></media_url> ================================================ Thus the add_on_products won't be found and the Directory and Repository Name will be declared as 'Unknown' in the installation section of add_products. Can anyone help me with this problem? Workaround(?): I'll try to make a "sed" pre-script substitution. I'll let you know it it works. Regards Ruediger -- Ruediger Gunreben Tel: +49 811 99829 116 Fax: +49 811 99829 216 GSM: +49 178 7072030 E-Mail: ruediger.gunreben(a)isarnet.de CCIE R+S #21614 ________________________________________ Support IsarFlow Tel.: 0811 99829 270 E-Mail: support(a)isarflow.de IsarNet Software Solution GmbH Terminalstrasse Mitte 18 85356 Muenchen http://www.isarflow.de http://www.isarnet.de ________________________________________ IsarNet AG Terminalstrasse Mitte 18 85356 Muenchen Sitz der Gesellschaft: Oberding Handelsregister Muenchen, HRB 127295 USt.-ID Nr. DE203054669 Vorstand: Andreas Perthel, Harald Weikert Vorsitzender des Aufsichtsrates: Andreas Gallenmueller ________________________________________ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

[opensuse-autoinstall] Unable to Create Repository SLED 11.0
by Bart Wahlgren 28 Jun '10

28 Jun '10

I used Yast Product Creator to create a custom installation DVD for SLED 11.0. AutoYast fails when trying to create the repository with the following error: Unable to create repository from 'url dvd:///' Details Valid metadata not found at specified URL History - Signature verification failed for content Does anyone have suggestions on what I did wrong in the configuration of the product or how to troubleshoot this error? Thanks Bart Wahlgren Network Administrator Speed Script Pharmacy Systems Direct: 913-643-2454 Fax: 913-894-1802 bwahlgren(a)speedscript.com Speed Script is a registered trademark of Digital Simplistics, Inc. This electronic message, including any attachments, may contain confidential or privileged information and is intended for the individual or entity named above. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify the sender immediately and destroy all electronic and hard copies of the communication, including attachments. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] "Invalid partition table" on SLES10SP2/3 with soft RAID
by Andreas Taschner 17 Jun '10

17 Jun '10

Hi This may very well not be an AutoYaST problem, but ... I am trying to duplicate a problem at a customer that has a RAID1 setup with /boot, / and other partitions on md. For this I install SLES10SP2 as step one and upgrade to SLES10SP3 as step2. Doing this manually works fine, but when installing SP2 or upgrading to SP3 using AutoYaST, the system fails to boot and reports "Invalid partition table" before even reaching the grub menu. Whether I use initialize true on sda, sdb and md in the installation profile or not, makes no difference. The strange thing is when I install SLES manually after being in the error situation, it recognizes all partitions and RAID setup. When booting into rescue mode and doing an fdisk -l it sees all sd{a,b}* partitions correct, bootable is /dev/sdb1. It also lists the /dev/md{0-4], but only md0 is claimed to contain a valid partition table (though not containing any partitions). md1-4 are marked as invalid. mdadm --scan --detail print shows that all RAID devices contain two devices. /boot/grub/menu.lst refers to /dev/md? and I have tried configuring device.map to map to both /dev/sd? and /dev/disk/by-id/*. Another funny observation : Switching the bootable flag from sdb1 to sda1 changes the boot error from "Invalid partition able" to "No operating system" So it looks like the RAID setup somehow does not make it to disk when using AutoYaST. Any ideas ? Thank you. Best regards Andreas Taschner Designated Support Engineer Novell -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] registration against SMT using autoyast
by Matthew Delves 08 Jun '10

08 Jun '10

Hey List, I'm wondering if there is a known way of registering a server against SMT using autoyast. Thanks, Matt Delves. -- --------------------------------------------- Matthew Delves System Administrator Information Systems Networks & Infrastructure University of Ballarat ph: 03 5327 9732 email: m.delves(a)ballarat.edu.au -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2