* Gregory Edigarov <greg@bestnet.kharkov.ua> [2010-04-19 14:56]:
quoted text
> On Mon, 19 Apr 2010 08:34:12 -0400
> Simon Perreault <simon.perreault@viagenie.ca> wrote:
> 
> > On 2010-04-19 08:31, Gregory Edigarov wrote:
> > > sometimes it is better and necessary to have interfaces named under
> > > one standartized name like fether0... fetherN for example
> > 
> > Why? And how can groups not accomplish that?
> > 
> > Simon
> suppose you need to configure some interfaces of different makes:
> em0, bge0, rl0, ath0
> to have name like:
> ether0, ether1, ether2, ether3...
> so you may plug in another card instead of ether2 for example.
> without interface renaming you will end up rewriting the whole seciton
> of your interface configuration script, while with it - you will only
> have to change one line:
> ifconfig bge0 name ether0 

your what?
mv hostname.em2 hostname.em3 is not black magic.

-- 
Henning Brauer, hb@bsws.de, henning@openbsd.org
BS Web Services, http://bsws.de
Full-Service ISP - Secure Hosting, Mail and DNS Services
Dedicated Servers, Rootservers, Application Hosting