On Sat, Apr 08, 2006 at 12:19:30AM +0200, Frans Pop wrote: > > On Saturday 08 April 2006 00:03, Jack Carroll wrote: > > During kernel download, ls /target/boot shows > > System.map-2.6.15-1-686 > > config-2.6.15-1-686 > > initrd.img-2.6.15-1-686.new > > vmlinuz-2.6.15-1-686 > > Good so far. I'm assuming that you are looking while the initrd is being > generated and that it still has to be renamed. > > > At the end of kernel download, all those files have been > > automatically deleted. > > Huh? Are you very sure about that? I know of _nothing_ in the installer > that would delete files in /target/boot and I have never seen a similar > error. > Is /target/boot a separate file system? If it is, is it still mounted when > you check? > > There must be some kind of mounting and unmounting going on here to > explain this.
I'm sure. I stopped the installation as soon as the files were deleted. A little follow-up. I restored the MBR with a generic GRUB floppy, so Sarge will again boot from /dev/hda1 and /dev/hda5. With that, I mounted /dev/hda2 and/dev/hda6, which were /target and /target/var respectively. /target/boot really is empty, and ls -R /target | grep vmlinuz finds nothing. So: these files weren't renamed. They were deleted. So, the question is still: is my debian-installer boot floppy incompatible with the rest of the installer floppy set, and does that make this test irrelevant? I already know that a full set of Etch RC2 installer floppies doesn't work. It fails earlier, when attempting to install the initrd tools. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]