Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!ucsd!nosc!marlin!mocko From: mocko@marlin.NOSC.MIL (Gary S. Mocko) Newsgroups: comp.sys.mac.misc Subject: Re: Joining binhexed files? Message-ID: <1386@marlin.NOSC.MIL> Date: 9 May 90 22:12:48 GMT References: <1990May3.134238.20598@usenet.ins.cwru.edu> <3254@umbc3.UMBC.EDU> <1990May8.014517.10451@agate.berkeley.edu> <2818@crystal9.UUCP> <1383@marlin.NOSC.MIL> Reply-To: mocko@marlin.nosc.mil.UUCP (Gary S. Mocko) Organization: Naval Ocean Systems Center, San Diego Lines: 27 In article aland@chaos.cs.brandeis.edu (Alan D Danziger) writes: >In article <1383@marlin.NOSC.MIL> mocko@marlin.NOSC.MIL (Gary S. Mocko) writes: > > doesn't anyone else think the major ftp sites ought to include a few > tutorial paragraphs in a file called something like: > > tutorial.ftp.transfers.[please.read.this.before.you.start.asking.questions. > about.ftp.or.what.to.do.with.these.files.after.you.get.them].txt? > >I seem to remember there being a file README.00 or something similar >on most FTP sites, in at least one directory. And I have a vague >memory of that file being instructions on FTP'ing and using the files. >-- ------------------------------------------ i'll admit i'm a UNIX rookie. i have yet to find an =ftp= command that'll let me read a =README= file. i find it annoying to transfer one of these and then quit to have to read it. the other alternative is to transfer more than one, in which case they either get clobbered or a forget where they came from in the first place. anyone can say =README= ... i just thought a more helpful title could be thought of, [and i know that one i suggested is the other extreme of ridiculous]. ...gary