From owner-freebsd-stable  Sat Dec  6 10:49:08 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA05615
          for stable-outgoing; Sat, 6 Dec 1997 10:49:08 -0800 (PST)
          (envelope-from owner-freebsd-stable)
Received: from mail.san.rr.com (san.rr.com [204.210.0.1])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA05610
          for <freebsd-stable@freebsd.org>; Sat, 6 Dec 1997 10:49:04 -0800 (PST)
          (envelope-from Studded@dal.net)
Received: from dal.net (dt051n19.san.rr.com [204.210.32.25])
	by mail.san.rr.com (8.8.7/8.8.7) with ESMTP id KAA00157;
	Sat, 6 Dec 1997 10:49:26 -0800 (PST)
Message-ID: <34899DD9.21955D8B@dal.net>
Date: Sat, 06 Dec 1997 10:47:53 -0800
From: Studded <Studded@dal.net>
X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE i386)
MIME-Version: 1.0
To: Nate Williams <nate@mt.sri.com>
CC: freebsd-stable@freebsd.org
Subject: Re: Interested in patches for dhcp in rc.*?
References: <34890C94.972D09DC@dal.net> <199712061804.LAA06159@mt.sri.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Nate Williams wrote:
> 
> > A lot of people have been asking about our support for DHCP, and as
> > cable modems become more popular, I think that those requests will
> > increase. I use one, and I've been working on integrating it into my
> > system.  I've got things going basically the way I want them, and it
> > occured to me that adding options for it into rc.conf and rc.network
> > would be useful.
> 
> Would it be possible to have the ISC/DHCP port 'patch' the system easily
> for these kinds of things, or better yet add a new 'rc' file that gets
> run *after* rc.conf but before rc.network, thereby relying less on
> FreeBSD's changing file?  

	Unless I'm missing something, this would involve patching rc instead of
rc.network, which seemed to me to be a more serious thing.  In either
case, you'd still want an option to prevent it from loading, since you
don't always want to bring it up on boot. My thinking was to keep the
dhcp_client options in rc.conf very generic so that at some point in the
future when we integrate it into the base system, rc.conf won't have to
be changed. 

> Then, you'd have the best of both worlds, the
> ability to keep the 'base' stuff clean from non-existant FreeBSD
> sources, and also the flexibility of being able to have the new
> functionality at boot time.

	I did note the concern regarding including options for things that are
not part of FreeBSD in my original post. The use of dhcp is growing in
popularity, so I thought it would be nice to get out ahead of the curve
with scripting hooks now that could be tied into later when we have
sources in the tree.

> Ff/when DHCP gets integrated into the tree I think it should get 'hooks'
> in the standard files.

	Agreed.

Doug