public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nick Cunningham <nick@monkeydust.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Tips/Tricks for Gentoo on low-spec computer?
Date: Tue, 20 Jan 2009 17:22:34 +0000	[thread overview]
Message-ID: <e99b2eae0901200922s2e498a0bm1777dbd1797a3052@mail.gmail.com> (raw)
In-Reply-To: <60a795cd0901200915g59b5436cvf1a837cc74dd176c@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]

2009/1/20 Alejandro <elcorreodeale@gmail.com>

>
>
> 2009/1/20 Volker Armin Hemmann <volkerarmin@googlemail.com>
>
>> On Dienstag 20 Januar 2009, Grant Edwards wrote:
>> > I'm in the process of installing Gentoo on a rather old
>> > machine. It's an old HP Pavilion with a 450MHz Celeron
>> > Mendocino and 256MB of PC133 SDRAM.  I'm using an nVidia PCI
>> > FX6200 video board instead of the i810 on-board chip, and it's
>> > got a decent hard drive (160GB).
>> >
>> > I was wondering if there were any particular tips/tricks for
>> > getting the best performance out of such a machine.  It's to be
>> > used for basic word processing and a few games.  Hopefully the
>> > nVidia 6200 will allow OpenGL to run fast enough for something
>> > like TuxRacer.
>> >
>> > I chose XFCE for the desktop along with both Abiword and
>> > OpenOffice. I probably should have installed OOo from a binary
>> > package, but I decided to build it just to see how long it
>> > would take (so far it's at about 26 hours and counting).
>>
>> if you don't need any special features, kde+koffice needs less ram than
>> xfce+openoffice.
>>
>> And installing ooo from source is unsupport. The build breaks all the time
>> and
>> you don't get anything from it. All it does is starting a second faster.
>> It
>> does not need less ram nor does it run faster.
>>
>>
>>
> "installing ooo from source is unsupport" How is this? Maybe you
> missundertand i think he run emerge openoffice and not openoffice-bin
>

I believe he means that generally speaking, trying to build OO from source
on a low-end (and especially low RAM) machine is ill-advised and can often
be the cause of build failures as OO is well known to require a lot of RAM
and hdd space while it compiles.

- Nick

[-- Attachment #2: Type: text/html, Size: 2492 bytes --]

  reply	other threads:[~2009-01-20 17:26 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 17:05 [gentoo-user] Tips/Tricks for Gentoo on low-spec computer? Volker Armin Hemmann
2009-01-20 17:14 ` Paul Hartman
2009-01-20 17:15 ` Alejandro
2009-01-20 17:22   ` Nick Cunningham [this message]
2009-01-20 17:32     ` Paul Hartman
2009-01-20 18:42       ` Neil Bothwick
2009-01-20 18:53         ` Dirk Heinrichs
2009-01-20 19:37         ` [gentoo-user] " Grant Edwards
2009-01-21 19:01           ` Daniel Troeder
2009-01-20 19:20       ` Grant Edwards
2009-01-21 15:57         ` Grant Edwards
2009-01-24 14:43     ` [gentoo-user] " Steven Lembark
2009-01-20 17:27   ` Volker Armin Hemmann
2009-01-20 17:37     ` Paul Hartman
2009-01-20 17:56       ` Volker Armin Hemmann
2009-01-20 18:00         ` s3b4sm4gr1
2009-01-20 19:23           ` [gentoo-user] " Grant Edwards
2009-01-21  1:00           ` [gentoo-user] " Dale
2009-01-24 14:53             ` Steven Lembark
2009-01-24 15:47               ` [gentoo-user] " Grant Edwards
2009-01-24 15:55               ` [gentoo-user] " Dale
2009-01-20 17:37   ` [gentoo-user] " Grant Edwards
2009-01-21  0:54 ` [gentoo-user] " Dale
2009-01-21  2:18   ` [gentoo-user] " Grant Edwards
2009-01-21  3:28     ` Paul Hartman
2009-01-21  3:49       ` Grant Edwards
2009-01-21  4:02         ` Paul Hartman
2009-01-21  3:39     ` Shawn Haggett
  -- strict thread matches above, loose matches on Subject: below --
2009-01-20 16:46 [gentoo-user] " Grant Edwards
2009-01-20 17:05 ` Paul Hartman
2009-01-20 17:11   ` Nick Cunningham
2009-01-20 17:38 ` Mark Knecht
2009-01-20 18:01 ` Dirk Heinrichs
2009-01-20 18:09 ` kashani
2009-01-21  0:50 ` Dale
2009-01-24 14:40 ` Steven Lembark

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=e99b2eae0901200922s2e498a0bm1777dbd1797a3052@mail.gmail.com \
    --to=nick@monkeydust.net \
    --cc=gentoo-user@lists.gentoo.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