From: Steffen Maier <maier-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: David Dillow <dave-i1Mk8JYDVaaSihdK6806/g@public.gmane.org>
Cc: "Min Jun,Xi" <xi.minjun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: Failed to use read-only NFS as the root filesystem
Date: Mon, 05 Jul 2010 11:23:20 +0200 [thread overview]
Message-ID: <4C31A488.2030608@linux.vnet.ibm.com> (raw)
In-Reply-To: <1278263760.4311.59.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
On 07/04/2010 07:16 PM, David Dillow wrote:
> On Mon, 2010-07-05 at 00:48 +0800, Min Jun,Xi wrote:
>> Hi All,
>> there's one problem here.
>> I tried to set one read-only NFS directory as the root filesystem, but
>> there're several problems, and lead to one situation that the root
>> filesystem is remounted using read-write option.
>
>> Is there any option or flag which can be used to disable it? I think
>> the developers from redhat should know about it.
>
> Search /etc/rc.d/rc.sysinit for /etc/sysconfig/readonly-root. I don't
> know if it is well documented or not. You can also use "readonlyroot" on
> the command line I think, but using the file lets you set more options.
> Expect more issues related to this, the last time I looked at it, it
> took some tweaking to make work well.
Even thought it focuses on a specific use case on s390x, the following
document for readonly root-fs on RHEL 5.3 might help you with some more
background information:
http://www.linuxvm.org/Present/misc/ro-root-RH5.pdf
Steffen
Linux on System z Development
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
prev parent reply other threads:[~2010-07-05 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-04 16:48 Failed to use read-only NFS as the root filesystem Min Jun,Xi
[not found] ` <AANLkTimW2-WTf1oqheGOQgfIHcUVpFOEakpnAO8aiQGf-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-04 17:16 ` David Dillow
[not found] ` <1278263760.4311.59.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2010-07-05 9:23 ` Steffen Maier [this message]
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=4C31A488.2030608@linux.vnet.ibm.com \
--to=maier-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=dave-i1Mk8JYDVaaSihdK6806/g@public.gmane.org \
--cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=xi.minjun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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