this post was submitted on 21 Dec 2024
295 points (70.6% liked)
196
17082 readers
909 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
Other rules
Behavior rules:
- No bigotry (transphobia, racism, etc…)
- No genocide denial
- No support for authoritarian behaviour (incl. Tankies)
- No namecalling
- Accounts from lemmygrad.ml, threads.net, or hexbear.net are held to higher standards
- Other things seen as cleary bad
Posting rules:
- No AI generated content (DALL-E etc…)
- No advertisements
- No gore / violence
- Mutual aid posts require verification from the mods first
NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.
If you have any questions, feel free to contact us on our matrix channel or email.
Other 196's:
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
Calling something Linux is very specific, and it's just not true for macOS. E g. if someone brings you an encrypted drive that uses LUKS, you can't mount it in macOS. But both are Unix-like, macOS even being UNIX certified. However, from what I understand, these mostly concern a specific part of the stack that doesn't guarantee that you can work with the other system, this is rather something for applications to target. I mean cool I can enter a shell and list files on macOS, but that doesn't fix the problem.