From owner-freebsd-current Thu Jan 28 09:44:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17510 for freebsd-current-outgoing; Thu, 28 Jan 1999 09:44:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17501 for ; Thu, 28 Jan 1999 09:44:29 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id JAA19684 for freebsd-current@freebsd.org; Thu, 28 Jan 1999 09:43:33 -0800 (PST) (envelope-from dhw) Date: Thu, 28 Jan 1999 09:43:33 -0800 (PST) From: David Wolfskill Message-Id: <199901281743.JAA19684@pau-amma.whistle.com> To: freebsd-current@FreeBSD.ORG Subject: Re: DEVFS, the time has come... In-Reply-To: <199901272212.XAA03458@yedi.iaf.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Wilko Bulte >Date: Wed, 27 Jan 1999 23:12:18 +0100 (CET) >Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this >just a matter of taste or is there more to it? I for one don't see any >advantage in eth[0-9] style device naming. It's a matter of whether you want the name to reflect the implementation vs. the function. For someone involved in the details of the implementation, being (acutely!) aware of those details can be very important. For someone who merely wants to have a certain physical port on the machine connected to a particular network, that level of detail is not always appropriate. It depends on your focus. Cheers, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message