On Fri, Nov 20 2009, Alan BRASLAU wrote:
> The tone of this exchange is not being constructive.
Yup. And also there is nothing left to be constructuve about,
this is now an old fashioned flame, with all even remotely relevant
issues resolved.
> I must strongly object to your defensiven
The tone of this exchange is not being constructive.
I must strongly object to your defensiveness and empty moralization.
It appears that you do not understand users.
On Friday 20 November 2009 15:59:29 sriva...@acm.org wrote:
> > I repeat, I am not doing anything "non-standard":
> >
> > $ cp /
> 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
kerne
On Friday 20 November 2009 08:15:34 sriva...@acm.org wrote:
>
> This is not really a critical bug. It is only triggered when
> the user asks for a XEN dom0 image, and is using grub2, and has not
> told grub2 to ignore vmlinux.
>
> In any case, 12.030 will not ship vmlinux unless
Alan BRASLAU writes:
> On Thursday 19 November 2009 23:55:43 Manoj Srivastava wrote:
> > Ou, Nov 19 2009, Alan BRASLAU wrote:
> > > kernel-package is now severly broken! Building and installing a[nd]
> > > new kernel image now results in *two* identical vmlinuz nodes with
> > > *identical* na
On Thursday 19 November 2009 23:55:43 Manoj Srivastava wrote:
> Ou, Nov 19 2009, Alan BRASLAU wrote:
> > kernel-package is now severly broken! Building and installing a[nd]
> > new kernel image now results in *two* identical vmlinuz nodes with
> > *identical* names under /boot. grub then rightly
Ou, Nov 19 2009, Alan BRASLAU wrote:
> kernel-package is now severly broken! Building and installing a[nd]
> new kernel image now results in *two* identical vmlinuz nodes with
> *identical* names under /boot. grub then rightly finds both images,
> *neither one which is bootable*.
I can
Package: kernel-package
Version: 12.028
Severity: normal
#556929
#556783
#551104
#556043
kernel-package is now severly broken!
Building and installing a new kernel image
now results in *two* identical vmlinuz nodes
with *identical* names under /boot.
grub then rightly finds both images,
*neither
8 matches
Mail list logo
