Boot Loader

[DMGrier]

So I just installed Fedora 16, I like but the only problem I am running into is when it boots up it ask me if I want to boot Fedora 16 or into recovery mode. I know that you have to edit the boot loader in terminal but I am unsure of how to do this. I could not find a way on google or the search for the forum and I am sure I am just typing the wrong thing in but I am just trying to figure out how to get into the boot loader and what I need to set to Zero. Have done it once but it was in Yast for opensuse. Thanks for any help.

[chdongsh]

you can sudo gedit /boot/grub2/grub.cfg, but this way is not recommended

[glennzo]

If you're talking about setting the boot menu timeout to zero then in /etc/default/grub add a line that reads

PHP Code:

GRUB_TIMEOUT=0 


Then run

PHP Code:

grub2-mkconfig -o /boot/grub/grub.cfg 


[sonoran]

It's okay to edit /boot/grub2/grub.cfg, according to this:

http://lists.fedoraproject.org/piper...er/407190.html

Sounds authoritative.

[fpmurphy]

It is perfectly OK to edit /boot/grub.cfg. Just remember not to run grub2-mkconfig afterwords or it will overwrite the changes you made in /boot/grub.cfg. grub2-config simply uses a series of configuration scripts to creates a new /boot/grub.cfg.

One way to avoid that possibility is to make grub2-mkconfig an empty shell script.

[DBelton]

Just for reference, too..

If you run grub2-mkconfig as others have stated, it would overwrite your manual changes to /boot/grub2/grub.cfg

But, updating your kernel wouldn't overwrite your changes since the update still uses grubby and not grub2-mkconfig. Grubby doesn't overwrite what you have in your /boot/grub2/grub.cfg, but basically copies what you have for your default kernel to the new kernel entry (as far as kernel options)

[sea]

If you install a new kernel, via yum update, i'd guess it would run grub2-mkconfig, hence else you could not boot into the new kernel, as it would not be listed.
Or am i wrong on this?

You may however change these files, with all your needs and pleases
/etc/grub.d/40_custom
/etc/grub.d/41_custom

[DBelton]

when you install a new kernel via yum, it uses grubby to update your grub.cfg file, not grub2-mkconfig.

There was a discussion on this a few weeks back where it was mentioned that having 2 different tools updating your grub.cfg was really not good, but that's the way it is, at least for now, anyway.

[nonamedotc]

I might be wrong, but, isn't it easier to install "system-config-boot" and edit the grub options ?

[DBelton]

system-config-boot doesn't work with grub2, neither does bootconf. Those are tools for working with legacy grub.

[nonamedotc]

oh ! I did not know that ! I thought I forgot to install that - but now i know it is not needed ! Thanks.

[DBelton]

I don't think that running one of those tools would affect grub2 and shouldn't do any damage, but it either wouldn't run, or make changes that grub2 wouldn't even see.

So, (I hope anyway) that those tools are harmless for someone running grub2, they just won't work.