On 29/03/13 13:38, Diego Elio Pettenò wrote:
> On 29/03/2013 12:29, Samuli Suominen wrote:
>> One you can control, the another you can't. So still not FUD.
>
> You do not really control it any more than the kernel. The fact that me
> and you can edit an udev ruleset to "control" it, does not mean that
> most users see it as a black box.

I don't agree with that, /etc/udev/rules.d and overriding udev rules is 
very basic administration, very basic...
I'll put a bit more trust on our users.

> The news item reads better. I would still either avoid showing the
> NET_PATH example or describe that that is not the final result because
> on a laptop, NET_PATH almost certainly will *not* match the final
> interface name:
>
> flame@saladin~ % udevadm test-builtin net_id /sys/class/net/eno1 2>/dev/null
> ID_NET_NAME_MAC=enx0026b9d7bf1f
> ID_OUI_FROM_DATABASE=Dell Inc
> ID_NET_NAME_ONBOARD=eno1
> ID_NET_LABEL_ONBOARD=en Onboard LAN
> ID_NET_NAME_PATH=enp0s25
>
> And I would not expect users to all go read the wiki and try to figure
> out why you said it would be named enp0s25 when it gets the name eno1.
>

Nod.
Attached new version again, more generic than before.
Hope it'll do what it's meant to do... push users into right direction...
It's not meant to be a complete documentation or rewrite of the upstream 
wiki page :-p
Just a push...