All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Baulig <iparanoid@gmx.de>
To: linux-hotplug@vger.kernel.org
Subject: Rules are not applied to node
Date: Thu, 01 Jun 2006 16:54:04 +0000	[thread overview]
Message-ID: <447F1BAC.5080902@gmx.de> (raw)

Hoi!

I'm currently having problems getting the rights of my graphics adapter 
set correctly. I have following rule in /etc/udev/rules.d/10-local.rules

KERNEL="card[0-9]*",           NAME="dri/%k", MODE="0666"

However, after booting if I ls -lisa my /dev/dri I get following output:

25119 0 crw-rw----  1 root root 226, 0 2006-06-01 18:02 card0

Well, I set udev_log to debug and searched my syslog for some 
Inforation. less /var/log/syslog | grep udev | grep card0 gives me 
following output:

Jun  1 18:02:11 localhost udevd-event[6621]: udev_rules_get_name: rule 
applied, 'card0' becomes 'dri/card0'
Jun  1 18:02:11 localhost udevd-event[6621]: udev_db_get_device: no db 
file to read /dev/.udev/db/class@drm@card0: No such file or directory
Jun  1 18:02:11 localhost udevd-event[6621]: udev_node_add: creating 
device node '/dev/dri/card0', major = '226', minor = '0', mode = '0666', 
uid = '0', gid = '44'
Jun  1 18:02:11 localhost udevd-event[6621]: udev_node_mknod: preserve 
file '/dev/dri/card0', because it has correct dev_t

It looks like eveything works fine, except that last line looks a little 
bit suspicious, however, I do not know what it means and google aswell 
as the mailing list archives gave me no interesting hits to 
udev_node_mknod - actually the list gave me none and google only 2 not 
of interest. I really don't know any further.

uname -r: 2.6.16-1-686
udevinfo -V: udevinfo, version 091

Greets

Daniel


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x107521&bid$8729&dat\x121642
_______________________________________________
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:[~2006-06-01 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 16:54 Daniel Baulig [this message]
2006-06-01 21:43 ` Rules are not applied to node Greg KH
2006-06-02  1:53 ` Alexander E. Patrakov
2006-06-02 16:34 ` Daniel Baulig

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=447F1BAC.5080902@gmx.de \
    --to=iparanoid@gmx.de \
    --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.