still just glowing over how quick things are at emerging. When my neighbor isn't downloading crap (we share his cable connex through a router) and when the masked packages *do* compile w/o errors, I find that it is so blazing fast I can't even take a ciggie/b33r break.

the install from stage1 (total time spent--including producing a new xf86config for a new vid card, and recompiling the kernel a couple times for missed drivers/options) took < 10 hours
bootstrap: < 1.5 hours
kernel compile: under 15 minutes (with a LOT of added shit--this is my desktop where the wacom, scanner/printer, etc. gets hooked up).

I can't get over how fast this baby is. And it really makes the tedium of emerge go away. Yay for the 1 gig of L2 cache (the 3200+ chip here).

How long did your install take? Impressed by compile times still or already a jaded user?_________________peribleptic anacolouthon.

I don't remember exactly but I mine up and running with KDE in one night. I want to say a matter of hours (beginning of system install to end). I didn't have to go to bed and wake up the next morning only to find it still crunching. That is for sure.

Reading all these "Look at how fast I can compile!" posts is making me drool even more for one of these systems. Once I get my tax refund this month, I'm gonna spring for a dual Opteron system. Can't wait!

the die is pretty big (used up the last of the last of my small tube of thermal paste)...

And yes, once you get your tax refund, satisfy your desires: go for the dual opteron =P you will not regret it. Get yourself some class-a ram to supplement the twin beasties too. Then laugh at all the flaky "lets speed up emerge" posts along with us =]_________________peribleptic anacolouthon.

well im sorry to say that the L2 cache is only 1Meg. And it only took me a minute to compile the kernel. It took about 10 on my old 2.4 P4, Xfree and kde took about 2 1/2 to 3 hours. I dont know what is wrong with your system but that's quite a bit different than mine.

jarsh16: doh. 1 meg, yes. Kernel took more than a minute on the first compile... and the system really only took as long as it did to install because I would leave expecting it to crunch for longer than it did. I'd come back to check, find it long done, and carry on. As far as I can tell, nothing is wrong with the system and I doubt much is different between our two setups other than kernel options and download speeds._________________peribleptic anacolouthon.

I am doing a Gentoo Stage1 install for someone I know on his workstation.
Specs: 2x Opteron 1.8 (can only use one when booting from the livecd, 'smp' kernel hangs)
2Gb RAM
Enough HD space
ATI Radeon 9800 (hope Ill get that one to work properly)
2x 19" TFT screens

Installed Gentoo for the first time ever a couple of days ago. With the 3200+ CPU and 512MB RAM it only took 8-9 hours to get FVWM working. One of those hours were used to figure out a way to get telnet working during the first install stage (need it to log onto the Internet ), so if I had had the ability to use something normal like ssh to connect the total time would have been down to 7-8 hours. Got to love this system _________________"There are only 10 kinds of people; those who know binary,
those who don't and those who start counting at zero"
:: www.golden-ratio.net::

I compiled my kernel in 3:24 seconds, hehehe.
My flags are -O2 -finline-limit=1200 -finline-functions -pipe -fomit-frame-pointer -fprefetch-loop-arrays -mfpmath=sse_________________If God has made us in his image, we have returned him the favor. - Voltaire

Now this machine just goes extremely fast. Even when booting from the livecd.
We changed one thing: removed all usb devices...
Then we had problems to start the kernel (panics), but this is also solved now (BIOS update).

I'm pretty sure I read the -mmmx -msse -msse2 get ignored on the amd64 because the cpu arch implies these and setting these flags often enables some wierd 32-bit assembler which would obviously not work quite as expected in 64-bit mode...just thought I'd share

I'm pretty sure I read the -mmmx -msse -msse2 get ignored on the amd64 because the cpu arch implies these and setting these flags often enables some wierd 32-bit assembler which would obviously not work quite as expected in 64-bit mode...just thought I'd share