A RAMdisk is not a partition of any HDD, therefore write to a RAMdisk
could not 'slip over the line' to another partition.
Partitions are nothing more than electronic "book marks" on the physical
platter of the HDD, for well behaved programs to use in reading/writing
files on/from the HDD. Should a program be badly behaved, it could
ignore those limitations and simply write to the "next available sector"
on the HDD ... regardless of whether or not that particular sector was
within the correct partition. It's like a coloring book, where "well
behaved children" stay "inside the lines."
But the RAMdrive is not a part of the HDD and the only thing which could
be written/miswritten within RAM would be outside the RAMdrive on a
different silicon molecule in RAM only. <G>
Another way to think of it: If you're using an computer drawing program
you can't "color outside the lines" of the physical coloring book on the
table by the computer.
l.d.
====
On Sat, 10 Mar 01 13:47:52, [EMAIL PROTECTED] (Howard Schwartz) wrote:
>> If you ever needed a little push to get you to install Arachne on a ramdisk,
>> here it comes:
> Later you say that putting arachne on a separate partition will not necessarily
> save files on other partitions. Why will a ramdisk be safer? Logically,
> a ramdisk is treated as another partition, i.e., another drive such as
> drive e:. Why would arachne not equally reach across the ramdisk to
> the hard disk partitions and wipe out files?
--
Join B'FOR - B'mothers For Open Records
<A HREF=" http://www.b-for.org "> B'FOR web site</A>
[Associate members of triad also welcome; membership confidential.]
Every member counts! We need numbers to produce valid statistics.
*******
A proud member of
<A HREF=" http://www.phenomenalwomen.com/ "> Phenomenal Women Of The Web</A>
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
