linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell Neches <russell@ccs.neu.edu>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.6.6/udev weirdness
Date: Thu, 13 May 2004 17:51:38 +0000	[thread overview]
Message-ID: <20040513175138.GA9929@heliopause.vort.org> (raw)
In-Reply-To: <20040512235509.GA3836@heliopause.vort.org>



> You wrote stupid rules :)

So I gather.

> > I've tried several permutations, and the above is the only way I
> > could obtain the desired results under 2.6.5, and under 2.6.6, I
> > can't get /dev/jumpdrive to point to /dev/sda1 at all. 
>
> Try disabling sg support if you don't want that.  Or just add the
> following to your rules: KERNEL="sd*"

Oh, I see. KERNEL="sd*[1-9]" seems to work.

> That should only make your names bind to the block devices, not the
> other scsi devices.
>
> > The likely stupidity of the above rules notwithstanding, the
> > underlying behavior of the system changed, and my rules broke. That
> > shouldn't happen, even if the rules are dumb. This is a Bad Thing. 
>
> Um, dumb rules are a Bad Thing, nothing we can do here about that :)

No doubt about that. My point is that dumb rules should probably
continue to do the same dumb thing, at least if you're only moving
between stable kernels.

I guess this is what I deserve for reading the documentation and
following the examples. The documentation does mention that some values
are stable, and thus worthy of matching against, and others are not.
However, it doesn't give any rational for distinguishing them. I
mistakenly assumed that by matching aginst the serial number the rule
would always do the same thing. And, it does seem to match the same
physical device... it just symlinks the wrong part of it (sometimes).
I'd guess it was a side effect of changing the tree of virtual devices.

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?

Russell




-------------------------------------------------------
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

  parent reply	other threads:[~2004-05-13 17:51 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 [this message]
2004-05-13 18:15 ` Kevin P. Fleming
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=20040513175138.GA9929@heliopause.vort.org \
    --to=russell@ccs.neu.edu \
    --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).