Bug#64408: boot-floppies: DHCP detection does not set domainname

To: Christoph Lameter <christoph@lameter.com>
Cc: 64408@bugs.debian.org
Subject: Bug#64408: boot-floppies: DHCP detection does not set domainname
From: Randolph Chung <tausq@debian.org>
Date: Tue, 23 May 2000 00:03:43 -0700
Message-id: <[🔎] 20000523000343.C17464@tausq.org>
Reply-to: Randolph Chung <tausq@debian.org>, 64408@bugs.debian.org
In-reply-to: <[🔎] Pine.LNX.4.10.10005222226580.3670-100000@home.lameter.com>; from christoph@lameter.com on Mon, May 22, 2000 at 10:27:15PM -0700
References: <[🔎] 20000522181125.B17464@tausq.org> <[🔎] Pine.LNX.4.10.10005222226580.3670-100000@home.lameter.com>

In reference to a message from Christoph Lameter, dated May 22:
> This is crap. No unix daemon does a lookup in /etc/resolv.conf.

have you ever seen how the hostname -f functionality is implemented?

randolph
-- 
Debian Developer <tausq@debian.org>
http://www.TauSq.org/

Reply to:

References:
- Bug#64408: boot-floppies: DHCP detection does not set domainname
  - From: Randolph Chung <tausq@debian.org>
- Bug#64408: boot-floppies: DHCP detection does not set domainname
  - From: Christoph Lameter <christoph@lameter.com>

Prev by Date: Bug#64408: boot-floppies: DHCP detection does not set domainname
Next by Date: Re: IBM PS/2 Potato Install Fails
Previous by thread: Bug#64408: boot-floppies: DHCP detection does not set domainname
Next by thread: Bug#64408: boot-floppies: DHCP detection does not set domainname
Index(es):
- Date
- Thread