🚀 go-pugleaf

Thanks to everyone who corrected my correction about the "rm *"
discussion--- I should have explicitly said that the *C shell* redirects
output first when you type "rm *>o", thus expanding the "*" to include
the new "o" file which is unlinked, too.  Other shells behave
differently, as you all correctly point out.

On that note, a "folklorish" condition exists on the Andrew system
here at CMU: the file system ("afs") remotely stores everyone's files
(there are over 10,000 users right now), and local workstations
retrieve files transparently.  BUT.  The local workstations have local
disks, too, for directories like /tmp, etc., which seem just the same
as the remote directories, but aren't.  So, if you use "mv" to move
a file from /tmp to your home directory (say), and if the file is too
big to fit (did I mention individual user disk quotas?), the "mv"
fails ("afs: failed to store file: over quota.")---and /tmp/bigfile is
now gone, too!  AARRGHHHH!  I lost some data like this once.  Needless
to say, this is only folklore (documentation doesn't mention it, and
the official position is that this is the way things should be).  I
think it's bad design, but then I'm only a luser...

	Sudheer.
-----------------------
...{harvard, uunet}!andrew.cmu.edu!sa1z
sa1z%andrew@CMCCVB.BITNET