An initrd image is needed for loading your SCSI module at boot time or if you are compiling the kernel with ext3 support as a module. If you do not need an initrd image, do not make one and do not edit lilo.conf or grub.conf to include this image.
Use the /sbin/mkinitrd shell script to build an initrd image for your machine. To use this command, the loopback block device must be available.
To build the new initrd image, run /sbin/mkinitrd with parameters such as this:
/sbin/mkinitrd /boot/initrd-2.4.18-0.12-jul2001.img 2.4.18-0.12-jul2001
In the above example, /boot/initrd-2.4.18-0.12-jul2001.img is the file name of the new initrd image. 2.4.18-0.12-jul2001 is the kernel whose modules (from /lib/modules) should be used in the initrd image. This is not necessarily the same as the version number of the currently running kernel.
Refer:- http://www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/custom-guide/s1-custom-kernel-initrd.html
Difference Between LILO and GRUB.
1) GRUB (Grand Unified boot loader) most important ability to navigate file system,so you can read file without loading a kernal.
2)LILO (Linux Loader) has no interactive command interface,whereas GRUB does.
3) LILO does not support booting from a network,whereas GRUB does.
4) LILO stores information regarding the location of the operating systems it can to load physically on the MBR. If you change your LILO config file, you have to rewrite the LILO stage one boot loader to the MBR. Compared with GRUB, this is a much more risky option since a misconfigured MBR could leave the system unbootable. With GRUB, if the configuration file is configured incorrectly, it will simply default to the GRUB command-line interface
Port number list.
Go to this link:-- http://www.iana.org/assignments/port-numbers
Sunday, February 17, 2008
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment