From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Thomas Schmitt <scdbackup@gmx.net>
Subject: Re: How important is the MBR partition offset of grub-mkrescue ?
Date: Sun, 03 Nov 2013 16:48:24 +0100 [thread overview]
Message-ID: <52767048.9050902@gmail.com> (raw)
In-Reply-To: <27179651378991409308@scdbackup.webframe.org>
[-- Attachment #1: Type: text/plain, Size: 2865 bytes --]
On 03.11.2013 16:21, Thomas Schmitt wrote:
> Hi,
>
>> Isn't this HFS+ catalog sufficient for the problem at hand?
>
> I see the misleading link to /dev/sdb1 with Debian 6
> and with a Debian 7 based distro. Dunno which udev rule
> first looks at /dev/sdb for an ISO PVD and then links
> ./by-label to the first partition of that device.
>
> The filesystem itself is not necessarily mounted.
> Actually, the /dev/sdb1 with start at LBA 1 cannot be mounted.
> Neither as ISO nor as HFS+ (if that was present). An offset
> of 512 bytes would spoil any address that works in an ISO image.
>
If GPT is present it takes precedence over MBR contents. And GPT would
point nicely to HFS+
>
>> Can we detect presence of this bug?
>
> It is a bug of the perceiving system. Linux specific. Lifetime
> at least for Debian 6 and 7, i'd say.
>
> Put a grub-mkrescue generated ISO on a USB stick (e.g. /dev/sdb),
> replug, and see what your Linux has in /dev/disk/by-label.
> (If it has such a directory, at all.)
>
So it's bug in Debian, not in xorriso?
>
>> Additional problem you don't mention: consumption of space by additional
>> headers. We use xorriso for making floppies as well (and it works).
>
> The feature is easy to add by user arguments of grub-mkrescue
> anyway. No need for action inside grub-mkrescue.
> I am mainly fishing for experience with pure GRUB2 boot setups
> and Linux. Most distros let BIOS boot ISOLINUX.
>
> Is there a distro which produces its ISO images with grub-mkrescue
> and uses all or most of the BIOS, UEFI, and Apple features ?
>
> As soon as i have a working ISO image, i can play with it.
> I never learned to build operating systems or boot loaders myself.
> It would be helpful to have a copy of the grub-mkrescue script
> which was used for image production. I understand it evolves.
>
It's in our git repo in util/ . There are 2 versions currently: sh one
and C one. It wasn't decided yet as to whether we'll switch to C one.
http://git.savannah.gnu.org/cgit/grub.git/tree/util?h=phcoder/install_c
grub-mkrescue.in is sh one and grub-mkrescue.c is C one.
>
>> Another solution is to have a hybrid ISO + FAT or ISO + HFS+ + FAT layouts.
>
> But will this help against udev madness ?
>
FAT would make it look like most common USB stick.
> Whatever. If i remember correctly, we still have open plans
> about adding FAT to the super-hybrid layout.
> See the very end of
> http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/view/head:/doc/boot_sectors.txt
>
> (I see that i did not yet document the --grub2-boot-info
> patching.)
>
>
> Have a nice day :)
>
> Thomas
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next prev parent reply other threads:[~2013-11-03 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 18:57 How important is the MBR partition offset of grub-mkrescue ? Thomas Schmitt
2013-11-02 23:42 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-03 12:21 ` Thomas Schmitt
2013-11-03 13:05 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-03 15:21 ` Thomas Schmitt
2013-11-03 15:48 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-11-03 16:19 ` Thomas Schmitt
2013-11-03 16:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-03 17:16 ` Thomas Schmitt
2013-11-04 12:08 ` Andrey Borzenkov
2013-11-04 14:03 ` Thomas Schmitt
2013-11-04 14:10 ` Andrey Borzenkov
2013-11-04 14:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52767048.9050902@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--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.
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 NNTP newsgroup(s).