From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: ram disk question
Date: Sat, 4 May 2002 09:17:36 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0205040916010.272-100000@igueths> (raw)
In-Reply-To: <20020504170344.A6409@joana.gotss.net>
Hi Raul. This is just a suggestion, but possibly edit the default value in
ramdisk.c
to reflect the amount of ram in the system? Or rebuild your kernel with a
different max_ramdisk_size? This may not even work, just thought I'd put
it out there as a suggestion. On Sat, 4 May 2002, Kerry Hoath wrote:
> Upper limit of a ramdisk is 16 meg I believe,
> you'd have to look in ramdisk.c but i think that is correct.
> On Thu, May 02, 2002 at 04:43:25PM -0500, Raul A. Gallegos wrote:
> > Hi. Question regarding ram disks.
> >
> > I've looked at various howtos but I'm either missing on what I need to
> > read or what I want to do is not possible.
> >
> > I'm wanting to populate around 100 megs of data onto a virtual partition
> > le'ts say made of a ram partition on a machine that all it has is a
> > cdrom and 1 gig of ram. I tried doing:
> >
> > dd if=/dev/zero of=/dev/ram0 count=195555
> >
> > to get a ramdisk around 100 mb in size but I get the error no space left
> > on device.
> >
> > On another machine with a hard drive I can do this if I just create a
> > file /tmp/tmpfs and do the dd command there. I can then mke2fs the file
> > and mount it and have a 100 mb loop block device. So in short, how can
> > I do this but with a ram disk?
> >
> > Thanks.
> > --
> > If you perceive that there are four possible ways in which a procedure can
> > go wrong, and circumvent these, then a fifth way will promptly develop.
> > Raul A. Gallegos - http://www.asmodean.net
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
> --
> Kerry Hoath: kerry@gotss.net kerry@gotss.eu.org or kerry@gotss.spice.net.au
> ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Raul A. Gallegos
` Kerry Hoath
` Brian Borowski
` Igor Gueths [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0205040916010.272-100000@igueths \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).