[ That's why not to crosspost lists! Please send further
follow-ups just to the "SourceForge" list, or the SUSE one if
you're not on SourceForge. ]
> I'm not using anything so high-tech as I couldn't make those work.
That is, the fstab/modules.conf stuff didn't work for you?
> Now, I
> compile in the core code plus the HID code I need for my keyboard & mouse. My
> printer and scanner modules are then dynamically loaded as part of my startup
> sequence (via a simple script in /etc/rc.d/rc5.d that modprobe's them).
Right, this rc.usb can be invoked through rc5.d too, but
it seemed that stuff like USB keyboards should "always" be
usable even when they're modular. Hence rc.sysinit as
my preferred solution, after a bout with single user mode.
It works on a different "partially modular" configuration,
and likely on that one. (I've had everything except the
core be modular, everything including the core be modular,
and the core plus other random bits be modular.)
> I'd be interested in more high tech solutions (especially those driven by the
> addition or removal of the device). It strikes me that this ought to be do-able
> with some kind of daemon and some help from the driver (a signal to the daemon
> process for example).
In fact, that's what this script will do in conjunction with a
USB daemon invoking /etc/usb/policy script to autoload drivers.
The very latest jUSBD (from CVS) works better than the last one
released (http://jusb.sourceforge.net), but I may fix that soon.
And that kUSBD patch might work on post-ac10 releases too! :-)
It could be factored a bit differently, but I like the model
that as soon as USB is started everything "just works". For
stuff that's needed earlier, link it statically (as you do).
- Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
