From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Vacfs/9pfuse problems?
Date: Thu, 11 Sep 2008 13:46:04 +0800 [thread overview]
Message-ID: <140e7ec30809102246y5da1fa90wb97eebf62788d417@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a0809100741k4fa77e88o775f9bd7d3c4a1ec@mail.gmail.com>
On Wed, Sep 10, 2008 at 10:41 PM, Russ Cox <rsc@swtch.com> wrote:
> There may be two bugs here. One happens when you start 9pfuse in
> one terminal and then interrupt a program in that same terminal.
This looks fine, I can start 9pfuse and then in the same terminal
ctrl-c to my heart's content without killing 9pfuse.
> The second is what happens when any I/O to the 9pfuse server
> gets interrupted, in any terminal. That one:
>
> I think I fixed this on July 24.
> http://hg.pdos.csail.mit.edu/hg/plan9/rev/18d28bd28f4b
Yep, seems to be fixed after updating to tip. Thanks!
-sqweek
prev parent reply other threads:[~2008-09-11 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 13:49 Venkatesh Srinivas
2008-09-10 4:25 ` sqweek
2008-09-10 14:41 ` Russ Cox
2008-09-11 5:46 ` sqweek [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=140e7ec30809102246y5da1fa90wb97eebf62788d417@mail.gmail.com \
--to=sqweek@gmail.com \
--cc=9fans@9fans.net \
/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).