While technically the truth, it can be a hassle to make sure you restart all relevant services after updating a given library.

I just like being able to restart underlying system to take care of any possible straggler without thinking, and the services broadly be provided by multiple systems so the “experience” is starting up through a rolling reboot

Not sure what your signature is supposed to do here but now I have 3rd degree burns and a fireball has engulfed my office wall

My home generator is automatic but you still need an ups because the transfer switch and power on process for the generator isn’t instant. Takes like 10-30 seconds depending on how cold it is and how recently I serviced the generator.

You also ideally need a higher quality ups that can handle the shitty power coming from a generator, although the overall ups doesn’t need to be as “hefty” as a result. My ups is the kind that has extra filtering and stabilization of incoming power. My old ups was a cheaper cyberpower and it died after a few months of generator usage (we lose power here roughly every 4-6 weeks, thus the auto generator). The cheaper cyberpower would be fine in the majority of home circumstances tbh otherwise.

Pretty sure batteries can be set up for ups. One of the companies I worked for had part of the power for the building as ups. They used orange outlets to mark them. They constantly had to keep telling people not to overload it.

Battery should be automatic, but yeah not certain how quick the switchover is. At least you could go for the smallest capacity UPS there is as long as it can manage the wattage you are going with.

I have had minimal issues from my manjaro desktop but I just dont like it as much as my mint based systems because everything feels wrong and I can barely remember how to update my graphics drivers on manjaro vs mint where I am confident I could run my entire system mostly command line from installs to updates and random other shit that I just can’t remember how to do through arch systems because I dont run them as hard for some reason

A lot of windows errors are actually hardware acting up. Such as an aggressive overclock or random issues.

An operating system cannot prevent that

Also ‘fuck’

Those who manage the dedicated server racks service kept my stuff intact. Thankfully. Just disrupted my uptime.

[User “error” since, has cost me a TB of data. “Error”, fearquoted, because it was intentional… probably unnecessary clearing of space, partly regretted since.]

I don’t know how big the fire was, happened over 1000 miles away from here.

So, it really was fine. :3

The sun was angry that day, my friend…

The same tools.

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.

Nope it’s just apt update & upgrade. Iirc apt tells you when the kernel was updated and needs a reboot as well.

I think you can do apt upgrade --update now.

Borg

restic (thanks @Xylight@lemdro.id )

backrest (restic with WebUI)

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=7d

With an uptime of greater than 5 years I’m going to be concerned about the system potentially not coming back up after a reboot/power outage, especially for physical hardware

At a bank I worked at, we had an old IBM Power server which was at that point purely used for historical data. It had multiple years of uptime and was of course a good 10+ years old. When we went to take it offline, we actually just disabled the nic on the switch so we could reduce the number of powercycles it would see in fear that it would not power on anymore. Theoretically the data on it is purely historical, backed up and not needed, but there was enough question marks on each of those fronts we just played it safe

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.

I haven’t seen it in a while either, but also, if there is a kernel update, uname -s always returns the old kernel until a reboot.