From: Brad Hards <bhards@bigpond.net.au>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Fwd: Linux 2.4.0ac7]
Date: Sat, 13 Jan 2001 07:50:54 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97937225432009@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97927164317434@msgid-missing>
Miles Lane wrote:
> 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.
>
> 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.
OK, I have 2.4.1pre3 (compiled on one machine, but not the hotplug test
laptop machine), modutils 2.4.1 and the CVS hotplug from
http://www.linux-usb.org
Is the CVS OK with 2.4.1 pre3, or are there additional patches (Keith's
and Matt's patches)?
I noted that the hotplug/README states:
For more information about Linux hotplugging:
http://linux-hotplug.sourceforge.org/
That should be .net, rather than .org
It lacks a bit of detail too :)
I am planning to do the install on my laptop at the USB BOF for
linux.conf.au, where I won't have a lot of time/tools/privacy to sort
out my problems, so I could use some tips here...
Brad
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-13 7:50 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 [this message]
2001-01-13 8:52 ` Miles Lane
2001-01-13 15:24 ` David Brownell
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-97937225432009@msgid-missing \
--to=bhards@bigpond.net.au \
--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).