Bill Triplett wrote:
>
> Derek, from your paper:
>
> > This was a fun set of runs. The most exciting thing to happen was
> > the complete failure of gcc under two seperate runs under the 2.2.19
> > kernel! gcc died on the inital run with "parse error" messages. To
>
> When is the last time the RAM was tested in that machine? The same gcc
Recently. The memory's all good, at least according to memtest. I
really think it was related to the hard drive. I hate Toshiba laptop
hard drives. Plus it's not a well-known IDE interface (it's all
"Compaq" chipsets in this thing) so it's entirely possible that enabling
DMA, 32-bit I/o and all that like I did would eventually cause some kind
of rare timing issue and corrupt some data someplace. During the
heaviest runs with the 2.2 kernel, the drive light was on and stayed on
continuously and the machine was barely capable of interactive work. It
was really hardcore slammed. It wouldn't surprise me if one of those
one-in-a-billion chance timing issues that we know are in the kernel in
a few places actually occurred.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
#!/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.cs.cmu.edu/~dst/DeCSS/Gallery/
http://www.eff.org/ http://www.anti-dmca.org/
http://www.sciencemag.org/cgi/content/full/293/5537/2028
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:38:29 EDT