From: Boyd Roberts <boyd@strakt.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] WebDAV file system
Date: Wed, 30 Oct 2002 12:06:41 +0100 [thread overview]
Message-ID: <3DBFBD41.3040400@strakt.com> (raw)
In-Reply-To: <ccf226e9c208384a410bf7b7edaffce8@plan9.bell-labs.com>
Russ Cox wrote:
>The hard part about ftpfs is parsing the directory listings
>and caching the results so that things like ls work reasonably.
>
Well, yes and no. The RFC says you should not* parse the machine dependent
[LIST] output and you should use the results of NLST. The trouble is
that the
latter doesn't actually tell you very much. Anyway a lot of the detail
is useless,
but knowing the size is useful.
When I did ftpfs with NFS I decided to use NLST, forge the link count
[who cares?],
cd into everything (giving file/directory info), forge the mode and set
the size to 0. As
stuff got read/written, sizes were 'learnt'. Modes were learnt too as a
result of getting
read/write permission errors. If was a fools errand anyway, but it did
demonstrate [again]
that NFS was a lousy protocol.
* It actually says '... may be hard to use automatically in a program'.
I guess I read that as 'I'll be buggered if I'll code up any more system
dependent string smashing in C -- dealing with NFS and XDR has
been bad enough'.
next prev parent reply other threads:[~2002-10-30 11:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 6:29 Russ Cox
2002-10-30 11:06 ` Boyd Roberts [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-04 18:49 Charles Forsyth
2002-11-04 15:15 Skip Tavakkolian
2002-10-31 14:38 Skip Tavakkolian
2002-11-04 18:38 ` Peter Downs
2002-11-05 18:47 ` Dan Cross
2002-10-31 5:26 okamoto
2002-10-31 5:15 okamoto
2002-10-31 6:35 ` Jim Choate
2002-10-31 4:17 Skip Tavakkolian
2002-10-31 13:58 ` Jim Choate
2002-10-31 18:21 ` Dan Cross
2002-11-01 11:26 ` Boyd Roberts
2002-11-01 20:50 ` Dan Cross
2002-11-01 23:30 ` Roman V. Shaposhnick
2002-10-31 2:59 okamoto
2002-10-31 5:18 ` Jim Choate
2002-10-30 18:21 rob pike, esq.
2002-10-30 22:00 ` Jim Choate
2002-10-30 17:21 Russ Cox
2002-10-30 21:55 ` Jim Choate
2002-10-30 15:42 Skip Tavakkolian
2002-10-30 10:45 Geoff Collyer
2002-10-30 13:17 ` rob pike
2002-10-30 13:27 ` Lucio De Re
2002-10-30 18:11 ` Jim Choate
2002-10-30 14:40 ` Ronald G Minnich
2002-10-30 19:13 ` John E. Barham
2002-10-30 20:34 ` Dan Cross
2002-10-30 9:37 C H Forsyth
2002-10-30 8:55 okamoto
2002-10-30 8:31 Charles Forsyth
2002-10-30 13:14 ` rob pike
2002-10-30 14:16 ` Jim Choate
2002-10-30 4:10 Skip Tavakkolian
2002-10-30 3:12 John E. Barham
2002-10-30 5:53 ` Jim Choate
2002-10-30 6:14 ` John E. Barham
2002-10-30 14:13 ` Jim Choate
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=3DBFBD41.3040400@strakt.com \
--to=boyd@strakt.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).