Peter Memishian wrote:
> In Nevada, backward compatibility concerns have stopped us from changing
> the default naming convention, so one is still stuck with unintelligible
> names like e1000g2.
So given that this can't happen until the second release of Indiana, will
that also have compatibility concerns? Will upgrade from the first Indiana
to the second one have to know about this to migrate /etc/hostname.e1000g2 to
/etc/hostname.eth2 or are we just assuming all Indiana users use NWAM and have
no config files to migrate?
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
