http://qa.mandrakesoft.com/show_bug.cgi?id=2585
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
------- Additional Comments From [EMAIL PROTECTED] 2003-03-07 15:47 -------
This is the real bug behind bug 1583 (the really popular one).
drakconnect does not set HOSTNAME in /etc/sysconfig/network.
Also, the hardcoding of the zeroconf name in /etc/tmdns.conf means that hostname
resolution is also broken in the case of dhcp assigning a hostname (only
localhost is in /etc/hosts, tmdns resolves the zeroconf name, which is
non-existent anywhere else, and many dhcp-serving routers don't do dynamic dns).
Note that this also breaks some aspects of the Windows Domain Authentication
feature (winbind-based), which uses the `hostname` when joining the windows
domain. If the zeroconf hostname were applied when the network is started at the
end of install, it would be possible to have a normal windows domain account (on
a Windows 2000 domain) be given the right to join a machine name to the domain,
without the user having to be a Domain Admin. This was possible in 9.0. Good
thing no-one has advertised this yet.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEW
creation_date:
description:
9.1 RC1 - I supplied a non-dotted zeroconf hostname during installation, but
internet wizard and boot messages still show localhost as machine name.
