From mboxrd@z Thu Jan 1 00:00:00 1970 From: presotto@plan9.bell-labs.com Message-Id: <200007311606.MAA20180@cse.psu.edu> Date: Mon, 31 Jul 2000 12:06:28 -0400 To: 9fans@cse.psu.edu Subject: Re: Réf._:_[9fans]_problems MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-zggngobcgwdelhafnyzkfoqzxw" Topicbox-Message-UUID: efca31fc-eac8-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-zggngobcgwdelhafnyzkfoqzxw Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit I dinna understand. Why shouldn't I use SYST? --upas-zggngobcgwdelhafnyzkfoqzxw Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Mon Jul 31 07:01:21 EDT 2000 Received: from cse.psu.edu ([130.203.3.50]) by plan9; Mon Jul 31 07:01:20 EDT 2000 Received: from localhost (majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) with SMTP id GAA12221; Mon, 31 Jul 2000 06:47:28 -0400 (EDT) Received: by claven.cse.psu.edu (bulk_mailer v1.5); Mon, 31 Jul 2000 06:47:18 -0400 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id GAA12185 for 9fans-outgoing; Mon, 31 Jul 2000 06:47:13 -0400 (EDT) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from indosuez.com ([195.115.40.229]) by cse.psu.edu (8.8.8/8.8.8) with ESMTP id GAA12181 for <9fans@cse.psu.edu>; Mon, 31 Jul 2000 06:47:08 -0400 (EDT) From: boyd.roberts@ca-indosuez.com Received: from SNPAR12. (mailer@fw-local [192.168.192.6]) by indosuez.com (8.9.3/8.9.3) with SMTP id MAA20750 for <9fans@cse.psu.edu>; Mon, 31 Jul 2000 12:44:44 +0200 (MET DST) Received: by SNPAR12.(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 4125692D.00412104 ; Mon, 31 Jul 2000 12:51:22 +0100 X-Lotus-FromDomain: BANQUE INDOSUEZ To: 9fans@cse.psu.edu Message-ID: <4125692D.00412021.00@SNPAR12.> Date: Mon, 31 Jul 2000 12:48:12 +0200 Subject: =?iso-8859-1?Q?R=E9f._:_[9fans]_problems?= Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-9fans@cse.psu.edu Reply-To: 9fans@cse.psu.edu Precedence: bulk 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. --upas-zggngobcgwdelhafnyzkfoqzxw--