Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!agate!agate!adrianho From: adrianho@barkley.berkeley.edu (Adrian J Ho) Newsgroups: comp.music Subject: Re: Access to Canon and Fugue Message-ID: Date: 14 Jun 91 20:49:05 GMT References: <9106112033.AA06604@hplpm.hpl.hp.com> <17050@darkstar.ucsc.edu> <1991Jun14.162855.21572@agate.berkeley.edu> Sender: usenet@agate.berkeley.edu (USENET Administrator) Organization: University of California, Berkeley Lines: 19 In-Reply-To: maverick@mahogany.Berkeley.EDU's message of Fri, 14 Jun 1991 16: 28:55 GMT In article <1991Jun14.162855.21572@agate.berkeley.edu> maverick@mahogany.Berkeley.EDU (Vance Maverick) writes: >Note incorrect assumption that ftp would let me read the current >directory from wherever it logs you in..... Well, the _real_ reason is: ftp> pwd 257 "/tmp" is current directory. is where your ftp session starts. Folks, don't assume that all ftpd's do a chroot(). With regards to AFS (Andrew File System), all such bets are off. Also, don't be fooled by: >230 Filenames can not have '/..' in them Take it literally: You _can_ do a "cd .." -- you just can't cd with a path spec that has the _string_ "/.." in it.