linux-kernel - Re: Differend udev names with different kernels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 24 Sep 2008 23:09:03 -0700
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Stefan Richter" <stefanr@...6.in-berlin.de>
Cc:	linux-kernel@...r.kernel.org, linux-hotplug@...r.kernel.org
Subject: Re: Differend udev names with different kernels

On Wed, Sep 24, 2008 at 22:59, Stefan Richter <stefanr@...6.in-berlin.de> wrote:
> I wrote:
>>>
>>> On Wed, Sep 24, 2008 at 13:01, Tino Keitel <tino.keitel@....de> wrote:
>>>>
>>>> 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.
>>
>> I will watch what will happen in 2.6.28-rc.
>>
>>>> With 2.6.27-rc7, it is called
>>>> /dev/disk/by-id/scsi-1WDC_WD10EACS-00D6B0_WD-WCAU41668315.
>
> Uh, sorry, I misunderstood.  It is a regression of mainline then.

Yeah, I have more reports from people, that with recent kernels, the
ieee1394-* links showed up and replaced the scsi-* links, which they
say never happended before.
We ship these rules for a long time now, so I just guessed, they never
really worked before, but as all depends on timing, it's probably not
predictable what happens. Regardless of the needed fix for scsi sysfs,
we should provide both links, I guess.

Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/