From: Robby Workman <rw@rlworkman.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: SOLVED: rule won't change group or permissions
Date: Sat, 02 Sep 2006 16:02:39 +0000 [thread overview]
Message-ID: <44F9AB1F.5030000@rlworkman.net> (raw)
Dexter Filmore wrote:
> Slackware 11.0rc3, kernel 2.6.17.9, udev 097
>
> In ruled.d I added a file dvd.rules whcih contains:
>
> BUS="ide", KERNEL="hdc", SYMLINK+="dvd", GROUP="xcdwrite", MODE="0666"
> BUS="ide", KERNEL="hdd", SYMLINK+="brenner", GROUP="xcdwrite", MODE="0666"
>
> While the symlinks are set properly and hence the rule seems to be parsed and
> processed, the group and permissions settings do not take effect.
> I don't know what I'm doing wrong here.
Solved offlist on ##slackware@freenode.
The dvd.rules file entries above were properly setting ownership,
but the default udev.rules file (which is looked after dvd.rules)
was changing them to the system default gid of "cdrom." Changing
the GROUP="whatever" to GROUP:="whatever" makes it permanent -
from udev(7):
:= Assign a value to a key finally; disallow any later changes,
which may be used to prevent changes by any later rules.
RW
--
http://rlworkman.net
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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
reply other threads:[~2006-09-02 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44F9AB1F.5030000@rlworkman.net \
--to=rw@rlworkman.net \
--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).