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.
\\\\\ Katarina Machalkova
\\\\\\\__o YaST developer
__\\\\\\\'/_ & hedgehog painter
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org