All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Subject: Re: How important is the MBR partition offset of grub-mkrescue ?
Date: Sun, 03 Nov 2013 18:16:09 +0100	[thread overview]
Message-ID: <1974651407333528403@scdbackup.webframe.org> (raw)
In-Reply-To: <52767048.9050902@gmail.com>

Hi,

i believe to have found the udev rules in Debian 6 which
govern the population of /dev/disk/by-label.

File
  /lib/udev/rules.d/60-persistent-storage.rules
has
  # probe filesystem metadata of disks
  KERNEL!="sr*", IMPORT{program}="/sbin/blkid -o udev -p $tempnode"
  ...
  ENV{ID_FS_LABEL_ENC}=="?*",     ENV{ID_FS_USAGE}=="filesystem|other", \
          SYMLINK+="disk/by-label/$env{ID_FS_LABEL_ENC}"

I understand that if blkid sets variable ID_FS_LABEL_ENC to
a non-empty value, then this will become the link name in ./by-label.
The link target is the device that is being examined by the rule.

From a USB stick with partition start LBA 1, i get:

  $ /sbin/blkid -o udev -p /dev/sdb 
  ID_PART_TABLE_TYPE=dos
  ID_FS_LABEL=epidemic-4.1-b1-1-ts-amd64
  ID_FS_LABEL_ENC=epidemic-4.1-b1-1-ts-amd64
  ID_FS_TYPE=iso9660
  ID_FS_USAGE=filesystem
  $ /sbin/blkid -o udev -p /dev/sdb1
  $

So why the hell does /dev/sdb1 become link target ?
Its ID_FS_LABEL_ENC must be empty.

Any idea how to get a verbous log of these decisions ?


Have a nice day :)

Thomas



  parent reply	other threads:[~2013-11-03 17:17 UTC|newest]

Thread overview: 15+ 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
2013-11-03 16:19           ` Thomas Schmitt
2013-11-03 16:32             ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-03 17:16           ` Thomas Schmitt [this message]
2013-11-04 12:08             ` Andrey Borzenkov
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
2013-11-04 15:44               ` 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=1974651407333528403@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.