All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev not reading permissions
Date: Sun, 06 Feb 2005 02:28:43 +0000	[thread overview]
Message-ID: <1107656923.6297.11.camel@localhost.localdomain> (raw)
In-Reply-To: <4203F24C.7070403@healeyonline.com>

On Sat, 2005-02-05 at 14:22 -0800, Mark Healey wrote:
> Kay Sievers wrote:
> > On Sat, 2005-02-05 at 09:06 -0800, Mark Healey wrote:
> > 
> >>Kay Sievers wrote:
> >>
> >>>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?
> >>
> >>>>#]cat /etc/udev/rules.d/05-marks.rules
> >>>>SYSFS{idVendor}="0c88" SYSFS{idProduct}="0021" NAME="pilot"
> >>
> >>>>#]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"
> >>
> >>permissions file now reads:
> >>pilot:root:root:0666
> >>
> >>rules file now reads (minus mailer induced wraping):
> >>SYSFS{idVendor}="0c88", SYSFS{idProduct}="0021", NAME="pilot", MODE="0666"
> >>
> >>Still get:
> >>crw-------  1 mark root 188, 1 Feb  5 08:45 /dev/pilot
> > 
> > 
> > Strange. What does:
> >   udevinfo -q all -n /dev/pilot
> 
> [mark@buttercup ~]$ udevinfo -q all -n /dev/pilot
> P: /class/tty/ttyUSB0
> N: pilot
> T: c
> M: 020666
> S:
> O: root
> G: uucp
> F: /etc/udev/rules.d/05-marks.rules
> L: 1
> U: 18508
> R: 0
> 
> > print?
> 
> I don't know what you are asking here.

I was asking for the content of the udev database. Your rules is applied
correctly. You can see the 0666 for the mode. 

Btw: That looks like a very old version of udev and not an actual FC3
one.

> After reading Erik ban Konijnenburgs post I did some experiments.
> 
> [root@buttercup rules.d]# cat 05-marks.rules
> SYSFS{idVendor}="0c88", SYSFS{idProduct}="0021", NAME="piKYO7135", 
> MODE="0666", SYMLINK="pilot"
> 
> [root@buttercup rules.d]# ll /dev/pi*
> crw-------  1 mark root 188, 1 Feb  5 13:49 /dev/piKYO7135
> lrwxrwxrwx  1 root root      9 Feb  5 13:49 /dev/pilot -> piKYO7135
> 
> [root@buttercup rules.d]# cat 05-marks.rules
> SYSFS{idVendor}="0c88", SYSFS{idProduct}="0021", NAME="piKYO7135", 
> MODE="0666"
> 
> [root@buttercup rules.d]# ll /dev/pi*
> crw-rw-rw-  1 root root 188, 1 Feb  5 13:52 /dev/piKYO7135
> 
> [root@buttercup rules.d]# cat 05-marks.rules
> SYSFS{idVendor}="0c88", SYSFS{idProduct}="0021", NAME="piKYO7135", 
> SYMLINK="pilot"
> 
> [root@buttercup rules.d]# ll /dev/pi*
> crw-------  1 mark root 188, 0 Feb  5 13:54 /dev/piKYO7135
> lrwxrwxrwx  1 root root      9 Feb  5 13:54 /dev/pilot -> piKYO7135
> 
> It looks like when there is a SYMLINK the MODE is ignored and the 
> SYMLINK is 777ed no matter what.

You can see that something other, probably the pam-console stuff changed
the owner of the node to your username along with the permissions. As
Erik pointed out, that looks like the reason for this.

> Mabey the NAMEs and SYMLINKs should take permissions file type values. 
> Such as:
> 
> NAME="pilot:hotsyncer:hotsyncgroup:0666"

We have OWNER, GROUP, MODE. What's the problem with that?

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

  parent reply	other threads:[~2005-02-06  2:28 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
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 [this message]
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=1107656923.6297.11.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 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.