Re: reboot after upgrade? and best practice

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 20 Jul 2020 at 04:44, Samuel Sieb <samuel@xxxxxxxx> wrote:
On 7/19/20 9:21 PM, Anil Felipe Duggirala wrote:
> I would like to ask what is the best practice for upgrading (updating all packages, ie. "dnf upgrade") in my Fedora 32 Workstation. The Gnome Software graphical application provides a way for me to do this, but it can also be achieved in the command line. Do these two methods achieve exactly the same results? I would also like to plainly ask if in any occasion it is necessary or advisable to perform a system reboot after doing an "dnf upgrade". I have noticed that when the upgrade is performed with Gnome Software, a reboot is always performed after the upgrade.

If you reboot after the dnf upgrade then the results are the same.
Until then you will still be using old versions of libraries and old
version of applications until you restart them.  You can only use a new
kernel by rebooting.  Some applications like Firefox can get unhappy if
you upgrade while they're running and can crash or have strange behaviour.

Any application that makes extensive use of dynamically loaded libraries can
potentially run into trouble if it loads a recently upgraded library while still using 
older versions of other libraries.   The problems may not always be highly 
visible (e.g., silent corruption of a database) and if visible are likely to be 
interpreted as a "buggy" update and can generate nuisance bug reports 
and cause users to avoid updating. 

When you use Gnome Software to do the upgrade, the reboot is not after
the upgrade, the reboot is required to *do* the upgrade.  Only the
downloading of packages is done, then when you reboot, it will do the
upgrade, then reboot again into the updated system.

This method is the most robust way to ensure there are no problems
associated with updating.   It not only minimizes the chance of users
having problems with updates, it also reduces the workloads for the 
people who deal with bug reports.

--
George N. White III

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux