Re: why is a reboot needed before upgrading?

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

 



On Sat Apr26'25 10:05:22AM, Doug Herr wrote:
> From: Doug Herr <fedoraproject.org@xxxxxxxxxxx>
> Date: Sat, 26 Apr 2025 10:05:22 -0700
> To: Fedora Users <users@xxxxxxxxxxxxxxxxxxxxxxx>
> Reply-To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: why is a reboot needed before upgrading?
> 
> On Sat, Apr 26, 2025, at 7:53 AM, Marco Moock wrote:
> > If you are running an outdated kernel, you should reboot the current one
> > to be able to properly remove the old kernel during the upgrade.
> 
> Just to clear this up...
> 
> I think this is not actually correct (maybe part of the issue Ranjan was having).
>

Right, what you say below was my question.

> 
> The upgrade is done "offline", meaning that it is done early in a reboot. So...
> 
> 1. Run for days or weeks.
> 2. Do a regular update which adds a new kernel.
> 3. Do your Fedora version update without bothering to reboot.
> 4. Last step of that upgrade (before it applies the packages) is a "special" reboot.
> 
> The reboot that is used to get to the "offline" state where it applies the packages will actually use that new kernel that you installed in step 2. So it should then be able to remove your oldest kernel during the process.
> 
> The trouble is that you had not rebooted to verify that that new kernel actually runs on your system. If it does not then you might have a failure during the upgrade reboot.
> 
> Bottom line is back to the simple "best practice" of getting to a fully updated and *reboot* tested state before you do a full version upgrade.
> -- 

Thanks very much for this response and clarification! I decided to reboot before the upgrade just in case.

However, since I use an X-server (slim for login and openbox for WM), my upgrade resulted in a broken system (unable to get a login screen or a text console). So I went back to F41 for now in order to first investigate the problem. 

Best wishes,
Ranjan


> _______________________________________________
> 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
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- 
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[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