I don't think (b) is a good idea for the following reasons :
* When the user shuts the PC down, he doesn't expect to give it attention
anymore. An update can fail or be interrupted for some reasons (package
missing on a server, internet connectivity broken, kernel upgrade asks if
the menu.lst sho
Scott Kitterman wrote:
>> Ted Gould has been a proponent of a system / hardware indicator, and
>> I've been working on how to handle things like USB-unmount and
>> Bluetooth-connect and am coming round to the idea. What do you guys
>> think? If there's support for the idea, we could do a round of d
I'm just catching up on this thread, and want to help draw it to a
conclusion.
Updates-on-login are interesting, but I think fatally flawed because of
the common requirement to reboot after updates.
Updates are an irritation and interruption at any time, we must accept
that. I've seen people say
3 matches
Mail list logo
