From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: Réf._:_[9fans]_problems
Date: Mon, 31 Jul 2000 12:06:28 -0400 [thread overview]
Message-ID: <200007311606.MAA20180@cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 48 bytes --]
I dinna understand. Why shouldn't I use SYST?
[-- Attachment #2: Type: message/rfc822, Size: 2009 bytes --]
From: boyd.roberts@ca-indosuez.com
To: 9fans@cse.psu.edu
Subject: Réf. : [9fans] problems
Date: Mon, 31 Jul 2000 12:48:12 +0200
Message-ID: <4125692D.00412021.00@SNPAR12.>
3. 'ftpfs' doesn't completely cope with MacOS! What about the rest
of us? ;) I can work around it for now by moving whatever I want to
get with 'ftpfs' to the 'McIntoshHD'.
if i remember corectly, ftpfs uses SYST, when it really shouldn't.
yep it does:
http://offworld.fac.cs.cmu.edu/plan9/source/src/cmd/ftpfs/proto.c#L177
yer a boofhead, dave :-)
anyway i wouldn't call MacOS an OS. consider the 'brilliant' memory
management in the first macs -- ugh.
reply other threads:[~2000-07-31 16:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200007311606.MAA20180@cse.psu.edu \
--to=presotto@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).