From: Nix <nix@esperi.org.uk>
To: Phillip Susi <phill@thesusis.net>
Cc: Stefanie Leisestreichler
<stefanie.leisestreichler@peter-speer.de>, G <garboge@shaw.ca>,
linux-raid@vger.kernel.org
Subject: Re: Setup Recommendation on UEFI/GRUB/RAID1/LVM
Date: Fri, 24 Apr 2020 21:24:45 +0100 [thread overview]
Message-ID: <87ftcsk4xe.fsf@esperi.org.uk> (raw)
In-Reply-To: <87d07wr8z9.fsf@vps.thesusis.net> (Phillip Susi's message of "Fri, 24 Apr 2020 15:15:22 -0400")
On 24 Apr 2020, Phillip Susi stated:
>
> Nix writes:
>
>> Agreed. I avoided GPT like the plague for ages (shoddy early-2010s
>> motherboard firmware), but once I switched to it it was so much easier
>> to manage than old-style BIOS, and so much easier to deal with when
>> disaster struck, that I'd never consider going back. Does the BIOS have
>> anything like an EFI shell? No, no it doesn't. Can you hack your own
>
> My current and previous motherboard with UEFI boot support did not come
> with the shell. I once tried downloading one and running it but never
> could find anything useful to do with it.
It's mostly useful for emergency recovery, I'll admit :)
> I also haven't ever been able
> to find any useful UEFI drivers or programs.
They are very thin on the ground :( a shame, really: it seems like
something you *should* be able to use to build whole rescue
environments, but nooo. I guess it *is* easier to stick those in an
initramfs linked into a kernel built as an EFI stub, since at least it's
a Linux rather than the rather weird PE-based environment which is EFI.
next prev parent reply other threads:[~2020-04-24 20:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 13:02 Setup Recommendation on UEFI/GRUB/RAID1/LVM Stefanie Leisestreichler
2020-04-14 14:20 ` Wols Lists
2020-04-14 14:27 ` Reindl Harald
2020-04-14 15:12 ` Stefanie Leisestreichler
2020-04-14 17:35 ` Wols Lists
2020-04-14 19:13 ` Stefanie Leisestreichler
2020-04-14 19:36 ` Wols Lists
2020-04-17 23:06 ` Nix
2020-04-20 9:23 ` Stefanie Leisestreichler
2020-04-20 9:45 ` Stefanie Leisestreichler
2020-04-20 11:05 ` Nix
2020-04-20 12:01 ` Stefanie Leisestreichler
2020-04-16 1:50 ` David C. Rankin
2020-04-16 11:16 ` Wols Lists
2020-04-16 1:58 ` David C. Rankin
2020-04-14 16:00 ` G
2020-04-14 16:14 ` Stefanie Leisestreichler
2020-04-17 23:10 ` Nix
2020-04-24 19:15 ` Phillip Susi
2020-04-24 20:24 ` Nix [this message]
2020-04-14 16:20 ` Reindl Harald
2020-04-14 16:41 ` Stefanie Leisestreichler
2020-04-16 17:00 ` G
2020-04-14 18:14 ` Phillip Susi
2020-04-14 19:00 ` Stefanie Leisestreichler
2020-04-14 20:05 ` antlists
2020-04-17 23:24 ` Nix
[not found] ` <394a3255-251c-41d1-8a65-2451e5503ef9@teksavvy.com>
2020-04-15 15:53 ` Stefanie Leisestreichler
2020-04-15 16:10 ` Stefanie Leisestreichler
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=87ftcsk4xe.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=garboge@shaw.ca \
--cc=linux-raid@vger.kernel.org \
--cc=phill@thesusis.net \
--cc=stefanie.leisestreichler@peter-speer.de \
/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;
as well as URLs for NNTP newsgroup(s).