Who's a scofflaw?  I own original DVD's that I'm trying to play back
under Linux.  To h*ll with the MPAA if they don't like it.  They've
already gotten my money for it, so they can just sit back, shut up, and
enjoy the movie.

plug@arcticmail.com wrote:
> My goodness!  I didn't realize the PLUG list had such scofflaws! :)
> I hope that Paul is posting from China!
> 
> I think my favorite was the
#!/usr/bin/perl -w
# 531-byte qrpff-fast, Keith Winstein and Marc Horowitz
<sipb-iap-dvd@mit.edu>
# MPEG 2 PS VOB file on stdin -> descrambled output on stdout
# arguments: title key bytes in least to most-significant order
$_='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
> 
> On the Evolution mailing list, one of the developers has this in his
> > .signature.
> >       -Paul
-- 
Digital Wokan, Tribal Mage of the Electronics Age
Guerilla Linux Warrior


From Pete Buechler <peter.buechler@home.com>  Tue Mar 13 04:48:34 2001
From: Pete Buechler <peter.buechler@home.com> (Pete Buechler)
Date: Mon, 12 Mar 2001 21:48:34 -0700
Subject: kernel very unstable
In-Reply-To: <66037540DA72D31180D400A0C9D17D1F46622E@phoenix1.exponent.com>
References: <66037540DA72D31180D400A0C9D17D1F46622E@phoenix1.exponent.com>
Message-ID: <01031221483401.01581@boy>

On Sunday 11 March 2001 02:51 pm, Lucas Vogel wrote:
> > > My stock SuSE 2.2.16 kernel keeps intermittently crashing
> >
> > and hosing my
> >
> > > machine to where I have to do a hard reboot. It seems to
> >
> > generate some kind
> >
> > > of oops on the kmem_free function.
> >
> > In general, any regular crashing by a stock kernel points to hardware
> > problems on your end.  No kernel that ships with any of the major
> > distributions will give these kind of problems on halfway decent
> > hardware.  In general.
>
> How do I diagnose and fix something like this then?
>

Yikes. I did not see any replies from anybody who is an expert. So you will 
have to take my advice.

First examine your syslogs. You already did that, because you told us that 
you saw MARK in there a bunch of times. Anything else of use in there?

Second try to think of what you were doing at the time of the crashes. See if 
that gives you any ideas.

Third, if you have any Western Digital drives use hdparm to turn off DMA for 
them. Their implementation of UDMA-66 ignores CRC problems (dumm).

Fourth, make sure that you do not have any IRQ conflicts. Make sure you note 
which IRQs are used by what and double-check this by looking at the contents 
of /proc/interrupts.

Fifth, capture the oops (maybe with a pencil and paper) and run it through 
ksymoops (look for directions with the Linux kernel source code, under the 
Documentation directory in a file called oops-tracing.txt). If you can figure 
out where the code was when it crashed maybe you can get a hint as to the 
problem.

Sixth, see if you have any diagnostics for your hardware that came with them. 
Or, go to the web sites of the companies

Seventh, strip your system down to the bare essentials - monitor, keyboard, 
mouse, motherboard and one drive. See how that runs. Then add hardware back 
in one at a time, see what causes the destabilization.

Hardware problems can be a real pain to diagnose. I say we all go out and get 
computers built with self-checking pairs. That will help stimulate the 
economy :-)

-Pete-