Ok, I've got better things to do.

[tithonium]

So, stage1 gentoo on hladolet failed during glibc build. Repeatedly. Fine, I'll try stage2. Oh, except the stage2 .bz2 is corrupt. FINE, stage3. No, bzcat on the bootstrap system doesn't like it. Fine, decompress it on sedna and move the tar over. Fine, no problems.
Now, sync portage. And then telnetd goes away. I can no longer connect to the box. It doesn't respond to anything except ping. So, now there is no bootable chainloader on the drive anywhere, no operating system anywhere in a bootable condition, no anything. So, the box is now hosed. If I want to start over, I'll have to yank the drive, put it in another machine, put the chainloader on it, put it back in, and start over.

I really don't have the patience to deal with it any further. I don't /need/ this box right now, I can deal with it some other time.

Comments

[firesign3000.livejournal.com]

we messed around with gentoo some at work, and it was a royal pain in the ass. good luck. we ended up settling on fedora core.

[allanc.livejournal.com]

That screams "Bad RAM or CPU" to me. Every time I've had that many of that sort of problem with an install, that's turned out to be the case.