On Tue, Apr 22, 2008 at 10:29 PM, Peter Memishian <peter.memishian at sun.com> wrote: > > 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?
"Brilliant!" If you ask me, this is a prime opportunity to make things a little friendlier for folks coming from the GNU/Linux world. We could name the interfaces eth0, eth1, eth2, eth3, etc. That would certainly make things easier on new users/developers coming from that background. I personally prefer the more generic net0, net1, net2, etc. but the former is far more welcoming for transitioning users. -- Shawn Walker "To err is human -- and to blame it on a computer is even more so." - Robert Orben
