Skip to content

Extent options for read-only /var handling

Norbert Lange buildroot 1 version Applied

Status from this message: Applied to master, thanks.

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest7 patches 8 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/7system: introduce a choice for /var managementsystem/Config.in+19 -30 replies
2/7system: add overlayfs option for ro /varpackage/skeleton-init-systemd/overlayfs/[email protected] package/skeleton-init-systemd/overlayfs/[email protected] package/skeleton-init-systemd/overlayfs/overlay.mount.in +2 more+98 -02 replies
3/7package/skeleton-init-systemd: force permissions for buildroot runtime dirspackage/skeleton-init-systemd/00-buildroot.conf package/skeleton-init-systemd/skeleton-init-systemd.mk+8 -02 replies
4/7system: add systemd generator for /varpackage/skeleton-init-systemd/generator/br-mount-generator package/skeleton-init-systemd/skeleton-init-systemd.mk system/Config.in+41 -11 reply
5/7package/skeleton-init-systemd: fix var.mount optionspackage/skeleton-init-systemd/var.mount+1 -11 reply
6/7package/systemd: handle creation of /var/log/journalpackage/systemd/systemd.mk+7 -01 reply
7/7package/systemd: create the /boot directorypackage/systemd/systemd.mk+1 -01 reply

Reviews trailers per patch

1 of 7 patches has a Reviewed-by or Acked-by.

PatchNorbert Lange
1/7A-b
2/7
3/7
4/7
5/7
6/7
7/7

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [Buildroot] [PATCH 0/7] Extent options for read-only /var handling

This series is based on the work of Yann to allow variants for handling /var in respect to a read-only rootfs.

It contains a new version to use an overlayfs,
a version using a systemd-generator,
and a few more patches to improve the situation under a read-only root.

Further it tries to establish some buildroot runtime directories, namely /run/.br and /tmp/.br.
The /run/.br should used for any runtime directories/files that are specific tu buildroot. Since /run is expected to only contain a modest amount of content, /tmp/.br is also available for "fatter" stuff.

Those patches are tested to solve the /var issue while behaving nicely within systemd and not requiring special processing or modification of the rootfs.

The patches further allow systemd and its services to boot without errors, even if /var is plainly read-only.

Norbert Lange (6):
system: add overlayfs option for ro /var package/skeleton-init-systemd: force permissions for buildroot runtime
dirs
system: add systemd generator for /var package/skeleton-init-systemd: fix var.mount options package/systemd: handle creation of /var/log/journal package/systemd: create the /boot directory

Yann E. MORIN (1):
system: introduce a choice for /var management

 .../skeleton-init-systemd/00-buildroot.conf   |  7 +++
 .../generator/br-mount-generator              | 19 ++++++++
 .../overlayfs/[email protected]       | 26 ++++++++++
 .../overlayfs/[email protected]     | 26 ++++++++++
 .../overlayfs/overlay.mount.in                | 16 +++++++
 .../skeleton-init-systemd.mk                  | 26 ++++++++++
 package/skeleton-init-systemd/var.mount       |  2 +-
 package/systemd/systemd.mk                    |  8 ++++
 system/Config.in                              | 48 +++++++++++++++++--
 9 files changed, 174 insertions(+), 4 deletions(-)
 create mode 100644 package/skeleton-init-systemd/00-buildroot.conf
 create mode 100755 package/skeleton-init-systemd/generator/br-mount-generator
 create mode 100644 package/skeleton-init-systemd/overlayfs/[email protected]
 create mode 100644 package/skeleton-init-systemd/overlayfs/[email protected]
 create mode 100644 package/skeleton-init-systemd/overlayfs/overlay.mount.in
Signature · 6 lines
2.39.0

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot