linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tino Keitel <tino.keitel@gmx.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: Differend udev names with different kernels
Date: Thu, 25 Sep 2008 21:23:50 +0000	[thread overview]
Message-ID: <20080925212350.GA30425@x61> (raw)
In-Reply-To: <48DBFEEF.8090109@s5r6.in-berlin.de>

On Thu, Sep 25, 2008 at 23:13:19 +0200, Stefan Richter wrote:

[...]

>> Initially, my intention was to find a unique name for the hard disk,
>> that stays even if the disk is changed from Firewire to USB. However,
>> this doesn't seem to be possible with a default udev.

[...]

> An alternative though would be filesystem labels or filesystem UUIDs, if  
> unique and persistent identifiers at the filesystem level rather than at  
> the block device level are sufficient for your needs.

Not really. My initial problem was that a volume sometimes came up very
late, so that the lvm2 initscript didn't activate that volume group. So
I wanted to wait for this specific disk during boot. Meanwhile, I
created an udev rule that uses the vendor and device name, which also
has the advantage of being the same when the disk is connected via
Firewire and USB (or, should be the same at least, I didn't test USB
yet).

Regards,
Tino

  reply	other threads:[~2008-09-25 21:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 20:01 Differend udev names with different kernels Tino Keitel
2008-09-25  3:12 ` Kay Sievers
2008-09-25  5:08   ` Stefan Richter
2008-09-25  5:47     ` Tino Keitel
2008-09-25 21:13       ` Stefan Richter
2008-09-25 21:23         ` Tino Keitel [this message]
2008-09-25  5:59     ` Stefan Richter
2008-09-25  6:09       ` Kay Sievers

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=20080925212350.GA30425@x61 \
    --to=tino.keitel@gmx.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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).