Class F (logs) and Class G (temp/update) reshuffled.
Logs:
- /var/log was already a mount from /storage/.cache/log via
packages/sysutils/busybox/system.d/var-log.mount, so journald already
writes to /var/log/journal in FHS terms. runemu.sh debug log moves
from /storage/.cache/log/runemu-debug.log to /var/log/runemu-debug.log
(same physical bytes, FHS surface).
- createlog (top-level busybox script) packs archive zips into
/var/log/archr/archive instead of /storage/logfiles. ArchR tmpfiles
z_01_archr.conf creates the backing dir under the storage overlay so
the path is writable on first boot.
Update:
- /var/cache/archr/update is a bridge symlink to /storage/.update added
by the archr meta-package. archr-update, automount and the [update]
samba share all flipped to the FHS path.
- factoryreset still preserves /storage/.update by its real name in
the find regex; that path is also what the pre-boot bootloader
scripts read, so the backing path is the canonical one and the
bridge is just the userland surface. Comment added so this is
obvious to future readers.
- busybox/scripts/init keeps UPDATE_ROOT=/storage/.update because it
runs in the initramfs before /var is even available.
Overlayfs workdirs (/storage/.tmp/*-workdir) and /storage/.boot.hint
documented as no-op in fhs-mapping.md: the overlayfs kernel layer
requires upperdir and workdir to share a filesystem, and the boot
hint is part of the U-Boot handshake.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This ensures the /storage filesystem will have the correct options
(block size, inode_ratio etc) for the target partition size.
Signed-off-by: Matthias Reichl <hias@horus.com>
The settings addon no longer creates the trigger file that would activate
these functions. They're not necessary and we instead rely on RPi's
bootloader to do the right thing when presented with flash upgrade files.
Signed-off-by: Ian Leonard <antonlacon@gmail.com>
For the SYSTEM copy to /dev always use /dev/SYSTEM as target name
to not deal with fancy path or filenames.
Thanks HiassofT for clearing it up for me why that is best.
As far as i can tell all the rest of init is fine with BOOT_IMAGE and
SYSTEM_IMAGE having slashes in there.
Just toram was broken.
Only create a logfile for the previous boot if persistent journal
is being used.
Also applies some changes for shellcheck warnings:
`...` to $(...)
Verifying variable is set ${var:?} before rm'ing
Useless use of cat
Command grouping when the commands redirect to the same file
Use of == in [...]
[ test1 -a test2 ] to [ test1 ] && [ test2 ]
Signed-off-by: Ian Leonard <antonlacon@gmail.com>
Douglas Teles
John Williams
Christian Hewitt
Peter
Matthias Reichl
luzpaz
CvH
Ian Leonard
Peter Tuschy
mglae