From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Missing /dev/etherX ?
Date: Sat, 19 Apr 2014 18:21:48 -0400 [thread overview]
Message-ID: <2eae1c26ce6c2c64c6903167e0c9d6dc@brasstown.quanstro.net> (raw)
In-Reply-To: <CAGMcHPoybfxpzuXQwF3A4O3QuFw2=aSzb-Xc_RKFqFvBWv51mw@mail.gmail.com>
> bind -a '#l1' /net
> >
> That has indeed done it, thanks!
>
> Out of curiosity, what is it that is binding the first one automatically
> and not the second?
> It that just the standard behavior, or is it perhaps a script that was
> generated during installation with only one bind entry?
see /lib/namespace. also, remember that the second interface is
very often put in a second ip stack on /net.alt.
- erik
prev parent reply other threads:[~2014-04-19 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 21:56 Riddler
2014-04-19 22:07 ` erik quanstrom
2014-04-19 22:18 ` Riddler
2014-04-19 22:21 ` erik quanstrom [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=2eae1c26ce6c2c64c6903167e0c9d6dc@brasstown.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).