From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Exact setting in grub to default to a kernel by name?
Date: Mon, 14 Jun 2021 00:20:44 +0100 [thread overview]
Message-ID: <20210614002044.288d580d@digimed.co.uk> (raw)
In-Reply-To: <YMaNbYRWf5+BlYOV@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
On Sun, 13 Jun 2021 18:57:49 -0400, Walter Dnes wrote:
> When experimenting with this, I'll backup grub.cfg. If things go
> awry, boot with the USB key I used for the install, and copy back the
> old known working grub.cfg. I've done a first crack at this. I assume
> that nothing in /etc/default/grub will have any effect. Questions...
/etc/default/grub is only used when you call grub-mkconfig.
> 1) Is "insmod extfs3" necessary? I've built extfs3 into the kernels.
If the kernel is on an ext3 filesystem, yes. This is GRUB's module, it
uses it to read an ext3 filesystem in order to load the kernel.
> 2) I assume that the the first "menuentry" will be the default boot?
Yes, you'll see default=0 in the first part of grub.cfg.
> 3) Is the default timeout still 5 seconds?
Not sure on that one, but look at grub.cfg.
> 3) I assume that 640x480 is supported on just about every monitor
> out there. I want as large text as possible. My eyes are getting
> old... just like me.
My eyes are better than they were 40 years ago but don't ask about my
hearing, or if you must, do it loudly...
--
Neil Bothwick
Documentation: (n.) a novel sold with software, designed to entertain the
operator during episodes of bugs or glitches.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-06-13 23:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 4:07 [gentoo-user] Exact setting in grub to default to a kernel by name? Walter Dnes
2021-06-13 4:46 ` Hund
2021-06-13 13:33 ` Walter Dnes
2021-06-13 17:38 ` [gentoo-user] " Grant Edwards
2021-06-13 22:57 ` Walter Dnes
2021-06-13 23:20 ` Neil Bothwick [this message]
2021-06-14 2:34 ` Walter Dnes
2021-06-14 11:47 ` Neil Bothwick
2021-06-14 1:00 ` Grant Edwards
2021-06-14 6:44 ` Walter Dnes
2021-06-14 8:38 ` Grant Edwards
2021-06-14 20:25 ` Walter Dnes
2021-06-15 13:56 ` Neil Bothwick
2021-06-16 0:51 ` [gentoo-user] [SOLVED} " Walter Dnes
2021-06-13 18:05 ` [gentoo-user] " Neil Bothwick
2021-06-13 18:45 ` Michael
2021-06-13 20:09 ` Philip Webb
2021-06-13 20:58 ` Walter Dnes
2021-06-14 8:25 ` Peter Humphrey
2021-06-13 8:21 ` Neil Bothwick
2021-06-13 8:26 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210614002044.288d580d@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox