Subject: [bug#73494] mixup with tmpfs /run patch?

From: Vagrant Cascadian <[email-masked]>
Date: Wed, 05 Mar 2025 00:57:38 -0800

I noticed the commit:

e88018be70ffb8ea35819a4c95d44ec20868ca59
file-systems: %base-file-systems: Add tmpfs /run.

Which was then reverted:

2bb8ecbfbf20efb126670ec92a7cdd88a4805902
Revert "file-systems: %base-file-systems: Add tmpfs /run."

...strangely the patch contained no-suid flags, even though the original
patch submitted intentionally did not have this and was explicitly
mentioned, as it breaks e.g. /run/privleged-programs/bin/sudo ...

+(define %runtime-variable-data
+  (file-system
+    (type "tmpfs")
+    (mount-point "/run")
+    (device "tmpfs")
+    (flags '(no-suid no-dev strict-atime))
              ^^^^^^^

It might be worth re-testing with the no-suid part removed as originally
intended, as it might be breaking other things too... (e.g. if a service
relies on setuid bits or something?)

I looked forward to tmpfs /run that works! :)

live well,
  vagrant