All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niv <nivv@cs.bgu.ac.il>
To: linux-hotplug@vger.kernel.org
Subject: simple question
Date: Sun, 19 Feb 2006 00:12:42 +0000	[thread overview]
Message-ID: <43F7B7FA.2070601@cs.bgu.ac.il> (raw)

Hay,

I read the udev HOWTO and I still dont understand why /dev/cdrom get a 
root:root permision.


I switched to RC_DEVICE_TARBALL="no" - so I guess I am a udev "pureist"


the line in /etc/udev/rules/50-udev.rules say:


# cdrom symlinks and other good cdrom naming

BUS="ide",    KERNEL="hd[a-z]", ACTION="add", IMPORT="/sbin/cdrom_id 
--export $tempnode"
BUS="scsi",    KERNEL="sr[0-9]*", ACTION="add", IMPORT="/sbin/cdrom_id 
--export $tempnode"
BUS="scsi",    KERNEL="scd[a-z]", ACTION="add", IMPORT="/sbin/cdrom_id 
--export $tempnode"
BUS="scsi",    KERNEL="sg[0-9]*", ACTION="add", DRIVER="sr", 
GROUP="cdrom"


#---  look here --


ENV{ID_CDROM}="?*",        SYMLINK+="cdrom%e", GROUP="cdrom"

ENV{ID_CDROM_CD_RW}="?*",    SYMLINK+="cdrw%e"
ENV{ID_CDROM_DVD}="?*",    SYMLINK+="dvd%e"
ENV{ID_CDROM_DVD_R}="?*",    SYMLINK+="dvdrw%e"


so I see GROUP="cdrom" - so It should be root:cdrom - right?


Niv




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&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-02-19  0:12 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19  0:12 Niv [this message]
2006-02-19  0:44 ` simple question Greg KH
2006-02-19  2:19 ` Mark Rosenstand
2006-02-19  2:26 ` Niv
  -- strict thread matches above, loose matches on Subject: below --
2011-04-16  2:27 Simple Question Jeff
2007-05-22 12:35 simple question Filka Michal
     [not found] ` <da3a2a260705221120x3216601doee80f297904493a0@mail.gmail.com>
2007-05-23  5:33   ` Filka Michal
2006-04-14 19:27 Nebojsa Trpkovic
2006-04-15 18:33 ` Jacob Shin
2006-01-03 21:42 Simple question LWATCDR
2006-01-03 22:24 ` James Courtier-Dutton
2005-05-19  6:23 simple question Ivan Georgiev
2005-05-19  6:23 ` Mark Studebaker
2005-05-19  6:23 ` Simple Question Jean Delvare
2005-05-19  6:23 ` Craig H. Block
2005-04-27 10:35 simple question Askar
2005-04-27 10:50 ` Mohamed Eldesoky
2005-04-27 10:58   ` Askar
2005-04-27 11:04     ` Cedric Blancher
2005-04-27 11:07       ` Cedric Blancher
2005-04-27 14:21 ` Jason Opperisano
2004-05-05 15:27 Simple question Oriol Magrané
2004-05-05 16:19 ` Aleksandar Milivojevic
2004-05-05 16:25 ` Antony Stone
2004-05-05 17:43 ` Martijn Lievaart
2004-05-06 21:45   ` Antony Stone
2003-07-31 17:53 simple question Zyman, Andy
2003-07-31 19:14 ` David Hinds
2003-07-31 20:41 ` Zyman, Andy
2003-07-31 20:59 ` David Hinds
2003-07-31 21:26 ` Joshua Schmidlkofer
2003-02-12 18:32 Simple question j.logsdon
2003-02-12 18:53 ` Jesse Pollard
2003-02-12 21:40   ` j.logsdon
2003-02-12 23:28     ` Russell Coker
2003-02-12 20:45 ` Russell Coker
2003-02-12 21:47 ` Howard Holm

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=43F7B7FA.2070601@cs.bgu.ac.il \
    --to=nivv@cs.bgu.ac.il \
    --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.