> I repeat, I am not doing anything "non-standard":
>
> $ cp /boot/config-2.6.31-1-amd64 .config
> $ make-kpkg --initrd --revision=custom.1.2 kernel_image
That's [retty non-standard for a custom kernel. You are using
a distro kitchen sync config for making a custom kernel; and
kernel-package is mostly geared for individuals.
>
> *I* did not ask for XEN, this is part of the debian stock
> kernel image configuration.
Yes, you did, by using that config file.
> *I* did not instruct grub2 not to ignore vmlinux, my grub2
> configuration was installed as standard.
And you fed it a non-standard image, which had vmlinux in
it. kernel-package is not geared for people cargo culting.
> Until the recent change, I had never seen vmlinux,
> and therefore there was no problem. Why was the decision made
> to now produce this?
This is part of the effort to make kernel-package friendlier
to XEN, and as Xen moves closer to inclusion in mainline. Also, the
usage conventions for XEN are changing, and k-p has to be made to
adapt to it.
> Also, I can find no mention of "make defconfig" in
> /usr/share/doc/kernel-package/README.gz
kernel-package does not say _anything_ about how you get your
.configs. The defconfig is documented in upstream kernel
documentation.
> so please do not moralize me and recognize that there IS a bug!
I do not think there is a bug anymore, anyway. You are using
unstable, there is a reason it is called the bleeding edge. Behaviour
changes, and it sometimes takes a few days for things to stabilize.
manoj
--
Manoj Srivastava <[email protected]>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
