From: <mad.scientist.at.large@tutanota.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: Human configurable boot loader, OR useful grub2 documentation
Date: Tue, 9 Jul 2019 05:05:13 +0200 (CEST) [thread overview]
Message-ID: <LjJgI_w--3-1@tutanota.com> (raw)
In-Reply-To: <qfnmk9$523q$1@blaine.gmane.org>
Ok, you convinced me i can selectively read the grub2 manual for the essential commands less scripting. I'll try that tonight. I would like to know where to get the source of the legacy grub that observed gentoo use flags, I'm thinking about simpler systems including a couple of 32 bit systems i'd like to use occasionally for odd services and network play (on an isolated network so i can also practice incursion and it's detection, response, and prevention).
-- Quick to the airport Robin! We must beat the continental army to the airport or Gotham City is lost!
Jul 5, 2019, 8:25 AM by grant.b.edwards@gmail.com:
> On 2019-07-05, Francesco Turco <fturco@fastmail.fm> wrote:
>
>> On Fri, Jul 5, 2019, at 08:05, mad.scientist.at.large@tutanota.com wrote:
>>
>>> So, is there either a boot loader that a human can configure
>>> manually that can handle LUKS partitions? No uefi, but GPT would
>>> be nice.
>>>
>>
>> I have a LUKS-encrypted system, GPT partitions, no UEFI, systemd,
>> dracut, btrfs.
>>
>> I always manually create a /boot/grub/grub.cfg configuration file
>> without using the grub-mkconfig command: [...]
>>
>
> I used to hate grub2 with a passion and stuck with grub-legacy as long
> as possible. Then I realized that you can ignore the nightmarish
> auto-magical modular AI configurator stuff. Grub2 is still a bit
> bloated for my taste, but it's just as easy to use as grub-legacy if
> you configure it manually. My grub.cfg files are just as trivial as
> my grub-legacy config files were:
>
> -----------------------------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.
>
> --
> Grant Edwards grant.b.edwards Yow! Inside, I'm already
> at SOBBING!
> gmail.com
>
next prev parent reply other threads:[~2019-07-09 3:05 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 [this message]
2019-07-09 17:17 ` Ian Zimmerman
2019-07-09 19:53 ` Grant Edwards
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=LjJgI_w--3-1@tutanota.com \
--to=mad.scientist.at.large@tutanota.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