From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] vmware & replica
Date: Thu, 20 Feb 2003 16:56:14 -0500 [thread overview]
Message-ID: <891a0cb45fec0f01785428ab6335d7e0@plan9.bell-labs.com> (raw)
In-Reply-To: <20030220143328.24351.qmail@mail.prosyst.com>
I put out new kernels that fix this and a bunch
of other weird bugs you might have observed over
the last couple days. The new ipoput "no route" code
signaled the lack of route by erroring but some
callers weren't expecting an error. Dave changed
it to be a return value, and now things seem better.
In particular it should fix the DHCP problem.
Russ
prev parent reply other threads:[~2003-02-20 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 14:33 Nikolay Paskov
2003-02-20 21:56 ` Russ Cox [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=891a0cb45fec0f01785428ab6335d7e0@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).