Would it be possible for an upgrade not to rename to the new nomenclature, but a clean install would? With more and more configuration being moved into dladm, it also seems its getting easier to create an auto-migration facility for the nomenclature?
Also, having generic names would make it much easier to replace a NIC with one of a different chipset without changing all of the configurations. So +1 for net0, etc. being the default. -J On Wed, Apr 23, 2008 at 9:35 AM, Alan Coopersmith <[EMAIL PROTECTED]> wrote: > 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- [EMAIL PROTECTED] > Sun Microsystems, Inc. - X Window System Engineering > > > > _______________________________________________ > indiana-discuss mailing list > indiana-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/indiana-discuss > _______________________________________________ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
