This shell script facilitates installation of the GRUB boot loader on your system.
I recently tried out grubconfig and was impressed with its support for SCSI and IDE drives. However, it lacks support for RAID at the moment.
During the installation process, users have various options to choose from. The first step is to select where to install GRUB. This first step starts a new configuration file, /boot/grub/menu.lst. However, there are no OS's entered into it yet. Users will be given the option to install GRUB to their Master Boot Record or a Linux partition's superblock.
After starting a new /boot/grub/menu.lst file, users must add at least one OS before they can install GRUB. The next step is to add at least one Linux partition, which will hold the GRUB files in /boot/grub. Users may then add other partitions if they have any.
Another option is to add Linux and other DOS/WIN/BSD/OS2/HURD/QNX/PLAN9/BEOS/Minix partitions to the /boot/grub/menu.lst file. This step asks users which partitions they want to include in the grub menu and to assign a label to each partition. The label can have any name such as Redhat Linux, Windows Vista etc.
Once users are satisfied with their newly configured GRUB file, they can choose to install GRUB and exit the GRUB installation menu.
Other options include viewing the current /boot/grub/menu.lst file, which can be found in /boot/grub on the GRUB Linux partition. Additionally, if users haven't begun building a new menu.lst file, this choice allows them to take a look at the existing one.
If users want to make any changes after installation, they can edit /boot/grub/menu.lst by hand instead of running grubconfig again.
Overall, I found grubconfig to be a useful tool in configuring and installing GRUB. It is worth noting that grubconfig is based on liloconfig by Patrick Volkerding from the Slackware Linux distribution.
During the installation process, users have various options to choose from. The first step is to select where to install GRUB. This first step starts a new configuration file, /boot/grub/menu.lst. However, there are no OS's entered into it yet. Users will be given the option to install GRUB to their Master Boot Record or a Linux partition's superblock.
After starting a new /boot/grub/menu.lst file, users must add at least one OS before they can install GRUB. The next step is to add at least one Linux partition, which will hold the GRUB files in /boot/grub. Users may then add other partitions if they have any.
Another option is to add Linux and other DOS/WIN/BSD/OS2/HURD/QNX/PLAN9/BEOS/Minix partitions to the /boot/grub/menu.lst file. This step asks users which partitions they want to include in the grub menu and to assign a label to each partition. The label can have any name such as Redhat Linux, Windows Vista etc.
Once users are satisfied with their newly configured GRUB file, they can choose to install GRUB and exit the GRUB installation menu.
Other options include viewing the current /boot/grub/menu.lst file, which can be found in /boot/grub on the GRUB Linux partition. Additionally, if users haven't begun building a new menu.lst file, this choice allows them to take a look at the existing one.
If users want to make any changes after installation, they can edit /boot/grub/menu.lst by hand instead of running grubconfig again.
Overall, I found grubconfig to be a useful tool in configuring and installing GRUB. It is worth noting that grubconfig is based on liloconfig by Patrick Volkerding from the Slackware Linux distribution.
What's New
Version 1.33: N/A