From: kazumi iwane <kiwane@mx6.ttcn.ne.jp>
To: 9fans@cse.psu.edu
Cc: presotto@plan9.bell-labs.com
Subject: Re: [9fans] ip/rarpd problem
Date: Fri, 6 Sep 2002 07:18:06 +0900 [thread overview]
Message-ID: <20020905221725.LDPF17976.mta5p@isabella> (raw)
In-Reply-To: <d51f156a6b5abab4099b7eac8426549a@plan9.bell-labs.com>
presotto@plan9.bell-labs.com wrote:
> Forsyth is right. Rarpd looks like it was never converted when I
> made all internal addresses V6. There are other changes to bring it back
> to reality also. All the %I's should turn into %V's and there should be
> a fmtinstall for 'V'. I'll stick a new version on sources.
Thank you very very much.
I'd been off the net and I just got the new rarpd from sources
today. I think it's almot ok, but
if(write(edata, buf, 42) != 42)
error("write failed");
gets Etoosmall. write() only writes 40 bytes. I don't have time to
dig into it right now, but I will do so this weekend.
-- kazumi iwane
next prev parent reply other threads:[~2002-09-05 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 12:26 presotto
2002-09-05 22:18 ` kazumi iwane [this message]
2002-09-08 18:31 ` kazumi iwane
-- strict thread matches above, loose matches on Subject: below --
2002-09-08 18:35 presotto
2002-09-04 8:42 Charles Forsyth
2002-09-04 0:35 presotto
2002-09-03 22:10 kazumi iwane
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=20020905221725.LDPF17976.mta5p@isabella \
--to=kiwane@mx6.ttcn.ne.jp \
--cc=9fans@cse.psu.edu \
--cc=presotto@plan9.bell-labs.com \
/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).