From owner-freebsd-hackers Thu Apr 16 13:53:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28806 for freebsd-hackers-outgoing; Thu, 16 Apr 1998 13:53:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28791 for ; Thu, 16 Apr 1998 20:53:00 GMT (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.4) with UUCP id VAA05113; Thu, 16 Apr 1998 21:51:57 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Thu, 16 Apr 1998 21:49:40 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199804160151.SAA00388@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 16 Apr 1998 21:52:40 +0100 To: Mike Smith From: Bob Bishop Subject: Re: Discussion : Using DHCP to obtain configuration. Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:51 am +0100 16/4/98, Mike Smith wrote: > >There are three basic approaches we can take to integrating DHCP >clienthood with FreeBSD: > > 1 Nothing Should be quick and easy to implement :-) > 2 Offer a simple choice between "traditional" static configuration, and > "use DHCP" configuration. Preferable I believe, because... > 3 Use the DHCP client for everything. ...this option would introduce yet another chunk of mechanism which has to be working before one's system will DTRT. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message