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 11:06:21 +0200 [thread overview]
Message-ID: <d2bd93567f9bca7e6351290cbfc671c7@tobias.gr> (raw)
In-Reply-To: <zEzQsaVuLsL3sFv9Qe3zyU_6AJVhOBpxXYmj66jn_ZudGq5BqGuO-nmCkdcCdevp3Jel7r5wHyud3KgtyHfaqLsL_xbvmOCj36hsWJ328kU=@protonmail.com>
Pancake,
On 2020-09-21 3:32, Buttery Pancake wrote:
> I was looking at a NixCon 2019 session called "Guix from the Nix
> Perspective" (https://www.youtube.com/watch?v=bDGzCXr6VYU).
Bookmarked, thanks!
> I am wondering why Guix chose `/var/guix` path instead of
> `/gnu/var/guix` or `/guix/var/guix`, as Nix uses `/nix/var/nix`?
Only Ludo' can answer this, but I think it's an attempt to follow
FHS/GNU directory standards. Similar to how --localstatedir is wrong by
default.
I considered it a bike shed until recently, when I first heard of people
putting /gnu and /var on separate btrfs subvolumes for snapshotting. A
bad idea on most distributions, of course, but Guix's database and store
really are one unit -- like data and metadata. If your database gets
corrupted, lost, or significantly out of sync, Guix will happily delete
store items to match it, up to and including the last glibc. Ask me how
I know.
> I do think that having only one or two directories under root, `/gnu`
> and/or `/guix` is better, instead of having Guix related files under
> multiple directories (/var, /run etc.). It will be neat, clean and
> unique.
Moving the database to /gnu makes sense, but the rest of /var/guix
belongs in /var. Same for /run: it's the right place for what's there.
Don't let's reinvent the FHS poorly under /gnu. It's already pretty
neat, and we're already unique.
Kind regards,
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2020-09-21 9: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 [this message]
2020-09-21 9:13 ` Ricardo Wurmus
2020-09-21 14:45 ` Buttery Pancake
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=d2bd93567f9bca7e6351290cbfc671c7@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 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).