From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1O3EfV-0000U1-Kh for mharc-grub-devel@gnu.org; Sat, 17 Apr 2010 16:31:09 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O3EfS-0000Tb-6I for grub-devel@gnu.org; Sat, 17 Apr 2010 16:31:06 -0400 Received: from [140.186.70.92] (port=57147 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3EfP-0000TT-Db for grub-devel@gnu.org; Sat, 17 Apr 2010 16:31:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O3EfN-0006jz-Lr for grub-devel@gnu.org; Sat, 17 Apr 2010 16:31:03 -0400 Received: from mail-bw0-f225.google.com ([209.85.218.225]:39742) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O3EfN-0006jo-Gg for grub-devel@gnu.org; Sat, 17 Apr 2010 16:31:01 -0400 Received: by bwz25 with SMTP id 25so3604617bwz.8 for ; Sat, 17 Apr 2010 13:31:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type; bh=ZVWjZhmI+HSgth39BDm4PgKGUEgmP9uKCL7v5/FRe3I=; b=vz7JAQHWurNs6zULNTd/H4xo5R77APGdJCTYj3Mxti5itTlIWumx8WYk67T39itqCj 4/vQ9BNc+hxNNGzbZbOovYcKcv4HDJys2Vfu6v/183o2FdXCb31eCjgbOOh6UM1o5OOX LJw9ZWeNNHaPNsRNxzIU3xMHnpHUXCUV9EONU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type; b=uuqsuN3c3LXCOJWPLxEswm+CVZlzylAH6Nfn9tNmyeAmKFxlINDvZq5gIPUtaYe/SP eekchWeWBoFLngcBMMIgWlbJqVVt4VZchdsVh2A9DSlAvBN8yLilx6e2JCO+x2dxtDor PHVTDR908O/tjpO5btpTFpPaMHd3+pCkalOs4= Received: by 10.204.73.149 with SMTP id q21mr3090875bkj.57.1271536260158; Sat, 17 Apr 2010 13:31:00 -0700 (PDT) Received: from debian.bg45.phnet (52.115.63.81.cust.bluewin.ch [81.63.115.52]) by mx.google.com with ESMTPS id 16sm2428459bwz.1.2010.04.17.13.30.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 17 Apr 2010 13:30:59 -0700 (PDT) Message-ID: <4BCA1A75.4010702@gmail.com> Date: Sat, 17 Apr 2010 22:30:45 +0200 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20091109) MIME-Version: 1.0 To: The development of GNU GRUB References: <4BC9F848.5070906@gmail.com> <10642486746847@192.168.2.69> In-Reply-To: <10642486746847@192.168.2.69> X-Enigmail-Version: 0.95.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigCE411E619A2B0A5F3153A08F" X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: Re: How to prepare an ISO 9660 CD for booting via GRUB ? X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Apr 2010 20:31:06 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCE411E619A2B0A5F3153A08F Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thomas Schmitt wrote: > Hi, > > =20 >> I attach the patch I used for dirty checks >> =20 > > Oh. You already tested. > And ? Did it boot ? > > =20 Yes it booted in qemu-tianocore. >> Why not to determine it [-boot-load-size] from >> file size by default? >> =20 > > Because mkisofs doesn't do that, afaik. > One never knows what happens if one deviates from > the old ways by default. > =20 Ok, legacy :(. But --efi-boot would have no legacy. > (See Joliet and grub 1.96. I now go the old > way by default. So grub-mkrescue 1.96 boots from > CD.) > =20 It was a grub bug. > > =20 >> The problem is that I would like to have efi+bios cd with 2 eltorito >> entries: one with platformid=3D0 and another one with platformid=3D0xe= f. >> =20 > > Ahum. More than one boot table entry. > Would they point to different boot images ? > > =20 Yes > I.e would we have > -b [-boot-info-table] --efi-boot > > =20 Yes. Prototype is available at http://bzr.savannah.gnu.org/r/grub/people/phcoder/rescue-efi/ . > Is it possible to get an exact prescription, what > info to write at which byte in the boot catalog ? > > =20 BIOS+EFI one should look like Validation entry with id =3D 0 Default entry (BIOS). I would like that on hybrid BIOS always come in default entry to avoid hitting BIOS bugs Section header entry: 0x91, 0xef, 0x0001, 0, ..., 0 Section entry: 0x88, 0x00, 0x0000, 0, 0, , , 0, ..., 0 In case of just EFI the Section header entry and Section entry become Validation entry and default entry. > I have a PDF: El Torito 1.0, January 25, 1995. > Figure 1, "Multiple Boot-Image Configuration" > seems to be what you intend. > I will try to match this with the existing code > in libisofs (by Vreixo Formoso). > > > ------------------------------------------------ > > =20 >>> Do i get it right that you want the LBA [...] >>> to be as low as possible ? >>> =20 >> Yes and also the offset to files from boot/grub >> and metadata to reach it >> =20 > > I learned meanwhile that there is a feature > "weight" in libisofs by which one can influence > the sequence of the data LBAs. An IsoNode with > high weight will get a low LBA. > > So this is merely a matter of suitable options > in xorriso, by which one can put weight on files. > > =20 Nice > ------------------------------------------------ > > > Have a nice day :) > > Thomas > > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/grub-devel > > =20 --=20 Regards Vladimir '=CF=86-coder/phcoder' Serbinenko --------------enigCE411E619A2B0A5F3153A08F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iF4EAREKAAYFAkvKGoEACgkQNak7dOguQgkCQQEAmTAvidMPH8TRAAyGuqpR6Jvo A57RAWDC7xzl454CUjABAKSJuEdZJyud0kRcSnhs3xwpJ3S8mIHyrrUA7AC3yODA =TNIB -----END PGP SIGNATURE----- --------------enigCE411E619A2B0A5F3153A08F--