| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20151222023221.56a89345@jupiter.sol.kaishome.de> Date: Tue, 22 Dec 2015 02:32:21 +0100 From: Kai Krakow <hurikhan77@...il.com> To: linux-ext4@...r.kernel.org Cc: linux-btrfs@...r.kernel.org, linux-ext4@...r.kernel.org Subject: Re: Ideas on unified real-ro mount option across all filesystems Am Fri, 18 Dec 2015 03:01:06 +0100 schrieb Christoph Anton Mitterer <calestyo@...entia.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. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists