unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Walter Franzini <walter.franzini@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: gnu-system-demo feedback
Date: Wed, 16 Oct 2013 15:12:08 +0200	[thread overview]
Message-ID: <87k3hdgy1j.fsf@gnu.org> (raw)
In-Reply-To: <87k3hfipf8.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 14 Oct 2013 22:10:51 +0200")

ludo@gnu.org (Ludovic Courtès) skribis:

> Walter Franzini <walter.franzini@gmail.com> skribis:
>
>> On Mon, Oct 14 2013, Ludovic Courtès wrote:
>>
>> [...]
>>
>>>> 3. running guix gc as root empties /etc (broken symlinks)
>>>> 4. running guix gc as guest (!) empties /etc (broken symlinks)
>>>
>>> A bug: I forgot to register them as GC roots (see gnu/system/vm.scm.)
>>
>> Ok for the bug about GC roots, but I expected a 'guest' not to be able
>> to alter the system state (/etc).
>
> Unprivileged users can access the store via the daemon.  Notably, they
> can run the GC.
>
> The GC only ever deletes files that are no longer referenced.  These
> /etc files were clearly still referenced, but the GC just didn’t know
> about it.

I probably wasn’t clear.  The GC only takes care of files under
/nix/store, and it cannot remove anything outside of that directory.

The files in /etc are symlinks to files under /nix/store, and it’s those
files that were removed.  The symlinks were still there, just dangling.

Ludo’.

  reply	other threads:[~2013-10-16 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-12 21:36 gnu-system-demo feedback Walter Franzini
2013-10-14 12:45 ` Ludovic Courtès
2013-10-14 16:20   ` Walter Franzini
2013-10-14 20:10     ` Ludovic Courtès
2013-10-16 13:12       ` Ludovic Courtès [this message]
2013-10-16 16:12         ` Walter Franzini
2013-10-16 16:57           ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2013-10-13 18:43 Walter Franzini

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=87k3hdgy1j.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=walter.franzini@gmail.com \
    /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).