Thread (12 messages) 12 messages, 5 authors, 2008-11-26

Re: [PATCH] netdev: generate kobject uevent on network state transitions

From: Marcel Holtmann <marcel@holtmann.org>
Date: 2008-11-26 05:24:47

Hi Dave,
quoted
quoted
quoted
It is easier for some applications to deal with text based  
interfaces
like uevent, rather than using netlink to listen for events.

Note, this does not deal with network namespaces but that is a  
generic
problem that already exists with kobjects (see rename events).

Signed-off-by: Stephen Hemminger <redacted>
...
quoted
quoted
do we wanna copy just what ifconfig shows or do we might be a more
intelligent and have separate variables like RUNNING=1 etc.?
Was arbitrary choice to just use same flags as existing ifconfig.
What ever feels best I guess...
So what do folks want me to do here?  Should I put Stephen's
latest patch in, or do we want to make some kind of flags change?
I am thinking of using per value variables. My personal choice.

Kay, any pointers or opinions from you?

Regards

Marcel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help