Path: utzoo!utgpu!watmath!clyde!att!rutgers!mailrus!ames!pasteur!ucbvax!POSTGRES.BERKELEY.EDU!dillon
From: dillon@POSTGRES.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: Dillon's Shell Gripe...is it fixed?
Message-ID: <8901090859.AA22394@postgres.Berkeley.EDU>
Date: 9 Jan 89 08:59:04 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 21


	Yow!  strange.  This is a bug, but not in my shell.  This is a bug
in the filesystem.  Interesting though, when you do it in RAM: the directory
gets blown away but the memory is still allocated.

					-Matt

:Much to my chagrin, I have found a neat little "feature" of Dillon's Shell.
:Admittedly, I'm only using version 2.05 (or something like that), but I think
:this should have been thought of at the first. I had one directory that held
:almost half a year's worth of term papers and stuff on a disk. I was in the
:root directory and I thought I was somewhere in another subdirectory in the
:root. I accidentally typed "mv * df1:docs". As I casually noticed that I was
:in the root directory (aaaahhhhhh!!!!), I immediately hit ^C. Too late.
:The number of blocks used on the disk hadn't changed, but the shell had nicely
:moved the "docs" directory into itself, erasing the directory entry. Now I
:gotta think of a way to rebuild everything. Has this been fixed? Does shell
:check to see if a directory is being moved into itself? I hope so......
:
:Thanx.
:....Bill.