← Back to context

Comment by sbuk

13 hours ago

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.