From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sun, 02 Jan 2005 00:43:32 +0000 Subject: Re: Hotplugging ethernet cables. Message-Id: <1104626612.6801.45.camel@localhost.localdomain> List-Id: References: <41D74A49.2060607@are-b.org> In-Reply-To: <41D74A49.2060607@are-b.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Sun, 2005-01-02 at 02:11 +0100, oliver wrote: > They mention ifplugd and even though this seems to work reasonably, I > was wondering why hotplugging doesn't support ethernet hotplugging > nativly? Hotplug supports device add and remove, not state changes of hardware. > As I understand it the hotplugging daemon responds to events > created by several devices, where the ifplugd polls and the device. There is no such daemon involved in the hotplug handling. Hotplug is driven by more or less stateless scripts invoked by the kernel. The network link state changes can be received on a netlink socket from the kernel. These events are not hotplug events and don't really fit into the model of linux hotplug. Kay ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel