linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tino Keitel <tino.keitel@gmx.de>
To: linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org
Subject: Re: Differend udev names with different kernels
Date: Thu, 25 Sep 2008 05:47:09 +0000	[thread overview]
Message-ID: <20080925054708.GA18645@dose.home.local> (raw)
In-Reply-To: <48DB1CC4.2040004@s5r6.in-berlin.de>

On Thu, Sep 25, 2008 at 07:08:20 +0200, Stefan Richter wrote:
> Kay Sievers wrote:
>> On Wed, Sep 24, 2008 at 13:01, Tino Keitel <tino.keitel@gmx.de> wrote:
>>> what's the intention of /dev/disk/by-id/?
>>>
>>> My firewire hard disk seems to have different names with different
>>> kernels.
>>>
>>> With 2.6.26.3, it's name is
>>> /dev/disk/by-id/ieee1394-0030e001e0006585:00043c:0000.
>>>
>>> With someting after 2.6.27-rc7, merged with Arjan's fastboot branch,
>>> the disk has the same name.
>
> Then this is a regression of the fastboot patch or whatever.

It has the same name with 2.6.26.3 and with 2.6.27-rc7-something with
fastboot merged. So why would this be a regression? The different name
(scsi-...) happended with a vanilla 2.6.27-rc7.

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.

Regards,
Tino

  reply	other threads:[~2008-09-25  5:47 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 [this message]
2008-09-25 21:13       ` Stefan Richter
2008-09-25 21:23         ` Tino Keitel
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=20080925054708.GA18645@dose.home.local \
    --to=tino.keitel@gmx.de \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).