Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uunet!mcsun!hp4nl!utrcu1!kortink
From: kortink@utrcu1.UUCP (Kortink John)
Newsgroups: comp.sys.acorn
Subject: Filing system matters
Message-ID: <795@utrcu1.UUCP>
Date: 9 Feb 91 01:01:20 GMT
Reply-To: kortink@utrcu1.UUCP (Kortink John)
Organization: Utwente, Enschede
Lines: 31

dhmyrdal@lise.unit.no (Dag Haakon Myrdal) writes :

> (For those having access to a VAX: yes, this is similar to the way 
> the VAX handles file version-numbers)

Personally, I find VAX's version numbers a pain in the ***.

But unlimited length (well, up to disc space at least :-) filenames a-la
Unix would be great. Also, maybe a filetype could define an implicit
filename extension, like &FFF would make a file 'zap' be a 'zap.txt'.
Unix-like file links would be great too (but I realise this may need
a double-linked directory structure).

While on filing systems : did somebody besides me notice that the RAM
filing system takes *lots* more space when using many directories and
small files than ADFS ? Strange, when they're both filecore-based. (I
know that at least ADFS combines tiny files with directories, but does
this intelligence reside in ADFS or filecore ?).
Any comments (Roger perhaps) ?

John Kortink

-----------------------------------------------------------------------------
Student of Informatics at the University of Twente, The Netherlands
MAIL : kortink@utrcu1.uucp
DISCLAIMER : you know ....             "If language were liquid
                                        it would be rushing in
                                        Instead here we are
    Suzanne Vega (Solitude standing)    in a silence more eloquent
                                        than any word could ever be"
------------------------------------------------------------------------------