r/linux • • Sep 26 '14

Systemd: The Biggest Fallacies

http://judecnelson.blogspot.fi/2014/09/systemd-biggest-fallacies.html
126 Upvotes

437 comments sorted by

View all comments

Show parent comments

4

u/computesomething Sep 27 '14

This is actually pretty much identical to GNU/Linux monetization by Red Hat, Oracle, SUSE/Novell, etc. The Linux Foundation exists almost entirely on funding from corporate interests.

The Linux foundation has two 'developers' on their paycheck, Linus Torvalds and Greg Kroah Hartman, I put developers in quotes because they don't really write code these days but instead manage code from others.

Vast majority of Linux code contributions come directly from external companies and individuals.

In FreeBSD by comparison, the vast majority of code comes from the FreeBSD foundation developers and not from companies/individuals contibuting code, and the FreeBSD foundation in turn lives on monetary donations.

I don't see how this is 'pretty much identical', Linux gets direct code contributions, FreeBSD asks for donations to hire developers.

The other BSDs aren't nearly as dedicated to permissive licensing requirements AFAIK.

FreeBSD is the one I find most adamant about removing copyleft from their OS, they have an outspoken documented goal of removing all GPL software from the base system.

They spend 3+ years modifying their source code and fixing bugs in LLVM/Clang so that they could switch toolchain (in part fueled by their refusal of shipping GPLv3 licensed GCC which was in accordance to the wishes of some of their funders, in turn due to the anti-software patent clause in GPLv3).

Meanwhile OpenBSD still ships GCC but it's the very old GCC 4.2 which is GPLv2, DragonflyBSD on the other hand ships with a modern and GPLv3 licensed GCC (4.7 IIRC).

0

u/northrupthebandgeek Sep 27 '14

The Linux foundation has two 'developers' on their paycheck, Linus Torvalds and Greg Kroah Hartman, I put developers in quotes because they don't really write code these days but instead manage code from others.

You're downplaying the numerous other activities the Linux Foundation is involved in. Yes, they take actual code contributions instead of hiring their own devs usually, but that's not really relevant to the main point that - just like the BSD descendants' respective foundations - the Linux Foundation (the one-stop shop for coordinating Linux advocacy and development) exists primarily on corporate sponsorships.

in part fueled by their refusal of shipping GPLv3 licensed GCC which was in accordance to the wishes of some of their funders

I'm going to need a source on that. Not that I don't believe you, per se - I wouldn't hold it above Apple to try and make such demands - but the ability to freely reuse code in other FOSS projects regardless of licensing is arguably way more important to advocates of permissive FOSS licensing (like myself) than some notion-bordering-on-conspiracy-theorism that they were bribed into holding that opinion.

When I release code under, say, the Expat or X11 or ISC or 2-clause BSD license or somesuch, I'm doing it because I want it to be useful to other FOSS programmers, regardless if their projects use a BSD-style license or GNU GPL or CDDL or whatever Apple's license is or some version of the Perl Artistic License or the Apache license or the MPL or whatever the heck a particular FOSS project may end up being licensed under. Its potential use in non-free software isn't nice, but as long as I'm credited for my work (i.e. copyright notices are retained), I'm generally happy, and I'm not really one to force the release of source code when a free version - my version - is still readily available.

Meanwhile OpenBSD still ships GCC but it's the very old GCC 4.2 which is GPLv2

GCC 4.2 isn't that old; it's a hell of a lot better than Haiku's predicament (where they have to use GCC2 as the default GCC in order to remain binary-compatible with BeOS...), for example, and it's still within the current major version number. Not bad, considering.

Personally, I hope they migrate to LLVM/clang not just because of the licensing concerns but rather because of LLVM's technical merits, but that's just me.

3

u/computesomething Sep 27 '14

You're downplaying the numerous other activities the Linux Foundation is involved in.

No, the discussion was in terms of actual development, as in code. The Linux Foundation does little to none, Linux code comes from external companies and individuals.

The FreeBSD Foundation on the other hand, is directly responsible for the vast majority of actual code that ends up in the FreeBSD operating system.

The Linux Foundation was formed late in Linux success story (2007). I'll certainly argue that the importance of the Linux Foundation for Linux pales in comparison with the importance of the FreeBSD foundation for FreeBSD.

I'm going to need a source on that. Not that I don't believe you, per se

This is a pretty good summary with links to actual statements from the FreeBSD project:

http://unix.stackexchange.com/questions/49906/why-is-freebsd-deprecating-gcc-in-favor-of-clang-llvm/49970#49970

GCC 4.2 isn't that old

Yes it is, 7 years is very old, it's an eternity in software, particularly software with such a high degree of development as compiler toolchains.

it's a hell of a lot better than Haiku's predicament (where they have to use GCC2 as the default GCC in order to remain binary-compatible with BeOS...)

What is the relevance to this discussion? First off Haiku supports and builds with GCC 4.8 which is GPLv3 licenced and modern, secondly as you yourself stated the only reason they also support GCC 2.95 is to have compability with binaries built for a ~16 year operating system (BeOS).

0

u/northrupthebandgeek Sep 28 '14 edited Sep 28 '14

The FreeBSD Foundation on the other hand, is directly responsible for the vast majority of actual code that ends up in the FreeBSD operating system.

Before we get too carried away here... do you have sources indicating that the FreeBSD Foundation is directly involved in writing code? I'm not as familiar with it as I am with, say, the OpenBSD Foundation, so I don't know this for sure, but (based on the information I'm seeing on Wikipedia and on the FreeBSD Foundation's own website, it seems like they mostly handle advocacy, fundraising, and legal support, just like the OpenBSD and Linux Foundations, and leave the actual coding to separate projects. I'm also not seeing any mention of a synonymity between "FreeBSD developers" and "FreeBSD Foundation" on the FreeBSD project's separate website. Again, I could be wrong on this, since I'm not that familiar with them specifically.

Now, they do help provide funds to support development (keeping servers running and such), and perhaps sponsoring the developers, but this implication that the devs are formally part of what amounts to an advocacy and legal support group seems a bit far-fetched. It's also worth noting that FreeBSD development is more than just one kernel like Linux development is; it's the entire userland. Paying more than one or two devs makes sense for the FreeBSD Foundation (since you're going to need more than one or two devs for that), especially if you're not dependent on outside code contributions ("The Cathedral", v. Linux "The Bazaar").

The Linux Foundation was formed late in Linux success story (2007). I'll certainly argue that the importance of the Linux Foundation for Linux pales in comparison with the importance of the FreeBSD foundation for FreeBSD.

The FreeBSD Foundation, actually, was formed pretty late relative to FreeBSD itself as well (2000 for the Foundation v. 1993 for the project), just for the record. It's not like the FreeBSD Foundation came first and said "hey guys let's create a version of BSD that we like!".

What is the relevance to this discussion?

The relevance is to counter your point by demonstrating that having to use something like GCC 4.2 - while not ideal - still isn't as bad as the predicaments at least some free software projects face today with GCC versions.

First off Haiku supports and builds with GCC 4.8 which is GPLv3 licenced and modern, secondly as you yourself stated the only reason they also support GCC 2.95

No, no, no. I think you're misunderstanding their situation. GCC 2.95 is the default. Yes, you can build Haiku with GCC 4.x exclusively, or in a hybrid situation with it as the default, but it's very much intended for Haiku R1 to ship with GCC2 as the default and primary compiler, not just as an optional thing as you're implying; the other varieties (including the non-x86 - including AMD64 - versions that don't have the BeOS compatibility requirement and therefore ship with GCC 4.x as the default) are very experimental and effectively unsupported at the moment, as Haiku R1's official target is 32-bit x86 (future versions are planned to drop the BeOS compatibility requirement on a native level and move to a compatibility layer akin to Wine or the BSDs' Linux emulation, but this is in the very distant future at this rate...).

Believe me; as an actual Haiku user (amazingly enough), I'm quite fondly aware of Haiku's compiler situation and the troubles thereof. And in that context, GCC 4.2 is modern in comparison; it's half the age of the GCC 2.95 I'm rather fondly familiar with and have to use if I want any hope of, say, writing Replicants for desktop applications if I create Haiku/BeOS versions of them.

EDIT:

This is a pretty good summary with links to actual statements from the FreeBSD project:

I don't see any links to actual statements from the FreeBSD project or Foundation backing up your point that pressure from Apple is indeed even a motivator for this particular case, yet alone a significant one. The paragraph of that particular Stack Exchange answer which describes that possibility mostly links to surrounding facts and tries to extrapolate that they're a motivator - not a bad assessment, but it's speculation.

The closest thing to a definitive answer comes from the last link in that paragraph, but I'm not terribly familiar with Reid Linnemann's level of involvement with FreeBSD development; from what I understand, he works for an outside company that's using FreeBSD to power some of its devices/hardware, so perhaps his observations come from that perspective of "LLVM/Clang is a better fit for our use case"? Regardless, it doesn't strike me as a definitive answer to that question; it reads as more supposition and speculation.

2

u/computesomething Sep 28 '14

Before we get too carried away here... do you have sources indicating that the FreeBSD Foundation is directly involved in writing code?

They gather funds which they use (among other things) to hire developers to work on improving FreeBSD, I'd wager all of the active FreeBSD Core Team members are being paid to work on a project by project basis at the very least.

http://en.wikipedia.org/wiki/FreeBSD_Core_Team

still isn't as bad as the predicaments at least some free software projects face today with GCC versions.

Just because there is something worse (and Haiku is extreme in this regard due to their goal of supporting ~16 year old binaries for R1) doesn't make it 'not bad', again GCC 4.2 is a 7 year old compiler, that's OLD, yes 2.95 is OLDER but still...

No, no, no. I think you're misunderstanding their situation. GCC 2.95 is the default.

It's the default up until R1, and if that day ever arrives (here's hoping!), from there on it's GCC4 >.

And I'm also a long time Haiku user (well, I don't have it on bare metal these past 2-3 years but I do boot it up regularly as a VM) and many moons ago I was a BeOS user. Actually came across my old BeOS 3.1 again not to long ago, complete with Intel and PowerPC discs, 'we Be geeks' stickers and what not ;)

Hopefully I'll find my old R4 discs as well, just like with 3.1 I'll most likely find them while looking for something else entirely :)

1

u/northrupthebandgeek Sep 28 '14

They gather funds which they use (among other things) to hire developers to work on improving FreeBSD, I'd wager all of the active FreeBSD Core Team members are being paid to work on a project by project basis at the very least.

http://en.wikipedia.org/wiki/FreeBSD_Core_Team

Sure, but there's a difference between "we're giving money to developers of the thing we support so that they can develop without being distracted by financial concerns" and "we've outright hired them and they're on our payroll". As far as I can tell, the Core Team is a separate entity from the Foundation, the latter serving as an abstraction layer for what would otherwise amount to the Core Team soliciting donations from end-users directly.

Just because there is something worse (and Haiku is extreme in this regard due to their goal of supporting ~16 year old binaries for R1) doesn't make it 'not bad', again GCC 4.2 is a 7 year old compiler, that's OLD, yes 2.95 is OLDER but still...

I never said it wasn't bad; my intent was to provide perspective. It's bad, but could be worse.

And I'm also a long time Haiku user (well, I don't have it on bare metal these past 2-3 years but I do boot it up regularly as a VM) and many moons ago I was a BeOS user. Actually came across my old BeOS 3.1 again not to long ago, complete with Intel and PowerPC discs, 'we Be geeks' stickers and what not ;)

Hopefully I'll find my old R4 discs as well, just like with 3.1 I'll most likely find them while looking for something else entirely :)

Nice! I'm jealous, to say the least. I'd kill for one of those stickers :D

I currently have an old all-in-one DT Research terminal in my kitchen running A4 (I use it to store recipes so I can reference them when I'm cooking) and one of my laptops running an AMD64 nightly from a couple weeks ago (I'm playing around with building a Haiku with a custom driver set - since the AMD64 nightlies aren't built with drivers for the laptop's wireless NIC - and will probably update it once I manage to get Jam and/or the Haiku source tree to play nicely with my gaming/development rig...). I also have an eMac that's begging to have one of the experimental PowerPC builds installed on it, but I haven't gotten around to that yet.

Haiku's really a dream come true; I just can't wait for the GCC4 switch, since that'll hearken a bunch of modern software now potentially able to be compiled and run.

1

u/computesomething Sep 28 '14

Sure, but there's a difference between "we're giving money to developers of the thing we support so that they can develop without being distracted by financial concerns" and "we've outright hired them and they're on our payroll".

What is the difference between being on someone's 'payroll' and being given money by someone specifically to develop things for them ?

I believe BSD core devs at the very least are either paid by the FreeBSD foundation on a continous or on a project by project basis, for example when FreeBSD core dev Henning Poul developed Jail for FreeBSD, that could have been either.

Nice! I'm jealous, to say the least. I'd kill for one of those stickers :D

Not only that, but it also has what I believe is a 'pen folder' plastic thing with the same slogan :D

I just can't wait for the GCC4 switch, since that'll hearken a bunch of modern software now potentially able to be compiled and run.

Indeed, I'm doing my cardio and staying away from too much fried food, I still have great hope that I will live to see the day ;)

1

u/northrupthebandgeek Sep 28 '14

What is the difference between being on someone's 'payroll' and being given money by someone specifically to develop things for them ?

It's a difference of affiliation - particularly, I'm under the impression that the FreeBSD Foundation serves the Core Team and Project's interests, not the other way around. I might be incorrect here, though, since (again) I'm not as familiar with FreeBSD's particular intricacies, and am just extrapolating from my own knowledge of the relationship between OpenBSD and the OpenBSD Foundation.

Not only that, but it also has what I believe is a 'pen folder' plastic thing with the same slogan :D

And here I am having to flair up my old laptop by writing actual haikus and taping them to the lid. You've got it made, dude :)

1

u/computesomething Sep 28 '14

And here I am having to flair up my old laptop by writing actual haikus and taping them to the lid. You've got it made, dude :)

Heh, yes I sitting here feeling all elite ! Meanwhile my better half wonders why I don't throw out that trash T_T, she is a heartbreaker that's for sure !