From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: ignore some specific interfaces, such as non-hotpluggable eth*,
Date: Mon, 04 Feb 2002 21:03:03 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101285672914209@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101284314202868@msgid-missing>
> Although, I think pattern "ipsec*" should be configurable in
> /etc/default/hotplug (or /etc/sysconfig/hotplug on RedHat, maybe),
> does it make sense to apply such patch to net.agent?
Until the network device initialization model acquires some
consistency, I don't see a better solution than continuing to
add more special cases. Which won't work in all cases,
but I think that won't be a risk for the "ipsec" interfaces
(132224) or ppp ones in the way it would be for "eth"
interfaces (108857).
FYI with 108857 I think the bug might best be fixed in
the "ifup" code: if hotplug is doing its job, then that any
"ifup does modprobe" usage should expect that, and so
it should stop after the modprobe -- or find a way to tell
hotplug it should _in this case_ ignore that interface.
- Dave
> See more detail, look at http://bugs.debian.org/hotplug
Some of those might better be redirected upstream,
to the sf.net linux-hotplug bug database ... :)
> #108857: hotplug should not invoke ifup ethX for built in interfaces
> #132224: hotplug should ignor ipsec interfaces
_______________________________________________
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
prev parent reply other threads:[~2002-02-04 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 17:17 ignore some specific interfaces, such as non-hotpluggable eth*, ipsec* Fumitoshi UKAI
2002-02-04 21:03 ` David Brownell [this message]
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-101285672914209@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.