Am 18.04.2011 06:53, schrieb Joshua Murphy: > On Sun, Apr 17, 2011 at 9:44 PM, Dale <rdalek1...@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) >
My strategy for getting Gentoo on a netbook with an SSD is to use NFS for PORTAGE_TMPDIR. Works nicely and makes less work than building everything remote. The only problem is that the setuid bit seems to get lost. That's not too much of an issue, though. There are only a handful of setuid binaries on a system and you can compare the list of them with a normal desktop machine. Regards, Florian Philipp
signature.asc
Description: OpenPGP digital signature
