On Sunday 08 February 2004 03:08 pm, Hugh wrote:
I used to custom compile my kernel? In some machines I use SCSI card and a scsi hard disk. In other machines, I use ATAPI hard. I have been using reiserfs exclusively nowadays.
I used to hate modules. and I still make all those drivers be in the kernel., rather than modules. For this reason, I have thought I do not need ramdisk nor initrd stuff at all. Is my conclusion still true?
Yes, assuming that everything the kernel needs at boot time is compiled into the kernel, you do not need initrd.
For SuSE, /etc/sysconfig/kernel seems to control the boot process. and if you read inside the file, it seems to assume that initrd must be created. Then where? Why does the boot script checks /initrd instead of /boot/initrd-2.5.21-166-default for example?
SuSE's security announcement in http://www.suse.com/de/security/2004_01_linux_kernel.html
assumes that everyone using SuSE distribution uses their stock kernels. What should we know if we custom-compile our own kernels?
Finally, is my READONLY file system error during bootup related to this topic?
Thanks a lot.
Hugh
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 02/08/04 15:30 + +----------------------------------------------------------------------------+ "Life is like an analogy."