well, I’m not sure traditional is the right word, multiseat has been used for a very long time. It used to be a bit better supported. The issue is that since the migration to wayland, it has become… a lot less supported. It is still possible, but most of the guides are x11 guides for a reason.
EDIT: I should say I hope seatd at some point could support multiseat but at the current time I don’t think it has any facilities to, systemd-logind / elogind do support multiseat, but I dont currently use them
Arch based distros are easy AF. I’ve been on Linux for 2 years, I’ve tried 10+ distros, and Arch has been the easiest for me, and stable as it gets, while allowing me to get the latest drivers needed for gaming.
I’ve been using Crystal Linux, but got tired of it’s CLI only package helper, and since then I’ve moved to Manjaro KDE.
Whatever you chose, make sure you get automatic BTRFS snapshots, so you can roll back at boot whenever you wreck it.
I’ve read here on Lemmy that NixOS is a great concept but the execution leaves a lot to be desired, stating that it’s overly complicated and documentation is lacking.
If you only care about stability then you should go with Debian. If instead you want something that limits you so that you can’t easily wreck it, you could use an immutable distro like Vanilla OS, Fedora Silverblue, BlendOS or Ubuntu Core Desktop.
Kernel boot logs aren’t well disciplined to be careful about what is an error or not. Sometimes it’s just checking for the existence of hardware and reports the error it gets if it doesn’t exist.
Did a search for ubuntu “integrity: problem loading x.509 certificate” and the first result indicates out of date bios certificates needed for secure boot on older laptops. Disabling secure boot seems to be the suggested fix.
You might check your BIOS clock time too, if the certs are ‘expired’, it might be the future, or more likely, the past. Certs have validity timers that specify start and end.
It’s more likely that your BIOS is just old, and you’ll have to keep secure boot disabled from now on.
First of all: Do you need reproductibility? I.e. having the exact same system on multiple machines? If not NixOS might be a lot more complex than what you need.
Secondly: Instability does not mean what you think it means. People read instability and think the system will break, when instability actually means your system will be updated. In the context of a server, an update can be destructive, for day-to-day users it’s very rarely so.
Finally: why Arch or Nix, why not Ubuntu, Mint, Pop or any of the other dozens of distros that are usually recommended for new users?
I was setting up the containers to fix a problem when using wine, but found a different solution. I checked the system status. 0 units failed and x.509 isn’t mentioned
I learned Dvorak. It was a painful four months going from chicken pecking a few words per minute to touch-typing. I would echo this advice. DO NOT pop the keys off and replace them. There are too many things baked into the BIOS or when you reinstall the OS, and you need to find the right key on a QWERTY layout.
I know it’s painful, but learn to type without looking at the keyboard. Print off a paper guide and place it below the monitor, and reference THAT when key hunting. Being able to touch-type is a serious superpower you will thank yourself for learning in the future.
Don’t do that, if you get used to looking at the keys you will never truly learn to touch type. It’s annoying for a couple of weeks to have the layout opened in a window until you’ve learned it, but the payback is great, I also use colemak and my current keyboard is all blanks anyways.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.