On 11/24/2014 12:28:14 PM, Niels Thykier wrote:
> On 2014-11-24 16:00, Karl O. Pinc wrote:
> > On 11/24/2014 07:31:19 AM, Karl O. Pinc wrote:
> >> Attached is a patch that a) simplifies the language by cutting
> >> out words. b) adds a little additional explanation.
> >
> > I've not tried the documented upgrade process
> > (https://www.debian.org/releases/jessie/amd64/release-notes/ch-
> upgrading.en.html#newkernel)
> > but I
> > believe there's a serious problem here having to
> > do with recommending that a purge takes place
> > _before_ system reboot.
> >
> > 1st, the old kernel, although upgraded, will still
> > (AFICT) be running. Trying to purge a running kernel
> > is ungood. The purge of the kernel must be delayed
> > until after reboot.
> I am not particular concerned with the kernel. Due the to check you
> mentioned yourself, you have to manually approve of removing the
> running
> kernel. If the user removes the running kernel, it is not like
> purging
> it will make it much worse.
FYI: Removing the running kernel does not remove anything from
/boot. Purging does.
> That said, we could move this to a "pre-upgrade" text. From my point
> of
> view, the primary idea with this, is to ensure that people do not
> have
> old broken init.d scripts lying around on the system (that breaks the
> boot).
Pre-upgrade would work, to address your concerns.
But I also
think there should be a note to purge in post-upgrade (per
the original bug request). Post-upgrade is when somebody's
likely to be most familiar with what's being purged, rather
than years later when it's time for the next upgrade.
Jessie is sort of a special case since the boot system changes.
After jessie you might not need to purge pre-upgrade.
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
