Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!sri-unix!sri-spam!mordor!lll-lcc!well!ewhac
From: ewhac@well.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Some Filesystem Stuff I Cooked Up...
Message-ID: <4049@well.UUCP>
Date: Sun, 27-Sep-87 05:06:37 EDT
Article-I.D.: well.4049
Posted: Sun Sep 27 05:06:37 1987
Date-Received: Sun, 27-Sep-87 22:47:26 EDT
References: <4013@well.UUCP> <820@sugar.UUCP>
Reply-To: ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab)
Organization: Hole Earth 'Lectronic Loss (or words to that effect)
Lines: 33

In article <820@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
>Interesting idea. I like the multiple volumes. I don't like the hash tables.
>I like having directories as files (wonder why)?
>
	As I said in my original posting, I hadn't laid out a formal
directory/file spec.  However, directories under 'LEOS' are indeed files.
The hashtable information is at the beginning of that file.

>As for the naming convention, how about taking a leaf from UNIX' book.
>
>df0a: first volume on the drive...
>df0b: second volume on the drive...
>
	Hmm.  Not bad.

>The semantics of df0: wedge a little. diskcopy wants it to mean the whole
>drive. copy wants it to be the same as df0a:. For that matter what happens
>if you diskcopy df0a: df0b:?

	Grindgrindgrindgrindgrindgrindgrindgrindgrindgrindgrind.....

	Actually, DiskCopy would suddenly have to become more intelligent.
It would have to compare volume sizes (assuming we wanted it to operate on
volumes, not just the raw block device).  If the sizes were different,
DiskCopy would abort.

	Interesting theories, no?

_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Leo L. Schwab -- The Guy in The Cape	ihnp4!ptsfa -\
 \_ -_		Recumbent Bikes:	      dual ---> !{well,unicom}!ewhac
O----^o	      The Only Way To Fly.	      hplabs / (pronounced "AE-wack")
"Work FOR?  I don't work FOR anybody!  I'm just having fun."  -- The Doctor