From: brian via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
64775@debbugs.gnu.org, 61462@debbugs.gnu.org
Subject: bug#64775: /run should be cleaned on boot
Date: Tue, 29 Aug 2023 17:21:47 -0400 [thread overview]
Message-ID: <87ttshilxw.fsf@spork.org> (raw)
In-Reply-To: <87o7ipvbhh.fsf__48662.4622646318$1693341314$gmane$org@wireframe> (Vagrant Cascadian's message of "Tue, 29 Aug 2023 13:29:14 -0700")
Vagrant Cascadian <vagrant@debian.org> writes:
> On 2023-08-08, Ludovic Courtès wrote:
>> We could try to make that change: /run as tmpfs, or wiped by
>> ‘cleanup-service-type’.
>
> Or both, really!
>
> Filed:
>
> https://issues.guix.gnu.org/64775
I tried this a while ago, and the trivial case of mounting /run as tmpfs
in the operating-system definition causes errors during activation. It
turns out that the /run/current-system symlink is activated before all
non-root mounts, so mounting /run afterwards causes everything to break.
I don't have a solution, and haven't even looked at it past this, but
maybe this report will help.
-bjc
next parent reply other threads:[~2023-08-29 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r0uuehlr.fsf@nckx>
[not found] ` <129e8d298556f6a159fcb704ed3df4bf0709ddd3.1689465600.git.me@tobias.gr>
[not found] ` <87edl1yu2k.fsf@wireframe>
[not found] ` <87bkg5yt91.fsf@wireframe>
[not found] ` <87r0odpmot.fsf_-_@gnu.org>
[not found] ` <87o7ipvbhh.fsf__48662.4622646318$1693341314$gmane$org@wireframe>
2023-08-29 21:21 ` brian via Bug reports for GNU Guix [this message]
2023-07-21 19:23 bug#64775: /run should be cleaned on boot Vagrant Cascadian
2023-07-21 19:36 ` Csepp
2023-07-21 19:57 ` Vagrant Cascadian
2023-07-21 20:24 ` Saku Laesvuori via Bug reports for GNU Guix
2023-08-06 13:18 ` Hilton Chain via Bug reports for GNU Guix
2023-08-06 20:06 ` Vagrant Cascadian
2023-08-07 1:33 ` Hilton Chain via Bug reports for GNU Guix
2023-08-07 14:39 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ttshilxw.fsf@spork.org \
--to=bug-guix@gnu.org \
--cc=61462@debbugs.gnu.org \
--cc=64775@debbugs.gnu.org \
--cc=bjc@spork.org \
--cc=ludo@gnu.org \
--cc=vagrant@debian.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).