Jeff Maass <firstname.lastname@example.org> wrote:
I want a small (15M) RAMDISK accessable as “/ram” on my
system, and I start devb-ram as follows:
echo “Creating RAMDISK (/ram)…”
devb-ram blk automount=/dev/hd1t77:ram ram capacity=32768 &
After startup, “/dev/hd1t77” exists, and I have a directory “/ram”.
It appears to be intialized.
Do I need to do anything else to prepare “/ram” for use, or
can I immediately copy files into it as if it were just another
directory on my hard drive?
No, nothing else needs to be done (if you don’t specify the “ram nodinit”
option then it will automatically be partitioned and dinit’d as a
fs-qnx4 style filesystem). Later versions (not yet released) of devb-*
will actually support a ramdisk like the old QNX4, so you can combine
having a ramdisk with, say devb-eide, and not need a separate devb-ram
Once created, how can one verify that a RAMDISK is, in fact,
a RAMDISK rather than just another directory on the hard drive?
That’s pretty paranoid of you The devb-ram driver fakes out RAM
to look like a block device, so no-one actually knows the difference
(continuing the not-yet-release-ramdisk saga, this will report as being
type “blk-ram” to “df” and will have a blocksize of 4k). Hmmm … look
through “/proc/mount” for the “ram” entry and verify that the pid (in
the “0,0,0,0,0” stuff) is that of devb-ram and not that of devb-eide … ?