All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zvi Vered <veredz72@gmail.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] 2022.02.1: read-only file system
Date: Thu, 22 Sep 2022 06:10:16 +0300	[thread overview]
Message-ID: <CABRndgzJO7ct_r4p8MQRA3G7YNzgWaxPPCtR6Sok55kxXpdsJQ@mail.gmail.com> (raw)
In-Reply-To: <5762dfb5-832f-a075-3be9-7d32cb82b661@mind.be>


[-- Attachment #1.1: Type: text/plain, Size: 1556 bytes --]

Hi Arnout,

Thank you very much !

Best regards,
Zvika

On Sat, Sep 17, 2022 at 11:05 PM Arnout Vandecappelle <arnout@mind.be>
wrote:

>
>
> On 11/09/2022 19:58, Zvi Vered wrote:
> > Hello,
> >
> > I'm using buildroot 2022.02.1 under x86 embedded SBC.
> > The root file system is located on the on-board disk.
> > The boot argument contains 'ro' (checked with /proc/cmdline after login)
> but the
> > disk is not read-only.
>
>   There is a buildroot config option BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW
> which
> defaults to enabled. It will remount the rootfs to read-write as part of
> processing /etc/fstab. So you should probably turn that option off. Note
> that if
> you use systemd, you'll need to do a clean rebuild before the option is
> taken
> into account.
>
>
> > When I used the same boot args with busybox, it worked fine.
> > Of course with busybox I had to tailor all other mandatory files and
> directories.
> >
> > I need read-only rootfs to defend this embedded system in case of
> power-down /
> > cold reset.
>
>   Perhaps you're better off then to use an actual readonly filesystem,
> like
> erofs or squashfs? You have to make sure the corresponding kernel options
> are
> enabled, of course.
>
>   Regards,
>   Arnout
>
> >
> > Beyond the default configuration, the rootfs also contains ntp client,
> httpd,
> > pci tools.
> >
> > Thank you,
> > Zvika
> >
> >
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot@buildroot.org
> > https://lists.buildroot.org/mailman/listinfo/buildroot
>

[-- Attachment #1.2: Type: text/html, Size: 2282 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-09-22  3:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11 17:58 [Buildroot] 2022.02.1: read-only file system Zvi Vered
2022-09-17 20:05 ` Arnout Vandecappelle
2022-09-22  3:10   ` Zvi Vered [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=CABRndgzJO7ct_r4p8MQRA3G7YNzgWaxPPCtR6Sok55kxXpdsJQ@mail.gmail.com \
    --to=veredz72@gmail.com \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.