From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: chroot/aarch64 issues
Date: Tue, 05 Jul 2016 16:44:15 +0200 [thread overview]
Message-ID: <87d1msw3eo.fsf@gnu.org> (raw)
In-Reply-To: <20160705122848.GE6523@debian-netbook> (Efraim Flashner's message of "Tue, 5 Jul 2016 15:28:48 +0300")
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Tue, Jul 05, 2016 at 10:45:51AM +0200, Ludovic Courtès wrote:
>> Efraim Flashner <efraim@flashner.co.il> skribis:
>>
>> > On Mon, Jul 04, 2016 at 03:37:12PM +0200, Ludovic Courtès wrote:
>> >> Hi!
>>
>> If the kernel config corresponds to this kernel, I don’t see which of
>> the other EINVAL reasons given in clone(2) would apply. Does ‘dmesg’
>> show something?
>>
>> Could you maybe try a C program that invokes clone(2) and progressively
>> remove CLONE_ flags until you find the one that’s causing EINVAL?
>>
>> Thanks,
>> Ludo’.
>
> I grabbed the code from man 2 clone and ran that on the odroid, which
> told me "clone: Operation not permitted"
This is expected; quoth clone(2):
--8<---------------cut here---------------start------------->8---
EPERM CLONE_NEWIPC, CLONE_NEWNET, CLONE_NEWNS, CLONE_NEWPID, or CLONE_NEWUTS was specified by an unprivi‐
leged process (process without CAP_SYS_ADMIN).
--8<---------------cut here---------------end--------------->8---
Can you try running it as root?
Ludo’.
next prev parent reply other threads:[~2016-07-05 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 10:42 chroot/aarch64 issues Efraim Flashner
2016-07-04 13:37 ` Ludovic Courtès
2016-07-04 14:15 ` Efraim Flashner
2016-07-05 8:45 ` Ludovic Courtès
2016-07-05 11:45 ` Efraim Flashner
2016-07-05 12:28 ` Efraim Flashner
2016-07-05 14:44 ` Ludovic Courtès [this message]
2016-07-05 17:09 ` Efraim Flashner
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=87d1msw3eo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
/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.