Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site watdcsu.UUCP
Path: utzoo!watmath!watnot!watdcsu!haapanen
From: haapanen@watdcsu.UUCP (Tom Haapanen [DCS])
Newsgroups: net.os
Subject: Allocating filespace
Message-ID: <1941@watdcsu.UUCP>
Date: Tue, 3-Dec-85 21:04:16 EST
Article-I.D.: watdcsu.1941
Posted: Tue Dec  3 21:04:16 1985
Date-Received: Thu, 5-Dec-85 05:03:46 EST
Reply-To: haapanen@watdcsu.UUCP (Tom Haapanen)
Organization: U of Waterloo, Ontario
Lines: 24
Keywords: inodes, fat

So, we finally have net.os.  Three cheers to Andy Beals!

To get the ball rolling, I will pose the following question to the
readers of this newsgroup (I did not think this appropriate for
net.arch or other newsgroups in the pre-net.os days...):

I am familiar with the directory and inode structure on UNIX (4.2 BSD)
and with the directories and file allocation table on PC-DOS/MS-DOS,
so I have an idea of how a file is allocated disk space (and placed in
the right directory) on those systems.  

However, I am not familiar with VMS, TOPS-10, OS-9 or the UNIClones.
How do they go about it?  They all have hierarchical (sp?) file systems,
so there should be some similarities between some of them.  Right?

What are the tradeoffs between the different ways of doing this?  Can
someone enlighten me?

				   \tom haapanen
				   watmath!watdcsu!haapanen
I'm all lost in the Supermarket
I can no longer shop happily
I came in here for that special offer
Guaranteed personality				 (c) The Clash, 1979