vitko <[EMAIL PROTECTED]> writes:

>> I only know of two (in my eyes) valid reasons to build your own kernel:
>> 
>> 1. you hate initrd since it too often doesn't work
>> 2. you need/want some extra patch
>
> Two more reasons:
>
> 1) I don't like seeing errors / misdetected hardware in kernel messages.
> Far too many times I've seen loading drivers for hardware that was never
> there. As for kernel, I want it to be clean and do its work for the
> exact hardware I use,

Haven't seen that with the modularized kernels and discover. Matching
the pci IDs to hardware works well.

> 2) The may be some hardware I don't want / need supported, typically
> multimedia devices on servers. The less code runs, the smaller
> possibility something can go wrong in unexpected places.

You can blacklist modules.

> Just my USB 0.02.
>
> Vit

MfG
        Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to