Bug#338371: What is wrong?

[John Plate]

Jason Thomas wrote:

> > The problem is that, fx after installation, you have entries that
> > can boot the system.
> 
> What,
> 
> So after you install the system it is working fine.

After installing the system, it works fine.
 
> > If #kopt is changed and a homecompiled kernel is installed
> > (kernel-package) and removed (dpkg --purge) then the original entries
> > are changed according to the new #kopt setting.
> 
> Thats what its suppose todo.
> 
> > Then the system may become impossible to boot.

As said, after installing, raid-1 is installed. For future kernels,
the raid drive (/dev/md0 in my case) is the one to use. Then the "#
kopt" is set according to that. 

A new kernel (equal to the installed official image) is installed -
and de-installed. Then grub has changed the original settings for the
first kernel installed. The one that should be used as rescue kernel.

After the changes (the # kopt setting), nothing works. 

What I say is, grub should ONLY change what it installs and
de-installs. 

> > If you 1) install the official way, 2) install raid (as this is not
> > possible with my system because of other bugs) 3) compile a kernel the
> > official way and de-install the new kernel, the system cannot boot.
> > 
> > This must be a bug. Settings should reflect changes to menu.lst - NOT
> > old entries. Apparently grub mess up the entries in menu.lst. 

John