>Yes, this also is what NetBSD and FreeBSD do, although I do hope
>/dev/bpf0 can be removed some time in the future.
then you need to go do a ports audit; almost assuredly, prepare
yourself for disillusionment.
don't do it now. do it in a year.
On Tue, May 03, 2016 at 05:09:47AM -0600, Theo de Raadt wrote:
> > On 2016-04-27, Martin Natano wrote:
> >
> > > /dev/bpf0 is for compatibility with existing binaries and is to
> > > be removed after a transition period.
> >
> > What's the impact on ports going to be?
> >
> > (We still have fou
> On 2016-04-27, Martin Natano wrote:
>
> > /dev/bpf0 is for compatibility with existing binaries and is to
> > be removed after a transition period.
>
> What's the impact on ports going to be?
>
> (We still have four /dev/*random devices for compatibility.)
I believe we'll end up with /dev/bp
On 2016-04-27, Martin Natano wrote:
> /dev/bpf0 is for compatibility with existing binaries and is to
> be removed after a transition period.
What's the impact on ports going to be?
(We still have four /dev/*random devices for compatibility.)
--
Christian "naddy" Weisgerber
Following diff replaces /dev/bpf[0-9] with only /dev/bpf and /dev/bpf0.
The /dev/bpf node is unused for now, but I plan to convert all programs
in base to use it in a future diff. /dev/bpf0 is for compatibility with
existing binaries and is to be removed after a transition period.
install.sub cont
