From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: bug-xorriso@gnu.org, Thomas Schmitt <scdbackup@gmx.net>,
guix-devel@gnu.org
Subject: Re: ISO installer image: GPT versus MBR partitions
Date: Fri, 26 Apr 2019 16:41:27 +0200 [thread overview]
Message-ID: <871s1oltgo.fsf@gnu.org> (raw)
In-Reply-To: <20190426113444.7puwyenlcmoo3ghd@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Fri, 26 Apr 2019 13:34:44 +0200")
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> On Thu, Apr 25, 2019 at 06:34:16PM +0200, Ludovic Courtès wrote:
>> I lost track of the discussion. You’re looking at a MacBook-specific
>> issue, right?
>>
>> (The underlying question being: can this wait after 1.0 is out? :-)
>> If it’s MacBook-specific, I would answer “yes.”)
>>
>
> As I understand it, Thomas’ work is about
> - making a correct ISO image and
> - making it work on more machines.
>
> I would have hoped the 1.0 ISO could already be made correct.
> Older ISOs work on cooperative motherboards as well though, it appears
> only old Macs are affected. A more recent 2014 Macbook Air boots fine
> though.
So the ISO only “fails” (somehow?) on old Macs, is that correct?
If it’s “just” about old Macs, that’s not a 1.0 blocker for me (though
it’s something we should fix.)
If the issue might be broader, we need more data to estimate the scope
of the problem (your table mentioned UEFI vs. “legacy” boot and Lenovo
laptops, which I’m not sure how to interpret.)
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-04-26 14:41 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190415165451.dpzngealeisbibc7@pelzflorian.localdomain>
[not found] ` <1582867226375139246@scdbackup.webframe.org>
2019-04-16 9:57 ` bug#33639: ISO installer image is broken on i686 Gábor Boskovits
2019-04-16 13:40 ` ISO installer image: GPT versus MBR partitions (was bug#33639) Thomas Schmitt
2019-04-16 16:32 ` pelzflorian (Florian Pelz)
2019-04-16 17:57 ` ISO installer image: GPT versus MBR partitions Thomas Schmitt
2019-04-16 19:55 ` pelzflorian (Florian Pelz)
2019-04-16 20:31 ` pelzflorian (Florian Pelz)
2019-04-16 21:15 ` Thomas Schmitt
2019-04-17 8:59 ` pelzflorian (Florian Pelz)
2019-04-17 10:23 ` Thomas Schmitt
2019-04-17 10:30 ` pelzflorian (Florian Pelz)
2019-04-17 15:51 ` Thomas Schmitt
2019-04-17 22:35 ` pelzflorian (Florian Pelz)
2019-04-18 6:32 ` Thomas Schmitt
2019-04-18 7:00 ` Thomas Schmitt
2019-04-18 7:07 ` pelzflorian (Florian Pelz)
2019-04-18 8:13 ` Thomas Schmitt
2019-04-18 12:19 ` pelzflorian (Florian Pelz)
2019-04-18 13:50 ` Thomas Schmitt
2019-04-18 21:28 ` Thomas Schmitt
2019-04-19 7:29 ` pelzflorian (Florian Pelz)
2019-04-19 8:03 ` pelzflorian (Florian Pelz)
2019-04-19 9:01 ` Thomas Schmitt
2019-04-19 9:39 ` pelzflorian (Florian Pelz)
2019-04-19 10:58 ` Thomas Schmitt
2019-04-19 14:57 ` pelzflorian (Florian Pelz)
2019-04-19 11:30 ` pelzflorian (Florian Pelz)
2019-04-19 18:33 ` pelzflorian (Florian Pelz)
2019-04-19 19:23 ` Thomas Schmitt
2019-04-20 10:26 ` pelzflorian (Florian Pelz)
2019-04-20 10:50 ` Thomas Schmitt
2019-04-20 11:16 ` Thomas Schmitt
2019-04-20 11:29 ` Thomas Schmitt
2019-04-20 14:23 ` Thomas Schmitt
2019-04-20 14:54 ` pelzflorian (Florian Pelz)
2019-04-20 15:17 ` pelzflorian (Florian Pelz)
2019-04-20 15:33 ` pelzflorian (Florian Pelz)
2019-04-20 16:32 ` Thomas Schmitt
2019-04-21 7:58 ` pelzflorian (Florian Pelz)
2019-04-21 9:35 ` Thomas Schmitt
2019-04-21 11:10 ` pelzflorian (Florian Pelz)
2019-04-21 11:16 ` Thomas Schmitt
2019-04-21 11:56 ` pelzflorian (Florian Pelz)
2019-04-21 12:27 ` Thomas Schmitt
2019-04-21 14:11 ` pelzflorian (Florian Pelz)
2019-04-21 14:36 ` Thomas Schmitt
2019-04-22 13:11 ` Thomas Schmitt
2019-04-23 16:40 ` pelzflorian (Florian Pelz)
2019-04-23 17:23 ` Thomas Schmitt
2019-04-17 12:24 ` Ludovic Courtès
2019-04-17 13:42 ` pelzflorian (Florian Pelz)
2019-04-23 18:14 ` Thomas Schmitt
2019-04-23 19:50 ` pelzflorian (Florian Pelz)
2019-04-23 20:18 ` Thomas Schmitt
2019-04-23 21:43 ` pelzflorian (Florian Pelz)
2019-04-24 6:56 ` Thomas Schmitt
2019-04-24 9:13 ` pelzflorian (Florian Pelz)
2019-04-24 10:34 ` Thomas Schmitt
2019-04-24 22:13 ` Danny Milosavljevic
2019-04-25 7:07 ` Thomas Schmitt
2019-04-25 9:45 ` pelzflorian (Florian Pelz)
2019-04-25 13:44 ` Thomas Schmitt
2019-04-25 14:59 ` Danny Milosavljevic
2019-04-25 16:22 ` Thomas Schmitt
2019-04-25 17:55 ` Danny Milosavljevic
2019-04-25 18:46 ` Thomas Schmitt
2019-04-25 19:01 ` Danny Milosavljevic
2019-04-25 16:34 ` Ludovic Courtès
2019-04-26 11:34 ` pelzflorian (Florian Pelz)
2019-04-26 14:41 ` Ludovic Courtès [this message]
2019-04-26 15:30 ` pelzflorian (Florian Pelz)
2019-04-26 13:57 ` Thomas Schmitt
2019-04-27 13:20 ` Ludovic Courtès
2019-04-27 16:24 ` Thomas Schmitt
2019-04-28 12:53 ` Ludovic Courtès
2019-04-25 11:49 ` pelzflorian (Florian Pelz)
2019-04-25 15:09 ` Thomas Schmitt
2019-04-25 15:58 ` pelzflorian (Florian Pelz)
2019-04-25 16:40 ` Thomas Schmitt
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871s1oltgo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-xorriso@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pelzflorian@pelzflorian.de \
--cc=scdbackup@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).