From: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: James Youngman <jay-mXXj517/zsQ@public.gmane.org>
Cc: Niraj Kumar <niraj17-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
hch-jcswGhMUV9g@public.gmane.org,
nick.couchman-nV4p5R2ZCaoAvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] unrestricted_chown : userspace part
Date: Tue, 9 Dec 2008 11:56:07 +0100 [thread overview]
Message-ID: <20081209105607.GF15416@nb.net.home> (raw)
In-Reply-To: <c5df85930812090136v7a3bdce8o7a8b70c25ab2827b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, Dec 09, 2008 at 09:36:54AM +0000, James Youngman wrote:
> On Tue, Dec 9, 2008 at 4:32 AM, Niraj Kumar <niraj17-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >
> >
> > Unrestricted chown: Userspace patch for mount program
> >
> > This patch adds "unrestricted_chown" option to
> > mount program. This option is used to disable
> > the Posix _POSIX_CHOWN_RESTRICTED chown option on a given
> > filesystem which forbids non-privilegued users to give away files.
>
> The name [no]restrict_chown would be more in keeping with the names of
> the existing mount options. Failing that perhaps chown=restricted.
Yeah, the proposed name "unrestricted_chown" is ugly and terribly long.
Karel
--
Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-12-09 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 4:32 [PATCH] unrestricted_chown : userspace part Niraj Kumar
2008-12-09 9:36 ` James Youngman
[not found] ` <c5df85930812090136v7a3bdce8o7a8b70c25ab2827b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-12-09 10:56 ` Karel Zak [this message]
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=20081209105607.GF15416@nb.net.home \
--to=kzak-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=hch-jcswGhMUV9g@public.gmane.org \
--cc=jay-mXXj517/zsQ@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nick.couchman-nV4p5R2ZCaoAvxtiuMwx3w@public.gmane.org \
--cc=niraj17-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox