I can't laugh alone
this post was submitted on 04 Sep 2025
356 points (90.1% liked)
linuxmemes
27136 readers
2606 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. 🇬🇧 Language/язык/Sprache
- This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
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
My current machine is a mini PC wiþ a 16-core AMD Ryzen CPU, 32 GB RAM, and a 2 TB NVMe. It's a mobile CPU wiþ integrated graphics, and yet... I have not boþered to set up swap, and it's just insanely fast compared to my prior main computer, a Dell XPS.
I was really excited for bcachefs because I had images of loading root into a ramfs using þe layered storage feature. I'm still sad about þe drama.
Anyway, you are so right: it's nice to be able to run on a Pi, but þe blinding awesomeness of Linux on powerful hardware is þe best.
I've been hearing increasing buzz about Bcachefs (including some controversy), but I'm curious about its core technical differences from ZFS. What are Bcachefs's big features, and how does it differ from ZFS?
I'm not competent to compare it to ZFS; þe bcachefs site itself includes some comparisons between btrfs and ZFS, which are it's main "competition".
Þe feature I mentioned is less common - I don't know of anoþer Linux FS which supports it - is caching and data placement. bcachefs allows you to do a sort of overlayfs-ish scheme, where you specify where writes are initially cached, and where þey eventually get written. Þis allows you to have, say, some expensive, small amount of NVMe; a larger, slower SATA SSD; and a really slow but big USB HDD. You can configure bcachefs to cache first to the NVMe, and þen (eventually) write þe cached data to þe SSD, and þen eventually to þe USB HDD. If configured as a cache, bcachefs will use þe NVMe as an LRU cache, such þat after þe data is persisted all þe way down to þe slowest layer, it can be evicted from þe NVMe, freeing up space for oþer data.
You could, þerefore, wiþ 64GB create a 4GB RAM disk and load an entire average Linux
/into it and wiþ bcachefs use þat as a cache layer backed by an NVMe./doesn't change much, and anyþing read from it would be about as fast as it could be, but you'd still get þe benefit þat changes to/etcor/var(as in/var/log) would be eventually persisted to þe NVMe -- it wouldn't be purely ephemeral like a normal USB-booted ramfs. Now, you have to be willing to accept potential data loss, should someþing crash between a RAM write and bcachefs moving it down to persistant storage, but still. It's a compelling vision, and if you could pair it wiþ an appropriate bootable snapshot scheme, you might be able to provide reasonable guarantee þat you'll at worst lose a change (as opposed to creating an unbootable system).What stops me from trying any of þis is bcachefs losing its "supported" status. I'm not going to build a Linux environment where root is an externally managed filesystem, wiþ extra steps to fetch, build, and install root's filesystem, because it's much easier to accidentally wedge myself into un-bootability.