linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dark_mail@gmx.net
To: linux-hotplug@vger.kernel.org
Subject: How to find out which udev rule is applied?
Date: Mon, 29 Jan 2007 22:12:32 +0000	[thread overview]
Message-ID: <45BE7150.4050108@gmx.net> (raw)

First, I hope I'm on the right mailinglist for my question, and
apologize if I'm not ...

How can I find out which rule (at least which rule file) udev uses to
generate/assign device nodes?
udevmonitor doesn't give me much information on that.

To make myself clear, my actual problem:
I have a printer/scanner combo, which is working but one problem: Since
some time ago, /dev/usb/lp0 is assigned to root:scanner instead of
root:lp, causing cups to fail.

I already edited some rules files in hope to sort it out, but without
success.

Now I'd like to find out which rule is actually used to create the
device node, so I can either modify it or make my own rule setting the
permissions.

Is there a way to achieve this?

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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

             reply	other threads:[~2007-01-29 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-29 22:12 dark_mail [this message]
2007-01-29 22:29 ` How to find out which udev rule is applied? Kay Sievers

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=45BE7150.4050108@gmx.net \
    --to=dark_mail@gmx.net \
    --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).