Messages in this thread |  | | Date | Wed, 3 Jul 1996 00:26:08 -0400 | From | "Theodore Y. Ts'o" <> | Subject | Re: PATCH: Ramdisk version 2.0.1 |
| |
From: Albert Cahalan <albert@ccs.neu.edu> Date: Mon, 1 Jul 1996 03:54:51 -0400 (EDT)
Why even accept ramdisk=<size> or limit the size at all? Since the new ramdisk won't waste space unless it is actually used, there is no reason to have the parameter. If the intent is to protect against root doing 'cat /dev/zero >> /dev/ram0', then you won't protect a 4 MB system anyway. With this one, I think root should be allowed to shoot himself in the foot (with water-gun until foot rots off). Real protection would be to limit total ramdisk+mlocked memory to 75%.
The only reason why ramdisk is still supporting a ram disk limit is partiailly to protect sysops from their won stupidity, and so that commands that take a disk size (such as mke2fs /dev/ram) will still work properly.
- Ted
|  |