From: Bill Nottingham <notting@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: OT(?) -- Should the net.agent script cause "ifup lo" to be run?
Date: Thu, 01 Mar 2001 05:34:56 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98342501503711@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98309074821805@msgid-missing>
David Brownell (david-b@pacbell.net) said:
> > Please clarify. What I'm saying is that PPP is so fundamentally different
> > that you *can't* fit it into the ethernet model, even in a 2.5 framework,
> > unless you're willing to redesign the whole kernel/pppd/dialer interaction,
> > which would be a lot of code and would probably meet with a lot of
> > resistance.
>
> I didn't say turn PPP into Ethernet, or vice versa, but find the
> commonality. It's there somewhere in the OS ... if some parts
> of the initialization model are only available implicitly by using
> interface names (which can change, someone said) then it should
> be made explicit, so tools can work without heuristics. (OK,
> some folk really like heuristics there, I don't.) If the model is
> needlessly complex, simplify it.
>
> For one example, it can be argued that it's wrong for the kernel
> to report that "ppp0" has been "registered". It's in some config
> file somewhere, "registered" but just not known to the kernel.
> Maybe "register" is the wrong network hotplug event to report
> in such a case, hmm?
Maybe. It technically is a registration event, though, in that's
when the device is first registered. I guess the distinction
is that a ppp device is registered as *part* of the process of
bringing it up. Ethernet devices aren't.
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-03-01 5:34 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
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 [this message]
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-98342501503711@msgid-missing \
--to=notting@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).