SoylentNews is people
SoylentNews
Longtime Debian contributor Tollef Fog Heen has announced his resignation from the Debian systemd maintainer team. His announcement states that "the load of the continued attacks is just becoming too much."
He has since written a detailed blog article surrounding the circumstances of his resignation. As he puts it,
I've been a DD for almost 14 years, I should be able to weather any storm, shouldn't I? It turns out that no, the mountain does get worn down by the rain. It's not a single hurtful comment here and there. There's a constant drum about this all being some sort of conspiracy and there are sometimes flares where people wish people involved in systemd would be run over by a bus or just accusations of incompetence.
This is yet another dramatic event affecting the Debian project in recent months. The adoption of systemd has been extremely controversial, even going so far as to result in calls for Debian to be forked. There have been other problems as of late, too, ranging from a serious bug breaking Wine just days before the Jessie freeze deadline, to the possibility of Debian GNU/kFreeBSD being dropped from Debian 8. And it was only just over a week ago that Joey Hess — another longtime Debian contributor — left the project, citing the "very unhealthy directions" that Debian has been led in lately.
Is the internal tension and strife caused by systemd about to tear the Debian project apart? Recent events such as the aforementioned have suggested that this is becoming more and more of a possibility. The repercussions of this drama will no doubt be felt wide and far, given Debian's own popularity, as well it forming the basis of other major Linux distros such as Ubuntu and Linux Mint.
(Score: 3, Insightful) by c0lo on Monday November 17 2014, @11:45AM
Well, so what?
I'm gonna try BSD anyway... hope it works for me and I can let those drama queens behind. It was their choice, they'll have to live with it.
https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
(Score: 1) by radu on Monday November 17 2014, @12:38PM
I read this a lot during the last few month and kept waiting for someone mentioning servers. Didn't happen so I'll start here, even if it's not quite on topic.
I'm running a few VPS, no host seems to be offering BSD, only different Linux flavors. At least not in the price range I'm paying now (~5-15€/month for 512-2048MB RAM). Gentoo and/or Slackware (no plans to default to systemd yet) are also quite difficult to find (and somehow more difficult to administrate)
What do we do when/if no wide-spread Linux distribution without systemd is available any longer?
(Score: 2) by c0lo on Monday November 17 2014, @12:54PM
E.g. https://forums.freebsd.org/threads/freebsd-hosting-shared-vps-etc.21472/ [freebsd.org]
Seems many are Europe based.
https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
(Score: 1) by SNK on Monday November 17 2014, @01:09PM
You might want to try RamNode http://www.ramnode.com [ramnode.com]
It is even cheaper if you take 5 mins to google for discount coupons.
(Score: 2) by Geotti on Monday November 17 2014, @04:53PM
Thanks!
(Score: 5, Interesting) by zocalo on Monday November 17 2014, @01:12PM
Downsides... Well, there was obviously a learning curve, but nothing a competent *NIX admin would struggle with; no different from moving between any two unicies, really. We also have some COTS software which either won't run on BSD (not yet really looked into why that is in most cases) or runs but isn't supported/certified on BSD (in discussion with the vendors), but we're mostly still working through the standard builds that are easy migrations at the moment. We also have some systems that are so crufty and/or reliant on Linux specifics that we've not even considered moving them to BSD yet, plus personal preference - several of our staff are sticking with Linux on their desktops and we'll also be maintaining some Linux servers for testing & development work in addition to any production servers we can't migrate.
UNIX? They're not even circumcised! Savages!
(Score: 2) by forsythe on Monday November 17 2014, @03:53PM
I'm simply replying to this post because it's the first reply I happened to see using the spelling, but why are so many posters calling the software ``systemD?'' It seems to call itself ``systemd'' pretty clearly, for example in the Wikipedia entry [wikipedia.org], where I would expect to find the correct capitalization.
(Score: 2) by novak on Monday November 17 2014, @05:51PM
Maybe it was a typo and he meant to write substance D. http://en.wikipedia.org/wiki/A_Scanner_Darkly [wikipedia.org]
I think it fits. Substance D splits the two hemispheres of the brain, causing them to conflict, not unlike the two camps in the linux world.
novak
(Score: 2) by GungnirSniper on Monday November 17 2014, @06:31PM
Capitalizing the D makes it look less like a typo if you are already capitalizing the S in System per English language conventions for proper nouns.
Tips for better submissions to help our site grow. [soylentnews.org]
(Score: 2) by fnj on Monday November 17 2014, @09:39PM
Rather than get bogged down in whether systemd is a proper noun or not, I would just settle for long established Unix-type-OS practice. Other damons are not capitalized; it's "httpd" and "smtpd". It gives of a dumb hick smell to spell it System-D. In fact executables in general are not capitalized; it's "cp" and "rm".
freedesktop.org's systemd home page [freedesktop.org] even tells you how to spell it.
"Spelling
"Yes, it is written systemd, not system D or System D, or even SystemD. And it isn't system d either. Why? Because it's a system daemon, and under Unix/Linux those are in lower case, and get suffixed with a lower case d. And since systemd manages the system, it's called systemd. It's that simple."
(Score: 0) by Anonymous Coward on Tuesday November 18 2014, @04:17AM
As an intact Christian, your use of daemonic eunuchs disgusts me.
(Score: 2) by Pav on Monday November 17 2014, @12:50PM
BSD is not an answer for many of us. Desktop FreeBSD collapsed in a sad heap as soon as Apple decided to hire away key developers, and it has never really recovered. Was anyone surprised? In the early 90's when I discovered Unix Linux was fresh on the scene. The kernel only started getting a following because the GPL stopped closed forks (which was a big deal during the Unix wars) and the codebase didn't have the legal worries that came with BSDs commercial heritage. BSD was superior in almost every way, but developers voted with their feet. The second round of legal wrangling over BSD in 2003 seemed to be the final nail, at least among people I knew.
Perhaps the snarling and baring of teeth comes when paycheques and contracts are at stake. The Redhat and Ubuntu guys certainly seem to have invaded Debian and changed its ethos - Debian was a cooperative and volunteer-friendly distro for much longer than most of the others. I don't think the move-or-not to systemd would have been a problem once upon a time. Its hard to believe how much the culture of Linux as-a-whole has changed. I must admit I'm understanding the anger that had RMS performing coding-marathons against the commercial outfits, and mourning the non-commercial cooperative hacker culture at the AI lab. I just wish I had RMSs talent. ;) Still, I do what I can, and will lend my very small weight to any freedom-supporting alternative that respects its users.
(Score: 0) by Anonymous Coward on Monday November 17 2014, @12:58PM
That's all entirely your own fault. I invested in OpenBSD years ago and they are the same unmarketable asshole pricks as they were back then. Not even TSLA comes close.
(Score: 2) by c0lo on Monday November 17 2014, @01:02PM
I'm gonna try anyway. I intend to start with the LXDE port for FreeBSD [lxde.org]
https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
(Score: 1) by SNK on Monday November 17 2014, @01:17PM
Just make sure that you use pkg instead of pkg_add as mentioned in the LXDE manual.
(Score: 2) by c0lo on Monday November 17 2014, @01:21PM
https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
(Score: 3, Informative) by fnj on Monday November 17 2014, @08:48PM
You might also consider PC-BSD. It is FreeBSD with mostly, but not all, FreeBSD packages, configured with a graphical installer to end up with a perfectly working DE with zero tinkering or intervention. When I say it is FreeBSD, I mean it. Complete with freebsd-version and freebsd-update. They maintain their own package repo though.
The usual precautions to make sure you have supported hardware apply - particular attention to graphics and WiFi hardware.
(Score: 0) by Anonymous Coward on Monday November 17 2014, @03:24PM
Well said and thank you.
(Score: 2) by fnj on Monday November 17 2014, @08:52PM
Nonsense. No it didn't. FreeBSD is still very much alive and actively developed. I'll give you that desktop installations are not the raison d'etre or prime focus. For that you have the PC-BSD customized FreeBSD.
(Score: 0) by Anonymous Coward on Tuesday November 18 2014, @03:47AM
Not churning the desktop is a feature. Innovation isn't needed there, it is a solved problem. It works just like it always did, and it did always work.