From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ...recreating exactly the same applications on a new harddisc?
Date: Sat, 11 Apr 2020 17:37:38 +0200 [thread overview]
Message-ID: <2577149.vuYhMxLoTh@thetick> (raw)
In-Reply-To: <3014614.AJdgDx1Vlc@lenovo.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]
Am Dienstag, 7. April 2020, 01:38:01 CEST schrieb Michael:
> On Monday, 6 April 2020 22:15:20 BST Neil Bothwick wrote:
> > On Mon, 6 Apr 2020 22:02:04 +0100, antlists wrote:
> > > > This isn't strictly true, the ESP must be vfat, but you can still
> > > > have an ext? /boot.
> > >
> > > This isn't true at all - you've got the cart before the horse. The
> > > original (U)EFI spec comes from Sun, I believe, with no vfat in sight.
> > >
> > > A standards-compliant factory-fresh Mac boots using UEFI with no vfat
> > > in sight.
> >
> > That's true, but firmware on commodity PC motherboards can only be relied
> > upon to handle vfat. So while my use of "must" is a bit strong, it should
> > be vfat if you want to be sure it will boot on a PC.
>
> Perhaps older UEFI specifications allowed Mac-baked filesystems, or perhaps
> Apple were/are doing their own thing. The current UEFI specification
> *requires* a FAT 12/16/32 filesystem type on an ESP partition to boot an OS
> image/bootloader from - see section '13.3 File System Format':
>
> https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_final.pdf
>
> I can't recall the ESP partition format last time I installed and
> dual-booted Linux on a MacBookPro, c.2014, but I'd wager it was VFAT.
I checked my 2007 Mac Mini and its ESP is vfat. Of course, newer Macs or
other models might use something else.
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2020-04-11 15:38 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 17:34 [gentoo-user] ...recreating exactly the same applications on a new harddisc? tuxic
2020-04-04 17:59 ` [gentoo-user] " Ian Zimmerman
2020-04-04 18:03 ` tuxic
2020-04-05 17:41 ` Ian Zimmerman
2020-04-05 19:53 ` Jack
2020-04-05 19:57 ` Jack
2020-04-04 21:26 ` Neil Bothwick
2020-04-04 23:46 ` Peter Humphrey
2020-04-04 18:05 ` [gentoo-user] " Mark Knecht
2020-04-04 18:23 ` tuxic
2020-04-04 18:57 ` Mark Knecht
2020-04-04 18:33 ` Dale
2020-04-04 21:42 ` John Covici
2020-04-04 22:24 ` Dale
2020-04-04 18:25 ` Ashley Dixon
2020-04-04 19:05 ` tuxic
2020-04-04 19:29 ` Ashley Dixon
2020-04-04 19:30 ` Mark Knecht
2020-04-04 19:59 ` tuxic
2020-04-05 9:21 ` [OT] " Peter Humphrey
2020-04-05 9:29 ` Peter Humphrey
2020-04-04 21:56 ` Grant Taylor
2020-04-05 8:17 ` tuxic
2020-04-05 9:28 ` Ashley Dixon
2020-04-05 12:52 ` Neil Bothwick
2020-04-05 12:56 ` Ashley Dixon
2020-04-05 13:37 ` Michael
2020-04-05 14:56 ` Neil Bothwick
2020-04-05 18:08 ` Peter Humphrey
2020-04-05 19:39 ` Neil Bothwick
2020-04-06 10:17 ` Peter Humphrey
2020-04-06 21:02 ` antlists
2020-04-06 21:15 ` Neil Bothwick
2020-04-06 23:38 ` Michael
2020-04-07 15:23 ` antlists
2020-04-11 15:37 ` Marc Joliet [this message]
2020-04-08 1:02 ` William Kenworthy
2020-04-05 9:46 ` Michael
2020-04-05 10:52 ` tuxic
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=2577149.vuYhMxLoTh@thetick \
--to=marcec@gmx.de \
--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