Well, as I stated, I tested mine, both as ISO's and burned CD's. The md5sums came up fine on mine (though I admit, I didn't check the md5sum on all of the final burned copies, just a few of them to be sure). The writing on the disks I burned is in small lettering and is in blue ink. Anyway, the guy needs to fist do an md5sum test on the disks in question. If the disks are bad, I would not expect him to test each and every rpm he wants to install, I would just replace the things. As I said, I will gladly burn more if needed. Otherwise, give him some of the ones we have left over - provided the md5sums check out.

Cheers

Jason

Nick Rout wrote:
*sigh* Leo has a whole lot of burned cd's. There is also a box of 10
blanks left that I was going to keep and pay for, but they can be
burned if needed.


I thought you tested them all as you burned them jason? Maybe others
didn't.


I got the mandrake cd's from e-caf and copied them a few times then
dashed to the pre-fest meeting andd distributed them to the CD burning
team. The copying could have been dodgy I suppose.

If the person who thinks he has dud disks sould do the standard tests
and let us have the results? If there is a problem they should be
replaced, but I doubt all 4 are necessarily dodgy, he should specify
which ones.

There were instructions on the list a while ago and Jason, you know
how to do it, I do not and have no need to learn at this point, could
you tell the guy how to do it.

To test the rpm files individually (as opposed to the whole cd) you
can mount the cd and then cd to the RPM directory and run the
appropriate command to check them. I suppose most people are too lazy
to read the man page so: (CD mounted on /mnt/cdrom)

cd /mnt/cdrom/Mandrake/RPMS  (on cd 2 & 3 its RPMS2 & RPMS3
respectively)
rpm --checksig --nogpg *.rpm

that will flash by pretty quickly, so as an alternative:

rpm --checksig --nogpg *.rpm > ~/rpmtest

then you can peruse ~/rpmtest for errors. A quick check is:

wc -l ~/rpmtest   # tells you the number of lines in the file
grep OK ~/rpmtest | wc-l  #tells you the number of lines that contain OK

if there is a difference then one ort more lines contains an error.

However it is probably better to test the cd as a whole - Jason?



On Wed, 19 Mar 2003 20:52:24+1200
Jason<[EMAIL PROTECTED]> wrote:


Hi All,

I was afraid of that. I KNOW mine were fine after testing the ISO
md5sum plus checking the final burned CD md5sums. However, I couldn't
verify Chris or Nick's and on a box mine would install on Chris's
would not. If I can get some blank disks, I will burn from my ISO's
any replacements needed.

Nick?? CD's??

Cheers

Jason Greenwood

PS, any one else experiencing these problems, be aware, bad burns DO occur. 9.1 MDK is out from today, on mirrors soon. If your problem is not serious, I would wait for those disks. I will replace any one's
bung 9.0 disks with fresh 9.1's if they want to wait.


My details are:
address 31B Whiteleigh Ave ChCh (Addington)
Phone: 03-338-3805
Cell: 021-184-3160

Paul wrote:

I did an install on a guys computer and he paid for all 4 disks
(mandrake +plf), he has emailed me saying the disks are  "buggered",
which would explain why I couldnt get jump-n-bump working,
considering he was a VERY powerful computer, and open office didnt
even install.

Will someone replace his disks? We had quite a lot of spare CDs
didnt we? Please contact me with details.

Thanks,

Paul

Hi there,

Thanks for helping me install Linux on Saturday.

Unfortunately I have run into a few walls:

Firstly, I havn't been able to play any DVD's. Is there something
I need to set up to get this going?
Secondly, a lot of the rpm's on most of the install disks are buggered. The only reason I can think of this happening was if it
was a poor copy. This is why OpenOffice and JumpnBump wern't
installed properly. Where can I get another copy of the disks from?
Would Linuxnut.co.nz send me a new set of disks (since I paid them a hefty
$20 already)?


Thanks for your help,
Eion










Reply via email to