🚀 go-pugleaf

The ramdisk posting is not a joke. Many people have replied to me
saying that ramdisk is useless, but some people suggested
several uses.
1)Mount a floppy disk image (this is for those without floppy disk
drives)
2)Put cc, ccp and headers and includes and libraries on the ramdisk.
Also all object
files should go to ramdisk when compiled. When developing a program,
even the executables should reside on the ramdisk.
3)Put tex, latex, plain.fmt, latex.fmt, inputs, etc. onto the
ramdisk.
4)mount another ramdisk as /tmp, since a lot of comilation takes
place there. Putting it on the ramdisk is O.K. since /tmp gets erased
at startup anyway.
5)shared files on a NFS file server should be on the ramdisk to
improve the transfer time and decrease cpu load.

I do have a few problems with ramdisk, and that is why I have not
submitted it to nova.cc.purdue.edu yet.


Something is wrong with filesystems. Read and Write routines work
fine.
I cat some text into er (name for the ramdisk driver special block
file,
should really be something like /dev/rramd0a). But when I mkfs
on the ramdisk and mount it and try to look into the mounted dir,
the NeXT panics and reboots. When I take a disk image off the
floppy disk and load it into the ramdisk I also
have problems. I type

cat /dev/rfd0a>er
mount er /RAMDISK
cd /RAMDISK


NeXT does not panic, and I can look at the filesystem,
but things get confused: I can make new files and erase them
prefectly well, but when I try to read files which were on the floppy
disk, I get garbage (usually containing parts of the new files I
made). Looks
like inodes do not point to the right places. Any ideas?
Should I give some more options to mkfs besides the size and the
name?

/etc/mkfs er 2048

??


	Thanks,

		- Dmitri Linde
Please reply to dmitri@StarConn.com