...I believe I am confused... I do not mind a little automation, but currently in my lilo.conf I have 3 linux kernels that I use.
Linux [default] Old [Previous Image] Experment [Pointing to /usr/src/linux/arch/i386/boot/zImage] This kernel-package util seems as if it takes this functionality away from you and simply uses default (/vmlinuz) and that is it. I am not sure this is a fair trade off for correcting whatever problem I am having with FS modules. I am not saying it is a viable option, but if I cannot 'insmod isofs.o', somthing is pretty wrong with how I compiled the kernel. Perhaps I simply don't understand what you are telling me to do with this "kernel-package" when I go to install or test a new kernel. --Jay Barbee > Ya know, > > The 'kernel-package' package automates all of this for you. I had troubles > getting modules to work even though I thought I did all the steps (make > dep ; make clean ; make bzImage ; make modules ; make modules_install ; > depmod -a. Then symlinking the new kernel and running lilo. The kernel > booted and all built in support worked perfect but modules didn't. Leaving > my config file unchanged I used kernel-package and everything worked.). If > you use the kernel-package package you don't need to worry about copying > or editing or symlinking and files, it's all done for you and it works > PERFECTLY. At least for me. > > In the modules support section of the configuration make sure to enable > the third option that lets you use kerneld for autoloading of modules. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
