Posted by john_alan 11 hours ago
"1.12 Threads
1.12.1 Cancellation Points
Question 31: Which C stdio functions have cancellation points that occur when a thread is executing?"
https://www.opengroup.org/csq/repository/noreferences=1&RID=...
- The Linux kernel also has timer coalescing
- Linux also has lazy atime ('relatime') by default
- No Linux distro installs uucp by default, and certainly not suid
- Desktop distros will also run a file indexer of some sort
etc.
They were:
Inspur K-UX (expired on 3 February 2019)
Huawei EulerOS (expired in September 2022)
https://en.wikipedia.org/wiki/Inspur_K-UX
https://en.wikipedia.org/wiki/EulerOS
These were both based on Red Hat.
So legally at one point a Linux was Unix.
So, 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.
Then, and only then, is your macOS 15.0 actually UNIX® 03-certified.
This is batshit insane. I can guarantee you with 100% certainly not a single macOS installation in the entire history of macOS – let alone when just counting macOS 15.0 – has implemented even half of these changes. I’m sure there is a small number of people who have System Integrity Protection disabled permanently, and an even smaller number of people who have enabled the root account, and an even smaller number of people who have done both of those things – but that’s it. All the other changes are far too obscure and specific to be of any use to anyone.
the netbsd gallery (https://netbsd.org/gallery/) had a picture of somebody using that on windows xp (iirc) in order to compile pkgsrc packages in a "posix compliant" environment. the picture seem to be gone now :(
Btw, MacOS 27 (the current version) still has UUCP.
Traditional UNIX is does not mean having an open source core you're intended to tinker with. Traditional UNIX was entirely proprietary, connected with well-defined text-based interfaces. This is entirely orthogonal to user control and manipulation of the OS.
SIP is as much defense from the likes of Adobe and Google as it is from more traditional malware.
I think that piece by piece Apple wants to go into direction of making macOS just a desktop version of iOS, that is closed and impossible to modify. They will use of course security as an excuse, the practical thing is that with iOS they succeeded because they went to the market with an OS that was already closed, but making users accept that in new version downloading a software from the internet and installing it it's no longer possible takes time. But they are getting there soon to me.
AT&T was forbidden by its consent decree from productizing Unix. Licensees received the source code, on an as-is basis, with no official support from AT&T.
It doesn't mean end users had access to the source code.
In fact, vendors would have been prohibited from distributing AT&T source code to customers who weren't themselves AT&T licensees, just as CSRG was prohibited from distributing BSD to customers who weren't licensees before 4.4BSD-Lite.
The same goes for most other proprietary source-available products. For example, game developers can't open source Unreal Engine projects even though Unreal Engine source licenses are available to end users for free.
At a bare minimum, you would almost have to have source to the vast majority of the kernel because there was no kernel modules. Sysgenning for a particular system involved compiling the kernel for that set of hardware.
I'm literally working on an early sun system emulator right now, heavily assisted by the standard sec tape that came with the standard software distribution of sunos, which has plenty of AT&T code.
As a non corporation end user with a sublicense from one of the above licensees (which is the apt analogy for an individual user in my opinion) you most certainly did not receive the source or have the rights to it.
Perhaps Golden Gate simply hasn't yet passed certification.
It takes several months for the certification to appear on the site. What would be newsworthy is if we see a release next year without this release getting certification.
Even better, last year's 26 releases are still undergoing the process.
Looking now, I see almost no uses of the word UNIX on the website except the docs archive, so I guess they’ve decided to abandon both the certification and the use of the UNIX trademark in macOS.
So Apple's use of UNIX in marketing was to make sure they never ran into that as a disqualified on a government contract. My impression is that those contracts largely no longer require that (one small measure of common sense has caught up).
Developed WSL and discontinued SFU (Windows Services for UNIX), which they had since NT 4 days.
The original POSIX Subsystem (psxss.exe) was Cutler's team who implemented a minimal POSIX.1 subsystem server alongside Win32 and OS/2. This was done primarily to satisfy US Federal Government procurement requirements (FIPS 151-2).
In these efforts they also tried to create successor languages to C, Alef and Limbo (for userspace), and never cared that much about anything past C89.
He has settled with Linux because that is the winner of UNIX wars, which predated Linux wars on Distrowatch.
As for the original UNIX,
"Using Unix is the computing equivalent of listening only to music by David Cassidy"
-- Rob Pike
Today? It's all Linux or Windows (of course, now also Web/SaaS). All these different Unices have fallen by the wayside in favor of Linux. Yes, some are still around but the mindshare has been in Linux for the last 20 years.
I suspect you could rip out a ton of autoconf rules and no one would notice.
If they are in fact dropping it, that’s why. But… Apple often “finishes” the enterprise features with a point release.
What I care about, at least, are experiences of ease, convenience, compatibility, control, order, and freedom around a programmable system that invites the blurring of the lines between user and developer, between quotidian use and automation, and between decoration and reshaping. Such experiences still involve many of the same elements as they did two decades ago: a composable language of commands, commonly observed conventions, well-organized hierarchies of files, formal software freedom, powerful package management systems, great in-band/offline documentation, etc. But Unix certification isn't the center of gravity around which such experiences revolve, if it ever was. And for that matter, neither is macOS.
https://www.opengroup.org//openbrand/register/xy.htm
I imagine that the cert will be listed for Golden Gate soon.
Also the suggestion Apple was entirely removed is false; see https://www.opengroup.org/openbrand/register/apple.htm
For those that don't know how to use a filter drop down, check UNIX 03 version.
Which is a damn shame, because AI dev is going to result in a massive influx of new software right when Apple makes it ever more difficult to do so on its platform.
I still make Mac builds, but it is more of an afterthought on a secondary Mac build machine now.
You know something has peaked when they become less open and more “clawbacky”; that is basically collecting interest on an investment (marketshare) instead of remaining more open (at the cost of some things). “Increased security” is always the rationale.
If the platform I use is an afterthought for you then your software becomes afterthought for me as well.
Was it delisted from a different “product standard”, or is this submission about macOS 27 not being listed?