From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Nottingham Date: Thu, 12 Jun 2003 19:45:19 +0000 Subject: Re: [linux-usb-devel] Re: [PATCH] hotplug usb.rc changes Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org David Brownell (david-b@pacbell.net) said: > > 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. It's actually only for the second reason; so that the keyboard is there if (for example) fsck fails. Bill ------------------------------------------------------- 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