From: Buttery Pancake <butterypancake@protonmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Guix Paths
Date: Mon, 21 Sep 2020 14:45:46 +0000 [thread overview]
Message-ID: <iQZg_03HpiMsAH8UY-meBO3TgOMGeeua1rwTMeR6nLJ8_T1P9Ggf_0RIlnU49-oD30vBzQWZje_NZmbO0G-xpHSjVxdXGsbdOdXTNO8Yfoo=@protonmail.com> (raw)
In-Reply-To: <87wo0nsdae.fsf@elephly.net>
> 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`.
This way, `/gnu` and `/guix` will be unique and be easily tracked, backed-up, snap-shot, mounted-separately or won't interfere with other stuffs on file-system (like ever).
next prev parent reply other threads:[~2020-09-21 14:55 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 [this message]
2020-09-21 15:06 ` Tobias Geerinckx-Rice
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='iQZg_03HpiMsAH8UY-meBO3TgOMGeeua1rwTMeR6nLJ8_T1P9Ggf_0RIlnU49-oD30vBzQWZje_NZmbO0G-xpHSjVxdXGsbdOdXTNO8Yfoo=@protonmail.com' \
--to=butterypancake@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).