Tinkering is all fun and games, until it’s 4 am, your vision is blurry, and thinking straight becomes a non-option, or perhaps you just get overly confident, type something and press enter before considering the consequences of the command you’re about to execute… And then all you have is a kernel panic and one thought bouncing in your head: “damn, what did I expect to happen?”.
Nah, that’s when the fun really starts! ;)
The package refused to either work or install complaining that the version of glibc was incorrect… So, I installed glibc from Debian’s repos.
:D That one is a classic. Most distributions don’t include packagers from other distros because 99% of the time it’s a bad idea. But with Arch you can do whatever you want, of course
My two things:
I’ve heard about some new coreutils (rm, cp, cat… this time the name really fits the contents :D) and I decided to test it out. Of course it was conflicting with my current coreutils package and I couldn’t just replace it because deleting the old package would break requirements. So without thinking I forced the package manager to delete it “I’ll install a new one in just a second”. Turns out it’s hard to install a package without cp, etc :D
I don’t remember what I was doing but I overwrote the first bytes of hdd. Meaning my partition table disappeared. Nothing could be mounted, no partitions found. Seemingly a brick.
Turns out, if you run a rescue iso, ask it to try and recognize partitions and recreate the table without formatting, Linux will come back to life as if nothing happened
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
Security & Privacy: Device Unlock: Screen lock settings: Lock after screen timeout: Shortest duration you are comfortable with
These don’t affect “the amount of tracking and data collection these devices perform”. Might be good ideas in themselves, but bundling these with options that really diminish the amount of data broadcasted, washes the picture out IMO
I’m guessing that you’ve been using kernels from packages provided by your distribution and its maintainers simply haven’t decided yet that Wayland is used wide enough to put things it needs into default kernel. But that’s just a matter of time.
On distribution I use, for example, I did not have to compile my own kernel when I decided to check Wayland out. But that’s only because kernel package maintainers of my distribution have decided to enable it earlier
I’ve also found this article that doesn’t add nvidia to the mix. But in general it seems to work the same for both as long as you have the drivers proper for your hardware installed
And I was commenting on the article. Which only has two lists and at the bottom
By enabling all of these settings, you are significantly reducing the amount of tracking and data collection these devices perform, but keep in mind that you are not completely eliminating it.