From: ludo@gnu.org (Ludovic Courtès)
To: "Lluís Batlle i Rossell" <viric@viric.name>
Cc: guix-devel@gnu.org, nix-dev@cs.uu.nl
Subject: Re: [PATCH] Make sure /dev/pts/ptmx is world-writable
Date: Thu, 03 Apr 2014 09:28:07 +0200 [thread overview]
Message-ID: <87ob0ivpmg.fsf@gnu.org> (raw)
In-Reply-To: <20140403065303.GA8658@cubata.homelinux.net> ("Lluís Batlle i Rossell"'s message of "Thu, 3 Apr 2014 08:53:03 +0200")
Hello!
Lluís Batlle i Rossell <viric@viric.name> skribis:
> On Wed, Apr 02, 2014 at 11:41:11PM +0200, Ludovic Courtès wrote:
>> Hello,
>>
>> While running Python 3’s test suite, we noticed that on some systems
>> /dev/pts/ptmx is created with permissions 0 (that’s the case with my
>> Nixpkgs-originating 3.0.43 kernel, but someone with a Debian-originating
>> 3.10-3 reported not having this problem.)
Actually the doc confirms that:
https://www.kernel.org/doc/Documentation/filesystems/devpts.txt
>> There’s still the problem that people without
>> CONFIG_DEVPTS_MULTIPLE_INSTANCES=y are screwed (as noted in build.cc),
>> but I don’t see how we could work around it.
>>
>> Thoughts?
>>
>> Ludo’.
>
> Usually it's handled with the devpts special mountable device. The
> "ptmxmode" variable handles that. Don't you want to mount that in the
> chroot?
We do want to mount /dev/pts, yes. What’s the ‘ptmxmode variable’?
Ludo’.
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
next prev parent reply other threads:[~2014-04-03 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 21:41 [PATCH] Make sure /dev/pts/ptmx is world-writable Ludovic Courtès
2014-04-03 6:53 ` Lluís Batlle i Rossell
2014-04-03 7:28 ` Ludovic Courtès [this message]
2014-04-03 7:31 ` Ludovic Courtès
2014-04-03 10:38 ` Lluís Batlle i Rossell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ob0ivpmg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=nix-dev@cs.uu.nl \
--cc=viric@viric.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.