Douglas Koobs wrote:
>
> Not sure of the error, or if there even was one... the
> screen went blank, and the PC rebooted.
Try running the build again and see if you see anything in
/var/log/messages, /var/log/syslog, /var/log/kern.log, or another
logfile when the machine comes back up.
If it just spontaneously reboots during a compile, I would have to blame
hardware since I've *NEVER* in the years I've been running Linux seen a
bug in the kernel or any app that can spontaneously reboot the system
without first generating at least some kind of panic or segfault or
something. However, I've seen LOTS of times where faulty hardware
becomes unstable during heavy use, i.e. during a long compile.
If it always bombs during the same file during compilation, leave that
source extraction in place, but extract the source in another location
and try to rebuild it there. It could be a hard drive problem that's
freaking out whenever the system hits a particular block.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
#!/usr/bin/perl -w
$_='while(read+STDIN,$_,2048){$a=29;$b=73;$c=142;$t=255;@t=map
{$_%16or$t^=$c^=($m=(11,10,116,100,11,122,20,100)[$_/16%8])&110;
$t^=(72,@z=(64,72,$a^=12*($_%16-2?0:$m&17)),$b^=$_%64?12:0,@z)
[$_%8]}(16..271);if((@a=unx"C*",$_)[20]&48){$h=5;$_=unxb24,join
"",@b=map{xB8,unxb8,chr($_^$a[--$h+84])}@ARGV;s/...$/1$&/;$d=
unxV,xb25,$_;$e=256|(ord$b[4])<<9|ord$b[3];$d=$d>>8^($f=$t&($d
>>12^$d>>4^$d^$d/8))<<17,$e=$e>>8^($t&($g=($q=$e>>14&7^$e)^$q*
8^$q<<6))<<9,$_=$t[$_]^(($h>>=8)+=$f+(~$g&$t))for@a[128..$#a]}
print+x"C*",@a}';s/x/pack+/g;eval
usage: qrpff 153 2 8 105 225 < /mnt/dvd/VOB_FILENAME \
| extract_mpeg2 | mpeg2dec -
http://www.eff.org/ http://www.opendvd.org/
http://www.cs.cmu.edu/~dst/DeCSS/Gallery/
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:35:33 EDT