On 15 Feb 2014 19:59, "Kay Sievers" <<a href="mailto:kay@vrfy.org">kay@vrfy.org</a>> wrote: > > On Thu, Feb 13, 2014 at 12:56 AM, <<a href="mailto:Charles_Rose@dell.com">Charles_Rose@dell.com</a>> wrote: > > On 02/12/2014 09:21 AM, Kay Sievers wrote: > >> On Wed, Feb 12, 2014 at 2:12 PM, <<a href="mailto:Charles_Rose@dell.com">Charles_Rose@dell.com</a>> wrote: > >> > From: Charles Rose <<a href="mailto:charles_rose@dell.com">charles_rose@dell.com</a>> > >> > > >> > Dell servers contain a virtual usb nic for systems management. > >> > Name the device 'idrac' to easily identify it. > >> > >> The 75-net-description.rules is doe describe interfaces, not to carry > >> out any policy. > >> > >> Product specific matches do not really belong into default udev rules > >> shipped by systemd, we should not add more of them. > >> > >> They might have a place in the hardware database files. I'm not > >> exactly sure though, how to apply policy from the hwdb to renaming > >> network devices, there is no user like that at the moment. > >> > >> What tool is supposed to find that named interface? Can't it just ship > >> that rule in its own file? > > > The interface is generic in nature and would be used by multiple utilities/applications to access > > the iDRAC. > > > > The web browser, openwsman, ssh might be some of them for now. This can also be used by customers > > with custom scripts (python/shell) to fetch/set systems management information. > > Tom, > > any opinion about adding hardware/device-specific network interface > names to the hwdb, and apply them by default if nothing else specifies > a name? Should be ok, as long as we are very careful about what such names we add to the hwdb. We must somehow be very sure that these devices will always be unique, or we'll create a mess. Cheers, Tom