From owner-freebsd-current Wed Jan 27 23:15:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27971 for freebsd-current-outgoing; Wed, 27 Jan 1999 23:15:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.ucla.edu (Ulfus.CS.UCLA.EDU [131.179.48.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27965 for ; Wed, 27 Jan 1999 23:15:21 -0800 (PST) (envelope-from scottm@ulfus.cs.ucla.edu) Received: from ulfus.cs.ucla.edu (localhost [127.0.0.1]) by cs.ucla.edu (8.8.7/8.8.8) with ESMTP id XAA10746; Wed, 27 Jan 1999 23:14:59 -0800 Message-Id: <199901280714.XAA10746@cs.ucla.edu> X-Mailer: exmh version 2.0.2 To: Archie Cobbs cc: freebsd-current@FreeBSD.ORG Subject: Re: DEVFS, the time has come... In-Reply-To: Your message of "Wed, 27 Jan 1999 22:58:18 PST." <199901280658.WAA24316@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 Jan 1999 23:14:58 -0800 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think Solaris (?) requires you to do this, it's called "plumbing > your interfaces" or something (according to Julian). Solaris requires "interface plumbing" as the result of STREAMS; you have to push IP on top of the interface driver. For all intents and purposes, the device name identifies a particular driver (i.e. "le", "qe", "hme", "fa", &c). The number identifies an instance of the device which depends on probe order. [*] Fortunately, the BSD world avoided this particular form of brain damage, thank ! OTOH, as ph--ked as STREAMS happens to be, it does have a certain appeal wrt dynamically building and tearing down network stacks. The AT&T model just didn't have IP in mind when it was designed. -scooter [*] I'd written a hacked version of ifconfig based on the output of 'truss' and managed to get it right in a limited way, as in ifconfig only plumbs IP on top of devices. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message