Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles; site ea.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!inuxc!pur-ee!uiucdcs!ea!mwm
From: mwm@ea.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Diskless Unix? - (nf)
Message-ID: <13500019@ea.UUCP>
Date: Sun, 8-Jul-84 17:42:00 EDT
Article-I.D.: ea.13500019
Posted: Sun Jul  8 17:42:00 1984
Date-Received: Wed, 11-Jul-84 00:27:33 EDT
References: <162@tellab3.UUCP>
Lines: 24
Nf-ID: #R:tellab3:-16200:ea:13500019:000:968
Nf-From: ea!mwm    Jul  8 16:42:00 1984

#R:tellab3:-16200:ea:13500019:000:968
ea!mwm    Jul  8 16:42:00 1984

/***** ea:net.unix-wizar / utcsstat!advisor /  2:32 pm  Jul  6, 1984 */
Problem is, of course, the inability to address the amount of memory
you would need to hold all of your files. So you can have something
inbetween, like putting /tmp into memory, or some other similar
combo. Any comments?

milan strnad (..utcsstat!advisor)
/* ---------- */

No, the problem isn't the address space, it's the cost of the memory!  Most
people could probably live comfortably with the gigabyte address space on
the VAX, if they could afford that much memory (and expansion cabinets, and
floor space, and air conditioning, etc.). If that's not enough, you can use
a 68012, a 68020, or a 32032 to get more space.

Of course, given that much memory, you may not want a file system, but a
hierarchical name space on your editor buffers. Move all the commands to
swap, and you can get even more space by ripping the file system code out
of the kernel. But is it Unix after that?

	<mike