[opensuse-autoinstall] Added kernel boot options from autoyast control file
Hi, We're autodeploying NLD9 and SLES10 systems, for both native and vmware instances. I succeeded in using rules and classes (after some nasty problems caused by differences in NLD9 and SLES10 control syntax). But I now have to add to the vmware-i386 class the boot option: clock=pit and the vmware-x86_64 class the boot option: notsc and I cannot find instructions on how to do this. Is there a file that contains the complete list of possibilities one could use inside a control file (for both NLD9 and SLES10 ?). That would be most welcome. Thanks in advance, -- -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Mon, 1 Oct 2007, Dag Wieers wrote:
We're autodeploying NLD9 and SLES10 systems, for both native and vmware instances. I succeeded in using rules and classes (after some nasty problems caused by differences in NLD9 and SLES10 control syntax).
But I now have to add to the vmware-i386 class the boot option:
clock=pit
and the vmware-x86_64 class the boot option:
notsc
and I cannot find instructions on how to do this. Is there a file that contains the complete list of possibilities one could use inside a control file (for both NLD9 and SLES10 ?). That would be most welcome.
I found the kernel_parameters in the DTD and that will work. But I have a follow-up question. Is there a way to do a negative match, or specify an 'else' clause for a rule ? Eg. when I have: <rule> <mac> <match>^000c29</match> <match_type>regex</match_type> </mac> <result> <profile>profiles/vmware.xml</profile> </result> </rule> I would like to have an else-fallback. Or have a rule match everything except ^000c29. And I know you can play with <continue> to stop processing, but that is not an option in a complex environment. Also is it possible to call 2 profiles from one rule ? In the case where we do match with a vmware instance (mac ~= ^000c29) I want to call profile vmware.xml and vmware-@arch@.xml, however that does not seem to work (and I do not get a real error, I just see both are not being called). Copying the profile twice doesn't work either: <rule> <!-- Check if this is VMware (based on MAC address) --> <mac> <match>^000c29</match> <match_type>regex</match_type> </mac> <result> <profile>profiles/vmware.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <!-- Check if this is VMware (based on MAC address) --> <mac> <match>^000c29</match> <match_type>regex</match_type> </mac> <arch>*</arch> <result> <profile>profiles/vmware-@arch@.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> It stops after vmware.xml (or it does not match the vmware-@arch@.xml profile for some reason ?). -- -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Mon, Oct 01, 2007 at 04:23:55PM +0200, Dag Wieers wrote:
I would like to have an else-fallback. Or have a rule match everything except ^000c29. And I know you can play with <continue> to stop processing, but that is not an option in a complex environment.
What pops into my head is using a custom script. Basically do a short shell script that if something like ifconfig sees the mac addres, echo vmware, else echo your default.. something like: <rule> <custom1> <script> <![CDATA[ #!/bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin if [ -n "`ifconfig | awk '/HWaddr/{print $NF}' | egrep -i '^00:0C:29'`" ] then echo vmware else echo default fi ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> </rule> later.. your arch match can do.. <profile>@custom1@-@arch@.xml</profile> I think that would work.. and AFAIK you can use multiple variables like that. I get which disk profile to use for our image based on passed profile=profile_name using a custom script this way. We only use one variable mixed in another match rule. -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com Roz: "Physical contact extends our lives." Frasier: "Well then, you'll outlive Styrofoam." -- Frasier -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (2)
-
Dag Wieers -
Mike Marion