From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] problem with upas/fs and echo open >/mail/fs/ctl
Date: Fri, 20 Jun 2003 20:33:01 -0400 [thread overview]
Message-ID: <9d0b588aed587dcb13741f2925459996@plan9.bell-labs.com> (raw)
In-Reply-To: <%p%Ea.12506$m_2.89463013@news-text.cableinet.net>
> I thought I'd ask here before trawling into code (my first foray),
> whether this was expected behaviour or not? I'll have a dig around the
> sources when I find a bit of spare time.
It's not expected behavior. It is a subtle bug though.
If you're in the mood for a bug hunt, it's a fun one.
It's fixed on sources. A new binary should appear
tonight.
Russ
prev parent reply other threads:[~2003-06-21 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 8:42 Robby
2003-06-21 0:33 ` 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=9d0b588aed587dcb13741f2925459996@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).