Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The people that certify it say that you are wrong. What you think and what actually is are two entirely different things in this case. The fact remains that, according to the OpenGroup (and they are the one that matter here), macOS 26 is UNIX.




macOS 26 that is /altered/ is UNIX. macOS that ships on every Mac is not certified UNIX -- but it can be made to match if you're willing to give up security.

You should read through the actual certification - https://www.opengroup.org/csq/repository/noreferences=1&RID=... (there are a couple more in the repo).

To run the VSX conformance test suite we first disable SIP as follows: [...]

Feel free to disable SIP on your Mac. I certainly won't be doing so on mine.


You’re confusing operating mode with operating system.

SIP/SSV don’t create a different macOS, they restrict mutation and introspection. They don’t change the POSIX surface, the SUS semantics, or the kernel interfaces being certified. They just stop test harnesses from instrumenting the system without elevated privilege.

By your logic, no modern OS is anything it claims to be unless you run it in an insecure debug configuration. Linux isn’t POSIX because you need root. Windows isn’t Windows because kernel debugging exists. That’s obviously nonsense.

The Open Group certifies macOS 26 as shipped. Temporarily relaxing protections to run a conformance suite does not produce a “different OS”, it produces a different trust configuration of the same one.

Saying “it’s not really UNIX because SIP is on” is like saying a container isn’t Linux because it doesn’t let you mount /proc without extra privileges.


You didn't read the article, did you? SIP isn't the only alteration. And we don't know all of the changes required due to the waivers.

> if you want your installation of macOS 15.0 to pass the UNIX® 03 certification test suites, you need to disable System Integrity Protection, enable the root account, enable core file generation, disable timeout coalescing, mount any APFS partitions with the strictatime option, format your APFS partitions case-sensitive (by default, APFS is case-insensitive, so you’ll need to reinstall), disable Spotlight, copy the binaries uucp, uuname, uustat, and uux from /usr/bin to /usr/local/bin and the binaries uucico and uuxqt from /usr/sbin to /usr/local/bin, set the setuid bit on all of these binaries, add /usr/local/bin to your PATH before /usr/bin and /usr/sbin, enable the uucp service, and handle the mystery issues listed in the four Temporary Waivers.


Don't be rude. I did read TFA, hence my comments. You didn't understand my comment, did you?

Whether it disabling SIP, enabling root (see the bit about Linux and Posix in my previous comment), enabling case sensitivity in APFS (done for backwards compatibility), or any of the other stuff, the OS shipped remains the same as the tested one, and pay attention because this is the bit you seem to be incapable of grasping, with the extra bits turned on! Some are dumb, some for backwards compatibility and some are genuinely useful.

A Kia Ceed is still the same Kia Seed if the showroom add their stickers, changed the tyres and put some registration plates on it.


The certification test suites are clearly a superset of what most "Unix" applications require.

I haven't used UUCP since the 90's, have you? I ran a UUCP node for about 5 years. Fun times, but not exactly useful today.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: