Update manager mandating rebooting

[Jordon Bedwell]

On Wed, Oct 31, 2012 at 12:00 PM, Daniel J Blueman <daniel at quora.org> wrote:
> I was thinking along the lines of we have something in the indicator area to
> avoid forgetting to reboot. Point is, it's almost certainly not a convenient
> time to reboot after you just opened up to get something actually done and
> update manager scans in the background and find updates.

There is already something in the indicator that indicates a restart
is needed, your gear icon will turn red and warn you that you need to
restart, it does that for me even though I refuse to use update
manager (I'm old, and always in the terminal, I like my apt cookies
daily.)  When you click the gear icon it also says a restart or reboot
is needed.

> Of course, Debian derivatives relaunch background services. A desktop
> notification should be present to notify the user that a logout _or_ reboot
> is needed. There's just no need to reboot unless upstart is vulnerable (and
> then it doesn't publish services on the network).

That's a subjective point of view, if libssl is vulnerable or the
kernel is vulnerable you need to restart too, not because you can't
restart services or use a rolling Kernel (read KSplice) but because
there are multiple ways to look at it, from my perspective a login and
logout is just as fast as a reboot (because reboot requires less steps
for me since again I'm already in my terminal and my laptop boots at
blazing speeds.)  I would much rather reboot than trust a system that
assumes it knows every possible service that could be using a
vulnerable lib reliably and reboot them.  It's easier that way. Easy
is good but easy shouldn't be annoying like what you describe happens
with update manager when you update >.>