From owner-freebsd-current Mon Feb 8 22:29:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13602 for freebsd-current-outgoing; Mon, 8 Feb 1999 22:29:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA13594 for ; Mon, 8 Feb 1999 22:29:15 -0800 (PST) (envelope-from geoff@rucus.ru.ac.za) Received: (qmail 17760 invoked by uid 268); 9 Feb 1999 08:29:22 -0000 Message-ID: <19990209082922.17759.qmail@rucus.ru.ac.za> Subject: Re: adding DHCP client to src/contrib/ In-Reply-To: <199902090553.VAA05212@kithrup.com> from Sean Eric Fagan at "Feb 8, 1999 9:53:11 pm" To: current@FreeBSD.ORG Date: Tue, 9 Feb 1999 08:29:22 +0000 (GMT) Reply-To: "Geoff Rehmet" From: "Geoff Rehmet" X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Eric Fagan writes : > In article <19990209074440.15845.qmail.kithrup.freebsd.current@rucus.ru.ac.za> you write: > >Is DHCP core functionality? > > As much as an editor and PPP are, yes -- without it, some people simply > *cannot* get on the net. Your point is valid. Before it goes in, there are some points to look at though: - Integration with bootp functionality (if possible) - DHCP-WIDE requires you to have bpf configured into your kernel for a GENERIC kernel, this is VERY BAD - is there a more elegant way to handle this? I certainly would not like to see the generic kernel in the distribution going out into the world with bpf enabled. Geoff. -- Geoff Rehmet, The Internet Solution geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message