From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id D055A21AE2646 for ; Tue, 20 Jun 2017 05:33:07 -0700 (PDT) Received: by mail-io0-x22f.google.com with SMTP id i7so83532529ioe.1 for ; Tue, 20 Jun 2017 05:34:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=wvv9H0WQ/0LZQRTOZgyIeVUVR2j4HTOlGTomAoOce0I=; b=Tm4uVkYaC23j9R+JabDZHS55Z5Y8g6VT2zstiexr4T0125F+oml2LjVx4KT5SVHLX+ F98b1MbxZ0wEZA3EC3zo4epmUVBlXzvxk4/7T1/yokICXjlk5PL/xJXA6Vgr1yQcuIje 12Ynpee2kuMPqJkSrCbsP/hwX+djegHu8H1SU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=wvv9H0WQ/0LZQRTOZgyIeVUVR2j4HTOlGTomAoOce0I=; b=YpUoorrqHOxuhzRRWpiJhaNJnYFaxhfE2jY+0bu6vfKud8owTjNQeb4l/K9Map3Ae1 zJ9qj909o1eN07lgNeXv4Jo6DnM69Qc1UeSio8+B9cevTFfYWrCUEl7sePWbSkhCPh15 BDoku6Kb7bGQ42BFXLd98t+FEpyPDgSqv5piq7lQtYY0s46I5zx0IwWXkLnxv3tfNKd+ 3jAFLwpsmUhm736kTg31Z7EP42ZUZxN4QJqpemsMit8OzfG/oEVdPWAOxNYsYt670MhU +QdsI/dbLSS4HrLpehVW6kI7lfUgxauCAEArooNXr6jWSzuQT8DVeEGglf3ibxnUaIug keWQ== X-Gm-Message-State: AKS2vOw7Drp5KmG5UPLlzKSNPLIwXi+knhhkMFZByozDPJdVaz9OmQYg OOmnRwvdfumc+2IJfV9m6Q== X-Received: by 10.107.17.39 with SMTP id z39mr25406087ioi.107.1497962069567; Tue, 20 Jun 2017 05:34:29 -0700 (PDT) Received: from [10.229.36.134] ([119.145.15.121]) by smtp.gmail.com with ESMTPSA id 79sm8261505itj.15.2017.06.20.05.34.28 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Jun 2017 05:34:28 -0700 (PDT) To: "edk2-devel@lists.01.org" From: Heyi Guo Message-ID: <30c8ed8a-9ed5-0472-acbe-1d8b17fb38fb@linaro.org> Date: Tue, 20 Jun 2017 20:34:24 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Subject: How can we identify an ISO file is an EFI bootable ISO image? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2017 12:33:08 -0000 Content-Type: text/plain; charset=gbk; format=flowed Content-Transfer-Encoding: 7bit Dear experts, Is there any simple tool to parse ISO images (El Torito partition) and identify whether it is EFI bootable? I think EFI bootable image should contain a FAT volume so that EFI can load bootxx.efi file from the file system. Several tools like mount in Linux will show all files together including EFI/BOOT directory, so if an ISO image contains such files but not organizes the data in a FAT sub-volume as EFI requires, I can't see any difference. So the tool would need to print the detailed internal structure information of El Torito ISO files. Is there something like that? And is there any guide to create an EFI bootable El Torito ISO image? Thanks and regards, Gary (Heyi Guo)