On Sun, 31 Aug 2003, Charlie wrote:

> Yep, those are the numbers in the .asc files from the mirrors alright. But 
> when I check this way;
> # mkcd --checkmd5 MandrakeLinux-9.2rc1-CD1.i586.iso
> or disk 2 or 3, I get what I reported above. Now I'm lost again. 
> 
> As usual...:-)
> 
> So, I had set today aside to finally install RC1, and urpmi it to current 
> cooker. Is it safe to install RC1 from these (rsynced against sunet and 
> checked as reported above) or have I burned useless copies.


Well, you can check the majority of the data on the CDs, using 'rpm -K 
path/to/RPMS/*'. You can do this with the ISOs loop-mounted. Of course, 
this tells you nothing about DraxX, but if the RPMS all verify, chances 
are the 100MB of DrakX, stage2 etc should be ok.

> I used -RWs so it 
> doesn't matter. Or should I just say screw it and do the usual hd.img cooker 
> install. That's fine for me; but a friend has an old Compaq he wants to 
> "sacrifice to the testing Gods" and I'd need disks for him tomorrow.

Give them a try and find out.

> 
> I vaguely recall something similar in a previous release. Published md5sums 
> not matching the disks I mean. A couple of releases ago I think, and I had 
> already installed whichever version it was at the time without trouble.
> 

The ISOs on ftp.sun.ac.za/iso-images/mandrake-beta match the md5sums, this 
mirror rsync's from sunet.se, so I don't think this is the case.

Regards,
Buchan

-- 
|----------------Registered Linux User #182071-----------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x121
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
*****************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
*****************************************************************

Reply via email to