From owner-freebsd-hackers Mon Jun 11 11:50:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id ED8AA37B407; Mon, 11 Jun 2001 11:50:01 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f5BInpr23808; Mon, 11 Jun 2001 20:49:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: Brooks Davis , Peter Wemm , Brian Somers , hackers@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG Subject: Re: cloning network interfaces In-Reply-To: Your message of "Mon, 11 Jun 2001 14:40:54 EDT." Date: Mon, 11 Jun 2001 20:49:51 +0200 Message-ID: <23806.992285391@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Robe rt Watson writes: >> 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. As I already said: a device with no other precense in /dev has only "quick&dirty" reasons for using DEVFS cloning. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message