From: Jonathan Morton <chromi@cyberspace.org>
To: Pavel Machek <pavel@suse.cz>, Alan Olsen <alan@clueserver.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Recommended swap for 2.4.x.
Date: Fri, 2 Feb 2001 20:27:37 +0000 [thread overview]
Message-ID: <l03130312b6a0c807b32f@[192.168.239.105]> (raw)
In-Reply-To: <20010202145149.A129@bug.ucw.cz>
In-Reply-To: <Pine.LNX.4.10.10101291452120.31258-100000@clueserver.org>; from Alan Olsen on Mon, Jan 29, 2001 at 02:57:44PM -0800 <Pine.LNX.4.10.10101291348330.9791-100000@penguin.transmeta.com> <Pine.LNX.4.10.10101291452120.31258-100000@clueserver.org>
At 1:51 pm +0000 2/2/2001, Pavel Machek wrote:
>Hi!
>
>> I am asking because I have just ordered a new drive for my Vaio (8.1 gig
>> in a 8.45mm drive!) and I want to install 2.4.x on it. (I like getting
>
>8.1GB in under centimeter? That's 8.1GB in compactflash slot?
In general, i think the normal reccommendation is to put around double your
physical RAM size as a swapfile. In practice, I use 256Mb swap on most
(almost all) my machines, which have physical RAM from 28Mb up to 320Mb.
Only the 28Mb machine ever makes substantial use of that space.
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: chromi@cyberspace.org (not for attachments)
big-mail: chromatix@penguinpowered.com
uni-mail: j.d.morton@lancaster.ac.uk
The key to knowledge is not to rely on people to teach you it.
Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r- y+
-----END GEEK CODE BLOCK-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-02 20:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 21:51 2.4.0-test12: SiS pirq handling Linus Torvalds
2001-01-29 22:06 ` Sven Koch
2001-01-29 22:57 ` Recommended swap for 2.4.x Alan Olsen
2001-01-29 23:04 ` Linus Torvalds
2001-01-29 23:23 ` alex
2001-01-29 23:45 ` Mike Castle
2001-01-29 23:49 ` William T Wilson
2001-01-30 0:24 ` Kevin Krieser
2001-01-30 5:20 ` Jeff Chua
2001-01-30 19:21 ` James H. Cloos Jr.
2001-01-30 1:20 ` idalton
2001-01-30 11:48 ` Rik van Riel
2001-01-30 18:10 ` alex
2001-01-30 18:22 ` Rik van Riel
2001-01-30 18:40 ` Matthew Kirkwood
2001-01-30 18:43 ` Rik van Riel
2001-01-31 19:59 ` Russell King
2001-01-30 19:13 ` alex
2001-01-30 19:28 ` Rik van Riel
2001-02-02 13:51 ` Pavel Machek
2001-02-02 22:58 ` Alan Olsen
2001-01-29 23:17 ` 2.4.0-test12: SiS pirq handling Aaron Tiensivu
2001-01-29 23:44 ` Linus Torvalds
2001-01-30 0:34 ` Aaron Tiensivu
2001-01-31 10:19 ` Martin Diehl
2001-01-30 1:38 ` Adam Huffman
2001-01-31 10:21 ` [PATCH] minor ne2k-pci irq fix Martin Diehl
2001-01-31 12:11 ` davej
2001-02-01 0:01 ` Martin Diehl
2001-02-01 15:06 ` Jeff Garzik
2001-02-02 16:49 ` Martin Diehl
2001-02-02 17:05 ` Jeff Garzik
2001-02-03 20:20 ` Linus Torvalds
2001-02-02 20:27 ` Jonathan Morton [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='l03130312b6a0c807b32f@[192.168.239.105]' \
--to=chromi@cyberspace.org \
--cc=alan@clueserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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
all inboxes | Powered by JetHome®