From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH, UDEV] fix permission inconsistency in relation to symlinks.
Date: Sat, 05 Feb 2005 14:33:44 +0000 [thread overview]
Message-ID: <20050205143344.GA10544@wonderland.linux.it> (raw)
In-Reply-To: <200502051426.14173.mbuesch@freenet.de>
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
On Feb 05, Kay Sievers <kay.sievers@vrfy.org> wrote:
> Should we change that now, so that permissions are applied from a
> symlink-only rule too?
Yes!
I think it's the sensible semantic: the second rule adds a new SYMLINK
*and* sets the permissions of the node, which are two distinct
operations applied by the same rule.
Unless you think it's broken, I will add the patch to the debian package
of 051 (almost ready).
--
ciao,
Marco
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-05 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-05 13:26 [PATCH, UDEV] fix permission inconsistency in relation to symlinks Michael Buesch
2005-02-05 14:29 ` [PATCH, UDEV] fix permission inconsistency in relation to Kay Sievers
2005-02-05 14:33 ` Marco d'Itri [this message]
2005-02-05 14:54 ` [PATCH, UDEV] fix permission inconsistency in relation to symlinks Michael Buesch
2005-02-05 14:58 ` [PATCH, UDEV] fix permission inconsistency in relation to Kay Sievers
2005-02-05 15:09 ` [PATCH, UDEV] fix permission inconsistency in relation to symlinks Michael Buesch
2005-02-05 15:20 ` [PATCH, UDEV] fix permission inconsistency in relation to Kay Sievers
2005-02-05 15:25 ` [PATCH, UDEV] fix permission inconsistency in relation to symlinks Michael Buesch
2005-02-05 15:30 ` [PATCH, UDEV] fix permission inconsistency in relation to Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050205143344.GA10544@wonderland.linux.it \
--to=md@linux.it \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.