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

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 sudo in 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 figuresWe 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
    zephyr@lemmy.world
    rtxn@lemmy.world
    569
    Where to go now since Linux is mainstream (lemmy.today)
    submitted 3 days ago* (last edited 3 days ago) by evol@lemmy.today to c/linuxmemes@lemmy.world
    329 comments fedilink hide all child comments
     

    I can't even feel superior to everyone when theirs so many arch installers!! I use real arch btw. I thought "I guess I should go to Gentoo" but then wait, CHROMEOS IS A GENTOO INSTALLER!

    I feel like we only have two options now

    1. Ascend to BSD-land
    2. Ironically supporting Windows Unironically

    edit: I have decided to replace my debian laptop with BSD

    you are viewing a single comment's thread
    view the rest of the comments
    [–] evol@lemmy.today 11 points 3 days ago (1 children)

    The file system thing is really cool, are their downsides of implementing it like that? Curious why Linux would not implement something like that

    [–] BartyDeCanter@lemmy.sdf.org 13 points 3 days ago (2 children)

    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.

    [–] tal@lemmy.today 8 points 3 days ago (1 children)

    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.

    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

    Add /..namedfork/rsrc to the end of the file name to access the resource fork.

    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.

    The Windows NT NTFS can support forks (and so can be a file server for Mac files), the native feature providing that support is called an alternate data stream. Windows operating system features (such as the standard Summary tab in the Properties page for non-Office files) and Windows applications use them and Microsoft was developing a next-generation file system that has this sort of feature as basis.

    [–] The_Decryptor@aussie.zone 1 points 2 days ago

    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 __MACOS folder 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.