-11
Should we use *Linux when referring to the entire system, instead of Linux? (lemmy.ca)
submitted 4 days ago* (last edited 4 days ago) by thatonecoder@lemmy.ca to c/linux@programming.dev
17 comments fedilink hide all child comments

I've been thinking about the best way to refer to systems that use the Linux kernel, whilst avoiding the confusions that come with using the latter for both meanings. Since there are GNU and non-GNU (e.g, Alpine Linux) systems, I assume that *Linux would cover both. However, for users without a technical background, the asterisk means much less than it does to developers — this seems self-deprecating, considering that the point of the suggested term is to avoid confusion for NON-TECHNICAL users. Am I overthinking?

you are viewing a single comment's thread
view the rest of the comments
[-] neidu3@sh.itjust.works 40 points 4 days ago* (last edited 4 days ago)

You're overthinking. Non-technical people don't care aboutthe difference.

[-] jonathan@lemmy.zip 42 points 4 days ago

I am technical person and I don't care either.

[-] neidu3@sh.itjust.works 15 points 4 days ago* (last edited 3 days ago)

Good point. I've just gotten used to the fact that gnu-everything is required to compile gnu-anything, both gnuseful and gnuseless, but you eventually realize that you have the wrong version of gnu-something. So I stopped caring after dicking around with dependency resolutionfor far too long to make it work. Gnu is like furniture (Gnurniture) to me - it's just there, and the less I have to think about it living in my gnuserspace, the better.

load more comments (1 replies)
load more comments (2 replies)
this post was submitted on 14 May 2025
-11 points (35.1% liked)

Linux

7354 readers
236 users here now

A community for everything relating to the GNU/Linux operating system

Also check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev