ChojinDSL

How about no, and not generate any views and possible revenue for that garbage?

You could setup imapsync and sync your Gmail to a self hosted IMAP server and just never delete your mails.

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.

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.)

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.

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 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/[email protected]/

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.

Mailcow allows users to setup their own aliases similar to gmail with a “+” delimiter. E.g. [email protected].

As much as I would love to see that, I seriously doubt that orange buffoon will ever see the inside of a jail cell. The republicans will find some bullshit loophole or game the system, like they always do.

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.

That’s quite the lamest clickbait attempt I’ve come across in a while.

PC Games.

UPS with usb allows you to configure a script to properly shutdown your server when a power outage happens and the UPS battery is about to run out.

Sure, somebody has to keep an eye on AI. (Pun intended).

Nimm einen zweiten PC, z.b. Laptop und log dich per SSH ein und folge dem syslog, also z.b. mit “journalctl -f” Und lass das so laufen und benutze deinen Deskop PC bis er sich wieder aufhängt. Mit etwas Glück bekommst du vielleicht irgendeine interessante Fehlernachricht zurück. Ausserdem wäre interessant ob du bei einem aufhänger, dich noch per SSH verbinden kannst zu der Kiste oder nicht. Wenn z.b. per ssh noch alles geht, aber der Desktop nicht reagiert dann grenzt es das ganze schonmal etwas ein.

Wenn du meinst dein Laptop hat die exact gleiche Konfiguration, was heisst das genau? Dein desktop hat sicherlich keine mobile CPU oder GPU, das heisst da sind schonmal unterschiede.

Tritt das Problem immer erst nach einer gewissen Zeit auf? Oder manchmal schon direkt nach dem start?

Die tatsache das nachdem du einen KDE spin booten wolltest, nur ein schwarzer Bildschirm kam, lässt mich auf die GPU schliessen. Falls die Fehlerhaft ist, kann es ziemlich schwierig sein das zu debuggen, vor allem wen der Fehler nicht konstant reproduzierbar ist.

Also strom probleme können ihre spuren hinterlassen. Da muss es nicht heissen das das OS davon betroffen ist, sonder im schlimmsten Fall die Hardware. Das genau zu identifizieren kann z.b. schwierig sein. (Instabile Lötstelle, defekter Resistor, etc…)

OS Neuinstallieren kann man machen, aber ich würde eher mal verschiedene LiveUSB distros ausprobieren und die mal nen Tag lang laufen lassen und sehen ob das Problem auch da auftritt.

Bleibt die Kiste laufen, wenn du sie nicht benutzt? Also im idle Betrieb, oder hängt es sich da auch auf?

Mit motherboards ist das so ne Sache. Die können manchmal ziemlich zickig sein, je nach Hersteller und Firmware version. Egal ob übertaktet oder nicht, oder auch wenn alles auf default settings ist. Von BIOS bugs mal ganz zu schweigen. Ein guter Ansatz ist hier, das man z.b. alle strom sparsachen abstellt. Sowohl im BIOS als auch in Linux selber. Bluetooth, WLan und Netzwerk chips können da manchmal auch zickig sein. Ansonsten kannste probieren alle unnötige onboard hardware im bios zu deaktivieren. Also z.b. wlan, bluetooth, etc…

SSDs und NVMEs funktionieren oft einwandfrei bis sie es plötzlich nicht mehr tun. Da hilft auch S.M.A.R.T. nicht viel weiter, weil man oft keine vorwarnung bekommt. Bei rotierenden Platten schon eher.

Ich nehme mal an deine CPU und Motherboard hat keine onboard grafikkarte? Eventuell wäre das auch eine Möglichkeit. Praktisch die dedizierte GPU auszubauen, und nur mit der lahmen onboard karte zu testen.

Was du auch probieren kannst ist linux auf der maschine im reinen konsolen modus zu betreiben und dann z.b. einen vnc server darauf starten und vom laptop aus gewisse graphische desktop applikation auszuprobieren. Dann kannst du z.b. die GPU als fehlerquelle ausschliessen.

Im Prinzip ist das grösste Problem hier, alle möglichen unbekannten Variablen. “Liegts vielleicht an …?” Gehe systematisch vor, damit du eins nach dem anderen ausschliessen kannst. Eventuell auch protokollieren unter welchen Umständen das Problem auftritt. Wie lang lief die Kiste etwa, was hatte ich grad alles offen, usw…