[18656] in Athena Bugs
Linux-Athena: Incompatibities between syncconf, ifup-post, pcmcia, and DHCP
daemon@ATHENA.MIT.EDU (Derek Atkins)
Sun Jan 7 22:45:16 2001
To: bugs@MIT.EDU, linux-dev@MIT.EDU
From: Derek Atkins <warlord@MIT.EDU>
Date: 07 Jan 2001 22:45:10 -0500
Message-ID: <sjm66jqpv09.fsf@rcn.ihtfp.org>
Hi,
I just re-installed Heather's Laptop using the most recent SIPB
install (which should be 8.4.17, or so I'm told). Unfortunately the
machine never wanted to set it's hostname. DNS works. Network works.
It just wouldn't set the name.
I have the network configured to use DHCP. I also have "HOST" set
to something reasonable in rc.conf. However, syncconf ignores
the HOST setting if ADDR=dhcp. I suppose that is reasonable, because
it expects ifup-post to set the hostname when the network comes
up.
That's fine, too, except that ifup-post only sets the name when it's
called from the network script (i.e. when called with $2 == boot,
which only happens from the network script). Unfortunately the PCMCIA
network scripts do NOT set $2=boot. This means that ifup-post will
NOT set the hostname for pcmcia hosts (even at boot time).
I don't the _right_ fix for this. However in the short term I would
change syncconf so it sets HOSTADDR in /etc/sysconfig/network if HOST
is non-empty, even if ADDR=dhcp. This would let users set their
hostname, or they can choose to let the system set their hostname. It
would give users of DHCP a DWIW mode :)
Thanks,
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord@MIT.EDU PGP key available