From: Valdis.Kletnieks@vt.edu
To: Stephen Hemminger <shemminger@osdl.org>
Cc: linux-kernel@vger.kernel.org, chris.ricker@genetics.utah.edu
Subject: Re: Hotplug/PPP oddness n 2.5.73-mm1 - scripts not running, bad event
Date: Wed, 25 Jun 2003 23:07:43 -0400 [thread overview]
Message-ID: <200306260307.h5Q37hCV003595@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 25 Jun 2003 14:58:35 PDT." <20030625145835.14206ec7.shemminger@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
On Wed, 25 Jun 2003 14:58:35 PDT, Stephen Hemminger said:
> > This patch causes an external script API change.
> > Because network device go through the standard path, the action passed to t
he script
> > is no longer register or unregister but is now "add" or "remove" like other
devices.
> > This is a good thing. When testing (at least on RHAT) just change /etc/hot
plug/net.agent
> > case statement:
> >
> > case $ACTION in
> > add|register)
Yeah, that was the fairly obvious fix... now who's job is it to fix it on the
hotplug website, and when? Also, who gets to update the currently non-existent
entry in Documentation/Changes (i've cc'ed Chris Ricker)?
Or should this just get tacked on the "to do before 2.6.0 comes out" list for
now?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-06-26 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 20:28 Hotplug/PPP oddness n 2.5.73-mm1 - scripts not running, bad event Valdis.Kletnieks
2003-06-25 21:58 ` Stephen Hemminger
2003-06-26 3:07 ` Valdis.Kletnieks [this message]
2003-06-28 0:16 ` Greg KH
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=200306260307.h5Q37hCV003595@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=chris.ricker@genetics.utah.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.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).