From owner-freebsd-current Mon Feb 8 23:16:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17554 for freebsd-current-outgoing; Mon, 8 Feb 1999 23:16:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles225.castles.com [208.214.165.225]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17548 for ; Mon, 8 Feb 1999 23:16:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA00580; Mon, 8 Feb 1999 23:12:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902090712.XAA00580@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Geoff Rehmet" cc: current@FreeBSD.ORG Subject: Re: adding DHCP client to src/contrib/ In-reply-to: Your message of "Tue, 09 Feb 1999 08:29:22 GMT." <19990209082922.17759.qmail@rucus.ru.ac.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Feb 1999 23:12:16 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - 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. That's not "VERY BAD". Bpf imposes a slight performance, hit, but that's about all. Don't start whining about the "security issues"; they're so trivial to be beyond worry. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message