Should I refer to my system as gnu/i3/systemd/Mozilla/Linux?
It's easier to refer to modular systems using the one guaranteed common element, in this case, the kernel. It's not necessary to specify every major user-space program.
It's more like this: the whole OS is GNU (the coreutils), minus the kernel (most of which is device drivers). That's why they do it. Or at least why there are those that are passionate about the naming.
Also the reason why, had 4.3BSD not been in legal limbo, we'd all most likely be using GNU/FreeBSD.
Upd: https://www.gnu.org/gnu/why-gnu-linux.html
Quote: Granted that the GNU Project deserves credit for this work, is it really worth a fuss when people don't give credit? Isn't the important thing that the job was done, not who did it? You ought to relax, take pride in the job well done, and not worry about the credit.
This would be wise advice, if only the situation were like that—if the job were done and it were time to relax. If only that were true! But challenges abound, and this is no time to take the future for granted. Our community's strength rests on commitment to freedom and cooperation. Using the name GNU/Linux is a way for people to remind themselves and inform others of these goals.
[1] Acronym for free/libre/open
Including mindbogglingly complex tools such as wc and y.
> most of which is device drivers
Dull stuff that every bootcamp graduate can write.
I think you've captured the essence of why people thing "GNU/Linux" is such a pedantic moniker.
but, it's not. you can use e.g. debian/kFreeBSD or debian/hurd and the actual day-to-day user experience is pretty much exactly the same
Seems a bit of a stretch to say that providing a bunch of command line utilities gives operating system naming rights.