From: "Andrey Vul" <andrey.vul@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Reopen: OpenOffice dies on startup
Date: Thu, 9 Oct 2008 01:04:43 -0400 [thread overview]
Message-ID: <e38d12ff0810082204h70f19be1h9035a8bd941cdffb@mail.gmail.com> (raw)
In-Reply-To: <9acccfe50810082032m6a4b92a2p316d90fee3bceb21@mail.gmail.com>
On an 1.7 GHz Ahtlon Xp with 768 MB of SDR133, it takes about 8 hours
if X is *not* running and there are no other emerges nor anything else
that is CPU-/RAM-hunry. Basically, turn off X and your research
programs for up to 12 hours. nice -n -20 can shave your emerge time
even more, at the risk of decreased system responsiveness.
The only thing that takes a day or two is emerge -uvD --with-bdeps=y world .
Gentoo requires patience, with the reward of fast code. I actually
enjoy waiting for compiles to finish, so much so that I install from
stage 1 if possible and only use stage 3 if I have to get Gentoo
working in a short amount of time. At least the compiling makes a very
good screensaver :D
On 10/8/08, Kevin O'Gorman <kogorman@gmail.com> wrote:
> On Wed, Oct 8, 2008 at 6:28 PM, Andrey Vul <andrey.vul@gmail.com> wrote:
>> On Wed, Oct 8, 2008 at 5:55 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>> On 10/8/08, Dirk Heinrichs <dirk.heinrichs@online.de> wrote:
>>>> > > Am Mittwoch 08 Oktober 2008 04:23:35 schrieb ext Kevin O'Gorman:
>>>> > > Why did you choose Gentoo, then? Only by compiling OOo, you will
>>>> get one
>>>> > > that fits into _your_ system.
>>>
>>> For me, the reasons are
>>> 1. I wanted Gentoo for the toolchain and the things I'm developing.
>>> These are the things where I wanted support tailored to my 2xXeon (4
>>> core) system.
>>>
>>> 2. I've been using Oo-bin because it worked, and efficiency didn't
>>> matter because
>>> I don't even use it every week. Compiling it takes a day or so and
>>> accordingly it was spending more time compiling than I was spending
>>> using it. Now it no longer works and I'll probably use Word on my
>>> wife's laptop. But I won't like it.
>> Your system is 4 core and it takes a day to compile OOo? Something
>> sounds very off.
>> Honestly, my 3 year old laptop which has 1 core and a 1.8 GHz Turion
>> with 2GB of DDR333 takes 4 hours to compile.
>> What are you running apart from emerge (e.g. X, firefox, etc.)?
>>
>>
>> --
>> Andrey Vul
>
> This is a 6-year-old desktop, 1.6 GHz, 2 GB original DDR memory.
>
> I run KDE and sometimes a bunch of compute-bound research tasks of my
> own creation.
>
> I haven't compiled it in so long I may be confusing it with gnome or
> KDE or any of that collection of things that monopolize my machine
> from time to time. A couple of years back I went to 'bin' on things I
> don't use much, and did some trimming on modular packages like KDE to
> cut down my emerge times. There are just so many times when I want to
> break in to fool with some hardware and I'm loath to do it during an
> emerge. I just think of these measures as saving me days of emerging
> from time to time.
>
> ++ kevin
>
> --
> Kevin O'Gorman, PhD
>
>
--
Andrey Vul
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
next prev parent reply other threads:[~2008-10-09 5:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 23:31 [gentoo-user] Reopen: OpenOffice dies on startup Kevin O'Gorman
2008-10-06 16:43 ` Dirk Heinrichs
2008-10-08 2:23 ` Kevin O'Gorman
2008-10-08 5:50 ` Dirk Heinrichs
2008-10-08 21:33 ` b.n.
2008-10-08 21:28 ` Dirk Heinrichs
2008-10-08 21:55 ` Kevin O'Gorman
2008-10-09 1:28 ` Andrey Vul
2008-10-09 3:32 ` Kevin O'Gorman
2008-10-09 5:04 ` Andrey Vul [this message]
2008-10-08 22:27 ` Neil Bothwick
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=e38d12ff0810082204h70f19be1h9035a8bd941cdffb@mail.gmail.com \
--to=andrey.vul@gmail.com \
--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