Bug#338371: What is wrong?

[Jason Thomas]

On Thu, Nov 10, 2005 at 02:04:28PM +0100, John Plate wrote:
> Otavio Salvador wrote:
> 
> > I didn't understand what update-grub did wrong. kopt comment express
> > exactly what it intend to do and looks like it did its job.
> 
> 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.

> 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.

If you change kopt to something that is wrong it will not boot.
If you install the wrong kernel it will not boot either


kopt is where you put your `kernel options`, arguments that you want to
pass to the kernel. If you give the wrong ones it will not work.

"You" need to know what you are doing if you intend to change these
thing settings.

This is the same as if you want to change your fstab. If you put the
wrong info in there it won't mount the filesystem.

> 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