From: Vagrant Cascadian <vagrant@debian.org>
To: Hilton Chain <hako@ultrarare.space>, 64775@debbugs.gnu.org
Cc: Saku Laesvuori <saku@laesvuori.fi>, Csepp <raingloom@riseup.net>
Subject: bug#64775: /run should be cleaned on boot
Date: Sun, 06 Aug 2023 13:06:37 -0700 [thread overview]
Message-ID: <878raoylyq.fsf@wireframe> (raw)
In-Reply-To: <87wmy848d0.wl-hako@ultrarare.space>
[-- Attachment #1: Type: text/plain, Size: 2326 bytes --]
On 2023-08-06, Hilton Chain wrote:
> On Sat, 22 Jul 2023 04:24:17 +0800,
> Saku Laesvuori via Bug reports for GNU Guix wrote:
>>
>> [1 <text/plain; us-ascii (quoted-printable)>]
>> > > 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...
>>
>> I'd say it's effectively nothing for almost all devices capable of
>> running Guix. On my laptop the size of /run is 4804 (4.7M). In a quick
>> test one terminal window with only zsh running in it took almost 10
>> times as much ram.
>> [2 signature.asc <application/pgp-signature (7bit)>]
>> No public key for 257D284A2A1D3A32 created at 2023-07-22T04:24:17+0800 using RSA
>
> I'm currently using tmpfs for /tmp, /run and /var/run on my Guix
> Systems.
>
> If you are interested, this is my base file systems:
> --8<---------------cut here---------------start------------->8---
> (cons* (file-system
> (device "none")
> (mount-point "/tmp")
> (type "tmpfs")
> (check? #f))
>
> (file-system
> (device "none")
> (mount-point "/run")
> (type "tmpfs")
> (needed-for-boot? #t)
> (check? #f))
>
> (file-system
> (device "none")
> (mount-point "/var/run")
> (type "tmpfs")
> (needed-for-boot? #t)
> (check? #f))
You probably want to restrict permissions on /run and /var/run, as the
defaults for tmpfs are world-writeable, allowing any user or process to
create files or directories in potentially harmful ways...
For /tmp, these defaults are appropriate, however tricky a
world-writeable directory is...
Although I rarely have enough spare ram on a system to have /tmp be
tmpfs for Guix System because builds happen there by default, and
occasionally I need a lot more space than available ram in some cases.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2023-08-06 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2023-08-07 1:33 ` Hilton Chain via Bug reports for GNU Guix
2023-08-07 14:39 ` Maxim Cournoyer
-- strict thread matches above, loose matches on Subject: below --
2023-02-12 20:37 [bug#61462] Add support for file capabilities(7) Tobias Geerinckx-Rice via Guix-patches via
2023-07-15 23:59 ` [bug#61462] [PATCH v2 01/10] system: Disallow file-like setuid-programs Tobias Geerinckx-Rice via Guix-patches via
2023-07-21 18:53 ` [bug#61462] Add support for file capabilities(7) Vagrant Cascadian
2023-07-21 19:11 ` Vagrant Cascadian
2023-08-08 15:40 ` Ludovic Courtès
2023-08-29 20:29 ` [bug#61462] /run should be cleaned on boot Vagrant Cascadian
2024-09-15 22:29 ` bug#64775: " Ludovic Courtès
[not found] ` <87o7ipvbhh.fsf__48662.4622646318$1693341314$gmane$org@wireframe>
2023-08-29 21:21 ` brian via Bug reports for GNU Guix
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878raoylyq.fsf@wireframe \
--to=vagrant@debian.org \
--cc=64775@debbugs.gnu.org \
--cc=hako@ultrarare.space \
--cc=raingloom@riseup.net \
--cc=saku@laesvuori.fi \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.