This patch has now been committed to -CURRENT.
A conservative MFC schedule of at least 1 month is suggested. Devfs
cloning remains enabled by default as it breaks ppp, ssh, and many ports.
Regards,
BMS
___
freebsd-net@freebsd.org mailing list
http://
Hi,
I have cleaned up the style/mdoc bugs in the original patch, and cut a
new one against bleeding edge HEAD (we just took the kern_conf.c fix in
too):-
http://people.freebsd.org/~bms/dump/new-landon-tuntap.diff
PRs potentially resolved by this patch:
http://www.freebsd.org/cgi/query-pr.c
On Nov 7, 2006, at 15:37, Landon Fuller wrote:
Nick Barkas ([EMAIL PROTECTED]) and I have added interface cloning
support to the tun(4) and tap(4) drivers.
We maintained backwards-compatible support for devfs cloning, which
is now disabled by default -- it can be re-enabled via a sysctl.
On Nov 8, 2006, at 06:33, Bruce M. Simpson wrote:
Landon Fuller wrote:
Nick Barkas ([EMAIL PROTECTED]) and I have added interface
cloning support to the tun(4) and tap(4) drivers.
We maintained backwards-compatible support for devfs cloning,
which is now disabled by default -- it can be r
Landon Fuller wrote:
Nick Barkas ([EMAIL PROTECTED]) and I have added interface cloning
support to the tun(4) and tap(4) drivers.
We maintained backwards-compatible support for devfs cloning, which is
now disabled by default -- it can be re-enabled via a sysctl.
Interfaces that are created vi
Nick Barkas ([EMAIL PROTECTED]) and I have added interface cloning
support to the tun(4) and tap(4) drivers.
We maintained backwards-compatible support for devfs cloning, which
is now disabled by default -- it can be re-enabled via a sysctl.
Interfaces that are created via devfs cloning may
