unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Shea Levy <shea@shealevy.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Mark H Weaver <mhw@netris.org>,
	nix-dev@lists.science.uu.nl
Subject: Re: /dev/shm inconsistency in chroot
Date: Fri, 24 Jan 2014 16:45:31 -0500	[thread overview]
Message-ID: <52E2DEFB.1090709@shealevy.com> (raw)
In-Reply-To: <87wqhpyt9u.fsf@gnu.org>

On 01/24/2014 04:17 PM, Ludovic Courtès wrote:
> Sree Harsha Totakura <sreeharsha@totakura.in> skribis:
>
>> On 01/24/2014 06:13 PM, Mark H Weaver wrote:
>>> Shea Levy <shea@shealevy.com> writes:
>>>>> Another option is to mount  a devtmpfs there, for systems which support it.
>> devtmpfs may give different devices on each machine and they may hinder
>> our build reproducibility.
> OK.
>
>>> 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.
>> Sure, I agree.  I propose we start enumerating commonly needed devices
>> and create them.
> Sounds good.
>
> The major/minor device numbers may not be portable across OSes, which
> may be a problem for Nix, so that code may need to be #ifdef’d.

Generally a good idea, but note that for now chroot is not enabled on 
non-Linux

>> If in future, a package requires access to certain device while
>> building (or during tests) we can include it in our list of created
>> device nodes.
> Yes, but keep in mind that we’re not going to change that often, because
> it’s inconvenient.
>
> Thanks,
> Ludo’.

_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

  reply	other threads:[~2014-01-24 21:45 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 [this message]
2014-03-21  9:01         ` Ludovic Courtès

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=52E2DEFB.1090709@shealevy.com \
    --to=shea@shealevy.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mhw@netris.org \
    --cc=nix-dev@lists.science.uu.nl \
    /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).