Hi Yet another - and perhaps more hassle-free approach - is to name the NICs by bus-ID. This way you can ensure that the NIC in slot x always is ethx and you don't have to update the profile with different MAC addresses for every machine. I documented that in http://www.novell.com/support/viewContent.do?externalId=7006937&sliceId=1 a while ago. Best regards Andreas

...

...

On 2/28/2011 at 15:40, Erico Mendonça wrote: On Mon, Feb 28, 2011 at 10:04 AM, Sebastian Wenner wrote:

Hi,

Is there a way of specifying this in the autoyast file and at the boot prompt?

Yes, you can add a section under "networking":

<net-udev config:type="list"> <rule> <name>eth0</name> <rule>ATTR{address}</rule> <value>xx:xx:xx:xx:xx:xx</value> </rule> </net-udev>

where you should substitute "xx:xx:xx..." for the actual MAC address.

You could also use a placeholder string in that field, like "__MACADDR__" which could be substituted later via a pre-script.

Add more rules for other interfaces as needed.

-- -- Erico -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Frank Steiner wrote:

The "old" and ugly but often helpful way is module ordering via parameters for the installer. In this case you would use sth. like

linuxrc.debug=-udev.mods insmod=bnx2 autoyast=... install=...

e.g. in pxelinux.cfg. This way you can still force the order in which the modules are loaded and make the bnx2 driver load before the e1000.

By the way, for linuxrc there is also udev.rule like this udev.rule="mac=00:11:d8:39:4e:d0,name=eth0" See http://en.opensuse.org/Linuxrc Cheers Michael -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

I will use xsltproc as mentioned by Uwe's blog entry http://ugansert.blogspot.com/2010/04/autoyast-and-its-tools.html Thus the final xml file will be created by xsltproc and not by autoyast. Example: Mynode1 *Project1.software.xml *Project1.dns.xml *Project1.ntp.xml *Project1.nis.xml *MyNode1.specialsettings.xml Mynode2 *Project1.software.xml *Project1.dns.xml *Project1.ntp.xml *Project1.ldap.xml *MyNode2.specialsettings.xml Will result in a final Mynode1.autoinst.xml and Mynode2.autoinst.xml which will be selected by a simple rule during installation. Advantage imho - I can create dynamically configuration for nodes based on a config file. - In case a xml file need a change because for example the dns has been change, the dns.xml will be updated and used for new installation AND be used to the change running systems via "export TERM=vt100; screen -D -m yast /usr/share/YaST2/clients/ayast_setup.ycp setup filename=/tmp/$i" Thus i am able to INSTALL and to MAINTAIN a Suse Linux environment in an easy way. I hope i have not reinvented the wheel. Cheers Hajo -----Original Message----- From: Hans-Joachim Ehlers [mailto:HansJoachim.Ehlers@eumetsat.int] Sent: Monday, March 21, 2011 3:39 PM To: opensuse-autoinstall@opensuse.org Subject: [opensuse-autoinstall] Using more than 1 result in a rules file Hi, Given: SLES 11 SP1 Question: Can i use more than one result for a match ? Example: parsing a ntp.xml and a dns.xml based on memsize. Only one result per rule: ( standard ) <rule> <memsize> <match>256</match> greater </memsize> <result> <profile>dns.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <memsize> <match>256</match> greater </memsize> <result> <profile>ntp.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> More than one result per rule. ( What i would like to know ) <rule> <memsize> <match>256</match> greater </memsize> <result> <profile>dns.xml</profile> <profile>ntp.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> Motivation: With a single match a certain configuration could be build. Example: NodeTypeOne is build of standard.xml, nis.xml, dns.xml NodeTypeTwo is build of standard.xml, ldapclient.xml, dns.xml a.s.w tia Hajo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

On Tue, Mar 22, 2011 at 01:15:28PM +0100, Uwe Gansert wrote:

no, that can not work. The technical reason is, that autoyast will convert the <result> structure into a map also known as hash. The hash would have the same key ("profile") twice then and that can't work in YCP.

I ran into similar limitations a few years ago and found the way to work around it was to use pre-install scripts that do the same kind of things on the fly. Just output to /tmp/profile/modified.xml (and up to, I think, stock sle10 I found I had to then copy that to /tmp/profile/autoyast.xml due to it re-reading autoyast.xml instead of the modified.xml one). We do a lot of things like... - Determining swap size and any leftover into a /local partition we use, based on ram and a value passed via cmdline. - Networking config parts (we install using dhcp then convert to static based on the hostname lookup in DNS). - Some <package> adds/removes based on the profile (usually adding xen/kvm bits if it's going to be a hypervisor) while still using the default xml files. Pre install is also handy for doing things like saving off existing xorg.conf or ssh keys if they exist then dropping them back in the chroot. -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com Homer: "Oh.. I hate having parties. The toilet always gets backed up!" ==> Simpsons -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Hi there, According to , this email address is not subscribed to this list. Am I sending the request to the correct email address? I used : e.g opensuse-autoinstall+unsubscribe@opensuse.org Regards, Simon. ----------------------------- Hi, this is the mlmmj program managing the mailinglist opensuse-autoinstall@opensuse.org You are not subscribed to this list, so you cannot unsubscribe. To subscribe send a message to: opensuse-autoinstall+subscribe@opensuse.org And for help send a message to: opensuse-autoinstall+help@opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

on Monday 28 March 2011 Hans-Joachim Ehlers wrote:

Problem: A post script does not get executed during execution of ayast_setup

Analyse: If <filename>cfg_init_nisclient.sh</filename>

Is changed to

<filename>cfg_init_nisclient</filename> <!-- .sh has been removed -->

The script will be executed.

strange. Is there anything useful in the y2log file in the error case?

Additional question(s): Is it correct that only post scripts are supported via ayast_setup.ycp ? At least i could not get a init script running.

yes, init-script don't work like expected maybe. They are only executed during the boot process. So be prepared that they are executed next time you boot the machine if you had some in an XML file and used it with ayast_setup :) -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Hi Given: SLES11 SP1 / OpenSuse 11.1 Task: Merge 2 xml files which have a post-script section with xsltproc. So no classes or rules.xml is used Problem: Script sections does not get merged and the CDATA is missing. Note: I am aware of http://www.suse.de/~ug/autoyast_doc/merging.html but i do not how to implement this in my xml files.

From the above link the following is given:

rules.xml ... <element>partition</element> ... The reason for the whole stuff is that i would like to merge simple xml files like sw.xml + dns.xml + nis.xml which might have a post-script sections as well. In this way a xml file for a given node is build of dedicated xml files and these xml files can be used also to change an installed system since then might contain required "shell" code. I have read that "XIncludes" can be used as well but it is also not clear to me how they could help. I do not mind to have the final autoinst.xml build during installation by autoyast using many small xml files but so far i have not found an easy way todo so. Example to reproduce the problem: !$ xsltproc --novalid --param with "'script1.xml'" --param replace "'false'" --output script.out /usr/share/autoinstall/xslt/merge.xslt script2.xml With !$ cat script1.xml <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <scripts> <post-scripts config:type="list"> <script> <debug config:type="boolean">true</debug> <feedback config:type="boolean">false</feedback> <filename>cfg_post_nisclient</filename> <interpreter>shell</interpreter> <location></location> false <source><![CDATA[ echo "INFO: Running $(basename $0 )" ]]></source> </script> </post-scripts> </scripts> </profile> !$ cat script2.xml <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <scripts> <post-scripts config:type="list"> <script> <debug config:type="boolean">true</debug> <feedback config:type="boolean">false</feedback> <filename>cfg_post</filename> <interpreter>shell</interpreter> <location></location> false <source><![CDATA[ echo "INFO: $(basename $0 )" ]]></source> </script> </post-scripts> </scripts> </profile> Will result in: !$ cat script.out <?xml version="1.0"?> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <scripts> <post-scripts config:type="list"> <script> <debug config:type="boolean">true</debug> <feedback config:type="boolean">false</feedback> <filename>cfg_post_nisclient</filename> <interpreter>shell</interpreter> <location/> false <source> echo "INFO: Running $(basename $0 )" </source> </script> </post-scripts> </scripts> </profile> Thus the section cfg_post is lost as well as "<![CDATA[" and "]]>" Any help ? Tia Hajo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Given * SLES11 SP1 * post script with location tag ( tce-nisclient ) * post script with source tag ( script.xml ) Task: Both files get merged by autoyast via a rule.xml Problem: The result has a corrupted post script section with only one section having a location and source tag. ... <post-scripts config:type="list"> <script> <debug config:type="boolean">true</debug> <feedback config:type="boolean">false</feedback> <filename>cfg_post_tce_nisclient</filename> <interpreter>shell</interpreter> <location><![CDATA[http://@INSTSERVER@/export/suse/scripts/tce_nisclient.cmd]]></location> false <rerun config:type="boolean">true</rerun> <source><![CDATA[ echo cfg_post echo cfg_post ]]></source> ... Notes: Extract from the nisclient client xml <scripts> <post-scripts config:type="list"> <script> <filename>cfg_post_tce_nisclient</filename> <rerun config:type="boolean">true</rerun> <debug config:type="boolean">true</debug> <feedback config:type="boolean">false</feedback> <interpreter>shell</interpreter> <location>http://@INSTSERVER@/export/suse/scripts/tce_nisclient.cmd</location> </script> </post-scripts> </scripts> Extract from the script.xml <scripts> <post-scripts config:type="list"> <script> <filename>cfg_post</filename> <debug config:type="boolean">true</debug> <feedback config:type="boolean">false</feedback> false <interpreter>shell</interpreter> <source><![CDATA[ echo cfg_post echo cfg_post ]]></source> </script> </post-scripts> </scripts> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Hi, Another problem. Any idea how to debug pre scripts during autoyast installations ? Locks like that the output from the pre_script does not make it into /var/adm/autoinstall/logs. For some reason my modified.xml file does not get modified by the pre-script . BTW: Does autoyast used the /tmp/profile/modified.xml in SLES11 SP1 ? Tia Hajo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org