From: Padraig Brady <padraig@antefacto.com>
To: Mike Castle <dalgoda@ix.netcom.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ramdisk size clarification
Date: Tue, 18 Dec 2001 12:46:59 +0000 [thread overview]
Message-ID: <3C1F3AC3.7070109@antefacto.com> (raw)
In-Reply-To: <3C1E587C.9060300@antefacto.com> <20011217211429.GA8826@thune.mrc-home.com>
Mike Castle wrote:
> On Mon, Dec 17, 2001 at 08:41:32PM +0000, Padraig Brady wrote:
>
>>and also there is no upper limit on the amount of RAM used,
>>so the following will kill your system (well it did for me):
>>dd if=/dev/zero of=/dev/ram0
>>
>
> Bug in recent 2.4.*. It *should* stop. One line patch has been
> posted to the linux-kernel list a couple of times. Check the archive.
> It's probably in the recent pre-release kernels as well.
>
Great thanks!
http://marc.theaimsgroup.com/?l=linux-kernel&m=100797607432139&w=2
Padraig.
prev parent reply other threads:[~2001-12-18 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 20:41 ramdisk size clarification Padraig Brady
2001-12-17 21:14 ` Mike Castle
2001-12-18 12:46 ` Padraig Brady [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=3C1F3AC3.7070109@antefacto.com \
--to=padraig@antefacto.com \
--cc=dalgoda@ix.netcom.com \
--cc=linux-kernel@vger.kernel.org \
/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