From owner-freebsd-current Mon Aug 3 04:36:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10365 for freebsd-current-outgoing; Mon, 3 Aug 1998 04:36:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10359 for ; Mon, 3 Aug 1998 04:36:37 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id NAA26131 for ; Mon, 3 Aug 1998 13:41:07 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id NAA00469 for ; Mon, 3 Aug 1998 13:41:47 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id NAA04050; Mon, 3 Aug 1998 13:39:16 +0200 (CEST) Message-ID: <19980803133915.52291@deepo.prosa.dk> Date: Mon, 3 Aug 1998 13:39:15 +0200 From: Philippe Regnauld To: freebsd-current@FreeBSD.ORG Subject: Ethernet interface names Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a question+comment: Would it be very difficult to implement abstract naming on ethernet devices, à la Linux ? For example: eth0, eth1 instead of ed0, le1 I know there are potential problems with this (i.e.: user confusion, especially when building fw rules), but they already exist with multiple interfaces of the same type (ed0, ed1, ed2)... The advantage would be that you could pull out a dead card, plug a new (not necessarily of the same model), and there woudln't be any need to edit rc.conf, rc.firewall, etc... (Not that this had bothered me in any way). Also, what are the arguments in favor of _not_ doing this ? -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message