This bug was fixed in the package dhcp3 - 3.1.3-2ubuntu3
---
dhcp3 (3.1.3-2ubuntu3) lucid; urgency=low
* debian/dhclient-script.linux: Fix regression in host_name option
handling, so that it's always honored when /etc/hostname is not set,
fixes LP: #537978, #482313, #90388,
The upstart task sets the system hostname from /etc/hostname (falling
back to "localhost" if that file is not readable or is empty and no
hostname has yet been set).
The idea here would be honor new_host_name for the same use cases (if
the /etc/hostname file is non-empty). That would support both
Thierry,
hostname is set by upstart so the point is moot I think.
Regards
chuck
--
Lucid dhclient can't set hostname
https://bugs.launchpad.net/bugs/537978
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Regression was introduced by the fix to:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508804
It could be fixed by fixing the obviously wrong patch, and support two cases:
* Set hostname if new_host_name provided and hostname is not set
* Set hostname if new_host_name provided and old_host_na
The live-CD has an /etc/hostname set to "ubuntu", so what do you want me
to check? Apart from that, the /sbin/dhclient-script file is the same as
above, so the logic to change the hostname does not work and is not
conforming to the dhclient-documentation.
--
Lucid dhclient can't set hostname
http
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Lucid Lynx. It would help us greatly if you could
test with it so we can work o
