Really wanting to patch that out completely, or at least change it to just "Linux".
@inference uname just does the uname syscall so that must be what kernel reports. I'm pretty sure you'll break some scripts if you change that as they check against exactly "GNU/Linux". Even openwrt on my router, which uses busybox and uclibc, responds with "GNU/Linux" to "uname -o" 🤷
@inference You can probably disable the uname syscall altogether when building kernel and it probably even makes sense from security standpoint, but again it'll probably break some scripts. If even android and openwrt have it, why shouldn't we? 🤔
@inference Yeah, I get your point, but by now it's probably just some legacy shit. Look at this: "Mozilla/5.0 (Linux; Android 4.0.4; Galaxy Nexus Build/IMM76B)
AppleWebKit/535.19 (KHTML, like Gecko)
Chrome/18.0.1025.133 Mobile Safari/535.19"
By now Chrome has nothing to do with neither of Mozilla, WebKit, Gecko or Safari — but it still has it in its User-Agent string for compatibility's sake.
I understand the "free software" stuff, but saying you're the god of an entire kernel or OS just because your software runs there (without even considering the *other* software other than yours!) is just arrogance at its finest.
I don't care what anyone says, it will *never* be GNU/Linux to me.
@inference Well, it's just like bad habits — bad decisions from the past that live on because everyone is too lazy to do anything about it 😅
What's funny is I took Chimera Linux's GRUB patch and applied it to my own system.
https://git.inferencium.net/inference/cfg/commit/f5ad77642faab52d0c976ffdbce2f32d8ec57564
@inference 🤣
Ha-ha, yeah Daniel is very eager to drop everything GNU in Chimera, I think he even managed to get rid of binutils!
How's the system in general, did you check it out? AFAIK he's going to give up maintaining Void PowerPC port starting 2023 and it looks like it's a nice migration path for me.
Chimera Linux looks great, and it even uses the same as me, but switches coreutils for the much better FreeBSD utils (I'm not a fan of Busybox).
@inference
Not that I'm against GNU, but I do run musl flavour of Void almost universally and I do use clang/llvm where applicable, but I'm not ready to drop GNU userland completely.
Maybe Chimera will make it easier for me. Daniel (the one behind VoidPPC and Chimera) hasn't decided yet whether he wants to support 32-bit PPC. PowerPC machines are my main concern right now, but there are no images yet. I should probably try building rootfs myself and see if it suits me.
> Not that I'm against GNU
I'm not against GNU, I'm against their politicisation of Linux and marking it as their territory.
> I'm not ready to drop GNU userland completely.
I'm still using coreutils because I don't like how Busybox works.
> support 32-bit PPC
64-bit has been around for 20 years now. I don't see an issue with not supporting it. I've dropped 32-bit from all of my systems, and all software I write/compile targets 64-bit only.
@inference
Nah, it's not that easy. One of the machines I'm using is an old MacMini. It has G4 CPU which itself is 32-bit. I still have this box and it hosts transmission-daemon, nitter instance, web proxy and a few other services. I sometimes use it as an access point for 802.11b devices not to mess with my router.
I should probably replace it with something more energy-efficient ARM-based, but I have too much on my plate right now to do that.
