From: Russ Cox <russcox@gmail.com>
To: Joseph Holsten <pantosys@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] losing files with ftpfs(4)
Date: Tue, 7 Sep 2004 22:32:46 -0400 [thread overview]
Message-ID: <ee9e417a0409071932104bdd44@mail.gmail.com> (raw)
In-Reply-To: <873a03a604090718537c1bdf15@mail.gmail.com>
> Why can't it create an empty file to test write access, and then
> rewrite the file after it receives it?
Ftpfs could employ all sorts of heuristics, but it still
won't get the semantics right 100%. I agree that your
heuristic is probably worth implementing, but there
aren't many people who want to go near that code.
We typically use ftpfs as read-only. For writing, you're
better off with u9fs, perhaps invoked over ssh.
Russ
prev parent reply other threads:[~2004-09-08 2:32 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
2004-09-07 23:09 ` boyd, rounin
2004-09-08 1:53 ` Joseph Holsten
2004-09-08 2:32 ` 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=ee9e417a0409071932104bdd44@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=pantosys@gmail.com \
/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).