From owner-freebsd-arch Mon Jun 11 11:42:48 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 409DF37B401; Mon, 11 Jun 2001 11:42:40 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f5BIetf53922; Mon, 11 Jun 2001 14:41:00 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 11 Jun 2001 14:40:54 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Brooks Davis Cc: Peter Wemm , Brian Somers , hackers@FreeBSD.ORG, Poul-Henning Kamp , freebsd-arch@FreeBSD.ORG Subject: Re: cloning network interfaces In-Reply-To: <20010611092147.A7059@Odin.AC.HMC.Edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 11 Jun 2001, Brooks Davis wrote: > On Mon, Jun 11, 2001 at 08:27:37AM -0700, Peter Wemm wrote: > > Personally, I'd prefer create/destroy instead of plumb/unplumb. The Solaris > > plumb command is for doing 'STREAMS plumbing' - ie: connecting all the > > streams pipes and modules together. Creating/deleting interfaces on > > BSD systems IMHO has nothing in common with that concept. We are > > creating/destroying interfaces, not connecting/disconnecting streams > > nodes (plumbing). > > I've made create/destory the default names with plumb and unplumb > standing in as SysV compatability parameters because that seems to be > the ifconfig way. The diff at: > > http://www.one-eyed-alien.net/~brooks/FreeBSD/gif.diff > > has been updated. I'm still thinking about adopting the NetBSD > SIOIF{CREATE,DESTORY} interface. An advantage to also supporting the ioctl interface is that it permits interface cloning to be used on systems where devfs is not used, or where there are parts of the system where devfs is unavailable (i.e., various forms of chroots). I think devfs is cool and all, but given the existance of fairly sensical non-devfs ways to do things, I'm tempted suggest supporting them also. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message