From: <mad.scientist.at.large@tutanota.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Human configurable boot loader, OR useful grub2 documentation
Date: Fri, 5 Jul 2019 09:24:14 +0200 (CEST) [thread overview]
Message-ID: <Lj00Dit--3-1@tutanota.com> (raw)
In-Reply-To: <5a75d07f-811f-4747-a91a-209cd4eef86e@www.fastmail.com>
Thank you! Now I don't have to read all the grub2 manual right away. Works mostly like I thought but first attempt was to edit the mkconfig- grub.cfg and I failed to back it up Properly. I should have tried it first on a system that didn't have 4 other distros laying around.
"Would you like to see us rule again, my friend? All you have to do is follow the worms." Pink Floyd, The Wall, Waiting for the worms
Jul 5, 2019, 1:18 AM by fturco@fastmail.fm:
> 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:
>
> timeout=-1
> menuentry 'Linux-libre 5.1.15' {
> linux /@i3/vmlinuz-5.1.15-gnu rd.luks.uuid=luks-e384faa4-d3ad-4171-b38e-8961bddab43f root=UUID=90a73cbd-f378-4424-93d9-661cbfec9e5a rootfstype=btrfs rootflags=subvol=@i3 init=/lib/systemd/systemd quiet loglevel=3 rd.vconsole.keymap=it
> initrd /@i3/initramfs-5.1.15-gnu.img
> }
>
> It is pretty simple compared to what grub-mkconfig usually generates, and it works pretty well.
>
> --
> https://fturco.gitlab.io/
>
next prev parent reply other threads:[~2019-07-05 7:24 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 [this message]
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
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=Lj00Dit--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