On Thu, Apr 03, 2014 at 09:31:11AM +0200, Ludovic Courtès wrote:
> Lluís Batlle i Rossell skribis:
>
> > Usually it's handled with the devpts special mountable device. The
> > "ptmxmode" variable handles that. Don't you want to mount that in the
> &g
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.1
On Mon, Oct 14, 2013 at 09:15:25AM +0200, Ludovic Courtès wrote:
> Andreas Enge skribis:
>
> > commit e78fd4ca636a19bc286747f8d91bda22cd8f08fd
> > Author: Andreas Enge
> > Date: Sun Oct 13 18:02:49 2013 +0200
> >
> > guix: Make cmake build system aware of usual paths.
> >
> > * g
On Tue, Oct 01, 2013 at 02:06:06PM +0400, Nikita Karetnikov wrote:
> > I also seem to recall that gNewSense had only o32 support, years
> > ago. And not any n32/n64. Can it be?
>
> I think this is correct.
>
> > I'd simply try to avoid ext4 or even ext3, without changing the kernel. I
> > don't
On Tue, Oct 01, 2013 at 11:48:48AM +0400, Nikita Karetnikov wrote:
> > Sure the kernel, needs to have n64 support enabled, to run n64 binaries. I
> > imagine it would be detected at ELF header though, and not simply getting
> > failing syscalls.
>
> > I'm sorry, but I don't know what problem is th
On Tue, Oct 01, 2013 at 01:51:28AM +0400, Nikita Karetnikov wrote:
> > Could you try running the statically-linked bash from
> > ‘static-binaries.tar.xz’ and see if the same error occurs? Perhaps
> > strace it so we can see where that error comes from.
>
> I don’t see anything similar.
>
> > Loo
On Tue, Oct 01, 2013 at 01:25:39PM +0200, Ludovic Courtès wrote:
> Lluís Batlle i Rossell skribis:
>
> > On Tue, Oct 01, 2013 at 02:06:06PM +0400, Nikita Karetnikov wrote:
> >> > I also seem to recall that gNewSense had only o32 support, years
> >> >
On Tue, Oct 01, 2013 at 12:55:53PM +0400, Nikita Karetnikov wrote:
> > In fact I was reluctant to raise again the ext4 topic ;) But I think 3.5.3
> > has a
> > broken readdir() syscall in ext4. I think it's not a problem of kernel
> > options
> > active. You simply have to avoid using ext4 (or ev
