ChojinDSL

If the immutability in OS is well designed, then there shouldn’t be really an downsides or loss in comfort. That is, unless you’re a linux expert and like to tinker under the hood.

The general idea is, the core of the OS if read-only, and everything else that needs to be modified is mounted writeable. Ideally, protecting the core of the OS from writes, should for example prevent malware from installing a modified kernel or boot loader. Or maybe preventing the user from accidentally borking something so that their system becomes unbootable. How much of an advantage that is practice is dependent on use case. In the case of Steam OS on the steam deck, it’s perfect, since boot issues on the steam deck could potentially be tricky to fix as opposed to a standard PC.

Another advantage of immutable could theoretically be wear and tear of certain storage devices. e.g. Think of a raspberry PI and SDcards. If you could have most of the important stuff of the OS as read only on the SD card, and everything else on a usb disk or even an NFS mount, then the SD card should last much longer since no writes are happening on it.

As far as true security benefit is concerned… I can’t really say. It depends on how updates and eventual writes are actually handled to the immutable part of the OS. Obviously at some point, changes do happen. Like during a system update. In the case of Steam OS, The system portion is wiped and replaced the new version. Chimera OS, did something similar (I don’t know if they still use the same method). They had a read-only BTRFS partition, where they would then provide a new snapshot during an update, which would be downloaded and applied at the next reboot. This approach would hinder automated crypto malware for example (at least for system files).

Immutable in this context refers to an OS that can’t be changed while running. Steam deck does something like that. Basically the all of the OS system files are read only, so that the user or some malware can’t Bork the system. The only parts that are writable are the users profile directory and the logs.

You can still receive updates and install apps. It’s just that that’s handled a bit differently than with a standard OS.

E.g. it could be that the OS provider only issues complete updates, and then you either have to reboot. This is the case with steam os on the steam deck. The System portion of the OS is mounted read only during use.

I’d say PS2. The sheer amount of unforgettable classics and the fact that it was the best selling console of all time.

How about a quick summary. TL:DW?

Does anyone know if there is a way to use mythtv as a TV backend for jellyfin?

I used it back in the day when I still had analog Cable TV and a digital capture card. MythTV was a pain in the ass to setup. The UI was horrible and if you were trying to setup satellite, it could get really complicated if you didn’t know what you were doing.

That being said, MythTV is probably hands down the best digital recorder I’ve ever used. Like for LiveTV it sucks, because channel switching takes ages until it’s built a recording buffer. This might be less of an issue on SSDs now, like I said I haven’t used in ages. But MythTV had some of the best features in terms of scheduling recordings, avoiding conflicts and skipping commercials.

Once I started using MythTV, I stopped watching live TV entirely. Since I simply just recorded stuff I was interested in.

I’ve used MythTV, TVheadend and NextPVR. MythTV has the best recording features. TVheadend in combination with Kodi has the fastest channel switching, which is great if you just want to channel hop. NextPVR is decent and IMHO the easiest to setup out of the three. But is lacking in certain areas.

Not a place in particular, but if you’re driving, avoid any border crossings during peak holiday seasons. Specifically when you’re crossing from the EU into non-EU countries or crossing from Schengen into non-Schengen area. During peak times you might be waiting at the border for hours.

What if they ask him to bring watermelon and chicken to the cookout? ;-)

Not really with mdadm raid5. But it sounds like you like to live dangerously. You could always go the BTRFS route. Yeah, I know BTRFS Raid56 “will eat your data”, but you said it’s nothing that important anyways. There are some things to keep in mind when running BTRFS in Raid5, e.g. scrub each disk individually, use Raid1c3 for metadata for example.

But basically, BTRFS is one of the only filesystems that allows you to add disks of any size or number, and you can convert the profile on the fly, while in use. So in this case, you could format the new disk with BTRFS as a single disk. Copy over stuff from one of your other disks, then once that disk is empty, add it as a additional device to your existing BTRFS volume. Then do the same with the last disk. Once that is done, you can run a balance convert to convert the single profile into a raid5 data profile.

That being said, there are quite a few caveats to be aware of. Even though it’s improved a lot, BTRFS’s Raid56 implementation is still not recommended for production use. https://lore.kernel.org/linux-btrfs/20200627032414.GX10769@hungrycats.org/

Also, I would STRONGLY recommend against connecting disks via USB. USB HD adapters are notorious for causing all kinds of issues when used in any sort of advanced setup, apart from temporary single disk usage.

Stop fingering your mom. 😉 (Sorry, couldn’t resist)

Mailcow allows users to setup their own aliases similar to gmail with a “+” delimiter. E.g. username+randomalias@domain.com.

Nextcloud.

Windows, in the past has been known to sometimes overwrite the Linux boot loader after a windows update, so be careful with that, since windows assumes no other os exists in the universe. Depending on your windows version, it might not be a bad idea to backup the license key. Recent versions store your computer’s information in the cloud, so unless you change a lot of components, it should reinstall without much hassle. But it doesn’t hurt to extract the key just in case. Microsoft gonna Microsoft. There are tools for this. E.g. jellybean key finder (or something like that).

Depending on the distro, it might help to disable secure boot in the uefi bios.

That being said, take it one step at a time. Don’t try to recreate everything you were doing in windows right off the bat. Get comfortable with the desktop first. Try different apps for certain tasks. If you have an Nvidia GPU, the experience can vary greatly between different distros. As others have mentioned, most distros have a “live environment” on the installation cd, which you can test to see if your hardware is recognised straight away. That being said, don’t feel like you’re married to a specific distro. Most Linux users will distro hop quite a bit, before they settle on one that just feels right. And even then they might change again after a while, if they get bored.

If you don’t know, or aren’t sure. Backup everything if you have the space. Once you’ve hit a couple of disaster scenarios, it will become apparent what stuff is really important.

Obviously, the stuff you can’t recreate otherwise is most important. But apart from that, even the stuff you can recreate from other sources might be worth backing up because of time savings. E.g. faster to restore from backup than to recreate.

Back when I was still using Gentoo, configuring your own kernel was a rite of passage. It was kind of fun to try and configure it as minimalist as possible to cut down on the kernel compile time. Also, understanding all the different options and possibilities. And thanks to use flags, you had access to all these different patch sets for the kernel, which took a lot of the pain out of trying things like experimental schedulers or filesystems.

There is also the Hurd kernel, which has been in development for aeons.

Mislabeled files, not so much. Since there isn’t really a way to verify the content until it’s downloaded. You can adjust things like which file sizes are considered a certain quality, e.g. HD or 4k. But one approach could be that you define tags for release groups which you know and trust. And give those tags a higher score. This should lead to releases by those groups being preferred.

You can of course add multiple tags with positive and negative scores. For example I use tags to give a higher score to releases that have 5.1 audio, or which are non-hdr.

You can try to faff around with keywords and tags, e.g. give x264 or x265 a higher score rating, etc… As a failsafe you can configure a trashcan location and specify that all deleted files go there first and don’t get emptied for X amount of days.

Around 2003-2004. I was still a bit of a Linux noob, just getting to grips with Gentoo.

Had two no-name WiFi adapters that weren’t directly supported under Linux. Found some obscure forum thread that mentioned them, along with which lines in which source code driver to change to make these adapters work.

PC Games.