Linux Newbie help
 help / color / mirror / Atom feed
From: Chuck Gelm <nc8q@gelm.net>
To: linux-newbie@vger.kernel.org
Subject: Re: RAM and swap partition
Date: Fri, 13 Dec 2002 17:31:06 -0500	[thread overview]
Message-ID: <3DFA5FAA.56E26548@gelm.net> (raw)
In-Reply-To: 200212130451.gBD4pNUg019999@pegasus.wanadoo.be

Dear Heimo:

 If you will tell the list:
EXACTLY which distribution and version of linux and
EXACTLY which kernel and
EXACTLY which applications you will be using concurrently and
EXACTLY what your system's bogo MIPS is and
EXACTLY how fast your hard drive is and
EXACTLY how much RAM you have and
EXACTLY how much data your applications will be processing,
 it may be suggested EXACTLY how much swap space you will need.

 Until then, IMHO, the answer to this topic is,

 it depends.

 Tell us what you have and what you want to do with it,
and probably several fellows will suggest how much.
;-)

HTH, Chuck

Heimo Claasen wrote:
> 
> It's still not really clear for my when and if, how much swap space is
> needed.
> 
> There had been two opinions in this thread which clearly pointed to
> none at all - surely qualified, one from own experience re
> "workstations", the other (and that was the first time I heard about
> this at all) that swap is (only?) needed when compiling and in order
> to save a crash log.
> 
> The definition of "total (virtual) memory needed" for a/one programm
> appears logical (and "natural"); but then, there should be some means
> of measurement of precisely this, in order to do some reasonable -
> and economic - decision on that workspace indeed needed.
> 
> Furthermore, it seems rational to approach this in function of the
> actual use of (or installed) applications - i.e., to define, or even
> to resize if necessary (when a memory hog is added), the swap partition
> _after_ the otherwise complete installation of the "system".
> 
> // Heimo Claasen // <hammer at revobild dot net> // Brussels 2002-12-12
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2002-12-13 22:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13  0:00 RAM and swap partition Heimo Claasen
2002-12-13 22:31 ` Chuck Gelm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-16  0:00 Heimo Claasen
2002-12-16 21:33 ` Chuck Gelm
2002-12-15  0:00 Heimo Claasen
2002-12-15  4:07 ` Chuck Gelm
2002-12-09 18:22 james miller
2002-12-09 18:47 ` Ray Olszewski
2002-12-10  8:39   ` ichi
2002-12-09 20:59 ` Chuck Gelm
2002-12-09 20:59 ` Chuck Gelm
2002-12-10  8:15 ` ichi
2002-12-07  0:00 Heimo Claasen
2002-12-08  2:28 ` whitnl73
2002-12-07  0:00 Heimo Claasen
2002-12-08  0:24 ` james niland
2002-12-08 13:15   ` Rolf Edlund
2002-12-08 15:58     ` Ray Olszewski
2002-12-08 21:43       ` Chuck Gelm
2002-12-11 18:32         ` Rolf Edlund
2002-12-09  7:13       ` ichi
2002-12-08 21:39         ` whitnl73
2002-12-11 18:03       ` Rolf Edlund
2002-12-08  0:35 ` dashielljt

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=3DFA5FAA.56E26548@gelm.net \
    --to=nc8q@gelm.net \
    --cc=linux-newbie@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