Comment 25 for bug 290024

hi,
       I have found the reason why I could not boot after using cruft
remover tool. The reason was this: I have made a custom boot menu and I
always use to keep the same old boot menu whenever a new kernel is being
installed( I am lazy to update my menu.lst as doing it will coz my windows
partition to go away and i have to again change the menu.lst (sorry)) but
when i use cruft it removed old kernel but my old kernel was linked to
menu.lst so I could not boot in. So what I feel a good solution is whenever
cruft is used to remove old kernel it should check whether the menu.lst is
referring the old kernel or not. if it is referring old kernel then it
should inform the user that they should update the menu.lst or can it
automatically update the menu.lst if user enters no then it should not
remove the kernel.

On Tue, Nov 25, 2008 at 7:32 AM, Tux <email address hidden> wrote:

> Ok, thanks for the explanation. I'll continue to test. If I can help
> in any way, let me know.
>
> Tux
>
> 2008/11/25 Lars Wirzenius <email address hidden>:
> > Tux,
> >
> > about leaving configuration files when removing packages: I decided that
> > it is not safe to remove the configuration files automatically, since
> > they can contain important data if they have been modified. However,
> > because of time pressure from the intrepid release, I did not want to
> > incorporate a subsystem that lets the user see what has been modified.
> > This will be dealt with in the future, however, since, yes, removed but
> > un-purged packages are cruft.
> >
> > --
> > Cruft Remover removed most of the installed packages
> > https://bugs.launchpad.net/bugs/290024
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> Cruft Remover removed most of the installed packages
> https://bugs.launchpad.net/bugs/290024
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
~Srikalyan.