Path: utzoo!utgpu!water!watmath!clyde!att!ucbvax!RICHTER.MIT.EDU!krowitz
From: krowitz@RICHTER.MIT.EDU (David Krowitz)
Newsgroups: comp.sys.apollo
Subject: Re:  Domain network questions
Message-ID: <8809141440.AA07220@richter.mit.edu>
Date: 14 Sep 88 14:40:05 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 35

Some points ...

1) The virtual memory space for an Apollo node resides on the disk that
   the node is booted from. If the node is diskless, then the VM comes
   from the disk that its partner is booted from. Your friend's node
   is still being booted from the disk which is physically attached to
   it, so it has no more VM available than it did before. The way to
   solve this is to move his files onto your disk, thereby freeing up
   space on his disk which can be used for virtual memory. As an
   alternative, you can booted his machine as a diskless node off of
   your machine and then use the /com/mtvol command to mount his
   disk (the commmand is issued on his machine). This would allow you
   to delete the operating system from his disk, which would free up
   a lot of disk space.

2) The 155 and 348 MB disk drives on the DN3000/3500/4000/4500 use
   the EDSI controllers, which are faster than the controller used
   for the 72 MB drive. The upgrade price includes the price of the
   new controller. These drives are a lot faster than the smaller
   drive in addition to giving you more disk space. We you consider
   than the operating system takes up some 30 to 40 MB of disk space,
   a formatted 72 MB drive (62 MB) leaves you with only 20 to 35 MB
   of space for virtual memory and files. A formatted 155 MB drive
   (145 MB) leaves you with almost 100 MB of free space. The usuable
   disk space increases much faster than the raw size of the disk
   would indicate.


 -- David Krowitz

krowitz@richter.mit.edu   (18.83.0.109)
krowitz%richter@eddie.mit.edu
krowitz%richter@athena.mit.edu
krowitz%richter.mit.edu@mitvma.bitnet
(in order of decreasing preference)