From owner-freebsd-hackers Sat Jul 31 19:56:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id F1BC415022; Sat, 31 Jul 1999 19:56:16 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #1) id 11Alm6-0000NG-00; Sat, 31 Jul 1999 20:54:58 -0600 Message-ID: <37A3B701.851DF00B@softweyr.com> Date: Sat, 31 Jul 1999 20:54:57 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Sergey Babkin , Warner Losh , "Brian F. Feldman" , "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: So, back on the topic of enabling bpf in GENERIC... References: <199907302342.RAA85088@harmony.village.org> <37A25361.34799F96@bellatlantic.net> <199907310140.SAA95581@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :> 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. Do we have a list of all services that use bpf? I'm willing to edit the man pages, given a list. I guess I could just grep-o-matic here, huh? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message