Gitea or forgejo, for hosting your repo and managing access rights. WoodpeckerCI when you eventually need a CI/CD. (Is a fork of DroneCI and integrates nicely with gitea.)
ChojinDSL
joined 1 year ago
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.
"don't cross illegally"... If only the first settlers to America would have followed that rule.
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.
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.
Check out dattobd sometime. It's a tool that allows you to make a snapshot of a block device for backups, while the OS is running. Useful if your filesystem doesn't support snapshots.