A software developer and Linux nerd, living in Germany. I’m usually a chill dude but my online persona doesn’t always reflect my true personality. Take what I say with a grain of salt, I usually try to be nice and give good advice, though.

I’m into Free Software, selfhosting, microcontrollers and electronics, freedom, privacy and the usual stuff. And a few select other random things as well.

  • 0 Posts
  • 15 Comments
Joined 5 years ago
cake
Cake day: August 21st, 2021

help-circle

  • Did you read the Wiki? You need to either pass the compress_extension option when mounting it. The Arch Wiki lists how to enable compression on all text files. And I gave you the version with a ‘*’, which enables compression for all files. Or you do a chattr -R +c ... on specific files or directories to compress them. Maybe you missed that and that’s why it doesn’t compress?!

    There’s probably also a way to debug it and somehow figure out what it does and how many files/sectors got compressed on the filesystem. Linux usually buries that kind of information somewhere in /sys or /proc, or there’s special commands to figure it out. But I’m not really an expert on it.

    And there’s also files which just can not be compressed any further because they’re already compressed. Most images, for example. Or music or ZIP archives. If you try to compress those, they’ll usually stay the same size.











  • Ah, I get it. Yes. That section is weird. And it’s unalike the bureaucrat English around it. And I’d say the call to action: “Embark on a journey […]” is pretty much like ChatGPT sounded 2 years ago. I’m fairly certain the other text comes from humans with some expertise in writing legalese or specifications, and this will be a ChatGPT snippet.

    The committer also has this weird habit of naming their commits “Update Readme.md”. So I’m also fairly sure they’re not your average open-source developer using Git how it’s intended.

    Most other markdown files in that specific directory smell of ChatGPT as well.