On Fri, 7 Aug 2015, Peter Ross wrote:
Written by Rick Moen
(Your point is of course well taken about the wrongheadedness of systemd-journald binary logfiles, which tells you all you need to know about the wisdom of entrusting system architecture to these particular coders.)
The problem seems that commercial (or more sinister?) interests at work so it is possible that such things are happening.
All major Linux distributions have systemd now at its core, and I do not see any hope that it becomes easier to run Linux without it.
The smartphone segment is more or less monopolised by Google-controlled Androids.
So it's not much different than, lets say, OpenSolaris, which was practically controlled by Sun, and with Oracle taking over, game over. Yes, it's not exactly dead but it's a fringe community which works on "the leftovers".
Systemd is too much of a disruptive beast to be tolerated in an open-minded Open Source community. It is more or less a hostile init ABI without certainty of reasonable stability for the surrounding environment.
For me, it leaves FreeBSD as the "largest company independent open source operating system" (well, maybe not very good wording but you may get what I mean).
I know there are things out there "just for Linux". But for many many things you can use FreeBSD and it works as well, or often better, than Linux does.
I've been shat off with Linux's virtual memory management since at least 2001. A whole bunch of things have started shitting me off more in the past few years. But everytime I try to install kfreebsd or the like, I hit the mundane realities of hardware support and the like. It feels like Linux circa 1998. What do you mean I can only have 1024x768 on my 1920x1200 laptop and it takes a minute to draw an xterm? Blah, time to take up motorcycle mechanic courses. -- Tim Connors