udev not reading permissions

udev not reading permissions

[Mark Healey]

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?

#] ls -l /etc/udev/rules.d
total 28
-rw-r--r--  1 root root   60 Jan 31 21:56 05-marks.rules
-rw-r--r--  1 root root  146 Sep 29 06:38 10-wacom.rules
-rw-r--r--  1 root root 4739 Dec 15 07:34 50-udev.rules

#]cat /etc/udev/rules.d/05-marks.rules
SYSFS{idVendor}="0c88" SYSFS{idProduct}="0021" NAME="pilot"

#]ls -l /etc/udev/permissions.d
total 16
-rw-r--r--  1 root root   20 Feb  1 06:32 05-marks.permissions
-rw-r--r--  1 root root 3508 Dec 15 07:34 50-udev.permissions

#]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


-- 
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

Re: udev not reading permissions

[Greg KH]

On Fri, Feb 04, 2005 at 02:08:12PM -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?
> 
> #] ls -l /etc/udev/rules.d
> total 28
> -rw-r--r--  1 root root   60 Jan 31 21:56 05-marks.rules
> -rw-r--r--  1 root root  146 Sep 29 06:38 10-wacom.rules
> -rw-r--r--  1 root root 4739 Dec 15 07:34 50-udev.rules
> 
> #]cat /etc/udev/rules.d/05-marks.rules
> SYSFS{idVendor}="0c88" SYSFS{idProduct}="0021" NAME="pilot"
> 
> #]ls -l /etc/udev/permissions.d
> total 16
> -rw-r--r--  1 root root   20 Feb  1 06:32 05-marks.permissions
> -rw-r--r--  1 root root 3508 Dec 15 07:34 50-udev.permissions
> 
> #]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

What version of udev?

What does 'udevtest' for the device say?

thanks,

greg k-h


-------------------------------------------------------
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

Re: udev not reading permissions

[Kay Sievers]

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?
> 
> #] ls -l /etc/udev/rules.d
> total 28
> -rw-r--r--  1 root root   60 Jan 31 21:56 05-marks.rules
> -rw-r--r--  1 root root  146 Sep 29 06:38 10-wacom.rules
> -rw-r--r--  1 root root 4739 Dec 15 07:34 50-udev.rules
> 
> #]cat /etc/udev/rules.d/05-marks.rules
> SYSFS{idVendor}="0c88" SYSFS{idProduct}="0021" NAME="pilot"
> 
> #]ls -l /etc/udev/permissions.d
> total 16
> -rw-r--r--  1 root root   20 Feb  1 06:32 05-marks.permissions
> -rw-r--r--  1 root root 3508 Dec 15 07:34 50-udev.permissions
> 
> #]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"

Good luck,
Kay




-------------------------------------------------------
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

Re: udev not reading permissions

[Mark Healey]

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

How do I determine the version?  I'm just uning yum to keep things up to 
date.

-- 
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

Re: udev not reading permissions

[Kay Sievers]

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

print?

> How do I determine the version?  I'm just uning yum to keep things up to 
> date.

udevinfo -V

But the version in FC3 should be fine.

Kay



-------------------------------------------------------
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

Re: udev not reading permissions

[Erik van Konijnenburg]

On Sat, Feb 05, 2005 at 09:06:55AM -0800, Mark Healey wrote:
> Kay Sievers wrote:
> > On Fri, 2005-02-04 at 14:08 -0800, Mark Healey wrote:
> > ...
> >>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?
> ...
> >>#]ls -l /dev/pi*
> >>crw-------  1 mark root 188, 0 Feb  4 13:52 /dev/pilot

It could it be console.perms kicks in, overriding the udev permissions.

On my FC3 box:

	[root@aardbei security]# grep pilot /etc/security/console.perms
	<pilot>=/dev/pilot
	<console>  0600 <pilot>      0660 root.uucp
	[root@aardbei security]#

Your file modes are consistent with these settings.
Console.perms is interpreted by PAM when you log in.

Regards,
Erik


-------------------------------------------------------
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

Re: udev not reading permissions

[Mark Healey]

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

Re: udev not reading permissions

[Kay Sievers]

On Sat, 2005-02-05 at 14:22 -0800, Mark Healey wrote:
> 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.

I was asking for the content of the udev database. Your rules is applied
correctly. You can see the 0666 for the mode. 

Btw: That looks like a very old version of udev and not an actual FC3
one.

> 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.

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.

> 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?

Thanks,
Kay




-------------------------------------------------------
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

Re: udev not reading permissions

[Mark Healey]

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

Re: udev not reading permissions

[Kay Sievers]

On Sun, 2005-02-06 at 09:42 -0800, Mark Healey wrote:
> 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.

Be aware that the pam_console.dev uses the symlink names to match what
to apply.

> >>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.

Symlink permissions are meaningless. 

Thanks,
Kay



-------------------------------------------------------
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