this post was submitted on 09 Mar 2025
24 points (78.6% liked)
Linux
7126 readers
379 users here now
A community for everything relating to the GNU/Linux operating system
Also check out:
Original icon base courtesy of [email protected] and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This reads like it was written by some LLM.
Don't ever disable journaling if you value your data.
Neither of these schedulers exist anymore unless you're running a really ancient Kernel. The "modern" equivalents are
none
andbfq
. Also this doesn't even touch on the many tunables thatbfq
brings.Also changing them like they suggest isn't permanent. You're supposed to set them via udev rules or some init script.
None of this changes any settings like they imply.
No shit. Who would've thought that throwing more/better hardware at stuff will make things faster.
EDIT: More bullshit that I noticed:
Again this doesn't permanently change the maximum number of open files. This only raises the limit for the user who runs that command. What you're actually supposed to do is edit
/etc/security/limits.conf
and then relog the affected user(s) (or reboot) to apply the new limits.This doesn't even make any sense.