From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: Does OpenRC really need mount-ro
Date: Wed, 17 Feb 2016 09:24:58 +0100 [thread overview]
Message-ID: <f3c23737-b774-c979-fbba-95c509642c9c@gentoo.org> (raw)
In-Reply-To: <20160216180533.GB1450@whubbs1.gaikai.biz>
On 16/02/16 19:05, William Hubbs wrote:
> All,
>
> I have a bug that points out a significant issue with
> /etc/init.d/mount-ro in OpenRC.
>
> Apparently, there are issues that cause it to not work properly for file
> systems which happen to be pre-mounted from an initramfs [1].
Who is using that file system? Ideally if "we" are the last user of the
file system it should be safe to mount ro it as well.
In general this happens when there is a "too smart to fit /" filesystem
in use.
In general that means that the same stuff used in /usr to mount it
should live in the initrd...
In general deprecating split-/usr moves the problem in in supporting fat
initrds to begin with. (I guess needing a boot filesystem that is fuse
based and needs rabbitmq or postgresql might be extra fun btw).
> This service only exists in the Linux world; there is no equivalent in
> OpenRC for any other operating systems we support.
Given it is a safety feature I do not know how the other kernels achieve
the same out of box.
> The reason it exists is very vague to me; I think it has something to do
> with claims of data loss in the past.
I think any fuse-supporting system should have it for more or less
obvious reasons (see the evil example above).
lu
next prev parent reply other threads:[~2016-02-17 8:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 18:05 [gentoo-dev] rfc: Does OpenRC really need mount-ro William Hubbs
2016-02-16 18:22 ` Rich Freeman
2016-02-16 18:41 ` William Hubbs
2016-02-17 2:20 ` [gentoo-dev] " Duncan
2016-02-17 13:46 ` Rich Freeman
2016-02-18 8:57 ` Duncan
2016-02-18 12:22 ` Rich Freeman
2016-02-19 5:07 ` Duncan
2016-02-25 23:46 ` Raymond Jennings
2016-02-17 14:24 ` Richard Yao
2016-02-17 17:19 ` Rich Freeman
2016-02-17 17:30 ` James Le Cuirot
2016-02-17 18:06 ` Ian Stakenvicius
2016-02-17 18:32 ` Rich Freeman
2016-02-18 3:11 ` Richard Yao
2016-02-18 9:02 ` James Le Cuirot
2016-02-18 11:39 ` Rich Freeman
2016-02-17 21:50 ` Daniel Campbell
2016-02-18 3:02 ` Richard Yao
2016-02-18 10:48 ` Rich Freeman
2016-02-17 14:05 ` [gentoo-dev] " Richard Yao
2016-02-16 19:31 ` Patrick Lauer
2016-02-16 20:18 ` Rich Freeman
2016-02-17 14:06 ` Richard Yao
2016-02-17 19:01 ` Andrew Savchenko
2016-02-17 19:26 ` Rich Freeman
2016-02-18 3:26 ` Richard Yao
2016-02-18 7:53 ` Andrew Savchenko
2016-02-16 20:03 ` Daniel Campbell
2016-02-17 8:24 ` Luca Barbato [this message]
2016-02-17 14:00 ` Richard Yao
2016-02-18 7:02 ` Robin H. Johnson
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=f3c23737-b774-c979-fbba-95c509642c9c@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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