Search

[SOLVED] - I learned that this is a sure way to break your Debian, and no matter how you go about it, you'd wish you either waited or used a different distro altogether for this purpose. In my case, I got Nobara 41 working, which already has the latest mesa. Trying to install the latest from Debian unstable almost got me pretty turned around, and I'm glad I switched course when I did.

Original post: Apologies for my fairly low-level question. I spent all day yesterday spinning my wheels on this.

(I do fine using Debian Linux as my daily driver, but I'm not ashamed to admit that this (and things in this area) are beyond my experience. I've never compiled anything from source. I used to be a wiz with DOS 6.22 and Windows through 7, but my brain just stopped learning these things properly some time in the past.)

My distro (MXLinux 23.x) just announced they're almost ready to include Mesa 24.2.8. I purchased an AMD R

I've inherited a systemd service and it uses BindReadOnlyPaths to make certain paths available to the service (doc)

A bind mount makes a particular file or directory available at an additional place in the unit's view of the file system. Any bind mounts created with this option are specific to the unit, and are not visible in the host's mount table.

The service is running using a specific user and I would like the user to access those read-only paths outside of the service. Is there an possibility within systemd that would allow me to do that?

Edit: solved it with a systemd bind mount

cross-posted from: https://sh.itjust.works/post/21361730

Hello, I came across zram recently and I'd like to know if I should use it, my laptop only has ~4GB of ram, and for the most part it'll only stutter when I open multiple programs or a game, so would zram be adequate in my case?

Also, would the compressing and decompressing have a significant impact on my cpu?

Edit: solved since then

cross-posted from: https://lemmy.zip/post/16796976

Based on https://old.reddit.com/r/openSUSE/comments/1d798rc/another_update_breakage/ one option is to wait for the next snapshot, what are you guys doing?