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. > /target/var/cache/apt/archives lists the > linux-image-2.6-686 package under a couple of names. Not really relevant. > Clearly something is wrong. Is it worthwhile to run more tests, or > is it invalid because the current daily builds don't include a boot.img > of their own? What does boot.img have to do with this? Whether or not the boot floppy image builds is completely irrelevant to CD based installs. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
