From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: nicholas.clark@gmail.com
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH RESEND 2/2] Fuse2fs: add fakeroot option.
Date: Tue, 16 Oct 2018 16:02:23 -0400 [thread overview]
Message-ID: <20181016200223.GH24131@thunk.org> (raw)
In-Reply-To: <20181014150025.6477-3-nicholas.clark@gmail.com>
On Sun, Oct 14, 2018 at 09:00:25AM -0600, nicholas.clark@gmail.com wrote:
> From: Nicholas Clark <nicholas.clark@gmail.com>
>
> Add a new 'fakeroot' option to fuse2fs. When enabled, fuse2fs will
> will pretend to be root when checking file permssions. This allows
> fuse2fs to be used for building/modifying rootfs images as an
> unprivileged user.
>
> As per the maintainer's request, nosuid and nodev are automatically
> enabled when fakeroot is selected (on platforms that support them)
> to help prevent accidental misuse.
>
> Signed-off-by: Nicholas Clark <nicholas.clark@gmail.com>
Applied, thanks!
- Ted
next prev parent reply other threads:[~2018-10-17 3:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-14 15:00 [PATCH RESEND 0/2] e2fsprogs: fuse2fs bugfix and new 'fakeroot' feature nicholas.clark
2018-10-14 15:00 ` [PATCH RESEND 1/2] Fuse2fs: fix 'mount' entry in some cases nicholas.clark
2018-10-16 19:38 ` Theodore Y. Ts'o
2018-10-14 15:00 ` [PATCH RESEND 2/2] Fuse2fs: add fakeroot option nicholas.clark
2018-10-16 20:02 ` Theodore Y. Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-14 14:58 [PATCH RESEND 0/2] e2fsprogs: fuse2fs bugfix and new 'fakeroot' feature nicholas.clark
2018-10-14 14:58 ` [PATCH RESEND 2/2] Fuse2fs: add fakeroot option nicholas.clark
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=20181016200223.GH24131@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=nicholas.clark@gmail.com \
/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.