From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] auth server with two NICs
Date: Wed, 21 Jul 2010 08:38:30 -0400 [thread overview]
Message-ID: <203975f49e91f93a5b4df848ead8e5c2@kw.quanstro.net> (raw)
In-Reply-To: <AANLkTimNEg-prinJ0mMTNwQX8tu3AYndLjgGn7hEWfd8@mail.gmail.com>
> now, I have one concern and one problem -
> the concern: only ether0 is bound into /net,
> ether1 doesn't show up in there.
you need to add it to /lib/namespace.$node.
you also need to do the bind by hand in cpurc.
- erik
next prev parent reply other threads:[~2010-07-21 12:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 7:58 Akshat Kumar
2010-07-21 12:38 ` erik quanstrom [this message]
2010-07-21 16:12 ` Akshat Kumar
2010-07-21 16:24 ` Akshat Kumar
2010-07-21 17:31 ` erik quanstrom
2010-07-21 21:50 ` Akshat Kumar
2010-07-21 22:01 ` Akshat Kumar
2010-07-21 23:38 ` Akshat Kumar
2010-07-22 17:25 ` Akshat Kumar
2010-07-22 17:30 ` erik quanstrom
2010-07-22 17:55 ` Akshat Kumar
2010-07-22 20:15 ` Akshat Kumar
2010-07-21 16:03 ` Akshat Kumar
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=203975f49e91f93a5b4df848ead8e5c2@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).