Re: [9fans] dhcp & metanames

[David Presotto <presotto@closedmind.org>]

[-- Attachment #1: Type: text/plain, Size: 766 bytes --]

First of all, dom in our world is an FQDN. That means that both
.home.davidashen.net and .davidachen.net are wrong.

We ask dhcp for a hostname and a domain.  For the latter, dhcp's
seem to differ in what they give back, i.e., the FQDN of the machine,
the FQDN domain name that the machine is in, or that FQDN starting
with a '.'.    Ipconfig tries to deal with the situation, clearly
not well enough.  I'll try to do better but, if the server doesn't
return the hostname, its hard to guess.  the dom=.davidashen.net 
clearly indicates that we only got the domain and not the hostname.
This is a effect of the spread of windows where the hostname is
always in local storage and diskless boot is not really considered.

I'll try to do better in ipconfig.

[-- Attachment #2: Type: message/rfc822, Size: 2393 bytes --]

From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dhcp & metanames
Date: Sun, 7 Mar 2004 17:13:53 +0400 (AMT)
Message-ID: <200403071313.i27DDrDh079473@adat.davidashen.net>

/net/ndb:
ip=192.168.1.28 ipmask=255.255.255.0 ipgw=192.168.1.1
      dom=.davidashen.net
      dns=192.168.1.1

/lib/ndb/local:
sys=xotic ether=0002a5561d54 proto=il 
      ip=192.168.1.28 ipmask=255.255.255.0
      dom=.home.davidashen.net

Shouldn't dom in /net/ndb be .home.davidashen.net?

David