I'm trying to install SLES 10 SP1 (64bit)
XML file below:
<general> <ask-list config:type="list"> <ask> <path>ntp-client,peer,address</path> <question>Enter NTP server:</question> <stage>initial</stage> <default>timestate1.dss.la.gov</default> </ask> </ask-list> <ntp-client> <configure_dhcp config:type="boolean">false</configure_dhcp> <peers config:type="list"> <peer> <address>timeref.dss.la.gov</address> <initial_sync config:type="boolean">true</initial_sync> <options></options> <type>server</type> </peer> </peers> <start_at_boot config:type="boolean">true</start_at_boot> <start_in_chroot config:type="boolean">false</start_in_chroot> </ntp-client> .. .. </general>
..I get prompted to enter the NTP server and enter it at the start of the install. However, when the server finishes, timeref.dss.la.gov is in /etc/ntp.conf, not timestate1.dss.la.gov.
Do I have things in the wrong order? Does <ntp-client> need to be in another part of the XML file? Any help is appreciated.
Ryan
<general> <ask-list config:type="list"> <ask> <path>ntp-client,peer,address</path>
the <path> is wrong. Must be "ntp-client,peers,0,address"
<question>Enter NTP server:</question> <stage>initial</stage> <default>timestate1.dss.la.gov</default> </ask></ask-list> <ntp-client> <configure_dhcp config:type="boolean">false</configure_dhcp> <peers config:type="list"> <peer> <address>timeref.dss.la.gov</address>
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
On Wed, Feb 6, 2008 at 7:55 AM, in message
0B32D76A-7773-4944-BB42-3CD10BDA8924@suse.de, Uwe Gansert ug@suse.de wrote:
<general> <ask-list config:type="list"> <ask> <path>ntp-client,peer,address</path>
the <path> is wrong. Must be "ntp-client,peers,0,address"
What does the 0 signify?
Thanks, Ryan
On Mittwoch, 6. Februar 2008, Ryan McCain wrote:
<general> <ask-list config:type="list"> <ask> <path>ntp-client,peer,address</path>
the <path> is wrong. Must be "ntp-client,peers,0,address"
What does the 0 signify?
"peers" is a list of "peer"-elements. The 0 tells autoyast to change the first element (peer) in that list. Each time you want to change an element of a list, you have to specify the index of that element (starting with 0)
On Wed, Feb 6, 2008 at 10:49 AM, in message 200802061749.54484.ug@suse.de,
Uwe Gansert ug@suse.de wrote:
On Mittwoch, 6. Februar 2008, Ryan McCain wrote:
<general> <ask-list config:type="list"> <ask> <path>ntp-client,peer,address</path>
the <path> is wrong. Must be "ntp-client,peers,0,address"
What does the 0 signify?
"peers" is a list of "peer"-elements. The 0 tells autoyast to change the first element (peer) in that list. Each time you want to change an element of a list, you have to specify the index of that element (starting with 0)
Doesn't "address" tell AutoYast exactly where to go. It seems the 0 is redundant, no?
Thanks..
-----Original Message----- From: Ryan McCain [mailto:Ryan.McCain@dss.state.la.us] Sent: Wednesday, February 06, 2008 12:21 PM To: opensuse-autoinstall@opensuse.org Subject: Re: [opensuse-autoinstall] Trying to set NTP w/ <ask> on SLES10 SP1 (64bit)
On Wed, Feb 6, 2008 at 10:49 AM, in message
200802061749.54484.ug@suse.de, Uwe Gansert ug@suse.de wrote:
On Mittwoch, 6. Februar 2008, Ryan McCain wrote:
<general> <ask-list config:type="list"> <ask> <path>ntp-client,peer,address</path>
the <path> is wrong. Must be "ntp-client,peers,0,address"
What does the 0 signify?
"peers" is a list of "peer"-elements. The 0 tells autoyast
to change the
first element (peer) in that list. Each time you want to change an element of a list, you have
to specify the
index of that element (starting with 0)
Doesn't "address" tell AutoYast exactly where to go. It seems the 0 is redundant, no?
The "0" isn't specifying the element of the <peer> section to modify; it's specifying the child-element of <peers> to alter.
The XML tree looks roughly like this: <ntp-client> <peers config:type="list"> <peer> <address>xxxx</address> .....
So, the path would be ntp-client,peers,peer,address -- _but_, the "config:type=list" changes that. Since it's a list, just specifying the name of the element that you want to modify is ambiguous (even if there's only one element with that name).
So, in the case where there's an element in the path with config:type="list", you need to specify the index of its child that you want to modify, instead of the name of the child. That's what the "0" is doing.
The "0" isn't specifying the element of the <peer> section to modify; it's specifying the child-element of <peers> to alter.
The XML tree looks roughly like this:
<ntp-client> <peers config:type="list"> <peer> <address>xxxx</address> .....
So, the path would be ntp-client,peers,peer,address -- _but_, the "config:type=list" changes that. Since it's a list, just specifying the name of the element that you want to modify is ambiguous (even if there's only one element with that name).
So, in the case where there's an element in the path with config:type="list", you need to specify the index of its child that you want to modify, instead of the name of the child. That's what the "0" is doing. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
So, with this xml file. If I wanted to assign an IP address it would be 'networking,interfaces,2,ipaddr'?
<networking> <dhcp_options> <dhclient_additional_options></dhclient_additional_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain>dss.la.gov</domain> <hostname>dss-buildserver</hostname> <nameservers config:type="list"> <nameserver>10.120.11.85</nameserver> <nameserver>10.120.11.107</nameserver> </nameservers> <searchlist config:type="list"> <search>dss.la.gov</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth-id-00:1c:23:cb:7e:aa</device> <ipaddr>10.120.160.231</ipaddr> <netmask>255.255.254.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces>
-----Original Message----- From: Ryan McCain [mailto:Ryan.McCain@dss.state.la.us] Sent: Wednesday, February 06, 2008 12:57 PM To: opensuse-autoinstall@opensuse.org Subject: RE: [opensuse-autoinstall] Trying to set NTP w/ <ask> onSLES10 SP1 (64bit)
So, with this xml file. If I wanted to assign an IP address it would be 'networking,interfaces,2,ipaddr'?
<networking>
<snipped stuff that's not really important to this>
<interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth-id-00:1c:23:cb:7e:aa</device> <ipaddr>10.120.160.231</ipaddr> <netmask>255.255.254.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces>
It would be <path>networking,interfaces,0,ipaddr</path>
Translated into words, more or less, it would read as: - First find the networking element - then, find the child element of <networking> that's called "interfaces" - then, find the very first child element of <interfaces> - from there, find the child element called "ipaddr", and since it's the last element in the list, operate on it.
If the path were "networking,interfaces,2,ipaddr", the result would be this: <networking> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth-id-00:1c:23:cb:7e:aa</device> <ipaddr>10.120.160.231</ipaddr> <netmask>255.255.254.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>static</bootproto> <device>eth-id-00:1c:23:cb:7e:ab</device> <ipaddr>10.120.161.231</ipaddr> <netmask>255.255.254.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>static</bootproto> <device>eth-id-00:1c:23:cb:7e:ac</device> <ipaddr>OPERATING ON THIS ELEMENT BECAUSE THIS INTERFACE HAS INDEX "2"</ipaddr> <netmask>255.255.254.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces>
<networking>
<snipped stuff that's not really important to this>
<interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth-id-00:1c:23:cb:7e:aa</device> <ipaddr>10.120.160.231</ipaddr> <netmask>255.255.254.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces>It would be <path>networking,interfaces,0,ipaddr</path>
Translated into words, more or less, it would read as:
- First find the networking element
- then, find the child element of <networking> that's called
"interfaces"
- then, find the very first child element of <interfaces>
- from there, find the child element called "ipaddr", and since it's
the last element in the list, operate on it.
If the path were "networking,interfaces,2,ipaddr", the result would be this:
<networking> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth-id-00:1c:23:cb:7e:aa</device> <ipaddr>10.120.160.231</ipaddr> <netmask>255.255.254.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>static</bootproto> <device>eth-id-00:1c:23:cb:7e:ab</device> <ipaddr>10.120.161.231</ipaddr> <netmask>255.255.254.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>static</bootproto> <device>eth-id-00:1c:23:cb:7e:ac</device> <ipaddr>OPERATING ON THIS ELEMENT BECAUSE THIS INTERFACE HAS INDEX "2"</ipaddr> <netmask>255.255.254.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Ohhhh. I follow you now. I will try this out tomorrow. I have meetings the rest of the day. Thanks for clarifying.
autoinstall@lists.opensuse.org
-
Marlier, Ian -
Ryan McCain -
Uwe Gansert