> Er... Well, the traditional solution has been "don't build it into your
> kernel if you don't want it", but in the case of stock kernels, that
> isn't always an option, I suppose. Theoretically, the two devices
> shouldn't step on each other, but this is a computer. Theory is so far
> removed
Bryan Whitehead wrote:
>
> Is there a way I can disble a part of the kernel that is compiled into the
> kernel? For example I'd like to pass this to lilo: "usb=disable" and then
> the usb code is not loaded even though USB has been built into the kernel.
>
> Is such a feature stupid? Or has this
Is there a way I can disble a part of the kernel that is compiled into the
kernel? For example I'd like to pass this to lilo: "usb=disable" and then
the usb code is not loaded even though USB has been built into the kernel.
Is such a feature stupid? Or has this already been implemented?
It would
3 matches
Mail list logo