From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Human configurable boot loader, OR useful grub2 documentation
Date: Tue, 9 Jul 2019 19:53:23 -0000 (UTC) [thread overview]
Message-ID: <qg2rbj$277q$1@blaine.gmane.org> (raw)
In-Reply-To: 20190709171723.tc4rzcsr6z2uvzwq@matica.foolinux.mooo.com
On 2019-07-09, Ian Zimmerman <itz@very.loosely.org> wrote:
> On 2019-07-05 14:25, Grant Edwards wrote:
>
>> -----------------------------grub.cfg------------------------------
>> timeout=10
>> root=hd0,1
>>
>> menuentry 'vmlinuz-4.19.52-gentoo' {
>> linux /boot/vmlinuz-4.19.52-gentoo root=/dev/sda1
>> }
>>
>> menuentry 'vmlinuz-4.14.83-gentoo' {
>> linux /boot/vmlinuz-4.14.83-gentoo root=/dev/sda1
>> }
>> -------------------------------------------------------------------
>>
>> I shudder when I contrast that with many hundreds of lines of cruft
>> that the mkconfig system would generate.
>
> This is an overstatement
To be fair, I should state that I've never used the autoconfig stuff
on that particular system. When I converted from grub-legacy to
grub2, I just translated the old grub config file to the new syntax.
> matica!2 ~$ wc -l /boot/grub/grub.cfg
> 148 /boot/grub/grub.cfg
That's still a 15:1 ratio. It appears that Gentoo is a better than
some other distros. On a fairly simple Ubuntu server system with 3
kernel versions:
wc -l /boot/grub/grub.cfg
265 /boot/grub/grub.cfg
On other distros/machines I've often seen double or triple that using
the installation defaults. You _really_ don't want to see the auto
generated grub.cfg files on a machine with a dozen different linux
installations, each with several kernels. Unless you disable the OS
probing module, it gets bad.
> 2 kernels, no initrd, just like yourself.
>
> Maybe you do need to take a look at /etc/default/grub ?
If you spend some time tuning things in /etc/default/grub, it gets
better. But, for my Gentoo systems I still find it far less work to
just create a grub.cfg file manually.
The semantics of /etc/default/grub also seem to vary to an annoying
extent between distros and versions. The semantics of grub.cfg seem
to be far more stable.
--
Grant Edwards grant.b.edwards Yow! Were these parsnips
at CORRECTLY MARINATED in
gmail.com TACO SAUCE?
next prev parent reply other threads:[~2019-07-09 19:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 6:05 [gentoo-user] Human configurable boot loader, OR useful grub2 documentation mad.scientist.at.large
2019-07-05 7:18 ` Francesco Turco
2019-07-05 7:24 ` mad.scientist.at.large
2019-07-05 8:10 ` Mick
2019-07-05 14:04 ` Rich Freeman
2019-07-05 15:32 ` Grant Taylor
2019-07-05 19:57 ` Neil Bothwick
2019-07-05 20:56 ` Grant Taylor
2019-07-05 14:25 ` [gentoo-user] " Grant Edwards
2019-07-09 3:05 ` mad.scientist.at.large
2019-07-09 17:17 ` Ian Zimmerman
2019-07-09 19:53 ` Grant Edwards [this message]
2019-07-05 9:03 ` [gentoo-user] " Philip Webb
2019-07-09 4:30 ` Ian Bloss
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='qg2rbj$277q$1@blaine.gmane.org' \
--to=grant.b.edwards@gmail.com \
--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