linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev
Date: Fri, 12 Aug 2005 18:03:35 +0000	[thread overview]
Message-ID: <20050812180335.GD3546@kroah.com> (raw)
In-Reply-To: <20050811182850.GD15803@kroah.com>

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

  parent reply	other threads:[~2005-08-12 18:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 18:28 udev Greg KH
2005-08-11 18:29 ` udev Mike
2005-08-11 19:16 ` udev Greg KH
2005-08-11 19:21 ` udev Mike
2005-08-11 19:36 ` udev Kay Sievers
2005-08-12 15:33 ` udev Mike
2005-08-12 18:03 ` Greg KH [this message]
2009-11-02 11:10 ` udev Oleg Puchinin
2009-11-02 11:50 ` udev Oleg Puchinin
2009-11-02 14:35 ` udev Andrey Borzenkov
2009-11-02 16:57 ` udev Alan Jenkins
2011-03-22 19:48 ` Udev Paulo Eliseu Weber
2011-03-22 19:58 ` Udev Kay Sievers
  -- strict thread matches above, loose matches on Subject: below --
2010-08-18  9:51 UDEV Тима
2010-08-18 12:49 ` UDEV Greg KH
2010-08-19 15:27 ` UDEV Greg KH
2010-08-24 12:50 ` UDEV Greg KH
2004-08-08 22:47 udev Luke Kenneth Casson Leighton
2004-08-09 12:36 ` udev Luke Kenneth Casson Leighton
2004-08-09 12:40 ` udev Marco d'Itri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050812180335.GD3546@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).