• 0 Posts
  • 298 Comments
Joined 2 years ago
cake
Cake day: July 6th, 2024

help-circle









  • “Teams” is what came to mind for him first when he thought of online meetings. To me that suggests […]

    People who haven’t touched Google with a ten-foot pole for years still “google” stuff in general conversation because that’s what people generally understand. People who never used Twitter (or that modern renamed far-right bot paradise) talk about stuff that got “tweeted”.

    So no… associating colloquial use of terms with actual habits doesn’t work well.







  • it’s getting more prevalent as more stuff (especially servers) run on Linux […] Linux’s days of living in “security through obscurity” are over"

    Servers are primarily running Linux for decades. So any security through obscurity would be gone for as long, if it even existed ever…

    though I’ll admit to not having tested that sort of thing with Wine/Proton installed

    The more primitive the better the chances. And there are some really primitive cases of ransonware perfectly happy with running through Wine and encrypting your files. So limiting Wine’s file access (or better running it as a separate unpriviledged user with no access to anything but your games) is always a good idea.





  • pacman -S vulcan-mesa-implicit-layers

    Which will then probably tell you that it conflicts with vulkan-mesa-device-select and asks if you want to replace it. Which might either work or just get you another conflict because vulkan-mesa-device-select is required by some other package.

    Btw… pacman -Qi <package name> usually tells you anything you need to know about a package. In this context mainly why it was installed (as a requirement for which package) and which other packages are required as a dependency.

    So maybe you should take one step back first. Check why 'vulkan-mesa-device-select` was installed in the first place. If it’s not dependency of something else you can either remove it (or replace it) alongside its lib32 version.