From: Erik van Konijnenburg <ekonijn@xs4all.nl>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev not reading permissions
Date: Sat, 05 Feb 2005 19:10:14 +0000 [thread overview]
Message-ID: <20050205201014.A17478@banaan.localdomain> (raw)
In-Reply-To: <4203F24C.7070403@healeyonline.com>
On Sat, Feb 05, 2005 at 09:06:55AM -0800, Mark Healey wrote:
> Kay Sievers wrote:
> > On Fri, 2005-02-04 at 14:08 -0800, Mark Healey wrote:
> > ...
> >>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 /dev/pi*
> >>crw------- 1 mark root 188, 0 Feb 4 13:52 /dev/pilot
It could it be console.perms kicks in, overriding the udev permissions.
On my FC3 box:
[root@aardbei security]# grep pilot /etc/security/console.perms
<pilot>=/dev/pilot
<console> 0600 <pilot> 0660 root.uucp
[root@aardbei security]#
Your file modes are consistent with these settings.
Console.perms is interpreted by PAM when you log in.
Regards,
Erik
-------------------------------------------------------
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 19:10 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 [this message]
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=20050205201014.A17478@banaan.localdomain \
--to=ekonijn@xs4all.nl \
--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).