From: Stephen Hemminger <shemminger@vyatta.com>
To: Dan McGee <dan@archlinux.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] iproute2: Auto-detect the presence of setns in libc
Date: Wed, 20 Jul 2011 15:16:51 -0700 [thread overview]
Message-ID: <20110720151651.37895522@nehalam.ftrdhcpuser.net> (raw)
In-Reply-To: <CAEik5nOO9KQoEdvPUGwLBDJqOP9OWgz=G-3KMyvwiu4nwoyb=g@mail.gmail.com>
On Fri, 15 Jul 2011 19:34:04 -0500
Dan McGee <dan@archlinux.org> wrote:
> On Fri, Jul 15, 2011 at 7:26 PM, Eric W. Biederman
> <ebiederm@xmission.com> wrote:
> >
> > If libc has setns present use that version instead of
> > rolling the syscall wrapper by hand.
> >
I am more inclined to get rid of the wrapper completely
and just not put setns support in if libc doesn't support it.
prev parent reply other threads:[~2011-07-20 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 0:26 [PATCH] iproute2: Auto-detect the presence of setns in libc Eric W. Biederman
2011-07-16 0:34 ` Dan McGee
2011-07-20 22:16 ` Stephen Hemminger [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=20110720151651.37895522@nehalam.ftrdhcpuser.net \
--to=shemminger@vyatta.com \
--cc=dan@archlinux.org \
--cc=ebiederm@xmission.com \
--cc=netdev@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