From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Buttery Pancake <butterypancake@protonmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Guix Paths
Date: Mon, 21 Sep 2020 17:06:07 +0200 [thread overview]
Message-ID: <8e1eb152c1eef8703c628ea5a30bc8b9@tobias.gr> (raw)
In-Reply-To: <iQZg_03HpiMsAH8UY-meBO3TgOMGeeua1rwTMeR6nLJ8_T1P9Ggf_0RIlnU49-oD30vBzQWZje_NZmbO0G-xpHSjVxdXGsbdOdXTNO8Yfoo=@protonmail.com>
Hi!
On 2020-09-21 16:45, Buttery Pancake wrote:
>> which need to be user-writable, whereas the rest of /gnu only need to
>> be
>> writable by the daemon. This means that we end up mounting the same
>> directories more than once with different permissions.
>
> Yes. As default, wouldn't it be better to use `/guix/guix-var-stuff`
> instead of `/var/guix/guix-var-stuff`? Also, bringing
> `/run/guix-other-stuff` under `/guix/guix-other-stuff`.
/run is ephemeral: it is required to be a tmpfs on ‘modern’ system(d)s,
and to be at least emptied at boot on others. Thus nothing in it should
ever be
> backed-up, snap-shot, [or] mounted-separately [more than it already is
> today.]
As for
> won't interfere with other stuffs on file-system (like ever).
I don't think it interferes, does it? How?
I think adding yet another non-standard / subdirectory should be done
only for very good reason. /gnu has it, so would moving to /gnu/db/,
but I don't see a case for the others to be moved.
Kind regards,
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
prev parent reply other threads:[~2020-09-21 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 1:32 Guix Paths Buttery Pancake
2020-09-21 8:33 ` Andreas Enge
2020-09-21 9:06 ` Tobias Geerinckx-Rice
2020-09-21 9:13 ` Ricardo Wurmus
2020-09-21 14:45 ` Buttery Pancake
2020-09-21 15:06 ` Tobias Geerinckx-Rice [this message]
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=8e1eb152c1eef8703c628ea5a30bc8b9@tobias.gr \
--to=me@tobias.gr \
--cc=butterypancake@protonmail.com \
--cc=guix-devel@gnu.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 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.