Re: 4.0 userland on 6.1 kernel: sa_register failed

2016-02-03 Thread Stephen Borrill
On Wed, 3 Feb 2016, Edgar Fuss wrote: I tried updating a 4.0.1 machine (amd64) to 6.1 by first updating the kernel and I get a ``libpthread: sa_register failed: Invalid argument'' (when trying to start nslcd). Any hints? Is this down to the kern.no_sa_support sysctl? -- Stephen

4.0 userland on 6.1 kernel: sa_register failed

2016-02-03 Thread Edgar Fuss
I tried updating a 4.0.1 machine (amd64) to 6.1 by first updating the kernel and I get a ``libpthread: sa_register failed: Invalid argument'' (when trying to start nslcd). Any hints?

Re: 4.0 userland on 6.1 kernel: sa_register failed

2016-02-03 Thread Edgar Fuß
> Is this down to the kern.no_sa_support sysctl? Hm, probably yes. What's the point of that variable (I couldn't find anything useful in the archives)? At a first glance, it looks like kern.partly_break_4_compatibility_on_purpose.

Re: 4.0 userland on 6.1 kernel: sa_register failed

2016-02-03 Thread Edgar Fuß
> Scheduler activation has been fully removed. In 6.1? I should be getting ENOSYS, not EINVAL then, no?

Re: 4.0 userland on 6.1 kernel: sa_register failed

2016-02-03 Thread Joerg Sonnenberger
On Wed, Feb 03, 2016 at 04:42:32PM +0100, Edgar Fuss wrote: > I tried updating a 4.0.1 machine (amd64) to 6.1 by first updating the kernel > and I get a ``libpthread: sa_register failed: Invalid argument'' (when trying > to start nslcd). Any hints? Scheduler activation has been fully removed.

Re: 4.0 userland on 6.1 kernel: sa_register failed

2016-02-03 Thread Joerg Sonnenberger
On Wed, Feb 03, 2016 at 06:43:58PM +0100, Edgar Fuß wrote: > > Is this down to the kern.no_sa_support sysctl? > Hm, probably yes. What's the point of that variable (I couldn't find > anything useful in the archives)? At a first glance, it looks like >