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 19:43:30 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105544767027798@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105529235705938@msgid-missing>
Bill Nottingham wrote:
>>>We don't include ones, but the hotplug scripts we ship will use
>>>the USB one if they it's there (the pci one is commented out,
>>>sorry.)
>>
>>what values do they contain? It seems hotplug can perfectly work without
>>them.
>
>
> Whatever someone wants, I suppose. We just use the stock scripts that
> refer to them.
And Olaf had the right idea to ship the /etc/sysconfig/* files that
are referenced. I'm just thinking that just a "usb" file would be
enough; nothing much is shared between the different agents, and
having a "hotplug" file with only USB-specific options seems wrong.
>>And it would make much sense to load hid.o, mousedev.o and keybdev.o per
>>default anyway, so this x11 hack is obsolete. Or is there a reason why
>>one would not load the usb hid drivers? I dont see any.
>
>
> We actually load them outside of the usb hotplug framework.
Which is a bit of a problem in terms of getting convergence. It'd
be good to have a standard way to start up USB, and that's exactly
what "/etc/hotplug/usb.rc start" was intended to do.
If I understand why RedHat's rc.sysinit does it that way, there are
a few reasons. One is (a) to use "kudzu" static config data, which
knows various USB-specific, overlapping /etc/sysconfig/usb a bit.
The better (IMO) reason is (b) to ensure that USB keyboards/mice can
be used during system bootstrap, if the kernel (or its initrd) didn't
build them in. That's early for "usb.rc start", since hotplug agents
often can't run that early (filesystems unmounted or readonly, etc).
And it also doesn't use the same conventions as "usb.rc" does.
Seems like we would win by having an "rc.usb boot" way for RC scripts
to solve that input device problem, calling it later to handle the
"coldplug" problem like "rc.usb start" does today (synthesizing the
events that couldn't be handled that early).
- 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 19:43 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 [this message]
2003-06-12 19:45 ` Bill Nottingham
2003-06-12 20:10 ` David Brownell
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-105544767027798@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).