All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 26 Feb 2001 22:08:13 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98322600306094@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98309074821805@msgid-missing>

> It would be nice to be able to determine whether an interface
> is created because someone manually loaded the module or whether
> kmod loaded it, but I'm not sure how that would be instrumented.

One thing I'm saying is that such things shouldn't matter.
Intent shouldn't be asked; reliable program systems
rarely have "if (CameFrom (...)) ..." logic.

What should get tested is something explicit, such as
the interface state:  is it already "up", is there a carrier,
does it even need a carrier, and so on.  I don't know
that all the right information is available ... unless you
apply heuristics based on device names.  (Such
heuristics seem to be the only solution for now.)


> > In the 2.5
> > kernels it might be good to make all network interfaces
> > fit into a common initialization model.
> 
> I think you're fundamentally misunderstanding how PPP works; for

I think you're misunderstanding what I'm saying.  But since
network interface operation can't change for 2.4, and I
think that's what you're focussed on, I won't try to clarify.

- Dave


_______________________________________________
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

  parent reply	other threads:[~2001-02-26 22:08 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 [this message]
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-98322600306094@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.