Public SourceMage Discussion List

[Andrew <afrayedknot AT thefrayedknot.armory.com>]

in regards to everything being in ram, you could turn off the tmpfs
option, then it will try and take advantage of the file system cache
(probably better in the long run anyways).

also try turning off all power management.

view the compile log for glibc (someone posted a trick to get the compile
log onto another machine, try that out)

one thing that paranoid people like me do is copy your /lib (minus
subdirs) into say /tmp/lib then add /tmp/lib to /etc/ld.so.conf and run
ldconfig ive had some trouble building glibc where it mysteriously tossed
the libraries it was using, and hung itself and the system.

and of course make sure your sorcery is current, not an older tarball
lying around.


On Fri, Sep 20, 2002 at 08:49:27AM -0700, Michael Mikkelsen wrote:
> Hello,
> 
> I'm on my tenth iteration, or so, of this loop:
> 
> for (;;) {
>       1) install
>       2) sorcery update
>       3) die during sorcery update (hard lock -- usually during glibc 
> (loooong 
>               compile; all in ram))
>       4) sorcery/cast/etc hosed after reboot (spells gone -- from this 
> point on       
>               sorcery dies during Integrity check of spells)
> }
> 
> I believe that it's either a) screen blanking wiggin' out by GeForce4 and 
> causing kernel to lock or b) hard drive going to sleep and not waking up 
> during long, ram based, compiles.
> 
> Does anyone know how to stop either or both of these things?  Or have other 
> ideas?  I'm trying to figure out an hdparm command to disable hd sleeping 
> for 
> now...
> 
> 
> still enthusiastic... but having considerably less fun :-(
> 
> 
> -- 
> Michael D. Mikkelsen
> Micro Business Systems
> Fresno Linux Users Group
> 
> One By One The Penguins Steal My Sanity
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss