this post was submitted on 01 Feb 2026
569 points (96.9% liked)
linuxmemes
29744 readers
838 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.
- Don't come looking for advice, this is not the right community.
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
If you are nostalgic for BeOS, then the elevator pitch is, “It’s Be, only on modern hardware and more software support.”
If you are unfamiliar with BeOS, the pitch is: “Imagine an extremely lightweight desktop is with all of the things you would expect in a modern environment with none of the legacy. In an alternative universe, BeOS would have become OSX.”
There are so many things that Be did right from the very beginning that other OSs have adopted, but never as cleanly as Be did it.
For example, its file system. Most people don’t really notice or care about the file system, they all have directorys and hold files, maybe with permissions. BeFS does that as well, of course, but so much more. The entire file system acts as a database, so you can easily perform fast queries on it. You can also create virtual directories that are the result of those queries.
You want a “folder” that contains every markdown file created after 2020 between 20 and 1000kb in size? Bam, instantly done and live updated whenever something accesses it. The files aren’t actually copied there, just appear there to normal tools, almost like soft links.
BeFS also supports a resource fork system that it calls attributes. These can also be queried using the same database like tools as the rest of the system. File typing is done this way, every file gets a MIME type attribute and there is a daemon that sniffs them when a new file is downloaded or copied over.
Even more, this allows some crazy things like plain text files that have font, color and other formatting elements because all that is stored as an attribute.
Or their contact information app, which stores every person as a zero length file with details as attributes. You can create a virtual folder of all your contacts that meet a certain criteria and have other applications use that folder for whatever.
Or the email app which stores each email as a file, and adds the basic metadata like to, from, subject, read, etc as attributes. Then you can have different virtual folders based on those. This also means that the basic file system browser is the default way to view email, because it supports all the attribute viewing, queries and such you would need. Or you can do it all from the command line using either basic cli tools or some slightly specialized ones.
Combining attributes and virtual directories makes for a fantastic media library system, all built into the os for free. Imagine a directory that contains “Every metal song I have, from 1989 to 1993, that I haven’t played in three weeks” or whatever else you want.
Back when people used files and all applications were local first, this was probably much more exciting, but it’s still pretty cool.
The file system thing is really cool, are their downsides of implementing it like that? Curious why Linux would not implement something like that
I think there are a couple of reasons. First, the Linux kernel doesn’t support resource forks at all. They aren’t part of POSIX nor do they really fit the unix file philosophy. Second, most of the cool things that BeFS enables are very end user desktop oriented, and Linux leaves that desktop environments, not the kernel. BeOS was designed as a fully integrated desktop os, not a multiuser server os. Finally, I expect that they are a security headache, as they present this whole other place that malware could be stored. Imagine an innocent looking plain text file that has an evil payload sitting in an attribute.
The resource fork isn't gonna be really meaningful to essentially all Linux software, but there have been ways to access filesystems that do have resource forks. IIRC, there was some client to mount some Apple file server protocol, exposed the resource forks as a file with a different name and the data fork as just a regular file.
https://www.kernel.org/doc/html/latest/filesystems/hfsplus.html
Linux does support HFS+, which has resource forks, as the hfsplus driver, so I imagine that it provides access one way or another.
searches
https://superuser.com/questions/363602/how-to-access-resource-fork-of-hfs-filesystem-on-linux
Also, pretty esoteric, but NTFS, the current Windows file system, also has a resource fork, though it's not typically used.
searches
Ah, the WP article that OP, @evol@lemmy.today linked to describes it.
It's been a few years since I used a Mac, but even then resource forks weren't something you'd see outside of really old apps or some strange legacy use case, everything just used extended attributes or "sidecar" files (e.g. .DS_Store files in the case of Finder)
Unlike Windows or Linux, macOS takes care to preserve xattrs when transferring the files, e.g. their archiver tool automatically converts them to sidecar AppleDouble files and stores them in a
__MACOSfolder alongside the base file in the archive, and reapplies them on extraction.If course nothing else does that, so if you've extracted a zip file or whatever and found that folder afterwards, that's what you're looking at.
TIL https://en.wikipedia.org/wiki/Resource_fork But yeah good insights
Considering how the mainstream OSes dropped the ball on file metadata super hard without even approaching what you describe, exchanging files between Haiku and those OSes gotta be a pain.
Oh it absolutely is. Bringing files into Be is fine. The file type sniffer runs in the background and adds whatever metadata it can in a lightweight quick way. IIRC there are addons for specific file types like media files that add nice things like author, runtime, etc.
Sending them out is a pain though. All the metadata is usually lost and from what I recall even emailing a file from one Be machine to another could be difficult. IIRC you could zip them and the metadata would make it, but raw files and tgz would lose it.
do you know how many of the features you’re describing work on haiku?
All of these features work on Haiku OS.
thanks <3