James Richard Tyrer wrote: > On 03/31/2012 02:07 PM, Bruce Dubbs wrote: >> James Richard Tyrer wrote: >>> On 03/29/2012 03:38 PM, Bruce Dubbs wrote: >>>> James Richard Tyrer wrote: >>>>>>>>> I find that when I start : "dhclient" with the: "network" init.d >>>>>>>>> script >>>>>>>>> that the host-name of my computer is changed to: "dhcppc<n>". I have >>>>>>>>> looked through the documentation and can not seem to find out how to >>>>>>>>> prevent this. >>>> You need to set up /etc/dhclient.conf. Do not request a host-name. >>>> >>> OK, that sounds like a reasonable idea, but that is where I started. I >>> have the file from the BLFS page: "DHCP-4.2.3-P2 Client Configuration" >>> installed and need to modify it. I thought that all I needed to do was >>> remove: "host-name" and "domain-name" from the: "request" list. The >>> problem is that this does not fix the issue. >>> >>>>>>>>> It would be nice if this page of the book addressed this problem. >> I can't get to this in a while. Would you please create a ticket in >> BLFS fo rthis problem. >> > I had the time to run this down today. > > The problem is occurring in the: "sbin/dhclient-script" script which has > a conditional expression to reset the hostname. Part of it is: > > [ x$current_hostname = xlocalhost ] || \ > > which results in the hostname being reset if it is the default: "localhost". > > A good question is why am I using that hostname. IIRC, there was a bug > in WINE that was worked around by using that. > > Is there a reason not to use: "localhost"? -- security?
localhost is 127.0.0.1. If the $current_hostname is localhost, it means that it has not been set explicitly by the localnet script and that the name passed by the dhcp server should be used. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
