Folks,
As some of you may be aware, Clearview Nemo Unification and Vanity Naming
integrated into Nevada build 83. Among other advantages, the "vanity
naming" feature allows us to finally[1] move away from the current chipset
alphabet soup we have for network interface names, and instead standardize
on simple names like net0/net1. For more background, see:
http://www.opensolaris.org/os/project/clearview/uv/
http://www.opensolaris.org/os/project/clearview/uv/howto
In Nevada, backward compatibility concerns have stopped us from changing
the default naming convention, so one is still stuck with unintelligible
names like e1000g2. However, Indiana's experimental nature seems to make
it an ideal vehicle for making such a change, and its target userbase
seems suited for benefitting from such a change (e.g., networking
procedures aimed at new adoptees could simply assume the first network
interface is net0, rather than using placeholder interface names).
Thoughts?
PS. Please note that device information is still available -- e.g.,
post-build-83, "dladm show-phys" will show the underlying device
(e.g. e1000g2) associated with each link. Ongoing work (such as
NWAM's GUI) will likely provide detailed hardware information about
each network interface.
[1] This happened forever ago for other hardware like disks -- can one
imagine having /dev/seagate0 and /dev/maxtor1? Yikes.
--
meem
