Re: Re: [Lnx-bbc-cvs] Error building an i386 HEAD LNX-BBC image at Wed Apr 7 00:32:14 EDT 2004, build began at Apr 7 at 00:00

I cannot believe D. Joe Anderson said this on the ENTARNET:
> Just wanted to say it's good to see goose and the goosemaster back at it.

Yeah, so around the end of February my RAID backplane decided that one
of the drives had died.  I shut down goose, ordered a couple of new
ones overnight and waited.  When the new drives arrived, I put one in
to replace the dead old drive (about a year old), and it was 312MB
smaller than the other two.  They are exactly the same model, the
difference is some damn firmware revision issue.  So a few hours
later, I stuck the old dead drive back in just to see what would
happen, and lo and behold it spun up and the RAID controller started
rebuilding the data.  So I ran with it.  I think it was a heat
problem, which is why I call the server closet in my apartment The
Closet of Doom.  I figured the drive may actually be marginal, and so
I stopped the builds.  It's gone this long without trouble.  I check
the enclosure periodically and it's not nearly as hot (I've left the
case open).  So as of getting DSL at my new apartment, quarterdaily
builds on goose.movealong.org have resumed.

I've been looking into the current problem with gcc and 2.6 headers.
It looks like gcc's build is supposed to slurp asm-generic into
sys-include along with asm and linux, but it doesn't.  Maybe I'm wrong
about that, or maybe it's because we've stubbornly stuck with gcc 3.2.
I'm a bit hesitant to NUV gcc.  Toolchains are mad voodoo.

-Nate

-- 
--< ((\))< >----< [email protected] >----< http://www.movealong.org/ >--
pub  1024D/05A058E0 2002-03-07 Nate Riffe (06-Mar-2002) <[email protected]>
     Key fingerprint = 0DAC F5CB D182 3165 D757  C466 CD42 12A8 05A0 58E0