From: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
To: Sargun Dhillon <xbmodder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
lxc-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: Network namespaces tool
Date: Thu, 11 Dec 2008 10:23:28 +0100 [thread overview]
Message-ID: <4940DC10.6020609@free.fr> (raw)
In-Reply-To: <7c9d57ea0812110053o4a2753e0m3937ede52955ce4c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Sargun Dhillon wrote:
> I'm getting an error when I try to compile the netunshare tool.
> Do you have any ideas to the error:
>
> netunshare.c:50: error: conflicting types for 'unshare'
> /usr/include/bits/sched.h:78: error: previous declaration of 'unshare' was here
>
There is the lxc tools at:
http://sourceforge.net/projects/lxc/
In these tools there is the lxc-unshare allowing you to do the same.
lxc-unshare -n /bin/bash
If you find some problems with it, feel free to ask :)
I will release a new lxc-0.5.1, version fixing a few bugs very soon.
> Additionally, are there any plans to merge in sysfs support into the kernel?
>
The sysfs patchset has been rejected and the sysfs itself should be
reworked before submitting the sysfs per namespace. This is a long work,
Eric can probably say more on that.
In the meantime, a patch to make netns and sysfs to co-exist has been
pushed upstream, so we can create a network namespace without sysfs
virtualization. This modification will be available for 2.6.29. Until
this version is released, you can use the netdev development tree
available at:
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git
Thanks.
-- Daniel
prev parent reply other threads:[~2008-12-11 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 8:53 Network namespaces tool Sargun Dhillon
[not found] ` <7c9d57ea0812110053o4a2753e0m3937ede52955ce4c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-12-11 9:17 ` Benjamin Thery
2008-12-11 9:23 ` Daniel Lezcano [this message]
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=4940DC10.6020609@free.fr \
--to=daniel.lezcano-ganu6spqydw@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=lxc-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
--cc=xbmodder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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