linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Fwd: Linux 2.4.0ac7]
Date: Sat, 13 Jan 2001 15:24:34 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-97939937832510@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97927164317434@msgid-missing>

> > > Can you please send us a reality check?
> > > What exactly do we need in a test kernel?
> >
> > We need Matt's patch and Keith's hotplug patch;
> > paired with modutils 2.4.1 and with updated
> > usermode hotplug scripts.
> 
> I just noticed an important oversight in your 
> current hotplug README.  It doesn't state that
> hotplug.functions needs to be copied to /sbin
> and made executable just like /sbin/hotplug does.

Because it doesn't.  Extract the whole package
to /etc/hotplug, and only move "hotplug" to /sbin.

I suspect I'll provide an RPM to avoid all such
problems.  It'd be great if someone would also
volunteer to put together "apt" support (please
synch with me on the release points).


> One more thing.  I notice that the requirement for
> the 2.4.1 modutils is added to Documentation/Changes 
> by Kieth's patch, but I since there is now a 
> dependency on the latest hotplug package, I think 
> it is time to add linux-hotplug documentation to
> Changes.

Well, any hotplug package could work.  I'd rather
hold off just a bit on this one, until everything
works again.


> Lastly, Documentation/usb/hotplug.txt should be
> updated to include instructions on where to get
> the latest hotplug script and specific information
> on installing this latest version of the scripts.

I'll gladly update this and DOcumentation/Configure.help
to point to the linux-hotplug.sourceforge.net website,
after it's available there.

- Dave




_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2001-01-13 15:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12  1:43 [Fwd: Linux 2.4.0ac7] Miles Lane
2001-01-12  4:03 ` Keith Owens
2001-01-12  5:45 ` Miles Lane
2001-01-12 16:12 ` David Brownell
2001-01-13  5:32 ` Miles Lane
2001-01-13  5:57 ` Miles Lane
2001-01-13  7:50 ` Brad Hards
2001-01-13  8:52 ` Miles Lane
2001-01-13 15:24 ` David Brownell [this message]
2001-01-13 16:48 ` David Brownell
2001-01-13 19:57 ` 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=marc-linux-hotplug-97939937832510@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 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).