Adam Di Carlo <adam@onshore.com> writes:
> >After downloading the rescue image, though, I found that it
> >didn't appear to work. At first, I attributed the problem to a bad
Which one? 2.2.8? 2.2.9-pre? Christian's old set? We need details.
Things are changing very fast.
In fact, the new rescue disks aren't bootable by MILO at all because
there is no space for it (this is MILO's fault for being a pig, aboot
and APB both fit on a floppy with the kernel just fine). You should
be using a separate disk with MILO and linload.exe to get into MILO,
then boot the rescue disk from there.
> >Oddly enough, I could read the image from Linux (the system currently runs
> >Redhat 5.2), but an ls from MILO just gave me some % and /s, as well as
> >failing to boot. So I made a new image, copying the files from the
> >original image (I also uncompressed vmzlinux.gz, to make sure the gzipped
The rescue disks are not just plain ext2 filesystems. They also
contain SRM boot blocks. It's possible that srmbootfat is giving
problems. Since we don't use it anymore anyway (booting MILO from SRM
is just a bad idea), there won't be any more such problems.
If MILO can't read them while Linux can, then this is a bug in MILO.
> >Attached to this email is the new rescue image for potato (Alpha). You
> >should find that everything is the same - even the kernel, when
> >uncompressed, should match the kernel on your original rescue disk.
As noted above it's not really the same.
--
David Huggins-Daines, Senior Linux Consultant, Linuxcare, Inc.
613.562.1239 desk, 613.223.0225 mobile
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.