From: ludo@gnu.org (Ludovic Courtès)
To: Paul Boddie <paul@boddie.org.uk>
Cc: help-guix@gnu.org
Subject: Re: Bootstrapping on a new platform
Date: Tue, 12 Dec 2017 17:10:59 +0100 [thread overview]
Message-ID: <87indcorjg.fsf@gnu.org> (raw)
In-Reply-To: <201712111736.12484.paul@boddie.org.uk> (Paul Boddie's message of "Mon, 11 Dec 2017 17:36:09 +0100")
Paul Boddie <paul@boddie.org.uk> skribis:
> On Monday 11. December 2017 12.03.56 Ludovic Courtès wrote:
>>
>> Paul Boddie <paul@boddie.org.uk> skribis:
>> > This resembling what I showed before. Meanwhile in the child process log
>> > (/tmp/guix.797) the clone call with EINVAL is this one:
>> >
>> > clone(child_stack=0xbffedfa4,
>> > flags=CLONE_NEWNS|CLONE_NEWUTS|CLONE_NEWIPC|
>> > CLONE_NEWPID|CLONE_NEWNET|SIGCHLD) = -1 EINVAL (Invalid argument)
>> >
>> > Again, this is using the 4.9.67 kernel.
>>
>> This suggests that namespaces are not fully supported with this kernel.
>> The clone(2) page has this:
>>
>> EINVAL CLONE_NEWIPC was specified in flags, but the kernel was not
>> configured with the CONFIG_SYSVIPC and CONFIG_IPC_NS options.
>>
>> EINVAL CLONE_NEWNET was specified in flags, but the kernel was not
>> configured with the CONFIG_NET_NS option.
>>
>> EINVAL CLONE_NEWPID was specified in flags, but the kernel was not
>> configured with the CONFIG_PID_NS option.
>>
>> EINVAL CLONE_NEWUTS was specified in flags, but the kernel was not
>> configured with the CONFIG_UTS option.
>>
>> Could it be one of these?
>
> I ran "make menuconfig ARCH=um" and saw that "User namespace" and "PID
> Namespaces" were not enabled. So I enabled them, rebuilt the kernel, and then
> ran the User Mode Linux instance again.
>
> This time, it would appear that running the daemon and then running a build
> command gets the daemon to do some work. There have been some problems with
> hashes, as reported before, but the problem with clone seems to have been
> solved.
>
> Sorry for the noise, but I guess this is what happens when someone tries to do
> things the hard way. Thanks for identifying the cause of the problem!
Great that you found out!
Ludo’.
next prev parent reply other threads:[~2017-12-12 16:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 23:17 Bootstrapping on a new platform Paul Boddie
2017-12-03 6:46 ` Manolis Ragkousis
2017-12-03 9:54 ` Efraim Flashner
2017-12-04 18:24 ` Paul Boddie
2017-12-08 10:28 ` Ludovic Courtès
2017-12-08 13:40 ` Paul Boddie
2017-12-08 16:19 ` Paul Boddie
2017-12-11 11:03 ` Ludovic Courtès
2017-12-11 16:36 ` Paul Boddie
2017-12-12 16:10 ` Ludovic Courtès [this message]
2017-12-12 16:29 ` Paul Boddie
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87indcorjg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=paul@boddie.org.uk \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).