25GB=qemu@verein.service
17GB=auto-aur-builder.service
15GB=borgmatic.service
11GB=postgresql.service
6.2GB=qemu@arturimages.service
5.5GB=gitlab-puma.service
3.0GB=immich-server.service
2.7GB=cryptpad.service
2.3GB=immich-machine-learning.service
1.4GB=clamav-daemon.service
1.3GB=gitlab-sidekiq.service
1.3GB=gitlab-gitaly.service
1.3GB=systemd-journald.service
1.2GB=lemmy.service
1.1GB=peertube.service
1.1GB=docker.service

So pretty much, a tiny 11 VM and an autobuilding service, that probably has a memory leak. Then backups, permanently running, postgres containing all my data, and a linux vm. Then, various services.

Your post ended in “Edit: To the few of you who’re taking pot shots at me like the immature cunts you are - go back to Reddit for that.”, while the rules say "Be nice and; have fun

Doxxing, trolling, sealioning, racism, toxicity and dog-whistling are not welcomed in AskLemmy."

If you want no moderation, go to another platform.

You’re like a child punching someone and then being angry they get punished, or a carbrain running a red light and complaining about the ticket.

I mean, Bun itself serves a language that should not exist

Well, I tried piper before, and some other tool. Both did not work. iirc, piper did not even detect the device

Can’t really test that.

I may need to try ratbagd then :3

It does have generic tools (eg. xdotool -> ydotool), but the most powerful way is to configure it in the DE/WM itself (eg. KDE’s shortcuts or sway’s bind command). To know if what you are doing is possible with ydotool or on sway, I’d need more specific info.

But my point was rather that it’s cool to have such functionality in the kernel, independent of desktop stack and DE/WM.

I’ve never been able to actually program my G502X Lightspeeds buttons

Sucks for wayland users tho

And I prefer C/C++ and Python due to that.

Eg. JS devs need to version pin in NPM to not expose users to compromised packages. That means that, from now on, they need to be active at least every week and update the pinning to not expose users to vulnerable packages. Meanwhile, the users need to be on-edge about the dev actually being active, and, still, for every vulnerability and compromised package, need to scan their whole system for files relating to that package. And of course, that means a very long fix path of Vuln discovered -> Vuln fixed -> Dev knows that one of the dozen packages they use needs updating -> Dev updates -> Package managers updates -> User updates.

It’s a horrible experience for sysadmins. I’m actively switching to alternatives and rewriting smaller things in C++, because everything I’ve written in the latter has never broken in years, without recompilation, because the ABI stayed the same for all libraries, while the libraries get carefully curated by a dedicated team. And as soon as a vulnerability/backdoor is found and fixed? sudo pacman -Syu. nothing more, nothing less. Fix path: Vuln discovered -> Vuln fixed -> Package managers updates -> User updates.

Looking at more than just binary files in repos: I’m also actively rewriting PKGBUILDs to use the native python packages instead of building a venv, because that just works better in my experience. I’ve never had issues with incompatibility between python-* packages, simply because they are build for each other. And I mean, it took 30 minutes to build a component that converts a requirements.txt, which requires you to trust the dev (to be active) and pypi (which you can’t trust), to a collection of pacman packages. Universally applicable to all requirements.txt and uncomplicated. So yeah, idiots can continues using pip, I laugh with a list of packages neatly curated by a dedicated team.

The only component actually fucking up boot has been the NVidia driver. Otherwise, Arch with testing repos has never failed me for years on many devices.

If you want to have at least some thrill, use testing repos. I had to fix GitLab two (2) times due to the main package not being linked against testing libraries (it took 10 seconds to ln -s the new to the old version), and had one breakage due to dovecot revamping their whole config system, but publishing no example/useful docs.

And if it’s a dudes ass, no body would even care - is what I would have said if I wasn’t in a commited relationship with the fem"boy" with the best ass ever :3

Updated the comment. (The ICD is explicitly installed by vulkan-radeon, vulkan-intel or nvidia-utils/vulkan-nouveau. Just as with all linux-firmware categories/companies being their own package now, this is probably done to minize unused space/bloat.)

Vanilla Arch Linux, testing repos, with an RX 7800XT.

I’ve just always followed the Arch wiki, and never tried using Vulkan without vulkan-radeon on my one PC with an AMD card. The wiki states: “Install the mesa package, which provides both the DRI driver for 3D acceleration and VA-API/VDPAU drivers for accelerated video decoding.” and “For Vulkan support install vulkan-radeon (lib32-vulkan-radeon for 32-bit applications).”.The vulkan page itself says:

To run a Vulkan application, you will need to install the vulkan-icd-loader package (and lib32-vulkan-icd-loader from the multilib repository if you also want to run 32-bit applications), as well as Vulkan drivers for your graphics card(s). There are several packages providing a vulkan-driver and lib32-vulkan-driver:

    AMD: vulkan-radeon (or lib32-vulkan-radeon)
    Intel: vulkan-intel (or lib32-vulkan-intel)
    NVIDIA: there are two implementations:
        nvidia-utils (or lib32-nvidia-utils) - NVIDIA proprietary
        vulkan-nouveau (or lib32-vulkan-nouveau) - NVK (part of Mesa project)

The vulkan-radeon package provides the ICD (

# pacman -Qlq vulkan-radeon | grep -v '/$'
/usr/lib/libvulkan_radeon.so
/usr/share/drirc.d/00-radv-defaults.conf
/usr/share/licenses/vulkan-radeon/license.rst
/usr/share/vulkan/icd.d/radeon_icd.json

); so does nvidia-utils (

# pacman -Qlq nvidia-utils | grep -i icd | grep -v '/$'
/usr/share/vulkan/icd.d/nvidia_icd.json
/usr/share/vulkansc/icd.d/nvidia_icd_vksc.json
)

, but mesa does not.

mesa only coveres, OpenGL, according to the arch wiki.

also, the former, I couldn’t remember the correct word

It basically allows vulkan, the graphics engine, to work with AMD driver (which resides in the kernel). For OpenGL to work with it, you need the mesa package, but that’s usually installed anyway.

Edit: graphics API, not engine

Actually, there is one more package you might need: vulkan-radeon. The nvidia package, which you can remove then, provided that implementation itself.

Searching these devices produced no evidence relevant to the case. Nothing linked Klayme to the girl. No intimate images were found. Klayme did have a Kik account, but cops couldn’t even show that he had accessed the service during the period in question.

And then they want us to follow the law. Fucking fascists.

The trimonthly perchance post again.

We just need an autoban for posts containing “perchance”.