From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: OT(?) -- Should the net.agent script cause "ifup lo" to be run?
Date: Sun, 25 Feb 2001 23:45:19 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98314493318723@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98309074821805@msgid-missing>
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" <notting@redhat.com>
To: <linux-hotplug-devel@lists.sourceforge.net>
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
next prev parent reply other threads:[~2001-02-25 23:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 8:47 OT(?) -- Should the net.agent script cause "ifup lo" to be run? Miles Lane
2001-02-25 10:03 ` Adam J. Richter
2001-02-25 21:37 ` Bill Nottingham
2001-02-25 23:45 ` David Brownell [this message]
2001-02-26 0:38 ` Bill Nottingham
2001-02-26 3:40 ` David Brownell
2001-02-26 4:12 ` Bill Nottingham
2001-02-26 4:14 ` Bill Nottingham
2001-02-26 6:59 ` Miles Lane
2001-02-26 7:17 ` Miles Lane
2001-02-26 16:50 ` David Brownell
2001-02-26 17:31 ` David Brownell
2001-02-26 19:52 ` Bill Nottingham
2001-02-26 22:08 ` David Brownell
2001-02-26 22:14 ` David Brownell
2001-02-26 22:17 ` David Brownell
2001-02-26 22:24 ` Bill Nottingham
2001-02-26 22:30 ` Bill Nottingham
2001-02-26 22:48 ` David Brownell
2001-02-27 6:23 ` Miles Lane
2001-02-27 6:46 ` Miles Lane
2001-02-27 7:17 ` Miles Lane
2001-02-27 7:23 ` Miles Lane
2001-02-27 7:54 ` David Hinds
2001-02-28 5:14 ` Miles Lane
2001-02-28 16:50 ` David Brownell
2001-02-28 17:24 ` David Hinds
2001-03-01 4:37 ` David Brownell
2001-03-01 5:27 ` Bill Nottingham
2001-03-01 5:34 ` Bill Nottingham
2001-03-01 5:45 ` David Hinds
2001-03-01 17:27 ` David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-98314493318723@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.