How to have a custom Grub2 menu that is maintenance free

[Bashing-om]

Cavsfan; Uh Huh /

Looking good .

You have no idea how many times and places I recommend your method(s). Yeah we want it right and the simpler the better .

But

we do not knock what works

[Cavsfan]

Cavsfan; Uh Huh /

Looking good .

You have no idea how many times and places I recommend your method(s). Yeah we want it right and the simpler the better .

But

we do not knock what works

Well, thank you very much! I really appreciate that!

[Cavsfan]

OK, so I finally added some new pictures to the Wiki with some current versions.

I even found what I had always been meaning to add - the "Back to top" links.

See what you think. Did I get the "Back to top" links in the proper places?

Cheers

[Bashing-om]

Cavsfan; Yepper .

Look'n good . The - "Back to top" links are a nice touch and are functional . The link makes it so much easier for someone to make sure their thoughts are in order

just goes to show - no matter how good

can always be better

[Cavsfan]

Cavsfan; Yepper .

Look'n good . The - "Back to top" links are a nice touch and are functional . The link makes it so much easier for someone to make sure their thoughts are in order

just goes to show - no matter how good

can always be better

Thanks for taking a good look at it for me!

I hope the word gets around that's it's much, much simpler to do now.

I tried my best to change it to a logical order that one can follow in sequence.
Before you had to jump around from here to there and back, etc.

BTW, I found that the default Grub takes a long time updating when it's looking at /etc/grub.d/30_os-prober.
Probably because my system is so old and there often are 3 to 5 systems on it. It takes 3-5 minutes at that point for me.
It's torturous for me to go through a kernel installation where it updates Grub twice.
But, once customized it takes 2-3 seconds to update.

[Cavsfan]

I just discovered something interesting about recovery mode. I had the 17.10 alpha installed on a partition and accidentally installed the nVidia driver, which I knew would not work, so I tried to cancel it.

That did not work so, I tried recovery mode, dropped to a root shell and since it is read only I could not purge the nVidia driver, etc. so I edited the grub line and made it read/write. That worked like it should have in the first place.

So, I updated the Wiki for the Recovery line to be rw instead of ro.

I do not know why you would want to boot into recovery mode read-only when you are trying to fix your system; seems odd to me.
If you do not know what you are doing, you should not be in recovery mode in the first place, if that is why it is read only.

But, this sure saved me from doing another install of Artful 17.10. Plus why have to go through the process of editing the grub line to change it from ro to rw?

Win win I do believe....

If you find yourself needing to use recovery mode to drop to a root shell and do not have access to make the necessary updates, do this:
edit the recovery line at boot time and change the ro recovery nomodeset to rw recovery nomodeset so it will be a temporary change.

That will accomplish what you need.

[oldfred]

I thought it was read only so you could run fsck.
And does not recovery mode give a menu anymore, it used to have a menu with several options including command line with Internet, or continue booting, plus others?

[Cavsfan]

I thought it was read only so you could run fsck.
And does not recovery mode give a menu anymore, it used to have a menu with several options including command line with Internet, or continue booting, plus others?

Thanks for the reply!

Yes, it gives you the menu. The first item is normal boot and there are several others just as it has been normally.
I did not see a command line with internet, only an option to get the network started, then it comes back to that menu; this alpha failed to get the network started but, I didn't need that.
But, when I selected the option to drop to a root shell and purge the nVidia files I had installed it gave me errors because I was in read-only mode.

I tried to cancel out of installing them but, it was too late and 17.10 will not boot up with an nVidia driver installed this early.

Not sure why you would want to be in read/only mode to run fsck or how being in read/write mode could hurt that either.

But, when dropping to a root shell to fix your system read only mode will not allow it.

Arch Linux uses read/write mode for every boot option, I just made the recovery mode read/write mode because there is no problem during a normal boot in Ubuntu.

Do you foresee a problem booting into recovery mode in read/write mode?

[oldfred]

With fsck the partition must be unmounted, so that may be the same as ro?
Otherwise I do not know.

[Cavsfan]

With fsck the partition must be unmounted, so that may be the same as ro?
Otherwise I do not know.

Thanks, I'll check into it.