From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Healey Date: Sat, 05 Feb 2005 22:22:28 +0000 Subject: Re: udev not reading permissions Message-Id: <42054724.3030503@healeyonline.com> List-Id: References: <4203F24C.7070403@healeyonline.com> In-Reply-To: <4203F24C.7070403@healeyonline.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Kay Sievers wrote: > On Sat, 2005-02-05 at 09:06 -0800, Mark Healey wrote: > >>Kay Sievers wrote: >> >>>On Fri, 2005-02-04 at 14:08 -0800, Mark Healey wrote: >>> >>> >>>>I hope I'm not pissing anybody off but I can't find a support list. If >>>>I am, sorry. >>>> >>>>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? >> >>>>#]cat /etc/udev/rules.d/05-marks.rules >>>>SYSFS{idVendor}="0c88" SYSFS{idProduct}="0021" NAME="pilot" >> >>>>#]cat /etc/udev/permissions.d/05-marks.permissions >>>>pilot:root:root:666 >> >>>>#]ls -l /dev/pi* >>>>crw------- 1 mark root 188, 0 Feb 4 13:52 /dev/pilot >>> >>> >>>Hmm, does the rule work without ',' between the keys? >>>And please use 4 digit octal numbers for the mode. >>> >>>Other than that, I can't see what's going wrong here. How about just >>>adding the permissions to the rule. In newer versions of udev >>>the .permissions files are gone and you need to specify it along with >>>the rules anyway. >>> >>> SYSFS{idVendor}="0c88", SYSFS{idProduct}="0021", NAME="pilot", MODE="0666" >> >>permissions file now reads: >>pilot:root:root:0666 >> >>rules file now reads (minus mailer induced wraping): >>SYSFS{idVendor}="0c88", SYSFS{idProduct}="0021", NAME="pilot", MODE="0666" >> >>Still get: >>crw------- 1 mark root 188, 1 Feb 5 08:45 /dev/pilot > > > Strange. What does: > udevinfo -q all -n /dev/pilot [mark@buttercup ~]$ udevinfo -q all -n /dev/pilot P: /class/tty/ttyUSB0 N: pilot T: c M: 020666 S: O: root G: uucp F: /etc/udev/rules.d/05-marks.rules L: 1 U: 18508 R: 0 > print? I don't know what you are asking here. After reading Erik ban Konijnenburgs post I did some experiments. [root@buttercup rules.d]# cat 05-marks.rules SYSFS{idVendor}="0c88", SYSFS{idProduct}="0021", NAME="piKYO7135", MODE="0666", SYMLINK="pilot" [root@buttercup rules.d]# ll /dev/pi* crw------- 1 mark root 188, 1 Feb 5 13:49 /dev/piKYO7135 lrwxrwxrwx 1 root root 9 Feb 5 13:49 /dev/pilot -> piKYO7135 [root@buttercup rules.d]# cat 05-marks.rules SYSFS{idVendor}="0c88", SYSFS{idProduct}="0021", NAME="piKYO7135", MODE="0666" [root@buttercup rules.d]# ll /dev/pi* crw-rw-rw- 1 root root 188, 1 Feb 5 13:52 /dev/piKYO7135 [root@buttercup rules.d]# cat 05-marks.rules SYSFS{idVendor}="0c88", SYSFS{idProduct}="0021", NAME="piKYO7135", SYMLINK="pilot" [root@buttercup rules.d]# ll /dev/pi* crw------- 1 mark root 188, 0 Feb 5 13:54 /dev/piKYO7135 lrwxrwxrwx 1 root root 9 Feb 5 13:54 /dev/pilot -> piKYO7135 It looks like when there is a SYMLINK the MODE is ignored and the SYMLINK is 777ed no matter what. Mabey the NAMEs and SYMLINKs should take permissions file type values. Such as: NAME="pilot:hotsyncer:hotsyncgroup:0666" Anyway it looks like you have a conflict with some other service and will have to decide which will take priority. Thanks and Good Luck -- 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