All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Limited RAM - how to save it?
Date: Mon, 05 Nov 2001 14:15:19 -0800	[thread overview]
Message-ID: <3BE70F77.7030002@zytor.com> (raw)
In-Reply-To: <E160s6q-0006o6-00@the-village.bc.nu>

Alan Cox wrote:

>>4 MB was the practical minimum for even the very early versions of
>>Linux.  I would probably suggest backrevving to 2.0 (which is still
>>maintained) or even 1.2 (which isn't) for a start...
>>
> There is no 1.2 kernel tree that is secure from remote attack
> 

Doesn't matter much if your system is a standalone embedded system, does
it?  (Not that I know if the original poster's system was such, but such
systems definitely exist in plenty.)

	-hpa


  reply	other threads:[~2001-11-05 22:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05 11:52 Limited RAM - how to save it? Jan-Benedict Glaw
2001-11-05 13:02 ` Matt Bernstein
2001-11-06 10:58   ` szonyi calin
2001-11-06 11:23     ` Matt Bernstein
2001-11-05 20:21 ` H. Peter Anvin
2001-11-05 22:20   ` Alan Cox
2001-11-05 22:15     ` H. Peter Anvin [this message]
2001-11-06  6:58 ` Lars Brinkhoff

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=3BE70F77.7030002@zytor.com \
    --to=hpa@zytor.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.