[18586] in Athena Bugs
Re: linux 8.4.17: hostname set to (none) sometimes on boot with DHCP
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Dec 4 22:26:08 2000
Message-Id: <200012050325.WAA06240@egyptian-gods.MIT.EDU>
To: Camilla R Fox <cfox@MIT.EDU>
Cc: bugs@MIT.EDU
In-Reply-To: Your message of "Mon, 04 Dec 2000 20:40:30 EST."
<200012050141.UAA32291@pickled-herring.mit.edu>
Date: Mon, 04 Dec 2000 22:25:57 -0500
From: Greg Hudson <ghudson@MIT.EDU>
> The problem that I moved the pcmcia init script around for was much
> more obvious; in the version I installed, pcmcia came after network,
> and the network startup failed.
For the record, this is a more subtle bug than people sometimes
present it as. It's supposed to be okay to start network after pcmcia
and have everything come up correctly, just as it's supposed to be
okay to plug your network card in after the machine has booted.
However, in some cases, the delayed initialization doesn't work
correctly. I don't know why. I have a theory that it only works if
the device is named "eth0", since the default startup order worked for
me when I had an eth0 device and failed for me when I switched to a
wvlan0 device.
Regarding Mike's message, the services which start between network and
pcmcia are (athena-ws and attach are Athena-specific, of course):
apmd
athena-ws
random
syslog
attach
crond
Of these, syslog seems like it could experience a problem for lack of
network, trying to look up a logging hostname. The rest should be
fine, I think.
