On Monday 03 November 2008 21:36:04 Debian Bug Tracking System wrote: > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Bastian Blank > <[EMAIL PROTECTED]> by replying to this email.
Installing a linux-image-*-xen* package is all you need to do to get a Xen-enabled dom0 on Etch; if it's not that simple on Lenny, I consider that a bug. Having done a bit of poking around with help from some DDs on IRC, it seems that there are two here, one of which are not related to the kernel package directly. 1) The kernel package does not depend or recommend any of the Xen packages it will need to be correctly booted 2) the update-grub script is writing the menu.lst entry as if this were a standard kernel, not a Xen-enabled one. In answer to your "Please read the documentation before writing bugs", which documentation did you have in mind? If a kernel package is going to install itself and fail to boot, or require special massaging to be made to work, I'd expect this to be mentioned in /usr/share/doc/linux-image-2.6.26-1-xen-amd64 even if that just told me to install a kernel documentation package. Dave -- Dave Page <[EMAIL PROTECTED]> Jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
