From owner-freebsd-current Tue Feb 9 08:13:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03591 for freebsd-current-outgoing; Tue, 9 Feb 1999 08:13:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03586 for ; Tue, 9 Feb 1999 08:13:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.2) with ESMTP id IAA06849; Tue, 9 Feb 1999 08:12:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: mi@aldan.algebra.com cc: current@FreeBSD.ORG Subject: Re: DHCP, install, security In-reply-to: Your message of "Tue, 09 Feb 1999 11:03:25 EST." <199902091603.LAA09757@misha.cisco.com> Date: Tue, 09 Feb 1999 08:12:50 -0800 Message-ID: <6846.918576770@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How about putting bpf functionality into install-kernel, but not > into the GENERIC kernel? That's already going to happen since the dhcp client isn't going to be very useful otherwise. Since this affects only the installation kernel, it's nothing that anyone should take issue with. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message