From: nicholas.clark@gmail.com
To: nicholas.clark@gmail.com, linux-ext4@vger.kernel.org
Subject: [PATCH RESEND 0/2] e2fsprogs: fuse2fs bugfix and new 'fakeroot' feature
Date: Sun, 14 Oct 2018 08:58:35 -0600 [thread overview]
Message-ID: <20181014145837.6344-1-nicholas.clark@gmail.com> (raw)
From: Nick Clark <nicholas.clark@gmail.com>
Hi all,
I wrote a couple of patches for fuse2fs (from the e2fsprogs collection).
One is a minor bugfix to the displayed name in the mount command's output,
and the other is a new 'fakeroot' mount option, as described below.
When building cross-compiled Linux systems (for use on routers, consumer
devices, etc), it's often necessary to build rootfs filesystem images.
This commit adds a new 'fakeroot' mount option that gives a user full
control over the mounted filesystem, within the confines of FUSE.
When used, the new option allows treats allowed users as uid 0 for the
purposes of permission checks (within the mounted filesystem). This
allows the owner of a .img file to mount the file and make whatever
changes they want to any files inside of the image.
If the option is left disabled at mount-time, fuse2fs acts the same as
before - only root can edit "root"-owned files inside of the image. But
when enabled, fuse2fs becomes a powerful tool to build/modify filesystem
images.
What do you all think?
-Nick
Nicholas Clark (2):
Fuse2fs: fix 'mount' entry in some cases.
Fuse2fs: add fakeroot option.
acinclude.m4 | 47 ++++++++++++++++
configure | 134 ++++++++++++++++++++++++++++++++++++++++++++++
configure.ac | 4 ++
lib/config.h.in | 6 +++
misc/fuse2fs.1.in | 3 ++
misc/fuse2fs.c | 31 ++++++++---
6 files changed, 217 insertions(+), 8 deletions(-)
--
2.17.1
next reply other threads:[~2018-10-14 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-14 14:58 nicholas.clark [this message]
2018-10-14 14:58 ` [PATCH RESEND 1/2] Fuse2fs: fix 'mount' entry in some cases nicholas.clark
2018-10-14 14:58 ` [PATCH RESEND 2/2] Fuse2fs: add fakeroot option nicholas.clark
-- strict thread matches above, loose matches on Subject: below --
2018-10-14 15:00 [PATCH RESEND 0/2] e2fsprogs: fuse2fs bugfix and new 'fakeroot' feature 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=20181014145837.6344-1-nicholas.clark@gmail.com \
--to=nicholas.clark@gmail.com \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).