Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!sdcsvax!darrell From: darrell@sdcsvax.UUCP Newsgroups: mod.os Subject: Who needs files? Message-ID: <2850@sdcsvax.UCSD.EDU> Date: Tue, 10-Mar-87 10:58:25 EST Article-I.D.: sdcsvax.2850 Posted: Tue Mar 10 10:58:25 1987 Date-Received: Fri, 13-Mar-87 00:48:25 EST Sender: darrell@sdcsvax.UCSD.EDU Organization: DEC SWS, Landover, MD Lines: 15 Approved: mod-os@sdcsvax.uucp Some people call RAM "fast memory" and disk "slow memory" (and tape "very slow memory"). With large address spaces and virtual memory, who needs files? Why not define all storage as extended memory structures that may be loaded as needed. I realize that this is the de facto effect of paging systems, disk-caching, sparse addressing, runtime-loadable modules and workspace-oriented environments...why not make it de jure? This model would be inappropriate for some environments, but many small systems (32 bits && < 4Gbytes storage) would fit just fine. Non-inflammatory comments please.... -- ------------------------------------------------------------------------------- Bob Bagwill Are we not men? UUCP: {decvax,seismo,cbosgd}!decuac!bagwill INET: bagwill@decuac.DEC.COM