From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Subject: How important is the MBR partition offset of grub-mkrescue ?
Date: Sat, 02 Nov 2013 19:57:18 +0100 [thread overview]
Message-ID: <10533651190322788149@scdbackup.webframe.org> (raw)
Hi,
i stumbled over a problem in the handling of grub-mkrescue
images on USB stick by Linux in /dev/disk/by-label.
The first MBR partition begins at 512-LBA 1 and thus is
not mountable as ISO image. I understand this is intentional.
ISO filesystems have a label (Volume Id) which gets used
for auto-mounting and shows up in modern Linuxes as
symbolic link in directory /dev/disk/by-label.
But Linux (or its udev) insists in linking to /dev/sdX1
rather than to /dev/sdX, where the ISO filesystem is
mountable.
So this link cannot be used for mounting the ISO.
I hate automounters, but /dev/disk/by-label is also
a good way for a booting system to find its own
filesystem from where it stems.
----------------------------------------------------------
Is a workaround known on Linux side ? (E.g. is it a known
bug in udev configurations which can be fixed ?)
How important ist the partition start at LBA 1 in comparison
to this obvious drawback of grub-mkrescue images on Linux ?
(Start at LBA 0 solves the problem but makes the MBR part
of the first partition. I understand this is undesirable
somehow.)
Actually i wanted to show a system packager how to
use ./by-label instead of test-mounting all files in
/proc/partitions. Are there other methods which one
could use in the Linux initial RAM disk to find the
USB stick from where GRUB2 did boot ?
Have a nice day :)
Thomas
next reply other threads:[~2013-11-02 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 18:57 Thomas Schmitt [this message]
2013-11-02 23:42 ` How important is the MBR partition offset of grub-mkrescue ? 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
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=10533651190322788149@scdbackup.webframe.org \
--to=scdbackup@gmx.net \
--cc=grub-devel@gnu.org \
/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).