You're viewing a single thread.
Permanently Deleted
It's not unusual to see people talking about android users being Linux users "because android is Linux too" clearly not understanding the difference between Linux the OS, i.e. GNU/Linux, and Linux the kernel. So it's useful when you have to make such a distinction.
Exactly. When I say I want a Linux phone all I get are Android options. What I want is a GNU/Linux phone that I can run full Linux distros on.
Alpine or PostmarketOS works for older stuff. Some others will run Ubuntu as well.
Instead of "Linux on [phone]" try using Debian/Ubuntu or one of the mobile-targeting distros as a keyword
Alpine
Alpine is also arguably not "GNU/Linux", as it doesn't use GNU Core Utils or glibc. But I don't know anyone who would suggest that Alpine isn't "proper Linux".
Permanently Deleted
You are right, you're right to say it, and you're probably handsome as well.
Unfortunately for them this means that 99.99% of the Linux distributions out there do not qualify as >GNU/Linux, even the ones like Debian, Red Hat, or Ubuntu that did adopt the GNU/Linux name >scheme, because they all host, promote, or allow users access to non-free software in some way.
You are totally confused. In words of R. Stallman:
"The kernel is an essential part of an operating system, but useless by itself; it can only function in the context of a complete operating system. Linux is normally used in combination with the GNU operating system: the whole system is basically GNU with Linux added, or GNU/Linux. All the so-called “Linux” distributions are really distributions of GNU/Linux".
"Today there are many different variants of the GNU/Linux system (often called “distros”). Most of them include nonfree programs".
Permanently Deleted
I recently found myself forced to give a shit, when one of our projects started doing weird shit after switching to an Alpine-based docker image.
Can you elaborate? I'm aware alpine uses non-GNU stuff like musl & busybox. But overall, they're not too far off.
It was a dependency resolution issue. Npm couldn't install one of the packages without some package.json gymnastics, and those same gymnastics somehow fucked with our debian based images that we use for development. I can't say much more because I honestly don't know what exactly happened. I just diagnosed the issue and forwarded it to our resident node guru, who took it from there.