From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [PATCH] hotplug usb.rc changes
Date: Thu, 12 Jun 2003 20:10:10 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105544889729336@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105529235705938@msgid-missing>
Bill Nottingham wrote:
>
> It's actually only for the second reason; so that the keyboard is
> there if (for example) fsck fails.
So it looks like it'd be a win if "rc.usb boot" did that logic,
without the "coldplug" stuff to handle the system being only
partially booted. RH-specific logic won't be necessary.
Of course there's still that issue of which HCDs to load;
Olaf's patch says that's what the /etc/sysconfig file holds.
RH currently uses /etc/modules.conf for such stuff ... and
a pure hotplug model would use interact with what PCI says
is actually present.
- Dave
-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
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
next prev parent reply other threads:[~2003-06-12 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 0:43 [linux-usb-devel] Re: [PATCH] hotplug usb.rc changes David Brownell
2003-06-11 2:04 ` Bill Nottingham
2003-06-11 6:29 ` Olaf Hering
2003-06-11 16:22 ` Bill Nottingham
2003-06-11 17:00 ` Olaf Hering
2003-06-11 18:15 ` Bill Nottingham
2003-06-12 19:43 ` David Brownell
2003-06-12 19:45 ` Bill Nottingham
2003-06-12 20:10 ` David Brownell [this message]
2003-06-12 20:19 ` Olaf Hering
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-105544889729336@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).