Having downloaded Debian 3.0 r1 from the web, and burned a CD I get the following error every time I attempt to do a "simple" automatic (vanilla - I suppose) install by just following all the prompts and accepting the defaults:
File Corrupt: /instmnt/main/g/groff-base/groff version 2.17.2-15 or something quite like that.
I wend to another mirror site blueyonder and downloaded their
suggested FTP and used it to download
debian 3.0 r 0 , and burned a CD -- (two download, with 2 CDs in fact)
and get the similar message to above, but with a different file being declared
corrupt on both these new CDs: libc6
I am attempting to install to a 10 gigabyte disk that has a previous
version of Linux on it
( Previous Linux always died when it attempted to load and run the
GUI interface during bootup -- something to do with the fact that the built-in
video "shares" (steals) 8 MB of memory from my 128 MB plus 256 MB = 382
MB of SDRAM memory. -- But that is another story.)
So far I have tried RedHat 5.2 and Suse 6.4 on this motherboard without
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.
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???)
Any comments and advice GLADLY received!
You are doing a GREAT WORK in providing a stable operating system that gives us poor peons an alternative to Windoze!
David Buehler
d.bu@verizon.net
Attachment:
DBG_LOG.TGZ
Description: application/compressed