From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] losing files with ftpfs(4)
Date: Tue, 7 Sep 2004 19:07:39 -0400 [thread overview]
Message-ID: <2eaf9873306a51b68f8a8396a98c8318@plan9.bell-labs.com> (raw)
In-Reply-To: <05e501c49526$93826a30$f5667d50@SOMA>
On Tue Sep 7 18:08:07 EDT 2004, boyd@insultant.net wrote:
> ...
> did this 'disk full' patch get applied?
>
> brahma% diff /n/sources/plan9/sys/src/cmd/ip/ftpfs/proto.c .
> 991,992c991
> < getreply(&ctlin, msg, sizeof(msg), 0);
> < return off;
> ---
> > return getreply(&ctlin, msg, sizeof(msg), 0) == Success ? off : -1;
yes
next prev parent reply other threads:[~2004-09-07 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 21:11 Alberto Cortes
2004-09-07 21:41 ` Russ Cox
2004-09-07 22:03 ` boyd, rounin
2004-09-07 23:07 ` jmk [this message]
2004-09-07 23:09 ` boyd, rounin
2004-09-08 1:53 ` Joseph Holsten
2004-09-08 2:32 ` 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=2eaf9873306a51b68f8a8396a98c8318@plan9.bell-labs.com \
--to=jmk@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).