On 2023-07-21, Csepp wrote: > Vagrant Cascadian <vagr...@debian.org> writes: >> While I know that Guix does not really follow the FHS in most respects, >> maybe the intention of /run defined there should still be respected? >> >> https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s15.html >> >> 3.15. /run : Run-time variable data >> 3.15.1. Purpose >> >> This directory contains system information data describing the system >> since it was booted. Files under this directory must be cleared >> (removed or truncated as appropriate) at the beginning of the boot >> process. >> ... >> >> Many distros implement this by having /run on a tmpfs, but making sure >> to clean up /run at boot seems like a reasonable thing to do at the very >> least. >> >> I am not sure if it makes sense to do housecleaning of /run from guix >> system reconfigure ... as there may be legitimate uses for other >> processes to write there. ... > I vote for TMPFS, since that would also reduce flash wear. > Honestly I don't get why it's not already using TMPFS.
One argument could be how much ram it takes: $ du -sc /run/* 12 /run/blkid 0 /run/booted-system 0 /run/current-system 1312 /run/setuid-programs 524 /run/udev 1848 total That is with no explicit setuid programs configured, on a machine with a fairly minimal configuration. Not a *huge* amount of ram, but not nothing, either... live well, vagrant
signature.asc
Description: PGP signature
