From owner-freebsd-hackers  Fri Jul 30 18:41:35 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id DCAF414EE7; Fri, 30 Jul 1999 18:41:33 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id SAA95581;
	Fri, 30 Jul 1999 18:40:07 -0700 (PDT)
	(envelope-from dillon)
Date: Fri, 30 Jul 1999 18:40:07 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199907310140.SAA95581@apollo.backplane.com>
To: Sergey Babkin <babkin@bellatlantic.net>
Cc: Warner Losh <imp@village.org>,
	"Brian F. Feldman" <green@FreeBSD.ORG>,
	"Jordan K. Hubbard" <jkh@zippy.cdrom.com>, hackers@FreeBSD.ORG
Subject: Re: So, back on the topic of enabling bpf in GENERIC...
References: <Pine.BSF.4.10.9907301619280.6951-100000@janus.syracuse.net> <199907302342.RAA85088@harmony.village.org> <37A25361.34799F96@bellatlantic.net>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:> consistant with the meaning of "raw devices".
:
:Disabling bpf it will break rarpd (and also rbootd but it is less 
:important). I think such a thing should be mentioned in documentation.
:
:-SB

    Not if rarpd is started via the rc files... it would hook up to bpf
    prior to the securelevel being raised.

    But I agree about the documentation.  The various server documentation
    as well as the inetd documentation should mention that bpf-using servers
    need to be started from the rc's when securelevel is used.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message