🚀 go-pugleaf

Ted <*paree*@usa.net> wrote:
> I could only see something like: "...could not handle nul pointer....." and tons of numbers....


yes, the last time was with bad memory.

Try (== adapt) this script:

#!/bin/sh

VERSION=linux-2.1.127
FILE=/share/archives/linux/kernel/v2.1/$VERSION.tar.bz2
DIR=/usr/tmp/tt_$$

mkdir -p $DIR
chmod 700 $DIR

cd $DIR

bzip2 -d < $FILE | tar xf -

mv $VERSION linux.save

while :
do
  bzip2 -d < $FILE | tar xf -

  diff -U 3 -rN linux.save $VERSION
  if [ $? != 0 ]; then
     echo "ABORTING, data still there"
     exit 2
  fi
  sleep 30
  rm -rf $VERSION
done

cd ..
rm -rf $DIR

# If that script spews anything to the screen, you've failed your memory
# test.  The only exception to this is if your disk sub-system doesn't use
# DMA, then this test is not as good as it could be, but if your system uses
# DMA (such as a decent SCSI controller, or DMA IDE) then this test will show
# bad RAM much faster and more reliably than compiling a kernel.