Generally no. There are some parts of your system that you will have to reboot for (like the kernel). But apps? Installing a new service?
No.
Most systems you just install the app you want, and run it.
There are some immutable distros the require things that are installed as part of the base system to only be available after a reboot, but they provide ways to install things without making it a part of the base system. Thus no reboot required.
Both Windows and Linux are able to reload parts of their kernel without needing to reboot. It’s still suggested, but as long as the software doesn’t actually force you to you can just say “reboot later” then just start the program like normal.
gives me the idea that its likely safer to just do a proper reboot, if your alternative is kernel patching or loading a completely different kernel.
Plus, its likely that not every single bit of firmware running on your devices support live patching. Thus you will be rebooting eventually, unless you are fine with avoiding the updates.
I’ve run into probably half a dozen applications that request a reboot before installation, even if you just rebooted and the launcher was the first thing you ran.
Usually older and very niche software. Business shit from the AS400 era, medical applications (including modern), not generally your standard stuff most people are installing.
Ah, I was thinking that with anything modern I haven’t had that. Kernel needs a reboot, services can be restarted and apps just chug along until you restart them yourself
Is what necessary?
Reboot to install software?
Generally no. There are some parts of your system that you will have to reboot for (like the kernel). But apps? Installing a new service?
No.
Most systems you just install the app you want, and run it.
There are some immutable distros the require things that are installed as part of the base system to only be available after a reboot, but they provide ways to install things without making it a part of the base system. Thus no reboot required.
Both Windows and Linux are able to reload parts of their kernel without needing to reboot. It’s still suggested, but as long as the software doesn’t actually force you to you can just say “reboot later” then just start the program like normal.
Yes. Using kexec.
Though this is irrelevant for majority of users: I’ve never seen it as the default.
That +
gives me the idea that its likely safer to just do a proper reboot, if your alternative is kernel patching or loading a completely different kernel.
Plus, its likely that not every single bit of firmware running on your devices support live patching. Thus you will be rebooting eventually, unless you are fine with avoiding the updates.
In some cases, yes.
I’ve run into probably half a dozen applications that request a reboot before installation, even if you just rebooted and the launcher was the first thing you ran.
Usually older and very niche software. Business shit from the AS400 era, medical applications (including modern), not generally your standard stuff most people are installing.
Ah, I was thinking that with anything modern I haven’t had that. Kernel needs a reboot, services can be restarted and apps just chug along until you restart them yourself