On Sun, 31 Oct 1999 19:25:09 -0500, Paul W. Abrahams wrote:
Let me turn the question around. When is it better to include something in the kernel rather than load it as a module (assuming the kernel configuration allows you to load it as a module)?
As stated in previous emails, there are certain components that *must* be implemented by the kernel itself, such as the device type and file system that / resides on. In my case, that's IDE disk and ext2fs (as many, many other systems are). If you had, say, an Adaptec 2940 SCSI controller that you / disk was controlled by, you'd need aic7xxx built into the kernel, not as a module. Most other devices, such as other SCSI controllers (even if they are responsible for /home, /usr, or other file systems), ethernet cards, sound cards, or any extraneous IrDA, serial devices, etc, may generally be implemented as modules. Some hardware (though rare) simply cannot be accessed through modules, but the 2.2 kernel does most devices quite nicely. -- -=|JP|=- (Resident GNUbie) Jon Pennington | SuSE Linux 6.2 -o) super-suser@excite.com | Kernel 2.2.10 /\\ Kansas City, Missouri | AMD K6-III 450 _\_V ________________________________________________________________ Get FREE voicemail, fax and email at http://voicemail.excite.com Talk online at http://voicechat.excite.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/