From: Morgan Read <mstuff@read.org.nz>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev.rules can't set group or mode?
Date: Mon, 31 Jul 2006 21:55:08 +0000 [thread overview]
Message-ID: <44CE7C3C.3070805@read.org.nz> (raw)
In-Reply-To: <eac3k5$ces$1@sea.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1934 bytes --]
Kay Sievers wrote:
> On Sun, 2006-07-30 at 17:02 +1200, Morgan Read wrote:
>> Kay Sievers wrote:
>>> On Sat, 2006-07-29 at 23:29 +1200, Morgan Read wrote:
>>>> Kay Sievers wrote:
>>>>> On Fri, 2006-07-28 at 16:25 +1200, Morgan Read wrote:
>> ...
>>>> [morgan@morgansmachine ~]$ rpm -q udev
>>>> udev-084-13
>>>>
>>>> Changed rule to:
>>>> DRIVER=="ark3116", SYMLINK+="nokiaca42clone", MODE="0666"
>>>> (Was following the 0.6 version of
>>>> http://www.reactivated.net/writing_udev_rules.html.)
>>> Right, that should probably be mentioned, that we don't recommend
>>> changing 'default' names, except to make them match the 'default', like
>>> moving the input devices in a subdirectory where they have always lived,
>>> long before udev.
>>>
>>> Better create only symlinks, and nothing else will break by making
>>> (silly) assumptions about /dev.
>>>
>>>> Now the device files have the correct group and owner, but mode wont
>>>> change? With the new rule mode is 0660?
>>> That may be Fedora's pam_console, that comes into your way and changes
>>> it back. Look at udevtest again to see what udev is doing.
>> Hmm, but according to udevtest (below), pam is the last thing to run?
>> And, l 4 of udevtest says it's creating "mode = '0660'", which ain't
>> right? If the problem is pam_console, how would I deal to it?
>> '1', mode = '0660', uid = '0', gid = '14'
>
> No, it's not pam_console, udevd creates the device with 0660. Eigther
> your rule format is wrong, or some later rule matches too and overwrites
> the previous mode.
Hi Kay,
Many thanks - changed name from 10-local.rules to z-local.rules. Now
works fine. But, I understood that correct protocol was to name custom
rules to run before defaults - any risks in my new naming scheme?
M.
--
Morgan Read
NEW ZEALAND
<mailto:mstuffATreadDOTorgDOTnz>
fedora: Freedom Forever!
http://fedoraproject.org/wiki/Overview
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
[-- Attachment #2: Type: text/plain, Size: 348 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 226 bytes --]
_______________________________________________
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:[~2006-07-31 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 4:25 udev.rules can't set group or mode? Morgan Read
2006-07-28 22:12 ` Kay Sievers
2006-07-29 11:29 ` Morgan Read
2006-07-29 11:47 ` Kay Sievers
2006-07-30 5:02 ` Morgan Read
2006-07-30 10:19 ` Kay Sievers
2006-07-31 21:55 ` Morgan Read [this message]
2006-08-01 12:23 ` 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=44CE7C3C.3070805@read.org.nz \
--to=mstuff@read.org.nz \
--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).