[2909] in SIPB_Linux_Development
Warning: could not send message for past 1 day
daemon@ATHENA.MIT.EDU (Mail Delivery Subsystem)
Tue Aug 22 05:46:07 2000
Date: Tue, 22 Aug 2000 05:45:46 -0400 (EDT)
From: Mail Delivery Subsystem <MAILER-DAEMON@LCS.MIT.EDU>
To: <linux-dev@MIT.EDU>
This is a MIME-encapsulated message
--FAD18428.966937546/mintaka.lcs.mit.edu
**********************************************
** THIS IS A WARNING MESSAGE ONLY **
** YOU DO NOT NEED TO RESEND YOUR MESSAGE **
**********************************************
The original message was received at Mon, 21 Aug 2000 05:36:52 -0400 (EDT)
from SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]
----- The following addresses had transient non-fatal errors -----
<jsholmes@lcs.mit.edu>
----- Transcript of session follows -----
<jsholmes@lcs.mit.edu>... Deferred: Operation timed out with telesto.lcs.mit.edu.
Warning: message still undelivered after 1 day
Will keep trying until message is 5 days old
--FAD18428.966937546/mintaka.lcs.mit.edu
Content-Type: message/delivery-status
Reporting-MTA: dns; mintaka.lcs.mit.edu
Arrival-Date: Mon, 21 Aug 2000 05:36:52 -0400 (EDT)
Final-Recipient: RFC822; jsholmes@telesto.lcs.mit.edu
Action: delayed
Status: 4.4.1
Remote-MTA: DNS; telesto.lcs.mit.edu
Last-Attempt-Date: Tue, 22 Aug 2000 05:45:46 -0400 (EDT)
Will-Retry-Until: Sat, 26 Aug 2000 05:36:52 -0400 (EDT)
--FAD18428.966937546/mintaka.lcs.mit.edu
Content-Type: message/rfc822
Return-Path: <linux-dev@MIT.EDU>
Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2])
by mintaka.lcs.mit.edu (8.9.3/8.9.3) with SMTP id FAA31545
for <jsholmes@lcs.mit.edu>; Mon, 21 Aug 2000 05:36:52 -0400 (EDT)
(envelope-from linux-dev@MIT.EDU)
Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP
id AA23619; Mon, 21 Aug 00 05:36:15 EDT
Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45])
by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id FAA05492;
Mon, 21 Aug 2000 05:36:33 -0400 (EDT)
Received: from paradox.mit.edu (PARADOX.MIT.EDU [18.242.0.144])
by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id FAA16175;
Mon, 21 Aug 2000 05:36:33 -0400 (EDT)
Message-Id: <4.3.2.7.2.20000821053518.047e3008@po10.mit.edu>
X-Sender: techie@po10.mit.edu (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 21 Aug 2000 05:36:38 -0400
To: Will Koffel <wkoffel@MIT.EDU>
From: "Edward J. Ouellette" <techie@MIT.EDU>
Subject: Re: installing Redhat 6.2 on an old system
Cc: linux-help@MIT.EDU
In-Reply-To: <399D864F.3983DF7A@mit.edu>
References: <399D4520.1E8B3FF6@mit.edu>
<twy66oyabs4.fsf@baba-yaga.mit.edu>
<399D47C5.E08DE45D@mit.edu>
<udl66oytyry.fsf@multics.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Will,
I've experienced issues relating to floppy drives themselves (most are made
cheaply), whereby the head alignment is not exactly the same from drive to
drive, resulting in correct read/write/boot behavior on floppies formatted
on the particular drive, but dropped bits / failure to boot when the floppy
is taken to another drive. You may even be able to "see" the directory
structure, but files may copy corrupted. So, I suggest temporarily swapping
/ replacing the floppy drive in your friend's machine and trying again with
a stock RH 6.2 boot floppy.
Is the BIOS recognizing the CDROM ok?
cheers,
Ed
At 02:54 PM 8/18/2000 -0400, you wrote:
>"Aaron M. Ucko" wrote:
>
> >
> > Depending on where their bad sectors are, bad floppies might appear
> > good on casual inspection; you'd have to attempt to access all the
> > actual data (rather than just a directory listing) to tell. In
> > addition, your machine's floppy drive could be relatively sensitive to
> > bad floppies (relatively bad at coping with indistinct bits.)
>
>I believe that this explains the RH5.2 boot disk I have not getting fully
>through
>the kernel load. However, does it also explain why a fresh 6.2 boot.img
>will not
>even bring up the red and blue welcome screen with options for rescue,
>install,
>etc.? This happens before the kernel even loads. Perhaps it's also a bad
>floppy
>issue, but seems a lot less likely.
>
>In addition, I never got an answer concerning the chances of installing a
>fresh
>6.2 via another machine and then transferring it over to the machine in
>question. Should this work? Or am I missing something important about the
>install? Let me know if people have suggestions on this front, as I have a
>feeling it's the direction I'm going to forced to head. :)
>
> Will
___________________ _________
___ ____/______ /___ ________ _______________ /
__ __/ _ __ / __ | /| / /_ __ `/__ ___/_ __ /
_ /___ / /_/ / __ |/ |/ / / /_/ / _ / / /_/ /
/_____/ \__,_/ ____/|__/ \__,_/ /_/ \__,_/
_______ ____________ _____ _____
__ __ \____ _______ ___ /___ /_____ __ /___ /______
_ / / /_ / / /_ _ \__ / __ / _ _ \_ __/_ __/_ _ \
/ /_/ / / /_/ / / __/_ / _ / / __// /_ / /_ / __/
\____/ \__,_/ \___/ /_/ /_/ \___/ \__/ \__/ \___/
__o
_`\<,_
(+)/ (+)
techie@MIT.EDU
work: NE43-819 voice: (617) 253-5814 FAX: (617) 253-5060
home: 500 Memorial Dr. #455 Cambridge, MA 02139
voice/FAX: (617) 225-8955
--FAD18428.966937546/mintaka.lcs.mit.edu--
