On Tue, 07 May 2013 15:37:46 +0100
Gordon Scott <gordon@???> wrote:
> On Tue, 2013-05-07 at 14:43 +0100, Lisi wrote:
> > and I was wondering why on earth we needed to reboot.*
> -----8<-----
> > *In case you are wondering, when I went up to the chap and asked,
> > the answer was "To check that everything is O.K."
>
> I _like_ to reboot sometime after an upgrade, to confirm that
> everything is indeed OK, but it's a preference not a need.
>
> That preference applies also to the kernel. The present kernel is
> working, the new one probably also will, there's likely no hurry.
Agreed, the latest kernel possibly/probably has stuff that will never
be needed if like me you don't have any fancy requirements
I don't remember ever having to do a reboot after an upgrade because a
package required it, perhaps Debian is better at doing this sort of
thing ;-)
the most common problems I get when upgrading are in building modules
for virtualbox as today:-
> Setting up linux-headers-3.8-1-common (3.8.11-1) ...
> Setting up linux-kbuild-3.8 (3.8.11-1) ...
> Setting up linux-headers-3.8-1-amd64 (3.8.11-1) ...
> Examining /etc/kernel/header_postinst.d.
> run-parts: executing /etc/kernel/header_postinst.d/dkms 3.8-1-amd64
> Error! Bad return status for module build on kernel: 3.8-1-amd64
> (x86_64)
> Consult /var/lib/dkms/virtualbox-guest/4.1.18/build/make.log for more
> information.
> Error! Bad return status for module build on kernel: 3.8-1-amd64
> (x86_64)
> Consult /var/lib/dkms/virtualbox/4.1.18/build/make.log for more
> information.
but as I don't intend (for now anyway) re-booting to use the new kernel
installed today (linux-image-3.8-1-amd64) I'm not going to worry about
not having modules for virtualbox-guest.
I rarely use virtualbox anyway ;-)
--
John Lewis
Debian & the GeneWeb genealogical data server
--
Please post to: Hampshire@???
Web Interface:
https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL:
http://www.hantslug.org.uk
--------------------------------------------------------------
