public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Rod Smith <rodsmith@rodsbooks.com>, edk2-devel@lists.01.org
Subject: Re: How can we identify an ISO file is an EFI bootable ISO image?
Date: Tue, 20 Jun 2017 20:11:36 +0200	[thread overview]
Message-ID: <4e2544c2-3032-1aed-df3b-8b895286b358@redhat.com> (raw)
In-Reply-To: <648c681f-008b-e483-dd93-38d8bccaeb61@rodsbooks.com>

On 06/20/17 19:36, Rod Smith wrote:
> On 06/20/2017 12:47 PM, Laszlo Ersek wrote:

>> For UEFI boot, only the ElTorito image matters.
> 
> MOSTLY, yes; however, some EFI implementations include ISO-9660 drivers.
> This is definitely true of the EFI used by VirtualBox. I think I've seen
> this feature on one or two UEFI-based PCs, too, but I don't recall the
> details and I can't say I'm 100% certain of this. There are also
> ISO-9660 drivers floating around that can be loaded from a FAT
> partition. In either of these cases, the files on the ISO-9660
> filesystem can be used to boot from an optical disc, even if it lacks
> the El Torito image.

Good point!

> This is admittedly a corner case at best; but IMHO it's worth keeping in
> mind, since non-matching El Torito and ISO-9660 files could lead to user
> (or developer) confusion.

That has actually tripped up at least one OVMF user in the past; they
had some inconsistency between the two locations. The problem was
originally reported in  <https://github.com/tianocore/edk2/issues/93>
("OvmfPkg: UEFI Shell only sees EFI\BOOT\BOOTX64.EFI"), but now that the
edk2 github issue tracker is gone, the ticket cannot be viewed even in
read-only mode. :/

Thanks!
Laszlo


  reply	other threads:[~2017-06-20 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20 12:34 How can we identify an ISO file is an EFI bootable ISO image? Heyi Guo
2017-06-20 16:47 ` Laszlo Ersek
2017-06-20 17:36   ` Rod Smith
2017-06-20 18:11     ` Laszlo Ersek [this message]
2017-06-21  0:48   ` Heyi Guo

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-list 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=4e2544c2-3032-1aed-df3b-8b895286b358@redhat.com \
    --to=devel@edk2.groups.io \
    /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