This confuses me. How can you rely on an md5sum check from the Redhat disc during
install? How do you know that part of the disc isn't bad to start with?
I noticed this too when I downloaded the images so I could start on the
rpm failure thing.
I believe it to be some kind of funky horn dog
OK, I'm puzzled by this. Can anyone explain?
I installed RH8 from ISOs I downloaded. I verified each ISO file and they were all
good. I then burned CD's 1, 2 and 3 to CDR and attempted to verify them in the
following ways:
1. Performed 'diff /dev/cdrom /path/to/downloaded.iso'
2. Performed
On Tue, 15 Oct 2002, Tim Wunder wrote:
OK, I'm puzzled by this. Can anyone explain?
I installed RH8 from ISOs I downloaded. I verified each ISO file and they were all
good. I then burned CD's 1, 2 and 3 to CDR and attempted to verify them in the
following ways:
1. Performed 'diff
On Tuesday 15 October 2002 20:34, Keith Morse wrote:
On Tue, 15 Oct 2002, Tim Wunder wrote:
snip
So, I decided to try the disks anyway to see what would happen. As it
turns out, RedHat provides a disk check at the beginning of the install
process. I put each of the 3 disks thru redhat's
On Tue, Oct 15, 2002 at 09:56:13PM -0400, Tim Wunder wrote:
On Tuesday 15 October 2002 20:34, Keith Morse wrote:
On Tue, 15 Oct 2002, Tim Wunder wrote:
snip
So, I decided to try the disks anyway to see what would happen. As it
turns out, RedHat provides a disk check at the beginning of
On Tue, 15 Oct 2002 22:07:49 -0400
[EMAIL PROTECTED] wrote:
On Tue, Oct 15, 2002 at 09:56:13PM -0400, Tim Wunder wrote:
On Tuesday 15 October 2002 20:34, Keith Morse wrote:
On Tue, 15 Oct 2002, Tim Wunder wrote:
snip
So, I decided to try the disks anyway to see what would happen. As
