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] [day] [month] [year] [list]

Date:	Thu, 25 Sep 2008 23:23:50 +0200
From:	Tino Keitel <tino.keitel@....de>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	linux-kernel@...r.kernel.org, linux-hotplug@...r.kernel.org,
	Kay Sievers <kay.sievers@...y.org>
Subject: Re: Differend udev names with different kernels

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
--
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/