From: "andrey mirtchovski" <mirtchovski@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] multiple ethernet cards
Date: Sun, 19 Mar 2006 11:24:28 -0700 [thread overview]
Message-ID: <14ec7b180603191024i2160a50s8ad77023143e1fd@mail.gmail.com> (raw)
In-Reply-To: <14ec7b180603191022k69ec836ci841842928053d0aa@mail.gmail.com>
furthermore, if you want to choose which card appears as #l0 you can
do so by specifying ether0=type in plan9.ini (that's if the two cards
are of different types).
On 3/19/06, andrey mirtchovski <mirtchovski@gmail.com> wrote:
> man ipconfig. there's information there on how to bind a second
> interface. either edit the namespace.local or termrc (cpurc if running
> a cpu server) to bind it and a tcp stack in /net.
>
next prev parent reply other threads:[~2006-03-19 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 18:17 Glenn Holmer
2006-03-19 18:22 ` andrey mirtchovski
2006-03-19 18:24 ` andrey mirtchovski [this message]
2006-03-20 2:47 ` Glenn Holmer
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=14ec7b180603191024i2160a50s8ad77023143e1fd@mail.gmail.com \
--to=mirtchovski@gmail.com \
--cc=9fans@cse.psu.edu \
/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).