Date: Fri, 13 Apr 2007 19:45:20 +0100 From: Vince Hoffman <jhary@unsane.co.uk> To: Andre Oppermann <andre@freebsd.org> Cc: Peter Jeremy <peterjeremy@optushome.com.au>, Ian FREISLICH <ianf@clue.co.za>, brooks@freebsd.org, Andrew Thompson <thompsa@freebsd.org>, freebsd-current@freebsd.org Subject: Re: CFT: new trunk(4) Message-ID: <461FCFC0.6050109@unsane.co.uk> In-Reply-To: <461FB498.4030407@freebsd.org> References: <peterjeremy@optushome.com.au> <20070411191450.GE815@turion.vk2pj.dyndns.org> <E1Hbs1M-000FWA-7Z@clue.co.za> <20070412210957.GA31864@heff.fud.org.nz> <461FB498.4030407@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Andre Oppermann wrote: > Andrew Thompson wrote: >> On Thu, Apr 12, 2007 at 07:39:00AM +0200, Ian FREISLICH wrote: >> <snip> >> I think the unfortunate name of trunk(4) that we inherited from OpenBSD >> is causing quite some confusion. trunk(4) actually has nothing to do >> with vlan trunking which I think you are after. >> >> I can see this topic coming up again so it could save some time to >> rename the driver now. It would mean that we lose the naming link to the >> same driver in OpenBSD but you cant win em all. >> >> Some names that have been suggested are: >> >> linkag(4) >> agr(4) >> bond(4) <- same as linux >> >> Any suggestions! > > lacp(4)++ > Or fec(4) since this provides the same (and greater) fucntionality as ng_fec(4) (or for that matter at this rate we could call it bikeshed(4) ;) Vince
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?461FCFC0.6050109>