If I boot the rescue image from cd, I get fsck and e2fsck
in the boot images. Booting with the ftp install disk
and booting to the rescue image I don't. That seems
Basically, my ftp install installed 90% of the system,
and crashed. After trying a few things, install refused to
do anything because the disk needed to be fsck'ed. Unfortunately
the ftp install disk rescue image didn't contain the tools
needed to fsck the disk. At this point I was basically
out of luck - couldn't boot, since lilo didn't like the
partial system, couldn't boot the rescue disk and fsck the sytem.
There shouldn't be a space problem, since this is a ftp
image. Why isn't it there? Even if it was a space
image, I thought fsck (or at least e2fsck) would be an
important program on the rescue disk.
Added to future feature request list.
Moving to RESOVLED - DEFERRED from CLOSED - DEFERRED
Committed to rawhide CVS.
fsck & e2fsck are STILL not present in rescue mode from the bootnet.img ...
fsck & e2fsck are not present in rescue mode from the bootnet.img (using test
tree qa1212.1) ...
They dont fit in the image, so we cant do this at this time.