[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nix-dev] /dev/shm inconsistency in chroot
From: |
Ludovic Courtès |
Subject: |
Re: [Nix-dev] /dev/shm inconsistency in chroot |
Date: |
Fri, 24 Jan 2014 18:08:57 +0100 |
User-agent: |
Gnus/5.130007 (Ma Gnus v0.7) Emacs/24.3 (gnu/linux) |
Shea Levy <address@hidden> skribis:
> 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.
Both options look good to me. Using devtmpfs would be easier, but I
don’t see any documentation for it. Are its contents really
deterministic?
Thanks,
Ludo’.
- /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 <=
- Re: [Nix-dev] /dev/shm inconsistency in chroot, Mark H Weaver, 2014/01/24
- 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