Thomas Vogt wrote / napísal(a):

Hello

Is there a way to add nameserver values to the resolv.conf with autoyast.xml? After the installation of OpenSuSE 10.3 (i386) with autoyast my resolv.conf is always empty. Everything else works fine.

XML config:

<dns> false false <domain>mydomain</domain> <hostname>myhostname</hostname> <nameservers config:type="list"> <nameserver>1.2.3.4</nameserver> <nameserver>1.2.3.5</nameserver> </nameservers> </dns>

I also tried it with a post-script but with no luck.

<scripts> <post-scripts config:type="list"> <script> <debug config:type="boolean">true</debug> <feedback config:type="boolean">false</feedback> <filename>myscript</filename> <interpreter>shell</interpreter> <location></location> true <source><![CDATA[shell #!/bin/sh # Sort out resolv.conf cat > /etc/resolv.conf <<EOF nameserver 1.2.3.4 nameserver 1.2.3.5 EOF ]]></source> </script> </post-scripts> </scripts>

Any idea?

Regards, Thomas

Can you write a bugreport for that, please? Thank you. -- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec@suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

On Tue, Jan 29, 2008 at 12:05:12PM +0100, Thomas Vogt wrote:

<dns> false false <domain>mydomain</domain> <hostname>myhostname</hostname> <nameservers config:type="list"> <nameserver>1.2.3.4</nameserver> <nameserver>1.2.3.5</nameserver> </nameservers> </dns>

That's exactly how I'm doing ours here and it works great.. sles9-sp3 through sles/sled10-sp1. This probably isn't it, but that is inside the <networking> tags, right? Here's what my desktop entries look like in the cached xml file.. I build the file on the fly in the pre-install scripts too (actual names/ips mod'd of course): <networking> AUTO <dns> false false <domain>ourdomain</domain> <hostname>desktopname</hostname> <nameservers config:type="list"> <nameserver>1.2.3.4</nameserver> <nameserver>1.2.3.5</nameserver> </nameservers> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <ipaddr>192.168.1.50</ipaddr> <netmask>255.255.254.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <managed config:type="boolean">false</managed> <modules config:type="list"> <device>static-0</device> <module></module> <options></options> </modules> <routing> false <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>192.168.1.1</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> Installs happen using dhcp, the above is done (like I said) in a pre-install script (my pre.sh is a wrapper that just mounts an NFS path then does a basic "for script in $path/*; do $script; done" idea) that had read in some default values (like initial dns servers and such) and builds the above on the fly using the passed static ip, name dns server, etc, then spits out the above into the /tmp/profile/modified.xml. Has worked great across the sles/sled versions thus far. The reboot after initial install is done uses the above networking config and creates a valid resolv.conf. -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com The idea that an arbitrary naive human should be able to properly use a given tool without training or understanding is even more wrong for computing than it is for other tools (eg automobiles, airplanes, guns or power saws). -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org