From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.6.6/udev weirdness
Date: Thu, 13 May 2004 18:15:44 +0000 [thread overview]
Message-ID: <40A3BB50.7050802@backtobasicsmgmt.com> (raw)
In-Reply-To: <20040512235509.GA3836@heliopause.vort.org>
Russell Neches wrote:
> So, I think it's a fair question: how, generally, does one write stable
> rules? I can see easily enough how to write rules that always _match_
> the same thing, but what should I take into account to insure that the
> rule will always _do_ the same thing?
You need to make your rules as specific as you can without restricting
your ability to deal with port/slot/etc. changes. Using "scsi" as an
identifier is far too ambiguous, where "sd" is much better.
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click
_______________________________________________
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
next prev parent reply other threads:[~2004-05-13 18:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 23:55 2.6.6/udev weirdness Russell Neches
2004-05-13 5:59 ` Greg KH
2004-05-13 17:51 ` Russell Neches
2004-05-13 18:15 ` Kevin P. Fleming [this message]
2004-05-13 21:02 ` Greg KH
2004-05-15 5:42 ` Russell Neches
2004-05-16 9:21 ` Daniel Drake
2004-05-16 21:03 ` Russell Neches
2004-05-17 9:49 ` Daniel Drake
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=40A3BB50.7050802@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.