Bug#361180: Debian installer doesn't install kernel
On Sat, Apr 08, 2006 at 12:19:30AM +0200, Frans Pop wrote:
> It would also be nice if you used a mail address that does not have
> ridiculous blocking when I send from my normal address:
>
> Your message cannot be delivered to the following recipients:
>
> Recipient address: mykrowatt@comcast.net
> Reason: Server rejected MAIL FROM address.
> Diagnostic code: smtp;550-195.121.247.6 blocked by
> ldap:ou=rblmx,dc=comcast,dc=net B
> Remote system: dns;gateway-s.comcast.net (TCP|195.121.247.6|41321|
> 204.127.202.26|25) (sccrmxc22.comcast.net - Maillennium ESMTP/MULTIBOX
> sccrmxc22 #662)
This doesn't make any sense to me. I'll see if I can get an answer
from Comcast as to why it's doing this.
>
> 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.
I'm sure. It's been confirmed two ways now.
> Is /target/boot a separate file system?
No. It's part of /dev/hda2.
If it is, is it still mounted when
> you check?
/dev/hda2 is still mounted on /target. No other mounts have
changed, either.
>
> There must be some kind of mounting and unmounting going on here to
> explain this.
Unmounting wouldn't delete files, though.
>
> > /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.
I am not doing a CD based install. I'm booting from floppies and
installing from the network. The boot floppy set is what I'm testing.
Reply to: