From: Joshua Murphy <poisonbl@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Howzat!
Date: Mon, 18 Apr 2011 00:53:54 -0400 [thread overview]
Message-ID: <BANLkTik_iL5pS9TSVTngE4XNjP=ktqzzsg@mail.gmail.com> (raw)
In-Reply-To: <4DAB9773.3070605@gmail.com>
On Sun, Apr 17, 2011 at 9:44 PM, Dale <rdalek1967@gmail.com> wrote:
> Peter Humphrey wrote:
>>
>> Hello list,
>>
>> How's this for sheer persistence and grit?
>>
>> $ genlop -c
>>
>> Currently merging 321 out of 368
>>
>> * www-client/chromium-10.0.648.204
>>
>> current merge time: 11 hours, 41 minutes and 9 seconds.
>> ETA: any time now.
>>
>> This is my Atom N270 LAN server box.
>>
>>
>
> I got a very old Compaq rig with quad 200Mhz CPUs and 128Mbs of ram. I have
> always wondered how long it would take to compile OOo on that thing. 12
> hours to compile a browser does take patience. I hope you don't have a
> power failure right at the end. o_O
>
> How long does it take to open it when it gets done? Seconds? Minutes?
>
> Dale
>
> :-) :-)
>
>
Assuming a reasonable 1GB ram on the box (pretty well standard to low
with an Atom), and considering what my netbook does (the same single
core 1.6GHz with HT turned on for responsiveness in my case), about
2-3 seconds... but then I'm on a little SSD too. I should admit my
netbook's running Debian at the moment, though. Didn't want to abuse
the SSD too much with writes, and it's tedious to install things
through an intermediary system all the time. The fullsize laptop, when
it gets its rebuild over the next week (it's been a windows 2k3 server
development system lately)
--
Poison [BLX]
Joshua M. Murphy
next prev parent reply other threads:[~2011-04-18 5:11 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 1:28 [gentoo-user] Howzat! Peter Humphrey
2011-04-18 1:44 ` Dale
2011-04-18 4:53 ` Joshua Murphy [this message]
2011-04-18 7:52 ` Florian Philipp
2011-04-18 8:12 ` Neil Bothwick
2011-04-18 9:32 ` Florian Philipp
2011-04-19 22:40 ` Kfir Lavi
2011-04-19 22:54 ` Dale
2011-04-20 7:33 ` Joost Roeleveld
2011-04-20 8:42 ` Dale
2011-04-20 9:25 ` Joost Roeleveld
2011-04-20 9:49 ` Pandu Poluan
2011-04-20 10:24 ` Joost Roeleveld
2011-04-21 5:41 ` Pandu Poluan
2011-04-21 15:49 ` Paul Hartman
2011-04-20 12:37 ` Joost Roeleveld
2011-04-20 13:16 ` Alan McKinnon
2011-04-20 13:41 ` Joost Roeleveld
2011-04-20 20:06 ` Alan McKinnon
2011-04-20 21:38 ` Mick
2011-04-18 11:22 ` Peter Humphrey
2011-04-18 12:44 ` Neil Bothwick
2011-04-18 14:35 ` Peter Humphrey
2011-04-18 14:51 ` Florian Philipp
2011-04-18 15:48 ` Peter Humphrey
2011-04-18 15:59 ` Peter Humphrey
2011-04-18 21:56 ` Neil Bothwick
2011-04-19 5:34 ` Thanasis
2011-04-19 6:57 ` Joost Roeleveld
2011-04-19 8:04 ` Neil Bothwick
2011-04-19 12:07 ` Thanasis
2011-04-20 13:33 ` Neil Bothwick
2011-04-20 21:23 ` Thanasis
2011-04-20 22:01 ` Neil Bothwick
2011-04-21 7:44 ` Thanasis
2011-04-21 8:03 ` Neil Bothwick
2011-04-21 8:15 ` Thanasis
2011-04-21 10:57 ` Thanasis
2011-04-21 13:26 ` Neil Bothwick
2011-04-21 14:45 ` Thanasis
2011-04-21 22:09 ` Neil Bothwick
2011-04-22 5:05 ` Thanasis
2011-04-22 7:14 ` Neil Bothwick
2011-04-22 8:12 ` Thanasis
2011-04-22 13:00 ` Neil Bothwick
2011-04-22 15:26 ` Thanasis
2011-04-22 18:46 ` Neil Bothwick
2011-04-21 13:41 ` Mark Knecht
2011-04-21 22:42 ` Neil Bothwick
2011-04-22 0:38 ` Mark Knecht
2011-04-19 12:40 ` Joost Roeleveld
2011-04-20 10:40 ` Thanasis
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='BANLkTik_iL5pS9TSVTngE4XNjP=ktqzzsg@mail.gmail.com' \
--to=poisonbl@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