From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 45992@debbugs.gnu.org
Subject: bug#45992: A "live" profile is missing
Date: Sun, 31 Jan 2021 17:40:50 +0100 [thread overview]
Message-ID: <87ft2hm54d.fsf@gnu.org> (raw)
In-Reply-To: <YBSWSMC1t3iWRKrn@jasmine.lan> (Leo Famulari's message of "Fri, 29 Jan 2021 18:12:08 -0500")
Hi Leo,
Leo Famulari <leo@famulari.name> skribis:
> I don't think that this message is really relevant to the bug report. It
> describes some corrupted store items on my computer and might be
> interesting as examples of what goes wrong when /gnu/store is writable.
>
> This is on Debian, where /gnu/store is just a "regular directory",
> without the protection you get on Guix System.
We now provide a ‘gnu-store.mount’ systemd service that makes /gnu/store
read-only, as on Guix System. I suppose it wasn’t enabled on this
machine, right?
[...]
> │ ├── [Dec 31 1969] DejaVuSerif.ttf
> │ └── [Jun 17 2020] .uuid
> └── [Jun 17 2020] .uuid
> ------
>
> What's up with those '.uuid' files?
Not 100% sure, but my theory is that it’s a cache created by Fontconfig
and its friends. That can happen when running a Guix application as
root.
It’s in fact a relatively frequent problem and the reason why Guix and
before that NixOS made the store read-only.
HTH!
Ludo’.
next prev parent reply other threads:[~2021-01-31 16:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 18:56 bug#45992: A "live" profile is missing Leo Famulari
2021-01-20 18:55 ` Leo Famulari
2021-01-21 12:57 ` Ludovic Courtès
2021-01-21 17:36 ` Leo Famulari
2021-01-25 18:11 ` Ludovic Courtès
2021-01-25 19:54 ` Leo Famulari
2021-01-25 20:55 ` Ludovic Courtès
2021-01-25 21:51 ` Leo Famulari
2021-01-29 23:12 ` Leo Famulari
2021-01-31 16:40 ` Ludovic Courtès [this message]
2021-01-31 18:13 ` Leo Famulari
2021-01-25 20:55 ` Ludovic Courtès
2021-01-20 18:59 ` bug#45992: Empty guix Thorsten Wilms
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=87ft2hm54d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=45992@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.