By multiseat, do you mean allowing two people to use your Linux PC at the same time, using a separate monitor and keyboard/mouse, as of they’re on a separate computer? You can do this without installing additional software, though you must configure the seat from command line:
Wayland seems to support multiseat but I can’t seem to find any documentation or tutorial save for an article on phoronix: www.phoronix.com/news/MTM4MzA
Is it possible to isolate applications per user?
Each user with have their own login session, so ther application processes should be separate from each other.
Regarding Wayland, looking at this it seems that it might be pretty straightforward but then for example sway seems to be defining seats a little bit different. So it might require some tinkering in the end, depending which compositor you decide to use.
Loginctl seems to be X/Wayland independent and useful in both.
From what I’ve found it seems that there are more questions on the internet regarding something not working well in multi-seat or needing a patch for that, than how to set the multi-seat up. Situations like this usually mean that setting this thing up is quite straightforward. It might also be a niche, though
I don’t know where you are from, and what laptop you are using, but as others have said: use keyboard stickers. Just search for „colemak dh stickers [your laptop model]“
You can run multiple X servers for a graphical multiseat setup. It’s a lot of work to set it up and most of the information about it is out of date though.
So essentially it’s running a single computer we if it were two seperate workstations?
I could see an implementation that’s similar to those running a VM with a DGPU for gaming. User A could run a login against the primary GPU and OS. User B could run a VM with several cores allocated and the secondary GPU dedicated to the VM. If any shared did file resources in the primary OS are needed, KVM has ways to do that as well.
Not entirely sure why this reply is being panned (was at -6 when I first saw it).
OP is in the process of upgrading their PC to a Ryzen 9. If we make the assumption that this Ryzen 9 is on the AM5 platform, the CPU comes equipped with an IGPU, meaning the RTX 3060s are no longer needed by the bare metal. So, installing a stable, minimal point release OS as a base would minimize resource utilization on the hardware side. This could be something like Debian Bookworm or Proxmox VE with the no-subscription repo enabled. There’s no need for the NVIDIA GPUs to be supported by the bare metal OS.
Once the base OS is installed, the VMs can be created, and the GPUs and peripherals can be passed through. This step effectively removes the devices from the host OS – they don’t show up in lsusb or lspci anymore – and “gives” them to the VMs when they start. You get pretty close to native performance with setups of this nature, to the point that users have set up Windows 10/11 VMs in this way to play Cyberpunk 2077 on RTX 4090s with all the eye candy, including ray reconstruction.
Downsides:
Three operating systems to maintain: bare metal, yours, and your partner’s.
Two sets of applications/games to maintain: yours and your partner’s.
May need to edit VM configs somewhat regularly to stay ahead of anti-cheat measures targeted at users of VMs.
Performance is not identical to bare metal, but is pretty close.
VM storage is isolated, so file sharing requires additional setup.
Upsides:
If you don’t know a lot about Linux, you’ll know a bunch more when you’re done with this.
Once you get the setup ironed out, it won’t need to change much going forward.
Each VM’s memory space is isolated, so applications won’t “step on each other” – that is, you can both run the same application or game simultaneously.
Each user can run their own distro, or even their own OS if they wish. You can run Fedora and your partner can run Mint, or even Windows if they really, really want to. This includes Windows 11 as you can pass an emulated TPM through to meet the hardware requirements.
Host OS can be managed via web interface (cockpit + cockpit-machines) or GUI application (virt-manager).
It’s not exactly what OP is looking for, but it’s definitely a valid approach to solving the problem.
I came to the comment section to recommend Proxmox or another hypervisor as well. If it was a system with just one GPU, I wouldn’t, as splitting it between two VMs can be difficult. But, most of the time having two GPUs under one OS can be a lot worse too though. I think it’s definitely the cleaner & easier way to go. One caveat I’ll add is that resources are more strictly assigned to each seat, so memory & cpu can’t be sent to who needs it more as readily. Another positive though is that it would be super simple to create a third VM with a small amount of resources for running a small self-hosted server of some kind on the same box.
I imagine that to be pretty difficult with laptop keyboards like a scissor switch. But after googling a bit there seem to be a few tutorials so maybe it’s easier than I think.
With some models it can be done, but they are delicate things and going over the whole keyboard will most likely result in a couple of broken mechanisms and/or missing hooks on keycaps.
I’d say there’s no need for that. If you’re switching to Colemak I assume you’re gonna learn how to touch type with it, at which point it really doesnt matter what the labels on the keys say. Most typing websites like monkeytype have a finger position visualization so even while learning you dont need to look at your keyboard.
Probably a good idea to look for a different client, call me tinfoil but I wouldn’t want to touch a very old mechanism that is supported/pushed by a very recognisable 3 letter agency
A surprising amount of services (including Azure last I tried) can only handle RSA keys, so after trying ecdsa only for a while I ended up adding a RSA key again.
With that said - it’s 2023, in almost all cases you should have your keys in a hardware module nowadays, in which case you’d use a different command for keygeneration.
Actually it is the same story with TLS 1.3 and TLS 1.2. A bunch of sites still doesn’t support TLS 1.3 (e. g. arstechnica.com, startpage.com) and some of them only support TLS 1.2 with RSA (e. g. startpage.com).
You can try this yourself in Firefox by disabling ciphers (search for security.ssl3 in about:config) or by setting the minimum TLS version to 1.3 (security.tls.version.min = 4 in about:config).
Strange enough TLS 1.3 still doesn’t support signed ed25519 certificates :| P‐256, NIST P‐384 or NIST P‐521 curves are known to be “backdoored” or having deliberately chosen mathematical weakness. I’m not an expert and just a noob security/selfhoster enthusiast but I don’t want to depend on curves made by NSA or other spy agencies !
I also wondering if the EU isn’t going to implement something similar with all their new spying laws currently discussed…
I don’t use those two flags, but have several pis running docker with no issues. They’ve been running (almost) 24/7/365 going on maybe 2 years now with the same sd cards.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.