On Thu, Dec 03, 1998 at 05:34:08PM -0800, Eric House wrote:
> So there's no point in using ramdisks at all for non-boot tasks?
You could use it to build a diskless client, e.g. make an X-terminal out of
an old 486 with enough memory and a decent graphics card.
To use a ramdisk on a running system:
> > How do I use ramdisks once they're created? Just copy my files to the
> > disk and symlink to them from where they're expected to be? What do I
> > do to ensure that the files are written to (real) disk on shutdown or
> > at predefined intervals?
> Just like any other mounted filesystem. The
Eric House wrote:
> The HOWTOs talk about ramdisks as part of the install process, but not
> as something I can use every day. Assuming that I *can* have a ramdisk
> on hamm, how do I set it up?
>
The file /usr/src/linux/Documentation/ramdisk.txt contains all the info you
need. If
you haven't i
Eric House <[EMAIL PROTECTED]> writes:
| The HOWTOs talk about ramdisks as part of the install process, but not
| as something I can use every day. Assuming that I *can* have a ramdisk
| on hamm, how do I set it up?
|
| So far, I've:
| put 'ramdisk=2000' in my /etc/lilo.conf file (and run lilo).
The HOWTOs talk about ramdisks as part of the install process, but not
as something I can use every day. Assuming that I *can* have a ramdisk
on hamm, how do I set it up?
So far, I've:
put 'ramdisk=2000' in my /etc/lilo.conf file (and run lilo). dmesg tells
me that 16 2000K ramdisks were set up,
5 matches
Mail list logo
