From: Kai Krakow <hurikhan77@gmail.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Ideas on unified real-ro mount option across all filesystems
Date: Tue, 22 Dec 2015 02:32:21 +0100 [thread overview]
Message-ID: <20151222023221.56a89345@jupiter.sol.kaishome.de> (raw)
In-Reply-To: 1450404066.6498.70.camel@scientia.net
Am Fri, 18 Dec 2015 03:01:06 +0100
schrieb Christoph Anton Mitterer <calestyo@scientia.net>:
> The manpage says:
> > ro Mount the filesystem read-only.
> > rw Mount the filesystem read-write.
That means: the filesystem... Not the block device...
Sorry, it's kinda nitpicking. But actually, the file system IS
read-only: You cannot modify files from user's view.
What you actually want is not modifying the underlying storage which is
the block device and includes stuff like meta and journal data (which
is only indirectly visible to users at best).
You can argue that man pages are not particularly end-user friendly.
But for an admin this makes sense without being an fs developer.
--
Regards,
Kai
Replies to list-only preferred.
next prev parent reply other threads:[~2015-12-22 3:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 1:41 Ideas on unified real-ro mount option across all filesystems Qu Wenruo
2015-12-17 1:58 ` Qu Wenruo
2015-12-17 3:15 ` Eric Sandeen
2015-12-17 3:26 ` Darrick J. Wong
2015-12-17 14:08 ` Karel Zak
2015-12-18 1:29 ` Qu Wenruo
2015-12-18 2:01 ` Christoph Anton Mitterer
2015-12-18 2:51 ` Eric Sandeen
2015-12-18 4:20 ` Christoph Anton Mitterer
2015-12-22 1:32 ` Kai Krakow [this message]
2015-12-22 12:41 ` Austin S. Hemmelgarn
2015-12-23 23:22 ` Stewart Smith
2015-12-26 22:53 ` Dave Chinner
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=20151222023221.56a89345@jupiter.sol.kaishome.de \
--to=hurikhan77@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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).