From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [Nix-dev] /dev/shm inconsistency in chroot
Date: Fri, 21 Mar 2014 10:01:44 +0100 [thread overview]
Message-ID: <8761n89b7r.fsf@gnu.org> (raw)
In-Reply-To: <87sisdi9qm.fsf@netris.org> (Mark H. Weaver's message of "Fri, 24 Jan 2014 12:13:21 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> Shea Levy <shea@shealevy.com> writes:
>
>> On 01/24/2014 05:16 AM, Sree Harsha Totakura wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>>
>>> On 01/23/2014 08:56 PM, Mark H Weaver wrote:
>>>> We should not inherit /dev from the host system at all, but rather
>>>> create it from scratch with just the things we need. IMO, that's
>>>> the only truly proper solution.
>>> We can try creating a fixed set of device nodes, for example:
>>> /dev/null, /dev/random, /dev/urandom, /dev/sda etc. Has anyone tried
>>> this before?
>>
>> Another option is to mount a devtmpfs there, for systems which support it.
>
> The thing is, we don't actually want most of the system's devices to be
> in the build environment, do we? These are all impurities. I don't
> think we want /dev/sda, for example.
For the record, with
<https://github.com/NixOS/nix/commit/3fd01b171a74d28dc8e48b9ee5f2d0e9a3915fb8>,
the daemon creates /dev deterministically. (This change landed in
guix-daemon with the latest ‘nix-upstream’ update.)
Ludo’.
prev parent reply other threads:[~2014-03-21 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 19:21 /dev/shm inconsistency in chroot Sree Harsha Totakura
2014-01-23 19:56 ` Mark H Weaver
2014-01-24 10:16 ` Sree Harsha Totakura
2014-01-24 14:12 ` Shea Levy
2014-01-24 17:08 ` [Nix-dev] " Ludovic Courtès
2014-01-24 17:13 ` Mark H Weaver
2014-01-24 17:44 ` Sree Harsha Totakura
2014-01-24 21:17 ` [Nix-dev] " Ludovic Courtès
2014-01-24 21:45 ` Shea Levy
2014-03-21 9:01 ` Ludovic Courtès [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
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=8761n89b7r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).