Tim Heckman wrote: > I have an interesting problem that should actually be seen as a compliment > to Debian. My system is booting so fast that the /sbin/getty is spawning > before DHCP sets the hostname. So I get a prompt like this: > > ==== > Debian GNU/Linux 6.0 (none) hvc0 > > (none) login: > ==== > > If I log in, the hostname is set, and when logging back out it appears as > well. Am I correct in assuming that you have modified /sbin/dhclient-script to set the hostname from the dhcp'd hostname? (That is what I did when I was doing this.) > This configuration is destined to be used for mass deployments of Debian > Squeeze. So simply hardcoding the hostname is not a solution, > unfortunately. Is there an easy way to slow down when getty is launched so > that I leave enough time for the hostname to be set? I am curious if you have worked with this type of a system previously. I have and I was never satisified with it. For example if the hostname changes due to a dhcp changed IP address while the system is running then X Windows gets very upset and there were other problems. In my case I ended up setting the hostname to localhost. Since the client machines are true thin clients without any external services they don't need to have a hostname. That worked best for me. Perhaps it is something that might be a good option for you? Then it would be very similar to any live-cd boot system. Bob
Attachment:
signature.asc
Description: Digital signature