Debian admin here. Even Debian gets regular kernel upgrades that like a reboot afterwards. Security updates are more important than uptime. Also regular testing for clean recovery after a reboot is a must so a power outrage doesn’t bring any new surprises with it. Also test your backup restores regularly.
Novice homelaber here, is this just a case of apt update & upgrade or is there different commands for security and kernel updates? Also what’s your preferred backup/restore software? Thanks!
You should be reading the proposed changes before pushing yes. But regardless you can get stuck upgrading if you use only “upgrade” when dependences intentionally incompatibly change by package maintainers
Your note is very interesting about the difference between the commands and how autoremove will automatically remove stuff before or after the upgrade is performed. Should it always be done after, or are there instances when running it before is more beneficial? Is there any need to do both like this:
I can’t really imagine a benefit to --autoremove except for keeping old packages a bit longer before removing them.
Eg, if you run apt --update--autoremove upgrade -y once a day you’ll keep your prior-to-currently-running-version kernel packages a day longer than if you ran autoremove immediately after each upgrade.
To make things more confusing: the new-ish apt full-upgrade command seems to remove most of what apt autoremove wants to… but not quite everything. 🤷
Incredible that it’s not written everywhere, I always wanted to use something like this without the " update && upgrade" which looks like is not working oftentimes
Is it really not written? I saw apt upgrade --update and knew the standard shortcut would be -u, but that didn’t work so I tried -U, bingo bongo off I went.
It am quite sure in the manual, but if you just look on the interwebz tutorials every command line just writes the full shebang. So you don’t look up the manual and get flabbergasted when you see this post.
btw: if you are able to guess “what the standard shortcut would be”, you are a wizard Harry 🥳
I’m not the person you asked the question of. I’m a fellow novice homelaber.
I use Kopia to backup my data folders and Docker container data. Works really well. The project for this weekend is to set offsite backups to be uploaded to iDrive.
Yeah, people that brag about uptimes are just bragging about the fragility of their infrastructure. If designed correctly you should be able to patch and reboot infrastructure while application availability stays up.
I haven’t had a kernel update on Debian that triggered the “you should restart” message in quite some time. I was under the understanding that most newer systems now use splicing at the kernel level to not require periodic reboots.
Check for the existence of the for containing packages that recommend a reboot. Debian does not do live patching like Ubuntu does. Not least because updates to firmware are usually not applied until reboot. Also even if that were the case, regular checks for healthy reboots make sense.
Debian admin here. Even Debian gets regular kernel upgrades that like a reboot afterwards. Security updates are more important than uptime. Also regular testing for clean recovery after a reboot is a must so a power outrage doesn’t bring any new surprises with it. Also test your backup restores regularly.
Novice homelaber here, is this just a case of apt update & upgrade or is there different commands for security and kernel updates? Also what’s your preferred backup/restore software? Thanks!
Nope it’s just apt update & upgrade. Iirc apt tells you when the kernel was updated and needs a reboot as well.
Only if you installed the package
needrestartfull-upgrade probably a better pick
Is it? Afaik that also removes incompatible packages so if you’ve installed some custom stuff that might not be the best option.
You should be reading the proposed changes before pushing yes. But regardless you can get stuck upgrading if you use only “upgrade” when dependences intentionally incompatibly change by package maintainers
I think you can do
apt upgrade --updatenow.WHAT. Does this do both sudo apt update and sudo apt upgrade?
see also –autoremove
Your note is very interesting about the difference between the commands and how autoremove will automatically remove stuff before or after the upgrade is performed. Should it always be done after, or are there instances when running it before is more beneficial? Is there any need to do both like this:
# sudo apt --update --autoremove upgrade -y && sudo apt autoremove -yI can’t really imagine a benefit to
--autoremoveexcept for keeping old packages a bit longer before removing them.Eg, if you run
apt --update --autoremove upgrade -yonce a day you’ll keep your prior-to-currently-running-version kernel packages a day longer than if you ranautoremoveimmediately after each upgrade.To make things more confusing: the new-ish
apt full-upgradecommand seems to remove most of whatapt autoremovewants to… but not quite everything. 🤷I think so. I read it a few months back, but I don’t use any apt based systems to check on.
Yup
🤯
‘apt upgrade -U’
Incredible that it’s not written everywhere, I always wanted to use something like this without the " update && upgrade" which looks like is not working oftentimes
Is it really not written? I saw apt upgrade --update and knew the standard shortcut would be -u, but that didn’t work so I tried -U, bingo bongo off I went.
It am quite sure in the manual, but if you just look on the interwebz tutorials every command line just writes the full shebang. So you don’t look up the manual and get flabbergasted when you see this post. btw: if you are able to guess “what the standard shortcut would be”, you are a wizard Harry 🥳
Kernel updates are usually held back and need to be selected manually. E.g. apt-get install linux-image-amd64.
I prefer rsync for private backups and employ bareos in my company for all servers.
I’m not the person you asked the question of. I’m a fellow novice homelaber.
I use Kopia to backup my data folders and Docker container data. Works really well. The project for this weekend is to set offsite backups to be uploaded to iDrive.
When I update I use this:
sudo apt update && \ sudo apt upgrade -y && \ sudo apt full-upgrade -y && \ flatpak update -y 2>/dev/null; \ sudo apt autoremove -y && \ sudo apt autoclean && \ sudo journalctl --vacuum-time=7dYou can get rid of upgrade if you also use full-upgrade
As someone running a UPS on my ubuntu server, “uptime” represents the time since the last kernel release, and not much else.
Yeah, people that brag about uptimes are just bragging about the fragility of their infrastructure. If designed correctly you should be able to patch and reboot infrastructure while application availability stays up.
New fear unlocked.
The sun was angry that day, my friend…
Use kexec then
What do you use for backup restores ?
The same tools.
I haven’t had a kernel update on Debian that triggered the “you should restart” message in quite some time. I was under the understanding that most newer systems now use splicing at the kernel level to not require periodic reboots.
I haven’t seen it in a while either, but also, if there is a kernel update,
uname -salways returns the old kernel until a reboot.Check for the existence of the for containing packages that recommend a reboot. Debian does not do live patching like Ubuntu does. Not least because updates to firmware are usually not applied until reboot. Also even if that were the case, regular checks for healthy reboots make sense.
HOT SWAP!
https://www.youtube.com/watch?v=SYRlTISvjww