Date: Wed, 11 Apr 2001 06:56:32 -0700 From: Michael O'Henly <michael@tenzo.com> To: freebsd-questions@FreeBSD.ORG Subject: Re: Naming ethernet NICs Message-ID: <01041106563200.03731@pravda.tenzo.net> In-Reply-To: <009701c0c288$cfc4dce0$0508a8c0@lofi.dyndns.org> References: <000e01c0c24a$9c9edfc0$1401a8c0@tedm.placo.com> <009701c0c288$cfc4dce0$0508a8c0@lofi.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 11 April 2001 06:10, Michael Nottebrock wrote: [...] > One disadvantage of the BSD-type naming convention is that one does > end up putting rl0's, ed0's and the like into config-files or batches, > which have to be changed if the hardware changes, for example a > '/usr/local/sbin/dhcpd dc0' in /etc/rc.local or a 'set device > PPPoE:rl0' in /etc/ppp/ppp.conf, or (the most annoying) if you happen > to have lots of 'via <interface>' statements in your ipfw ruleset. Yes, this is what I meant. The reason I raised the questions is that I'm configuring a simple firewall for my home network and so far I've "hardcoded" NIC names in three or four different places. Presumably if I ever replaced a NIC with a different type/driver, I'd have to rediscover all the places I'd used the old name. M. -- Michael O'Henly TENZO Design To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01041106563200.03731>