Every political position should just be done by a Blåhaj.

My Blåhajar: Definitely not Hitlers, and also of course alive.

With the stock installer? Not really. However, technically the installer itself is a very, very minimal windows. Just open up a cmd (with Ctrl + F12 or smth I believe) and you can open notepad from there, meaning you have a graphical file “manager”. And from there you can do things such as executing BIOS installers, which will actually work - even though the WM looks pretty weird, you will be able to use very simple programs just fine - such as cmd, or the Intel BIOS installer.

Windows does not really have a version afaik, so I just update it every few months. Debian live is just for visually editing/moving partition in complex setups, and I can fix my Arch install with an installer/live iso that’s months old. It’s just that I don’t want multiple USB-Sticks, and need multiple ISOs at the same time (eg. Arch and debian live for rescuing my installs, or Win 10/11 for new Installs for more tech illiterate people - Win 10 is the “just functions” thing for my father, when we need a laptop for proprietary laptops, and 11 is for other people who need something set up. Additionally, I use Windows’ installer environment to update my Laptops, servers and workstations BIOS.)

Different Linux distros and Windows. Because I regularly need them.

NVidia borks my installation sometimes. Then my stupidity to choose the non-dkms beta driver from the AUR. But all in all, my non-NVidia-devices (server, workstation and laptop) run fine on arch testing, updated every time I use one of those devices.

Well in the time until Windows rebooted 15 times Windows 12 will be out.

Even that looks and probably IS better than Windows is, was, or ever will be.

Sounds like Windows.

Ich bin gelegentlich noch dabei, neue Dienste aufzusetzen, eine geteilte Ablage für alle Geräte in meinem Netzwerk hin zu bekommen, sobald wir Glasfaser bekommen und ich meinen Zweitwohnsitz in Frankfurt habe muss ich dann sämtliche Netzwerke umgestalten:

• Ein Servierer zu Hause, ein mal im Koaxialbasierten Netzwerk (1 GB hoch, 50 MB runter) meines Vaters, an der alten Fritz!Box 6660 Kabel, sowie meinem eigenen Glasfaser Netzwerk (1 GB hoch, 500 MB runter) , der Servierer dient als Brücke dazwischen.
• Ein Servierer in Frankfurt an meinem Koaxialnetzwerk (1 GB runter, 50 MB hoch). Die beiden Servierer sind baugleich und mit Kabelwache verbunden, sodass ich auf alles gegenseitig zugreifen kann. Die Servierer sind dabei für die Zurückhochs zuständig.

Also mein Bogen funktioniert einfach. Nach ein bisschen Konfiguration ist es auch Benutzer Tauglich. Und das dauert nicht mal länger, als Fenster ein zu richten und den unnötigen Krempel runter zu schmeißen. Andere wert geschätzte Nutzer wie @Peter_Arbeitslos@feddit.org werden dir dabei helfen.

Typisch Deutscher.

but.punctuationwouldntbefun!!!

So Meet/Hangout does not work on Firefox at all? (In case the zero users who use Meet/Hangout see this)

Windows 10, but before Windows 11 was even leaked I believe.

It’s a Dell Latitude 5420, with a Broadcom Corp. 58200. Per https://wiki.archlinux.org/title/Laptop/Dell#Latitude, the 5420 is supported with libfprint-2-tod1-broadcom. And of course, I use Arch btw.

The local backups are done hourly, and incrementally. They hold 2+ weeks of backups, which means I can roll back versions of packages easily, as the normal package cache is cleaned regularly. They also prevent losing individual files accidentally through weird behaviour of apps, or me.

The backups to my workstation are also done hourly, 15 minutes shifted for every device, and also incrementally. They protect against the device itself breaking, ransomware or some rouge program rm -rf’inf /, which would affect local backups too (as they’re mounted in /backups, but those are mainly for providing a file history as I said.)

As most drives are slower than the 1 Gbps ethernet, the local backups are just more convenient to access and use than the one on my workstation, but otherwise exactly the same.

The .tar.xz’d backups are actual backups, considering they are not easily accessible, and need to be unpacked and externally stored.

I didn’t measure the speeds of a normal SSD vs the raid - but it feels faster. Not a valid argument, of course. But in any way, I want to use it as Raid 0/Unraided for more storage space, so I can have 2 weeks of backups instead of 5 days (considering it always keeps space for 2 backups, I would have 200- GB of space instead of 700+).

The latest hourly backup is 1.3 GB in size, but if an application is used which has a single, big DB that can quickly shoot up to dozens of GB - relatively big for a homeserver hosting primarily my own stuff + a few things for my father. Like synapses’ DB has 20 GB alone. On an uneventful day, that would be 31 GB. With several updates done, which means dozens of new packages in cache, that could grow to 70+GB.

Like nearly all drivers lol

Drivers I needed to pay special attention to:

• NVidia (we all know the official stance on that topic)
• e1000e needs patching because my Laptops NIC somehow reports the wrong NVM checksum
• Some obscure chinese “USB to DVI-D” adapter
• The fingerprint sensor in my Laptop, as it’s still experimental

If it fails, I will just throw in a new SSD and redo the backup. I sometimes delete everything and redo it anyway, for various reasons. In any case, I usually have all copies of all files on the original drive, as local backup on the device and backup on the workstation. And even if those three should fail - which I will immediately know, due to monitoring the systemd job - I still have daily backups on two different, global hosters as well as the seperate NAS. The only case in which all full backups would be affected would be a global destruction of all electronics due to solar storms or a general destruction of earth, in which case that’s the least of my problems. And in case the house burns down, and I only have the daily backups, potentially losing 24 hours of data, that’s also the least of my problems. Yes, generally using Raid 5 for backups is better, but in my case I have multiple copies of the same data at all times, surpassing the 321 rule (by far - 622, and soon 623). As all of my devices are connected via Gigabit, getting backups from eg. the workstation after the PC (with backups) died is just as fast as getting backups from the local PC backup Raid itself. And using Raid 0 is better (in speeds) than just slapping them together in series.

Because that’s what Raid 0 for, basically adding together storage space with faster reads and writes. The local backups are basically just to have earlier versions of (system) files, incrementally every hour, for reference or restoring. In case something goes wrong with the main root NVMe and a backup SSD at the same time (eg. trojan wiping everything), I still have exactly the same backups on my “workstation” (beefier server), on also a RAID 0 of 3 1 TB HDDs. And in case the house burns down or something, there are still daily full backups on Google Cloud and Hetzner.