Unidentified subject!
To whom it may concern:
This is a sample of mails that have been on the debian users list over the past two days. I have had exactly the same problems. I felt that you should have the right to hear the complaints and do whatever you felt needed to be done to make this right. As you can see I am also sending this to the list. The notes below are from Eric Hanchrow, Chris Pererson, and Gary Jones. I am sorry if I left anyone out. Please let me know and I will fix it. Ray
I've no objections if you want to use my mail. I didn't get my CDs
direct from them so any refund I was due would probably have to come from
them. TBH its not the money I mind (3 pounds sterling each or so)
its the aggravation I've had as a result, and I don't think they can
refund that.
Yes, I apparently have the same problem. I bought Debian 2.2 CD-Rs from
Cheapbytes and Setup complains about missing rescue floppies. blah... I
guess that's $$ down the drain.
chris
----- Original Message -----
From: "Eric Hanchrow" <offby1@blarg.net>
To: <debian-user@lists.debian.org>; <debian-boot@lists.debian.org>
Sent: Wednesday, August 23, 2000 8:53 PM
Subject: Anyone else have CheapBytes CD trouble?
> I just received my Debian 2.2 CDs from Cheapbytes -- 3 binary
> CD-ROMS. I could not boot off the first one (the installation program
> complained that it couldn't mount the rescue image).
>
> I decided to run `md5sum' on each file on the CD-ROM, and compare its
> output with the file /cdrom/md5sum.txt. I was surprised to find that
> they differed. Here's how I did it:
>
> (cd /cdrom; find . -type f -print0 | xargs -0 md5sum)
>
> Here's one file whose sum isn't what the md5sum file says it should be
> (there are many other such files):
>
> 7eea9e34469920cf5b3de06e527186bb
./dists/potato/main/disks-i386/2.2.16-2000-07-14/images-1.44/rescue.bin
> dc8e866f3a26cfa8a38f15d328519c92
./dists/potato/main/disks-i386/2.2.16-2000-07-14/images-1.44/rescue.bin
>
> Some of the files seem to be random data; one file whose name ends in
> `.tgz' is actually text.
>
> Has anyone else had this problem?
Reply to: