From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcel Holtmann Date: Wed, 26 Nov 2008 05:24:47 +0000 Subject: Re: [PATCH] netdev: generate kobject uevent on network state transitions Message-Id: List-Id: References: <20081124150347.73050f98@extreme> <20081124201440.0e4d61cc@extreme> <20081125.010943.205685748.davem@davemloft.net> In-Reply-To: <20081125.010943.205685748.davem@davemloft.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: David Miller Cc: shemminger@vyatta.com, bhutchings@solarflare.com, kay.sievers@vrfy.org, linux-hotplug@vger.kernel.org, netdev@vger.kernel.org Hi Dave, >>>> 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 > ... >>> 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