From owner-freebsd-current Thu Jan 28 01:10:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12072 for freebsd-current-outgoing; Thu, 28 Jan 1999 01:10:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12063 for ; Thu, 28 Jan 1999 01:10:19 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA00584; Thu, 28 Jan 1999 09:11:42 GMT Date: Thu, 28 Jan 1999 09:11:42 +0000 (GMT) From: Doug Rabson To: Harlan Stenn cc: "Daniel O'Connor" , Wilko Bulte , current@FreeBSD.ORG, Archie Cobbs Subject: Re: DEVFS, the time has come... In-Reply-To: <20942.917503290@brown.pfcs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Jan 1999, Harlan Stenn wrote: > > Also the eth[0..x] thing means you can replace your ethernet card with a > > new one of a different type without having to look through your config > > code for references to ed0 or whatever. > > Just to ask, what happens when the probe order changes and your multiple > NICs start popping up on the wrong eth port? > > This may be *much* more difficult when one of several cards die (how do you > know which one broke?) and then you replace it and discover the new probe > order is different... > > Or will be be able to wire them down in the config file (which will at > least address part of the problem)? If we did this, there would obviously have to be some kind of wiring system. The same problem exists in a much smaller way for machines with more that one of the same type of card. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message