on software updates

[Casey Jao]

To clarify, I know that one can bypass the restart prompt by using dnf on
the command line. But my concerns pertained to the average user, who is
likely not familiar with the command line. And the average user when asked
to restart for *everything* (such as a browser update) might grow
increasingly inclined to keep postponing updates. That's what users were
conditioned to do on Windows, and it got so bad Microsoft started resorting
to extreme measures like forced reboots.

What's the expected time frame for the transition to sandboxed apps and
well-defined platforms? That seems like a major undertaking that will take
some time to mature. I'm just wondering whether anything can be or might be
done to improve the user experience in the interim.

On Sat, Jan 31, 2015 at 7:38 PM, Reindl Harald <h.reindl at thelounge.net>
wrote:

>
> Am 31.01.2015 um 22:57 schrieb Casey Jao:
>
>> Warning: long post ahead.
>>
>> Are there any plans to let packages specify that they do not require a
>> total system reboot to be updated?
>>
>> The other day, Gnome software prompted me to reboot just to update
>> google chrome. Given that nothing depends on chrome, and also that the
>> Linux version of chrome is specifically designed to tolerate having its
>> files on disk overwritten
>> (http://neugierig.org/software/chromium/notes/2011/08/zygote.html),
>> rebooting the whole system seems overkill to ensure a successful update
>>
>
> ignore all that GUI update crap and just use "yum upgrade"
> no need for reboot a linux system for every update
> that's not windows
>
> "lsof | grep DEL | grep /usr" will show you processes you may conisder to
> restart (and not the needs-restarting command was never relieable here)
>
>
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20150202/c04379b6/attachment.html>