If we are marking the birth of Linux and trying to call it GNU / Linux, we should remember our history.
Linux was not created with the intention of being part of the GNU project. In this very announcement, it says ânot big and professional like GNUâ. Taking away the adjectives, the important bit is ânot GNUâ. Parts of GNU turned out to be âbig and professionalâ. Look at who contributes to GCC and Glibc for example. I would argue that the GNU kernel ( HURD ) is essentially a hobby project though ( not very âprofessionalâ ). The rest of GNU never really not that âbigâ either. My Linux distro offers me something like 80,000 packages and only a few hundred of them are associated with the GNU project.
What I wanted to point out here though is the license. Today, the Linux kernel is distributed via the GPL. This is the Free Software Foundationâs ( FSF ) General Public Licenseâarguably the most important copyleft software license. Linux did not start out GPL though.
In fact, the early goals of the FSF and Linus were not totally aligned.
The FSF started the GNU project to create a POSIX system that provides Richard Stallmanâs four freedoms and the GPL was conceived to enforce this. The âfreeâ in FSF stands for freedom. In the early days, GNU was not free as in money as Richard Stallman did not care about that. Richard Stallman made money for the FSF by charging for distribution of GNU on tapes.
While Linus Torvalds as always been a proponent of Open Source, he has not always been a great advocate of âfree softwareâ in the FSF sense. The reason that Linus wrote Linux is because MINIX ( and UNIX of course ) cost money. When he says âfreeâ in this announcement, he means money. When he started shipping Linux, he did not use the GPL. Perhaps the most important provision of the original Linux license was that you could NOT charge money for it. So we can see that Linus and RMS ( Richard Stallman ) had different goals.
In the early days, a âworkingâ Linux system was certainly Linux + GNU ( see my reply elsewhere ). As there was no other âfreeâ ( legally unencumbered ) UNIX-a-like, Linux became popular quickly. People started handing out Linux CDs at conferences and in universities ( this was pre-WWW remember ). The Linux license meant that you could not charge for these though and, back then, distributing CDs was not cheap. So being an enthusiastic Linux promoter was a financial commitment ( the opposite of âfreeâ ).
People complained to Linus about this. Imposing financial hardship was the opposite of what he was trying to do. So, to resolve the situation, Linus switched the Linux kernel license to GPL.
The Linux kernel uses a modified GPL though. It is one that makes it more âopenâ ( as in Open Source ) but less âfreeâ ( as in RMS / FSF ).
Switching to the GPL was certainly a great move for Linux. It exploded in popularity. When the web become a thing in the mid-90âs, Linux grew like wild fire and it dragged parts of the GNU project into the limelight wit it.
As a footnote, when Linus sent this announcement that he was working on Linux, BSD was already a thing. BSD was popular in academia and a version for the 386 ( the hardware Linus had ) had just been created. As BSD was more mature and more advanced, arguably it should have been BSD and not Linux that took over the world. BSD was free both in terms or money and freedom. It used the BSD license of course which is either more or less free than the GPL depending on which freedoms you value. Sadly, AT&T sued Berkeley ( the B in BSD ) to stop the âfreeââ distribution of BSD. Linux emerged as an alternative to BSD right at the moment that BSD was seen as legally risky. Soon, Linux was reaching audiences that had never heard of BSD. By the time the BSD lawsuit was settled, Linux was well on its way and had the momentum. BSD is still with us ( most purely as FreeBSD ) but it never caught up in terms of community size and / or commercial involvement.
If not for that AT&T lawsuit, there may have never been a Linux as we know it now and GNU would probably be much less popular as well.
Ironically, at the time that Linus wrote this announcement, BSD required GCC as well. Modern FreeBSD uses Clang / LLVM instead but this did not come around until many, many years later. The GNU project deserves its place in history and not just on Linux.
Something is open source or isn't. There's a set, binary definition.
I get the feeling you're implying a difference/aversion between those two terms which doesn't exist. This and the combination with a nonsensical statement about amount of GNU packages vs non-GNU packed makes it feel like you're pushing an agenda here: There's far more free software than just GNU's - that's a success for free software and the GNU project. There's no connect between the argument you're obviously implying.
Also HURD never took off - but why should it? The GNU project's goal is a fully free operating system, with Linux being persuaded to adopt a proper license there's no real need for HURD. It doesn't mean it isn't a fun project.
Which two terms? Everyone has an agenda but I am not sure what I am being accused of here. Do you mean Free Software vs Open Source? The FSF goes to great lengths to distinguish between those two terms:
The error is in saying something is made "more open source". The definition: https://opensource.org/osd/
Does your license uphold these rules? It's open source. Does it not? It isn't.
FSF and OSI have slightly different definitions for software. FSF believes in free and open source software (copyleft i.e. GPL) whereas OSI believes in permissive, open source licenses (i.e. MIT/BSD).
In the 1990s, they had disagreements against each other because FSF and Stallman believe in FLOSS/FOSS and free software advocacy politics. OSI was more concerned with open source workflows and not with free software advocacy politics, which was initially more popular with businesses.
That is not correct. Who is this "they" you are talking about? The OSI?
Open source is a term with a definition - which has been written by software freedom advocates by the way.
With free software you have politics and a philosophy, in which somebody can have more freedom or less with a piece of software. I really wouldn't confuse that with the practicability of the OSI definition.
Copyleft or push-over is a whole separate topic. Copyleft might be favoured by software freedom enthusiasts, but I disagree with your idea of separation through that. Even if you don't care about software freedom, you could like the practical effects of the AGPL.
I feel like you're spreading at least misguiding information here.
The BSD license allows incorporation of BSD code in non-free projects. That was both an advantage for capitalists while simultaneously moving hobbyists away from it's development. Kind of an important bit of info.