From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Fri, 12 Aug 2005 18:03:35 +0000 Subject: Re: udev Message-Id: <20050812180335.GD3546@kroah.com> List-Id: References: <20050811182850.GD15803@kroah.com> In-Reply-To: <20050811182850.GD15803@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, Aug 12, 2005 at 11:33:09AM -0400, Mike wrote: > The main problem I was having is that when the system starts and all the > drives are there udev used my rules file and everything works. The > moment the system starts and say sdc is missing, it will read the file > and apply the rules for sda and sdb, but not apply it to any other the > drives from that point on. The default system takes over, so a drive > that I need to be sdd ends up being sdc. > > I had though about that, but wouldn't you have to regenerate the file > each time if there was a drive change? I figured the SCSI enumeration > would work the best, in the event of a fail the new drive can be plugged > in to the same particular channel and in be labeled correctly. I'll take > a look further in to the using the scsi_id Yes, use scsi_id, or a sysfs attribute. Not the scsi enumerated number, that will change all the time. good luck, greg k-h ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel