Date: Mon, 10 Jul 2000 23:03:09 -0700 From: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com> To: "Yevmenkin, Maksim N, CSCIO" <myevmenkin@att.com> Cc: "'freebsd-current@freebsd.org'" <freebsd-current@FreeBSD.ORG> Subject: Re: New version of TAP driver for FreeBSD -current Message-ID: <8009.963295389@localhost> In-Reply-To: Your message of "Mon, 10 Jul 2000 13:29:26 EDT." <E598F159668DD311B9C700902799EAF4473442@njb140po01.ems.att.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Long time back i sent request to the list and asked about including this > driver into the source tree. i still did not receive any reply. Some people > seems to be using this driver for Ethernet tunneling (with VTUN software). > Somebody even requested for OpenBSD port. So it would be really nice to > hear from one of the commiters. Hi Maksim, I've looked at this driver and think it looks useful, though I'm a little concerned about the handling of bridge support. We don't really encourage users to edit module Makefiles just to enable a given feature in the compiled module since that naturally leads to situations where one /modules directory is not the same as another (where you might want to copy things), even though all the same module names appear. It also leads to version skew between the kernel and the modules since sliding a new kernel into place which doesn't have BRIDGE support would now mysteriously break a module, leading to some confusion to any admin new on the scene. Isn't there a better way of enabling support in the module all the time and conditionally using it only if the kernel also provides the right support? At that point it would be my opinion (and mine only) that it was ready to come into FreeBSD-current as a new feature. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8009.963295389>