Users who have more than one Operating System or those with more than one Linux kernel are ideal candidates for Grubconf. This is because Grubconf's strengths are in managing Operating Systems. OSes can easily be added, edited, and removed with minimal effort and knowledge of GRUB or the OS being managed.
Grubconf needs to be run as root. If it is not, an error will be shown and will immediately quit. This is because editing the GRUB configuration is a privileged action, which should be restricted to privileged users.
Grubconf can be invoked using the following commands.
This will display usage information
This will force grubconf to create a new file if one does not exist
This will use the specified filename for future grubconf sessions if a filename had been specified.
Specifies the grub configuration filename, if not specified grubconf will use the last saved filename or "/boot/grub/menu.lst"
When grubconf is loaded with no command line options it will attempt to locate your configuration in /boot/grub/menu.lst. If /boot is found to be a separate partition and is not mounted, grubconf will attempt to mount that partition for you. If /boot/grub/menu.lst is not found it will attempt to load /etc/grub.conf.
If no configuration file was found, regardless of whether a file was specified on command line, grubconf will show a graphical error and quit. If you must create a new configuration file, type touch filename to create a blank file and then grubconf -f filename to build a configuration, replacing filename with the desired configuration file.