All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Alan Jenkins <sourcejedi.lkml@googlemail.com>
Cc: Linda Walsh <lkml@tlinx.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: disk Partition label changes and reflecting them in 	/dev/disks-by-label/
Date: Sun, 19 Jul 2009 14:19:16 -0400	[thread overview]
Message-ID: <4A6363A4.5020504@rtr.ca> (raw)
In-Reply-To: <9b2b86520907190922wb4f809dr5a315155211d6744@mail.gmail.com>

Alan Jenkins wrote:
>
> The latest version of udev listens for inotify events on block
> devices.  When a utility writes to the block device (or rather, when
> it closes it after opening it for writing), Udev will synthesize a
> "change" event.  The standard udev rules will re-check the device, and
> update the links under /dev/disk to reflect changes in labels etc.
..

Yes, it seems to catch LABEL changes just fine.

On a related note:
But not UUID changes for some reason (?).

      reply	other threads:[~2009-07-19 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-19 15:01 disk Partition label changes and reflecting them in /dev/disks-by-label/ Linda Walsh
2009-07-19 16:22 ` Alan Jenkins
2009-07-19 18:19   ` Mark Lord [this message]

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=4A6363A4.5020504@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@tlinx.org \
    --cc=sourcejedi.lkml@googlemail.com \
    /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.