From: ebiederm@xmission•com (Eric W. Biederman)
To: David Shwatrz <dshwatrz@gmail•com>
Cc: Renato Westphal <renatowestphal@gmail•com>, netdev@vger•kernel.org
Subject: Re: Move an interface to init_ne
Date: Wed, 28 Nov 2012 10:28:43 -0600 [thread overview]
Message-ID: <87hao9elok.fsf@xmission.com> (raw)
In-Reply-To: <CAJJAcofHM+D8_2u-w5jPJZKfeA0A7QOxX1gxTQ2vOgx-L9aZhQ@mail.gmail.com> (David Shwatrz's message of "Wed, 28 Nov 2012 17:31:15 +0200")
David Shwatrz <dshwatrz@gmail•com> writes:
> But when I run "modprobe 8139too" on namespace1, a device named "eth1"
> is created on the initial network namespace and not on namesapce1.
> I expected that in such a case, a device named "eth0" will be created
> on namespace1, since it was called from namespace1. Or maybe modprobe
> does
> not consider the namespace from which it was called ?
modprobe has no concept of the namespace from which it was called.
Eric
prev parent reply other threads:[~2012-11-28 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 14:39 Move an interface to init_ne David Shwatrz
2012-11-28 15:01 ` Renato Westphal
2012-11-28 15:31 ` David Shwatrz
2012-11-28 16:28 ` Eric W. Biederman [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=87hao9elok.fsf@xmission.com \
--to=ebiederm@xmission$(echo .)com \
--cc=dshwatrz@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=renatowestphal@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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