From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Tue, 26 Oct 2004 14:57:34 +0000 Subject: Re: permissions: udev vs. pam_devperm.so Message-Id: <20041026145734.GC2009@vrfy.org> List-Id: References: <417DF0A8.2060108@bio.ifi.lmu.de> In-Reply-To: <417DF0A8.2060108@bio.ifi.lmu.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Tue, Oct 26, 2004 at 03:20:40PM +0200, Frank Steiner wrote: > Kay Sievers wrote > > >Empty fields mean default permissions, so this will not work. udev will > >overwrite everything on "add". Only the inode may be preserved, if the > >node already exists with the correct major/minor. > > Just one comment: > Having "hdc*:root:disk:660" in udev.permissions and calling "udevstart" > will always set /dev/hdc to root:disk and 600. With owner and group > fields empty, udevstart will not change the owner and the group. I'm > not sure if udevstart triggers "add" events, likely not? > > With the permission field empty, udevstart will set the permissions > to 000, although udev.conf specifies 0600 as default, so I guess this > is wrong... Yes, this seems wrong. I will fix that tonight! Thanks, Kay ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ 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