From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev not reading permissions
Date: Sat, 05 Feb 2005 15:07:35 +0000 [thread overview]
Message-ID: <1107616055.5494.92.camel@localhost.localdomain> (raw)
In-Reply-To: <4203F24C.7070403@healeyonline.com>
On Fri, 2005-02-04 at 14:08 -0800, Mark Healey wrote:
> I hope I'm not pissing anybody off but I can't find a support list. If
> I am, sorry.
>
> Anyway, it seems that udev is ignoring my 05-marks.permissions. I would
> like to use my FC3 box to back up my Kyocera 7135 smartphone. Here is
> what I think is the relevant info. What am I doing wrong?
>
> #] ls -l /etc/udev/rules.d
> total 28
> -rw-r--r-- 1 root root 60 Jan 31 21:56 05-marks.rules
> -rw-r--r-- 1 root root 146 Sep 29 06:38 10-wacom.rules
> -rw-r--r-- 1 root root 4739 Dec 15 07:34 50-udev.rules
>
> #]cat /etc/udev/rules.d/05-marks.rules
> SYSFS{idVendor}="0c88" SYSFS{idProduct}="0021" NAME="pilot"
>
> #]ls -l /etc/udev/permissions.d
> total 16
> -rw-r--r-- 1 root root 20 Feb 1 06:32 05-marks.permissions
> -rw-r--r-- 1 root root 3508 Dec 15 07:34 50-udev.permissions
>
> #]cat /etc/udev/permissions.d/05-marks.permissions
> pilot:root:root:666
>
> #]ls -l /dev/pi*
> crw------- 1 mark root 188, 0 Feb 4 13:52 /dev/pilot
Hmm, does the rule work without ',' between the keys?
And please use 4 digit octal numbers for the mode.
Other than that, I can't see what's going wrong here. How about just
adding the permissions to the rule. In newer versions of udev
the .permissions files are gone and you need to specify it along with
the rules anyway.
SYSFS{idVendor}="0c88", SYSFS{idProduct}="0021", NAME="pilot", MODE="0666"
Good luck,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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:[~2005-02-05 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 22:08 udev not reading permissions Mark Healey
2005-02-05 7:50 ` Greg KH
2005-02-05 15:07 ` Kay Sievers [this message]
2005-02-05 17:06 ` Mark Healey
2005-02-05 17:16 ` Kay Sievers
2005-02-05 19:10 ` Erik van Konijnenburg
2005-02-05 22:22 ` Mark Healey
2005-02-06 2:28 ` Kay Sievers
2005-02-06 17:42 ` Mark Healey
2005-02-06 19:04 ` 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=1107616055.5494.92.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).