Message-ID: <45B468DE.7030902@tomt.net>
Date: Mon, 22 Jan 2007 08:33:50 +0100
From: Andre Tomt <andre@tomt.net>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
CC: Patrick Ale <patrick.ale@gmail.com>
Subject: Re: pata_sil680 module, udev and changing drive node order
References: <8d158e1f0701201623q1519c6e7m334f0c702553b666@mail.gmail.com>
In-Reply-To: <8d158e1f0701201623q1519c6e7m334f0c702553b666@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1081
Lines: 24

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/