[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPXgP11UEm49edrsyP3pD2HPNZCGRgGTWjSyw5VoqwsQT-UmOw@mail.gmail.com>
Date: Tue, 25 Oct 2011 09:57:00 +0200
From: Kay Sievers <kay.sievers@...y.org>
To: Alexey Gladkov <gladkov.alexey@...il.com>
Cc: David Miller <davem@...emloft.net>, kirill@...temov.name,
netdev@...r.kernel.org, kuznet@....inr.ac.ru, jmorris@...ei.org,
yoshfuji@...ux-ipv6.org, kaber@...sh.net, gregkh@...e.de
Subject: Re: [RFD] Network configuration data in sysfs
On Tue, Oct 25, 2011 at 01:54, Alexey Gladkov <gladkov.alexey@...il.com> wrote:
> 24.10.2011 16:46, Kay Sievers wrote:
>> Kirill, what exactly is the use case? And why what does udev support
>> mean in that context?
>>
>> I doubt that "not having /sbin/ip installed" should be a reason to add
>> and expose complex interfaces in /sys, while we already have a
>> perfectly working native way to do it.
>
> Adding NETLINK_ROUTE in udev is a way to perform some actions in case
> of network events without polling. Now there are only a few specific
> daemons (NM, connman etc) that are listen to the netlink socket and
> setup the network his own way.
I'm not really convinced that udev should be in charge of network
config changes, it's a really complex area. Udev is a generic kernel
device manager, not a network setup manager.
Our point of view is, that all services depending on network state
changes should listen to netlink themselves, and not be worked around
with tools like udev to execute stuff and notify them.
But again, what's the use-case for that you have in mind?
Kay
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists