Bug#395086: closed by maximilian attems <maks@sternwelten.at> (Re: Bug#395086: linux-image-2.6.18-1-686: disable suspend to disk on install)
On Wed, Oct 25, 2006 at 09:39:13AM +0200, maximilian attems <maks@sternwelten.at> wrote:
> reassign 395086 kernel-package
> retitle 395086 disable swsusp on new linux-image install
> stop
>
> On Wed, Oct 25, 2006 at 08:36:38AM +0200, Mike Hommey wrote:
> >
> > > On Tue, Oct 24, 2006 at 08:41:38PM +0200, Mike Hommey wrote:
> > > >
> > > > When installing a new kernel over the currently running one, and suspend to
> > > > disk is enabled, the system will fail to resume with the newer kernel at
> > > > resuming time. It would be safer if it was impossible to suspend to disk then.
> > > > I guess setting some value to /sys/power/resume would do the trick.
> > >
> > > this an userspace problem.
> >
> > And ? The kernel package has a check to warn the user he is installing
> > the same kernel as the currently running one. It could disable suspend
> > to disk at the same time. This *is* a kernel package problem.
>
> kernel-package != linux-image
I'm happy to learn the linux-image packages are now built with
kernel-package, which everyone should know, apparently, considering the
way you answered originally. Could you try to be helpful instead of
trying to get rid of bugs ?
> > Are you closing every non-debian-specific bugs ? do you know there is an
> > upstream tag for non-debian-specific bugs ?
>
> no need to cluter the debian bts with useless bugs hanging around,
> reassigned your bug report.
I'm happy to learn that bugs that may help users are useless. By the
way, the issue I was talking about is more about some black magic
between lilo/grub, the kernel, and distro-specific scripts, than
something that need to be discussed on lkml. But you're maybe just
trying to get rid of bugs by any means
Mike
Reply to: