From: Enrico Weigelt <lkml@metux.net>
To: Aleksa Sarai <asarai@suse.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux Containers <containers@lists.linux-foundation.org>
Subject: Re: plan9 semantics on Linux - mount namespaces
Date: Wed, 14 Feb 2018 12:27:44 +0100 [thread overview]
Message-ID: <24ddea73-5c84-e098-caae-8a4c14834cbd@metux.net> (raw)
In-Reply-To: <20180214102410.dxgbayb4i76h5exo@gordon>
On 14.02.2018 11:24, Aleksa Sarai wrote:
> What distribution are you using and which release?
On a self-compiled system.
Forgot to enable namespaces in the kernel. Now it seems to work
as root, but not as an unprivileged user:
daemon@alphabox:~ unshare -r -U
unshare: can't open '/proc/self/setgroups': Permission denied
daemon@alphabox:~ unshare -f -r -U
unshare: can't open '/proc/self/setgroups': Permission denied
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2018-02-14 11:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 22:12 Enrico Weigelt
2018-02-13 22:19 ` Enrico Weigelt
2018-02-13 22:27 ` Aleksa Sarai
2018-02-14 0:01 ` Enrico Weigelt
2018-02-14 4:54 ` Aleksa Sarai
2018-02-14 10:18 ` Enrico Weigelt
2018-02-14 10:24 ` Aleksa Sarai
2018-02-14 11:27 ` Enrico Weigelt [this message]
2018-02-14 11:30 ` Richard Weinberger
2018-02-14 12:38 ` Enrico Weigelt
2018-02-14 12:53 ` Richard Weinberger
2018-02-14 14:03 ` Enrico Weigelt
2018-02-14 14:19 ` Richard Weinberger
2018-02-14 15:02 ` Enrico Weigelt
2018-02-14 15:17 ` Richard Weinberger
2018-02-14 17:21 ` Enrico Weigelt
2018-02-14 17:50 ` Richard Weinberger
2018-02-14 18:01 ` Enrico Weigelt
2018-02-14 18:12 ` Richard Weinberger
2018-02-14 18:32 ` Enrico Weigelt
2018-02-14 20:39 ` Aleksa Sarai
2018-02-16 18:26 ` Eric W. Biederman
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=24ddea73-5c84-e098-caae-8a4c14834cbd@metux.net \
--to=lkml@metux.net \
--cc=asarai@suse.de \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome