Re: Bug#185610: Problem -- cannot complete install -- "File is corrupt" while creating base kernel
On Thu, 20 Mar 2003, David Buehler wrote:
> So far I have tried RedHat 5.2 and Suse 6.4 on this motherboard without
No joke, RHL 5.2 (and I suspect Suse 6.4) is several years old. Since
then, we've had 2.2 kernels, we're up to the 20th 2.4 kernel and are
eagerly awaiting 2.6.
Red Hat has completely rewritten the installer, its hardware detection
is about as good as there is, it includes contemporary GNOME and KDE,
and you can install it off the Internet, you don't _have_ to download
lots.
Debian is working on a new installer, because the old one isn't very
good.
> being able to run the full-fledged GUI Linux in any version.
> I am hoping for better success from Debian, which my nephew the guru
> just loves.
A kompromise. Download Knoppix. It's basically Debian with (mostly) Red
Hat hardware detection. Runs off a single 700 Mb CD, but you _can_
install to hard disk if you want.
I've booted the CD on a couple of computers here. With _no_ interaction,
it comes up in KDE with a reasonable screen resolution, sound enabled.
>
> It appears from reading the error messages on the attached floppy file
> that the initial partition hda is 2 sectors TOO SHORT and does not end
> on the proper boundary. I will try installing by choosing the
> INITIALIZE AND PARTITION option instead of using the existing
> partitions, formed by one of these previous installs. That Bug Reporter
> is a nifty tool! :)
>
> It has been quite frustrating not to have any option during install to
> get the corrupted file from some ALTERNATE source such as a floppy, and
> then continue with the install; nor to be able to simply to SKIP the
> offending file and continue. nor to have any precise information about
> the manner in which the file is "corrupt". I was able to copy the
> entire CD onto the DOS bit bucket "nul" file using the DOS 7 (Win98)
> command
> xcopy i:\*.* nul /s
> without producing any error messages. (This has always worked in the
> past to find and name files with a corrupted sector on a floppy or on a
> hard drive in my years of experience.) Looking at the file with
> XNVIEW.exe under Win98 produced a hex and ASCII dump that did not
> contain any obvious flaws -- except perhaps that the final two bytes "36
> 00" may not be the proper file termination under Unix -- and may be,
> correct, for all I know so far. (Is that correct, or is this file
> truncated???)
Unix knows how big its files are, and so does not require termination
markers.
>
> Any comments and advice GLADLY received!
I'm pretty sure that you will be happy with Debian once you get it up,
but get that nevvy round.
--
Cheers
John Summerfield
Please, no off-list mail at all at all. This address accepts mail only from Debian lists.
Reply to: