From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Fri, 17 Dec 2004 14:45:54 +0000 Subject: Re: Bug#286040: please allow permissions.d to follow symlinks Message-Id: <1103294755.14134.230.camel@localhost.localdomain> List-Id: References: <20041217083115.GA4050@wonderland.linux.it> In-Reply-To: <20041217083115.GA4050@wonderland.linux.it> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, 2004-12-17 at 15:35 +0100, martin f krafft wrote: > also sprach Kay Sievers [2004.12.17.1520 +0100]: > > Can you read code? > > Depends on who wrote it. Mostly me. > > If yes, please point me to the chmod() of a symlink. I will fix it. > > I was giving an example. And where is the pointer to the code to proof your loud/proud claim? > udev currently obtains the permissions to > use on node creation from the permissions.d list. Symlinks are > created without special permissions, or reference to the permissions > list. Right. > If you ask me, permissions.d list should be extended by inner join > with the symlinks list for each node. Then I would not have to touch > symlinks and only the actual device pointed to gets changed. I don't ask you. Please try to convince somebody else. For my part, I've made my points clear: The addition of symlinks should never affect the specified behavior of the device node. Kay ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ 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