From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Sun, 25 Feb 2001 23:45:19 +0000 Subject: Re: OT(?) -- Should the net.agent script cause "ifup lo" to be run? Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org I guess I don't see what you mean by "actual hotplug device". What PCI or USB device wouldn't be a hotplug device, why? What "drastic change"? That patch to not make the ppp/isdn/... interfaces go "ifup" is in CVS, by the way. Am I correct that the issue is that those devices get brought "up" differently than eth* interfaces? And "lo" has yet a third kind of init model magic? - Dave ----- Original Message ----- From: "Bill Nottingham" To: Sent: Sunday, February 25, 2001 1:37 PM Subject: Re: OT(?) -- Should the net.agent script cause "ifup lo" to be run? > Miles Lane (miles@megapathdsl.net) said: > > the hotplug scripts. If the answer is "almost > > none," then how should running of "ifup lo" > > get triggered when "ifup ethN" is getting run > > from /etc/hotplug/net.agent? > > I'd almost argue that the hotplug scripts should be > doing *less*. > > The current feature of automatically bringing up any interface > on device creation removal is OK for *actual* hotplug interfaces, > but for other interfaces is: > > a) a drastic change in behavior > b) annoying > c) seriously broken for non-hardware-tied interfaces (ppp/slip/plip) > > Bill > _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel