http://androidxref.com/4.2_r1/xref/bionic/linker/linker.cpp#...
This hilarious memset(3) bug was shipping for years:
https://android-review.googlesource.com/#patch,sidebyside,14...
Well, that's what you get when you NIH your libc...
[1]: http://catb.org/~esr/writings/taoup/html/ch02s01.html#id2880...
And I doubt IPC will work anyway, given that the Android kernel doesn't do UNIX IPC.
In terms of installed operating systems and the applications people interact with, Unix or Unix-alike systems win. I don't care if the desktops they use are Windows, or if the phones they run (which have a Unix/Linux kernel usually) don't expose a shell prompt -- the applications they run get the largest part of their functionality through server daemons running on systems running *nix.
The attempts to follow OS/400 footsteps with a managed userspace in Windows Phone 7.
The OS architecture of Windows Phone 8.
The way they are transitioning Windows into a App Container model with the WinRT execution model.
Why aren't you hearing about these features? Lots of reasons. Windows is closed-source, so the internal changes you hear about are the ones Microsoft wants you to hear about. Most of the shiny new toys are to support server features that you won't notice unless you're a Windows sysadmin. Most desktop users don't care about internal changes unless they break things, and Windows hasn't broken much on the internal side since Vista. Microsoft's own messaging about major changes has been targeted almost exclusively at Windows server admins.
Edit: That's not even getting into the new app development platform that shipped with 8/10, DirectX 12 adding Mantle-like APIs, first-class support for touch input, hybrid boot, booting from VHDs, etc. Microsoft has been busy over the past few years.
There's definitely some Unixes that are still trying to do something different, like DragonFly BSD, MINIX 3, Genode and so forth.
Most of it is academic efforts, as always.
Being an hybrid kernel, not like the other UNIXes.
Introducing a super root model, where the traditional root becomes a mere power user.
Being an UNIX where Objective-C and now Swift have the spotlight (with a little space for C++ on IOKit), not C.
Being a hybrid kernel barely has any significance when you don't exploit that fact, which XNU doesn't. Also, it's a hybrid of Mach, which is heavily anachronistic and clunky. DragonFly BSD, on the other hand, actually does through the vkernel mechanism.
I have no idea what you mean by the third one. Are you saying that the root user's privileges are segmented into multiple subsystems? POSIX has had capabilities for that. They suck and they're not actual capability-based security, but they do achieve logical privilege segmentation. Plan 9 and Inferno are the only ones from the Unix-ish lineage who successfully got rid of root entirely.
You can write applications targeting any subsystem provided there are bindings, which there are. For instance, Python and Vala are heavily used in contemporary Unix-like DEs for application programming.
It is not part of any POSIX compliant UNIX.
It also pushes developers into a micro-kernel style of application development, which isn't common in UNIX.
> Also, it's a hybrid of Mach, which is heavily anachronistic and clunky. DragonFly BSD, on the other hand, actually does through the vkernel mechanism.
Besides FreeBSD, I admit I hardly know any other BSD.
> I have no idea what you mean by the third one. Are you saying that the root user's privileges are segmented into multiple subsystems?
In El Capitan, you can only be real root in safe mode. In normal mode there are paths (e.g. /bin, /usr/bin,...) and APIs that aren't available even to processes running as root.
> You can write applications targeting any subsystem provided there are bindings, which there are. For instance, Python and Vala are heavily used in contemporary Unix-like DEs for application programming.
There is a big difference in being a first class language used in the vendor SDK and IDE, and a third party one used by some developers.
[1] = https://en.wikipedia.org/wiki/Usage_share_of_operating_syste...
OS X 10.10 ships with a version of bash from 2007. Without something like homebrew or macports to install an updated userland the "Unix" core of OS X is rotting away.
One might question the usefulness of SUS/POSIX in a world where most of the *nix ecosystem targets GNU, but saying it has no purpose beyond advertising is disingenuous.
I tried to download and run their test suite, but they lead to a page that says "For Purchase Enquiries please contact:"
They don't care about standards, they care about selling things.
Is the unix certification only for large companies who can afford to throw money at the open group in order to get certified?
According to the wikipedia page:
> By decree of The Open Group, the term "UNIX" refers more to a class of operating systems than to a specific implementation of an operating system; those operating systems which meet The Open Group's Single UNIX Specification should be able to bear the UNIX 98 or UNIX 03 trademarks today, after the operating system's vendor pays a substantial certification fee and annual trademark royalties
Right.. Please tell me how this is not a meaningless certification? FreeBSD is more unix than OS X, and would likely have no problems running the test suite, but is not certified as "real unix" because that certification is about money.
$ strings `which cp`|grep src
$FreeBSD: src/bin/cp/utils.c,v 1.46 2005/09/05 04:36:08 csjp Exp $
$FreeBSD: src/bin/cp/cp.c,v 1.52 2005/09/05 04:36:08 csjp Exp $
$ strings `which ls`|grep src
$FreeBSD: src/bin/ls/cmp.c,v 1.12 2002/06/30 05:13:54 obrien Exp $
$FreeBSD: src/bin/ls/ls.c,v 1.66 2002/09/21 01:28:36 wollman Exp $
$FreeBSD: src/bin/ls/print.c,v 1.57 2002/08/29 14:29:09 keramida Exp $
$FreeBSD: src/bin/ls/util.c,v 1.38 2005/06/03 11:05:58 dd Exp $
https://svnweb.freebsd.org/base/head/bin/cp/cp.c?view=log and https://svnweb.freebsd.org/base/head/bin/ls/ls.c?view=logshow various fixes and new features added since then.
$ strings /bin/* /sbin/* /usr/bin/* /usr/sbin/*|grep ,v
paints a pretty dismal picture.One interesting way to look at this. The first commit from freebsd for ls.c is:
Added Thu May 26 06:18:55 1994 UTC (21 years, 2 months ago) by rgrimes
Original Path: vendor/CSRG/dist/bin/ls/ls.c
File length: 13099 byte(s)
BSD 4.4 Lite bin Sources
The last commit apple has is: Modified Fri Jun 3 11:05:58 2005 UTC (10 years, 2 months ago) by dd
So apples version is almost closer in time to the original 4.4 sources as to the current version.In any case, why keep fiddling with the source code if the program does what it is intended to do?
$ du -hs big.log;time cat big.log > /dev/null
199M big.log
real 0m0.045s
user 0m0.002s
sys 0m0.043s
$ time gtr a b < big.log > /dev/null
real 0m0.334s
user 0m0.182s
sys 0m0.142s
$ time tr a b < big.log > /dev/null
real 0m33.105s
user 0m31.757s
sys 0m0.488s
$
I don't have a freebsd machine around to see if it's just apples tr that is broken.I'm sure it's related to unicode bullshit, but the usual env var tricks don't seem to help.
That bash version is actually very modern compared with their out-of-box experience.
I knew some sysadmins liked it. There definitely was a mindset of some admins that solaris boxes were great. You did a full install of solaris that took up like 8G of disk space. Then you installed oracle. Then you never touched the machine again. As long as you never actually needed to use the machine for anything, solaris was great.
Solid kernel.. terrible userland. Still some very smart people working on zfs/dtrace/kvm, will be intersting to see what the next few years bring.