On Thu, Dec 06, 2001 at 09:55:40PM +, Philip Blundell wrote:
USB is another example of a system that lets you load the protocol modules
independently of port drivers. This is definitely the way parport was intended
USB is different. The USB system is specifically designed for hot
in the game, set the bug to wishlist priority and we'll find a way to work
around the immediate modconf problem in boot-floppies.
I wouldn't call it a workaround as that's how it's supposed to work anyhow.
The only way for it to not work is if the parport_pc module was missing as
lp calls
So, it turns out that the reason parport_pc doesn't get loaded automatically
is that boot-floppies does echo /bin/true /proc/sys/kernel/modprobe, thus
defeating kmod. (This happens in /etc/init.d/rcS on the root disk.)
Perhaps we should set that back to /sbin/modprobe while running modconf.
On Thu, Dec 06, 2001 at 08:40:50PM +, Philip Blundell wrote:
In message [EMAIL PROTECTED], Herbert Xu writes:
Why should lp load if your haven't loaded the low level modules?
Because you might want to load them later. It's not supposed to be
sensitive to the order in which these
In message [EMAIL PROTECTED], Herbert Xu writes:
NFS is completely different, it's not a hardware device. IMHO you should
compare it with other parport devices, e.g., pd/pf/etc. They all fail to
load unless you actually have the devices present.
Right, but that doesn't mean they _should_. The
5 matches
Mail list logo
