[opensuse-autoinstall]
Hello, I use one and the same autoyast script to install SLES 10 and SLES 11. Looking in the /etc/hosts file on SLES 11 you can find a additional line:
127.0.0.2 hostName.domain hostName
On a SLES 10 based installation this line is not present. It looks like some default behaviour changed with SLES 11. But how can I avoid this in my autoyast file? Cheers, Edy -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Tuesday 28 April 2009 15:13:37 Eduard Diner wrote:
Looking in the /etc/hosts file on SLES 11 you can find a additional line:
127.0.0.2 hostName.domain hostName
On a SLES 10 based installation this line is not present. It looks like some default behaviour changed with SLES 11.
But how can I avoid this in my autoyast file?
should not happen. Can you attach your networking section please? -- 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 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
At least with OpenSuse 10.3 this is the standard behaviour as well. I have read some notes on the iNet regarding the hostname should be bound to 127.0.0.2 or not. cheers Hajo ...
Looking in the /etc/hosts file on SLES 11 you can find a additional line:
127.0.0.2 hostName.domain hostName
On a SLES 10 based installation this line is not present. It looks like some default behaviour changed with SLES 11.
But how can I avoid this in my autoyast file?
should not happen. Can you attach your networking section please? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hi,
At least with OpenSuse 10.3 this is the standard behaviour as well. I have read some notes on the iNet regarding the hostname should be bound to 127.0.0.2 or not.
Uwe pointed me to this list (mainly because of this particular thread) - so, to introduce myself, I'm 1/2 of yast2-network team and thought it could be really useful to subscribe, to be able to answer some questions, esp. those network related. But back to this 127.0.0.2 thing: The purpose of 127.0.0.2 entry is that if the active network connection is not available at the moment, a bunch of (buggy) applications (OpenOffice, bash, Firefox,...) try to do a hostname lookup, which of course can't succeed and takes long time to time out. Not surprisingly, users then complain that apps take up to 10 seconds to start if their laptop is currently offline. But on the other hand, the entry being there breaks other things - active directory integration, printing, some proxy autoconfiguration scripts and some enterprise customers want it off by default. There is a sysconfig variable controlling whether 127.0.0.2 entry is going to be included in /etc/hosts - WRITE_HOSTNAME_TO_HOSTS in /etc/sysconfig/network/dhcp and it is set to 'yes' by default. It can be overriden with product's control file - SLES11's one sets it to 'no'. Unfortunately, this is done in one installation client which is not called during autoinstallation, thus the value from sysconfig is used even though it should not be. To conclude - yes, this is a bug and it's been already reproduced in-house. Please file a bugzilla ticket. B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hello Uwe, I attached two versions. The first one is the "source": Lines beginning with an "@" define perl commands. A perl script parses these lines an inserts some useful informations depending on the distribution sles10 or sles11. The second version shows the resulting networking section for sles11. ### VERSION 1 ### <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">false</dhcp_resolv> <domain>wdf.sap.corp</domain> <hostname>$hostname</hostname> <nameservers config:type="list"> @foreach nameservers <nameserver>$address</nameserver> @end </nameservers> <searchlist config:type="list"> <search>wdf.sap.corp</search> <search>de.ibm.com</search> <search>ibm.com</search> </searchlist> </dns> <interfaces config:type="list"> @perl $i=0; @foreach interfaces <interface> <bootproto>static</bootproto> @perl if (substr($distribution,0,4) eq "sl10") { <device>eth-id-$macaddress</device> @perl } else { <device>eth$i</device> @perl } @perl $i++; <ipaddr>$ipaddr</ipaddr> <netmask>$netmask</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> @end </interfaces> <managed config:type="boolean">false</managed> <modules config:type="list"> <module_entry> <device>bus-vio-3000000a</device> <module>ibmveth</module> <options></options> </module_entry> </modules> <routing> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>$gateway</gateway> <netmask>-</netmask> </route> </routes> </routing> ### VERSION 2 ### <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">false</dhcp_resolv> <domain>wdf.sap.corp</domain> <hostname>ls3814</hostname> <nameservers config:type="list"> <nameserver>11.17.210.88</nameserver> </nameservers> <searchlist config:type="list"> <search>my.company.corp</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <ipaddr>10.17.205.167</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"> <module_entry> <device>bus-vio-3000000a</device> <module>ibmveth</module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>10.17.204.1</gateway> <netmask>-</netmask> </route> /networking Thanks a lot! Bye, Eduard 2009/4/29 Uwe Gansert <ug@suse.de>:
On Tuesday 28 April 2009 15:13:37 Eduard Diner wrote:
Looking in the /etc/hosts file on SLES 11 you can find a additional line:
127.0.0.2 hostName.domain hostName
On a SLES 10 based installation this line is not present. It looks like some default behaviour changed with SLES 11.
But how can I avoid this in my autoyast file?
should not happen. Can you attach your networking section please?
-- 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
-- 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
participants (4)
-
Eduard Diner -
Hans-Joachim Ehlers -
Katarina Machalkova -
Uwe Gansert