From mboxrd@z Thu Jan 1 00:00:00 1970 From: martin f krafft Date: Fri, 17 Dec 2004 14:52:11 +0000 Subject: Re: Bug#286040: please allow permissions.d to follow symlinks Message-Id: <20041217145211.GA27638@cirrus.madduck.net> MIME-Version: 1 Content-Type: multipart/mixed; boundary="y0ulUmNC+osPPQO6" List-Id: References: <20041217083115.GA4050@wonderland.linux.it> In-Reply-To: <20041217083115.GA4050@wonderland.linux.it> To: linux-hotplug@vger.kernel.org --y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable also sprach Kay Sievers [2004.12.17.1545 +0100]: > > > 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? Why do you need a pointer? Please consider standard usage scenarios instead! You are defending the integrity of your code when I try to tell you that it does not optimally service the user. Your code is fine, I am arguing that you should take a different perspective to permissions management: a perspective that is pragmatic, not theoretical and pedantic. > > 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. >=20 > I don't ask you. Please try to convince somebody else. Oh bother, why is it that open source developers always assume that they are smarter than the rest of the world? > For my part, I've made my points clear: The addition of symlinks > should never affect the specified behavior of the device node. =2E.. unless the administrator specifies permissions to be used for the device identified by the symlink. --=20 .''`. martin f. krafft : :' : proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system =20 Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! --y0ulUmNC+osPPQO6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBwvKbIgvIgzMMSnURAo9XAJ9125xS5zpPTOS/1KbwGGlVa/O+XACgxMgW gZyuZi7gO47+SRFiKTxaC7U= =8MHy -----END PGP SIGNATURE----- --y0ulUmNC+osPPQO6-- ------------------------------------------------------- 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