On Wed Mar 14 2001 at 18:35, mshiju@in.ibm.com wrote: > module. I read somewhere that ISAPNP drivers with ISAPNP enabled in kernel > should only be build as modules so that we can keep the order of execution > . Is this true.? Have any one of you tried this . I'd believe what you have read. The general philosphy is that most device drivers are almost always best built and made available as modules. Besides, there really are distinct advantages in being able to unload device drivers at runtime (eg, you can reconfigure the IRQ or dma etc for the driver by simply unloading and reloading it - without otherwise resorting to a system reboot which would be the case if the driver was compiled into the kernel itself). If you need to load any device drivers before actually booting the kernel itself (eg, an nfsroot kernel which needs an ethernet driver), then that problem is solved by creating (and making available with lilo or bootp or whatever) an initrd image that can preload the device drivers it needs before actually attempting to mount the root filesystem. (Fairly easy to do this with something like redhat's mkinitrd utility). Cheers Tony -=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=- Tony Nugent <Tony@growzone.com.au> Systems Administrator, RHCE LinuxWorks - PO Box 5747 Gold Coast MC Queensland Australia 9726 Ph: (07) 5526 8020 Mobile: 0408 066 336 -=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=- - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
