Re: [systemd-devel] Configuring ethernet link fails with No such device

[David Miller]

From: Bob Ham 
Date: Tue, 12 Apr 2016 09:58:12 +0100

> On Mon, 2016-04-11 at 15:46 -0700, Stefan Agner wrote:
> 
>> Or in other words: Is this a Kernel or systemd issue?
> 
> From what I recall, both; an issue with the FEC driver, and issues in
> systemd/udevd's handling of link-level settings.

This is my impression of the situation as well.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Configuring ethernet link fails with No such device

[David Miller]

From: Stefan Agner 
Date: Mon, 11 Apr 2016 15:46:08 -0700

> What is the expectation/definition when link configuration should be
> possible? Only after the network device got opened or before?

Only after it is open.  Drivers almost always have the entire chip in
powerdown state when it is not open, so we wouldn't be able to
properly do link settings even if we wanted to when the device is
closed.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [PATCH] vlan: set sysfs device_type to 'vlan'

[David Miller]

From: Doug Goldstein car...@cardoe.com
Date: Sun, 4 Nov 2012 23:45:56 -0600

 As Ben Greear pointed out this would allow shell scripts and other
 scripting languages to better detect vlans. Kay pointed out that this
 would allow better uevent filters in the future as well. So there are
 some merits to this patch. If you'd prefer I can resubmit with a
 better commit message entailing the reasons behind it.

For the thousandth time:

All of those scripts and other users of this new facility will
need to have backup code to detect vlan devices when this
sysfs thing is not present.

They are already to determine this information already, and
they alreayd have to be ugly to handle EVERY EXISTING KERNEL
ON THE PLANET.

So the effective value is zero.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [PATCH] vlan: set sysfs device_type to 'vlan'

[David Miller]

From: Doug Goldstein car...@cardoe.com
Date: Mon, 5 Nov 2012 00:19:19 -0600

 By this argument we shouldn't ever improve any API or add new syscalls
 since we'll have to have fallback code to handle the old interfaces
 when the new ones aren't available.

It makes sense to add new APIs when existing mechanisms are too
difficult _AND_ code doesn't already exist that works reasonable well
with existing facilities.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [PATCH] vlan: set sysfs device_type to 'vlan'

[David Miller]

From: Doug Goldstein car...@cardoe.com
Date: Mon, 22 Oct 2012 00:53:57 -0500

 Sets the sysfs device_type to 'vlan' for udev. This makes it easier for
 applications that query network information via udev to identify vlans
 instead of using strrchr().
 
 Signed-off-by: Doug Goldstein car...@cardoe.com

You're extremely misguided.  This change, in fact, makes it ten times
harder for such applications to query such devices.

Because now the application has to decide whether it wants to support
EVERY EXISTING SYSTEM OUT THERE or not.  Hundreds of millions of Linux
systems do not provide this attribute.

Applications have to handle the case of not having the 'vlan' device
type available attribute essentially forever.

So providing it in new kernels provides zero value whatsoever.

I'm not applying this patch, sorry.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [PATCH] vlan: set sysfs device_type to 'vlan'

[David Miller]

From: Kay Sievers k...@vrfy.org
Date: Tue, 23 Oct 2012 12:34:11 +0200

 On Tue, Oct 23, 2012 at 8:36 AM, David Miller da...@davemloft.net wrote:
 From: Doug Goldstein car...@cardoe.com
 Date: Mon, 22 Oct 2012 00:53:57 -0500

 Sets the sysfs device_type to 'vlan' for udev. This makes it easier for
 applications that query network information via udev to identify vlans
 instead of using strrchr().

 Signed-off-by: Doug Goldstein car...@cardoe.com

 You're extremely misguided.  This change, in fact, makes it ten times
 harder for such applications to query such devices.
 
 That makes not much sense, really. Every new interface would fall into
 that category. At least I can't see any mis-guidance here. The other
 devtypes for the major netif types are not that much older.

Only interfaces which provide a facility available in another way
fall into this category.

Thanks for the scarecrow, but no.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel