linux-kernel - Re: pata_sil680 module, udev and changing drive node order

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]

Message-ID: <45B468DE.7030902@tomt.net>
Date:	Mon, 22 Jan 2007 08:33:50 +0100
From:	Andre Tomt <andre@...t.net>
To:	linux-kernel@...r.kernel.org
CC:	Patrick Ale <patrick.ale@...il.com>
Subject: Re: pata_sil680 module, udev and changing drive node order

Patrick Ale wrote:
> The drivers load correctly but my drives seem to be in a different
> order all the time, which is not very convinient when your run md
> devices.

md does not rely on device names, it can work on array UUID's too (check 
out man mdadm.conf).

> So, my question is: how do I force a fixed order for a module handling
> two PCI cards, or how do I tell udev to always use the same mapping
> for the device nodes in /dev?

To avoid these kinds of pitfalls I usually only specify UUID's for mdadm 
to assemble, not device-names. Mount can also work with partition UUID's 
  if you are not using something like devicemapper or md in between that 
has a static device name scheme.

Beware that you may need a fairly modern initramfs/initrd setup to get 
all this to work cleanly, especially if the root device is involved.
-
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/