Could have sworn that the betacam format used in video production has very little in common with the betamax format sold to the public.
Apple would perhaps grok it, if they where at all interested in corporate IT. But they are a fashion boutique sidelining in IT.
Google and MS are software houses, as such they need the version churn to stay afloat.
Frankly the pure software house it a pox on the IT world.
That both the pid1 binary and that overall project is called systemd may be fueling the 4th point.
One reason i was told for them getting Moblin going originally was that Microsoft was unwilling to provide Windows support for a x86 chip without PCI device enumeration. Intel had removed that from their more mobile oriented Atom to save on overall battery drain.
I am not quite sure why Intel and Nokia partnered up, but Moblin1 had a fair bit of overlap with Maemo at the time (Both Debian based etc). By the time Meego had been formed Intel had moved to a RPM base for Moblin2 however. And things seems to have gone wonky from that point on.
Really hope not, as the last thing the world needs is another locked up portable media player with a mobile network connection.
I had high hopes for Around 3.x/4.0, but since then Google has bent over backwards to placate big media while trying to pass the changes off as security improvements.
I was recently corrected on the connection between Meego and Tizen. Apparently Meego was abandoned fully upon the foundation of Tizen, and the only connection between the two was that Intel was involved with both (tough they seem to have since pulled out of Tizen).
In essence the only remnant of Maemo/Meego is Sailfish, the continuation of Mer.
Yeah, except it started as a init. And the init binary is still called systemd. End result is that there is a logical confusion between systemd the init and systemd the project. A confusion that the proponents don't make any effort to clean up, and sometimes appear to even leverage as a cheap way to make opponents look bad.
But then the script backs away. Systemd comes with a massive warning that any changes done outside of systemd's toolchain will be overwritten by systemd. Meaning that once systemd has assumed control over your firewall, do not for one second attempt to adjust iptables directly.
I got the impression that the idea of only having a single cgroup manager has since been reversed.
but it require that a very specific process runs as pid1...
Not yet, but it will take over tty duties soon.
Systemd has long since surpassed launchd in terms of "features"...
Or they have taken Nixon's mad man thesis to the logical endpoint...
Also likely makes it that much harder to use smuggled in hardware to reach the outside world.