I think it tends to be easier to tell the user to reboot than to log out and back in again. Or even "killall nautilus". I generally just get my parents to reboot - they're more familiar with that process.
As for kernel upgrades, I'd review the changelog and see if the issues fixed affect you. e.g. if it's an NFS vulernerability patch and you use NFS then it's worth rebooting. If you don't then probably not worth it. If it's a local exploit and you trust everyone with physical access to the computer then don't bother... Play it by ear basically. Benjie. On 9 May 2011 09:12, john lewis <johnle...@hantslug.org.uk> wrote: > Running Debian sid means the I get fairly frequent kernel updates, > mostly 'point' upgrades. > > I'm reluctant to reboot un-necessarily but do reboot when it is a major > change (like when it went from 2.6.37 to 2.6.38) but should I also > reboot on the more minor upgrades? > > Incidentally I was surprised a few days back to have a message pop up > telling me I needed to reboot to complete a software update. No idea > what that was about and I ignored it ;-) > > -- > John Lewis > using Debian sid > > -- > Please post to: Hampshire@mailman.lug.org.uk > Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire > LUG URL: http://www.hantslug.org.uk > -------------------------------------------------------------- >
-- Please post to: Hampshire@mailman.lug.org.uk Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire LUG URL: http://www.hantslug.org.uk --------------------------------------------------------------
