On 12/15/2014 06:27 PM, Lennart Poettering wrote:
On Mon, 15.12.14 08:01, Ken Werner (k...@linux.vnet.ibm.com) wrote:
From: Ken Werner k...@linux.vnet.ibm.com
Since the order of the first and second arguments of the raw clone()
system call is reversed on s390 and cris it needs to be invoked
From: Ken Werner k...@linux.vnet.ibm.com
Since the order of the first and second arguments of the raw clone() system
call is reversed on s390 and cris it needs to be invoked differently.
Signed-off-by: Ken Werner k...@linux.vnet.ibm.com
---
src/nspawn/nspawn.c |6 +++---
src/shared
From: Ken Werner k...@linux.vnet.ibm.com
Since the order of the first and second arguments of the raw clone()
system call is reversed on s390 and cris it needs to be invoked differently.
Signed-off-by: Ken Werner k...@linux.vnet.ibm.com
---
src/nspawn/nspawn.c |8
1 files changed
From: Ken Werner k...@linux.vnet.ibm.com
Hi there,
It appears that systemd-nspawn doesn't work on s390 (and cris probably). The
clone() fails because the signature of the raw system call is slightly
different on these architectures. Since the order of the first and second
arguments
