From: Mark Healey <marklist@healeyonline.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev not reading permissions
Date: Sun, 06 Feb 2005 17:42:02 +0000 [thread overview]
Message-ID: <420656EA.2080000@healeyonline.com> (raw)
In-Reply-To: <4203F24C.7070403@healeyonline.com>
Kay Sievers wrote:
> Btw: That looks like a very old version of udev and not an actual FC3
> one.
I never installed it independently. Mabey Redhad it laging on keeping
this one up to date.
> 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.
As long as it ignores symlinks I can get by.
>>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?
I was thinking so that you could do symlinks seperately.
--
Mark Healey
marklist@healeyonline.com
-------------------------------------------------------
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-06 17:42 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
2005-02-06 17:42 ` Mark Healey [this message]
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=420656EA.2080000@healeyonline.com \
--to=marklist@healeyonline.com \
--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.