From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] magic loopback
Date: Mon, 18 Sep 2006 18:16:21 -0500 [thread overview]
Message-ID: <6c63b7ab45d861910b54390a0dca3147@quanstro.net> (raw)
In-Reply-To: <e75bceb07c08cadfda9a8c6c584d5f43@hamnavoe.com>
i totally missed that one.
this doesn't really seem to be an administration problem too me, though. if fossl+venti on the
same machine is a common setup, shouldn't they should be able to communicate without the
network stack? this would eliminate the need for boot setting up 127.1.
- erik
next prev parent reply other threads:[~2006-09-18 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 20:02 erik quanstrom
2006-09-18 3:18 ` erik quanstrom
2006-09-18 8:56 ` Richard Miller
2006-09-18 23:16 ` erik quanstrom [this message]
2006-09-19 8:04 ` Richard Miller
2006-09-19 23:07 ` erik quanstrom
2006-09-19 23:25 ` Russ Cox
2006-09-19 23:36 ` erik quanstrom
2006-09-20 0:54 ` Russ Cox
2006-09-20 9:48 ` Charles Forsyth
2006-09-20 9:55 Fco. J. Ballesteros
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=6c63b7ab45d861910b54390a0dca3147@quanstro.net \
--to=quanstro@quanstro.net \
--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).