this question might sound silly, and another user answered it to me already, but I wanted to ask more people because offline-upgrade seems a bit less popular, so perhaps someone knows.
anyway, after I finished with offline upgrades (restarted and installed everything), and I just wanna install some new apps, do I install them with the regular dnf install package, or is there also some sort of offline method for package installation?
To add new packages use dnf install as that will not effect already installed and running apps.
The advantage of the offline update is that running apps will not be affected. Some may crash during an update in the worst case.
you mean, during a non-offline update?
Potentially yes.
However, I have used ādnf upgradeā for many years with the system fully operational and have seldom encountered disturbances of running apps.
I tend to do the upgrade then reboot after the upgrade completes.
YMMV
The suggestion has been to do offline upgrades for anything where the app being upgraded is one that is already open and operating.
Yes online update can run into issues.
There are apps, for example, that dynamically load libraries at runtime.
The app may crash if it dynamically loads a new library version.
But this is a rare situation.
Personal I do on-line updates, but not while logged into a desktop for this reason.
I was upgrading and restarting right away too. But still. Somehow, just about 2 weeks after install, my Fedora got a lot slower, laggier, and started having freezes. I reinstalled it yesterday and now itās so much faster and has no lags (yet). Iām so confused as to why it was problematic earlier. I had several possible guesses, including the fact that I wasnāt using offline-upgradeā¦ I was thinking, it could be my old damaged drive, which showed errors on a SMART scan (even though the overal assestment was āOKā), but then why would a new install on the same drive be so fast and not have any issues?
I donāt know, I guess Iāll see how things go, and if it repeats, Iāll probably create a separate post about it, asking for help.
That is a huge hint not to trust the drive after you backup your data.
My guess is that it slowed down when it read from failing parts of the disk.
By reinstalling you will have avoided the parts of the disk that went bad.
But expect to see the problem come back.
Suggest you get a new disk.
I would, if there was am opportunity. Oh well. For now Iāll hope itāll be fine.
A damaged file system (drive) can cause dramatic problems with speed. The system reads the data, finds there is an error then is forced to read it again and again until it finally gets a good copy.
Smart showing errors is a giant red flag telling you to stop trusting that drive and replace it as quickly as possible.
I understand that there are reasons that replacing hardware can be difficult.
But you cannot fix hardware with hope or software.
Wishing you luck!
Old hard drives often have problems reading certain sectors because mechanical wear and tear affects the predictability of head positioning. As a result, it may take multiple attempts to read the sector, which users see as a slowdown. A reinstall uses the āwornā head location, so the drive performs properly at first, but will fail soon. My experience with hard drives in the past decade is that manufacturing tolerances have reached the point that a heavily used drive will fail shortly after the warranty expires (lightly used drives can last much longer).