From owner-freebsd-current@FreeBSD.ORG Fri Apr 13 19:45:47 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B473716A404 for ; Fri, 13 Apr 2007 19:45:47 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from unsane.co.uk (www.unsane.co.uk [85.233.185.162]) by mx1.freebsd.org (Postfix) with ESMTP id 3DFED13C4B9 for ; Fri, 13 Apr 2007 19:45:47 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from [10.0.0.173] ([10.0.0.173]) (authenticated bits=0) by unsane.co.uk (8.14.0/8.14.0) with ESMTP id l3DJixlP049272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Apr 2007 20:44:59 +0100 (BST) (envelope-from jhary@unsane.co.uk) Message-ID: <461FCFC0.6050109@unsane.co.uk> Date: Fri, 13 Apr 2007 19:45:20 +0100 From: Vince Hoffman User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Andre Oppermann References: <20070411191450.GE815@turion.vk2pj.dyndns.org> <20070412210957.GA31864@heff.fud.org.nz> <461FB498.4030407@freebsd.org> In-Reply-To: <461FB498.4030407@freebsd.org> X-Enigmail-Version: 0.94.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Peter Jeremy , Ian FREISLICH , brooks@freebsd.org, Andrew Thompson , freebsd-current@freebsd.org Subject: Re: CFT: new trunk(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2007 19:45:47 -0000 Andre Oppermann wrote: > Andrew Thompson wrote: >> On Thu, Apr 12, 2007 at 07:39:00AM +0200, Ian FREISLICH wrote: >> >> 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