From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] broken acme
Date: Wed, 19 Feb 2003 09:17:13 -0500 [thread overview]
Message-ID: <7f294f0c9ca83c8bb853d0c6f2e71e57@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0302191556470.26156-100000@diogenis.ceid.upatras.gr>
> acme fails with the bleeding edge CD(downloaded on 14/2/2003)
you did not answer my earlier question.
this problem seems more indicative of
aux/vmwarefs (which provides a /dev/snarf
shared between your plan 9 vm and the host os)
not handling /dev/snarf right.
please try the commands i sent.
russ
next prev parent reply other threads:[~2003-02-19 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 12:27 Anastasopoulos S
2003-02-19 13:49 ` Russ Cox
2003-02-19 14:01 ` Anastasopoulos S
2003-02-19 14:17 ` Russ Cox [this message]
2003-02-19 16:18 ` Jack Johnson
2003-02-19 16:58 ` Russ Cox
2003-02-20 13:19 Anastasopoulos S
2003-02-20 14:44 ` Russ Cox
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=7f294f0c9ca83c8bb853d0c6f2e71e57@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).