Segher, what is the the 'other alias' mechanism you are referring
to that should be dropped?  Is it this proposed linux,network-index
property?  or something else?

Just the

	pic0: pic@700 {
		...
	}

labeling thing -- it becomes redundant when the flat tree
stuff would support OF-style aliases, so it can be phased
out then.

For who doesn't know the aliases thing, it looks like this:

/ {
	aliases {
		pic0 = "/some/path/to/pic@700";
		pic1 = "/some/path/to/pic@800";

		enet  = "/some/path/to/some/ethernet";
		enet0 = "/some/path/to/some/ethernet";
		enet1 = "/some/path/to/some/other/ethernet";
		enet2 = "/some/path/to/yet/another/ethernet";
	
etc.  Note you can have multiple aliases to the same
node, that comes in quite handy sometimes (like "disk"
is the default boot disk, ...)

Path name resolution looks at the aliases whenever
a path name doesn't start with a '/' character.


Segher