[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nix-dev] /dev/shm inconsistency in chroot
From: |
Mark H Weaver |
Subject: |
Re: [Nix-dev] /dev/shm inconsistency in chroot |
Date: |
Fri, 24 Jan 2014 12:13:21 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
Shea Levy <address@hidden> 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.
Mark
- /dev/shm inconsistency in chroot, Sree Harsha Totakura, 2014/01/23
- Re: /dev/shm inconsistency in chroot, Mark H Weaver, 2014/01/23
- Re: /dev/shm inconsistency in chroot, Sree Harsha Totakura, 2014/01/24
- Re: [Nix-dev] /dev/shm inconsistency in chroot, Shea Levy, 2014/01/24
- Re: [Nix-dev] /dev/shm inconsistency in chroot, Ludovic Courtès, 2014/01/24
- Re: [Nix-dev] /dev/shm inconsistency in chroot,
Mark H Weaver <=
- Re: [Nix-dev] /dev/shm inconsistency in chroot, Sree Harsha Totakura, 2014/01/24
- Re: [Nix-dev] /dev/shm inconsistency in chroot, Ludovic Courtès, 2014/01/24
- Re: [Nix-dev] /dev/shm inconsistency in chroot, Shea Levy, 2014/01/24