Slashdot Mirror
Matthew Garrett Forks the Linux Kernel
jones_supa writes: Just like Sarah Sharp, Linux developer Matthew Garrett has gotten fed up with the unprofessional development culture surrounding the kernel. "I remember having to deal with interminable arguments over the naming of an interface because Linus has an undying hatred of BSD securelevel, or having my name forever associated with the deepthroating of Microsoft because Linus couldn't be bothered asking questions about the reasoning behind a design before trashing it," Garrett writes. He has chosen to go his own way, and has forked the Linux kernel and added patches that implement a BSD-style securelevel interface. Over time it is expected to pick up some of the power management code that Garrett is working on, and we shall see where it goes from there.
It is now official. Netcraft has confirmed: Linux is dying
One more crippling bombshell hit the already beleaguered Linux community when IDC confirmed that Linux market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that Linux has lost more market share, this news serves to reinforce what we've known all along. Linux is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be the Amazing Kreskin to predict Linux's future. The hand writing is on the wall: Linux faces a bleak future. In fact there won't be any future at all for Linux because Linux is dying. Things are looking very bad for Linux. As many of us are already aware, Linux continues to lose market share. Red ink flows like a river of blood.
All major surveys show that Linux has steadily declined in market share. Linux is very sick and its long term survival prospects are very dim. If Linux is to survive at all it will be among OS dilettante dabblers. Linux continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, LInux is dead.
The ideal Linux kernel fork would panic if it detected a systemd infection.
Remember that forks sometimes do succeed.
Take Linux. It forked from OpenBSD which itself was forked from QNX with smatterings of FreeBSD code.
QNX programmed itself from vacuum tubes and trace wires left on the ground at Quantum Software in Ottawa one evening. Dan Hildebrand (RIP) apparently had something to do with this metamorphosis.
Meanwhile across the ocean, FreeBSD was forked from Windows 95 which itself came from the unholy union of MS-DOS and the GEM environment. MS-DOS was bought from a company in Washington State and was a fork of CP/M. GEM was a stand alone thing and should never have been born.
Where was I? Oh yeah, CP/M. CP/M was a copy of Apple's SOS used in the Apple
Apple SOS was a mix/fork of Apple ProDOS and TRS-80's OS; I forget the name, not important. Radio Shack forked their TRS-80 OS from some source code they saw in Lions' Commentary on UNIX 6th Edition.
Fact.
Trolling is a art,
You won't care. Not a single mainstream user of the kernel will switch to this fork.
Oh Ya? How about SJW Linux where all resources are shared and have equal priority!
Oh Ya? How about SJW Linux where all resources are shared and have equal priority!
For far too long, Linux has discriminated against "differently abled" code, with all its segregationist notions of kernel-vs-userspace. And even within userspace, could the very word "permissions" get any closer to "privilege"???
At long last, viruses we have historically relegated to the slums of Windows will finally have the right to run in the ivory sandbox of Linux - We need "Runtime Justice" for all code, whether CLI or GUI, whether drivers or devices, whether signed or malware!
There is no such thing as an "illegal" instruction!
That's the beauty of FOSS. If you're in a pissy, childish mood, you can take a copy of someone else's ball and go home to pout. :P
I do not fail; I succeed at finding out what does not work.
I forked the linux kernel in 1998, porting it to a new processor that the company I was working for was developing. Seventeen year later, linux appears to be fine in much the same way my old company isn't.