f00f/eris

It’s very new. Previously the system would just drop to a console with a message saying “Kernel panic: not syncing: [reason]” and a whole bunch of debug info.

But still, on a well-maintained system, that pretty much never happens. Mainly because Linux is significantly more resilient to faults in device drivers than Windows.

I’m against a megathread. That would be too busy and I think there will be more than enough to discuss about each episode.

For entirely selfish reasons, I’d like individual discussion threads for each episode that come out one or two a day, since that’s the pace I expect to be watching it (optimistically).

Though, I think the best option for everyone might be five-episode blocks. That would allow both bingewatchers and slower viewers to enjoy the conversation without spamming the feed, and will match up well enough with the “parts” it would have been split into if it aired on Nickelodeon that both broad and individual episode discussions will make sense.

The major tradeoff with zRAM is that programs are much more likely to crash due to running out of memory, but will run faster when memory is running low and freezes are less likely. You can think of it as offloading the pressure that traditional swap puts onto your disk, onto the (much faster) CPU. There will be an impact on CPU usage, but not enough to cause noticeable slowdown; in my experience running Linux, the CPU is almost never the reason something is slow, and is only going to be under significant pressure if you’re running a 3D game in software rendering, compiling a large program, or another complex CPU-bound task.

I wouldn’t recommend making the switch unless you often encounter system freezes or slowness while running tasks that use a lot of RAM (like web browsing on certain sites, or gaming), but it will improve things in that case.

You can install an antivirus, but you really don’t need to. Malware for Linux is rare, and malware that targets desktop Linux users is extremely rare (to the point that it’s a newsworthy story every time it does appear). Most distros have ClamAV and the frontend ClamTk in their repos, but it’s primarily used to scan servers for Windows malware before it reaches its intended target. Some Windows malware can still be harmful if run with Wine/Proton, but unless you’re downloading and running a lot of Windows software from unofficial sources (which you shouldn’t have any reason to) that won’t be a risk.

It’s not systemd’s fault, though systemd most often implements offline updates. The arguments for and against offline updates have nothing to do with systemd.

A lot of Linux distros, and graphical package managers like Discover and GNOME Software, are moving in that direction, under the argument that updating while online can cause disruptions to running software, in the worst case including the package manager itself (which can brick the system if it occurs in the middle of a critical update), and updates can’t be applied until the affected program (or the system, in case of critical components like the kernel) restarts anyway. Fedora Magazine explains the reasoning here: https://fedoramagazine.org/offline-updates-and-fedora-35/

In my personal experience though, I have never had an issue enabling automatic online updates on Debian Stable, and have had computers stay online for several months without any noticeable issues beyond Firefox restarting, so the risk is there but it’s pretty minor.