this post was submitted on 17 Apr 2024
12 points (83.3% liked)

KDE

5313 readers
133 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago
MODERATORS
carlschwan@lemmy.kde.social
Bro666@lemmy.kde.social
herzenschein@pawb.social
Aniqakhokhar@lemmy.kde.social
12
KDE Neon using tmpfs for /tmp seems like an horrible idea? (lemmy.kde.social)
submitted 6 months ago by lumirell@lemmy.kde.social to c/kde@lemmy.kde.social
14 comments fedilink hide all child comments
 

I get the idea behind it for sure but why use our available ram for this? I thought whatever init functionality would just wipe clean /tmp at boot.

Right now what I'm looking at is that if a system has 16gbram KDE Neon uses half of it for /tmp.

The thing is applications could output to /tmp for a plethora of reasons that could maximize that. Whether you are a content creator or processing data of some sort leaving trails in /tmp the least I want is my ram being used for this thing regardless.

Basically if you drop-in a 10GB file in /tmp right now (if your setup has tmpfs active) you will see a 10GB usage in your htop. Example in https://imgur.com/a/S9JIz9p

I'm not here to pick a fight but as a new KDE Neon user I'm scratching my head on the why after years in Arch Linux.

you are viewing a single comment's thread
view the rest of the comments
[–] recursive_recursion@programming.dev 3 points 6 months ago (1 children)

wouldn't that open up additional vulnerabilities?

[–] CameronDev@programming.dev 2 points 6 months ago

Are you thinking rowhammer? My understanding is limited, but doesnt rowhammer require being able to write to memory at a consistent address, co-located with the data being attacked? Im not sure thats doable with tmpfs, but probably worth an investigation by someone more knowledgable than me :)