On Sat, Mar 29, 2014 at 8:37 PM, David Miller wrote:
> From: Tom Gundersen
> Date: Sat, 29 Mar 2014 10:46:02 +0100
>
>> The issue I see with that is that there are several ways to generate
>> predictable names, and the user may want to chose between them, so
>> this is arguably policy that should
From: Tom Gundersen
Date: Sat, 29 Mar 2014 10:46:02 +0100
> The issue I see with that is that there are several ways to generate
> predictable names, and the user may want to chose between them, so
> this is arguably policy that should not be in the kernel. If you don't
> think that's a problem,
On Sat, Mar 29, 2014 at 2:42 AM, David Miller wrote:
> From: Tom Gundersen
> Date: Fri, 28 Mar 2014 23:39:57 +0100
>
>> You mean coordinate with each other in userspace? If so, I still don't
>> see how this can ever be anything else than fragile. It will depend on
>> each userspace component actu
From: Tom Gundersen
Date: Fri, 28 Mar 2014 23:39:57 +0100
> You mean coordinate with each other in userspace? If so, I still don't
> see how this can ever be anything else than fragile. It will depend on
> each userspace component actually opting in to whatever scheme we
> devise, and does so cor
On Fri, Mar 28, 2014 at 10:21 PM, David Miller wrote:
> From: Tom Gundersen
> Date: Fri, 28 Mar 2014 21:51:53 +0100
>
>> On Fri, Mar 28, 2014 at 7:54 PM, David Miller wrote:
>>> From: David Herrmann
>>> Date: Wed, 26 Mar 2014 14:05:13 +0100
>>>
The main use-case is to allow udev to skip ap
From: Tom Gundersen
Date: Fri, 28 Mar 2014 21:51:53 +0100
> On Fri, Mar 28, 2014 at 7:54 PM, David Miller wrote:
>> From: David Herrmann
>> Date: Wed, 26 Mar 2014 14:05:13 +0100
>>
>>> The main use-case is to allow udev to skip applying reliable ifnames to
>>> virtual
>>> devices. For instance
From: David Herrmann
Date: Fri, 28 Mar 2014 20:34:47 +0100
> However, as mentioned in the discussions on v1, there're more
> use-cases than that. Imagine a 3rd party initrd renames a
> network-device early, if udev runs in the main system, we would rename
> the device again. If we could detect th
On Fri, Mar 28, 2014 at 7:54 PM, David Miller wrote:
> From: David Herrmann
> Date: Wed, 26 Mar 2014 14:05:13 +0100
>
>> The main use-case is to allow udev to skip applying reliable ifnames to
>> virtual
>> devices. For instance, if wifi-P2P devices are created, wpas already
>> provides a
>> su
Hi
On Fri, Mar 28, 2014 at 7:54 PM, David Miller wrote:
> udev can look at the device type, and policies can be defined that key
> off of that device type, entirely in userspace.
Regarding wifi-P2P devices, udev can indeed use nl80211 to get the
exact IF-type. An attribute would be much easier t
From: David Herrmann
Date: Wed, 26 Mar 2014 14:05:13 +0100
> The main use-case is to allow udev to skip applying reliable ifnames to
> virtual
> devices. For instance, if wifi-P2P devices are created, wpas already provides
> a
> suitable naming-policy and udev shouldn't touch these devices. Sam
Hi
This is v5 of the netdev naming-policy series. You can find v4 here:
http://article.gmane.org/gmane.linux.kernel/1668161
Changes since v4:
- none
This series implements a new sysfs attribute for netdevs called
"name_assign_type". It provides an integer that describes where an interface
na
11 matches
Mail list logo
