Hi, Thanks David ...
On Sun, Jan 29, 2012 at 01:48:12PM +0000, Debian Bug Tracking System wrote: > Processing commands for [email protected]: > > reassign 657860 debian-reference > Bug #657860 [www.debian.org] www.debian.org: debian-reference/ch05.en.html, > about sending the hostname to DHCP server > Bug reassigned from package 'www.debian.org' to 'debian-reference'. > -- > 657860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657860 Well this is certainly not the bug for www.debian.org :-) But is it a bug for me. I clearly state: "After preparing the system by Section 5.4.1, “The DHCP connection with the Ethernet”,..." There I specifically mention to use the dhcp3-client package. But ithe original bug reporter did not and complaining. So I can say it is not my bug just from the text of the original report :-) But I should think why he reported this. .... Yah, .... OK ... I know things change with release. ifupdown has moved to new ip based system instead of ifconfig based one. So maybe this is something to do with the transition .... Oh I see. For Wheezy, dhcp3-client is basically dead. So we need to update this section to isc-dhcp-client . I guess I need to update: http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_dhcp_connection_with_the_ethernet There I should mention isc-dhcp-client. But I thought the following used to be standard way. == hostname "mymachine" === Old installer used to put this anyway ... Well recent installer does not seem to set it. I thought it was documented by ifupdown upstream.... let me see ... But "man interfaces" is so old and mention nothing and point to Debian Reference. Agh ...It mentions the old URL for debian reference and also mention ifconfig. This clearly illustrate it has not updated. The official documentation of ifupdown does not make any clear message about this hostname feature. Let's see its source. inet.defn | method dhcp | description | This method may be used to obtain an address via DHCP with any of | the tools: dhclient, pump, udhcpc, dhcpcd. | (They have been listed in their order of precedence.) | If you have a complicated DHCP setup you should | note that some of these clients use their own configuration files | and do not obtain their configuration information via *ifup*. | | options | hostname hostname -- Hostname to be requested (pump, dhcpcd, udhcpc) | leasehours leasehours -- Preferred lease time in hours (pump) | leasetime leasetime -- Preferred lease time in seconds (dhcpcd) | vendor vendor -- Vendor class identifier (dhcpcd) | client client -- Client identifier (dhcpcd, udhcpc) | hwaddress class address -- Hardware Address. /class/ is one of \ | *ether*, *ax25*, *ARCnet* or *netrom*. \ | /address/ is dependent on this choice. Hmmm... ISC one is dhclient so no wonder it is missing hostname support It lloks like removing hostname "mymachine" from 5.5.4. The network interface served by the DHCP is good idea. Then add a bit more pointer to 5.4.1. The DHCP connection with the Ethernet pointing to dhclient.conf(5) is good idea. Osamu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
