From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fs/skeleton: allow rootfs not to be remounted read-write
Date: Tue, 05 Jul 2011 22:33:17 +0200 [thread overview]
Message-ID: <4E13750D.3080607@lucaceresoli.net> (raw)
In-Reply-To: <CALR4fEKRmHBdjGznPFeS4R2DOkC9DE+X7_rfb6T=Rw4N1=xzzw@mail.gmail.com>
Hi Diego,
Diego Iastrubni wrote:
> On Sun, Jul 3, 2011 at 1:56 PM, Luca Ceresoli <luca@lucaceresoli.net
> <mailto:luca@lucaceresoli.net>> wrote:
> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net
> <mailto:luca@lucaceresoli.net>>
> +config BR2_REMOUNT_ROOTFS_RW
> + bool "remount root filesystem read-write during boot"
> + default y
> + help
> + The root filesystem is typically mounted read-only at boot.
> + By default, buildroot remounts it in read-write mode early
> during the
> + boot process.
> + Say no here if you would rather like your root filesystem to
> remain
> + read-only.
> + If unsure, say Y.
> +
> endif # BR2_ROOTFS_SKELETON_DEFAULT
>
>
> Wait... nothing breaks...? this just works?
It does not break anything.
If the new BR2_REMOUNT_ROOTFS_RW option is left at its default value (y),
then the generated filesystem does the same thing it used to do in the past.
If you disable it, BR will simply comment out the "mount -o remount,rw /"
line in /etc/inittab, thus the rootfs will stay read-only.
It works quite well, unless your apps need to write the rootfs.
I use it since >1 year without problems.
The only issue I notice is that the random seed cannot be saved on shutdown.
But this is a no-issue on those embedded devices that can be shut down only
by removing power: these will never see a clean shutdown.
Luca
next prev parent reply other threads:[~2011-07-05 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 10:56 [Buildroot] [PATCH] fs/skeleton: allow rootfs not to be remounted read-write Luca Ceresoli
2011-07-04 20:25 ` Diego Iastrubni
2011-07-05 20:33 ` Luca Ceresoli [this message]
2011-07-05 20:25 ` Thomas Petazzoni
2011-07-10 20:45 ` Peter Korsgaard
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=4E13750D.3080607@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--cc=buildroot@busybox.net \
/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