@evana Knowing nothing about how garmin build firmware, my suspicion is it's something like: this is a list of all OSS present in their Yocto source tree, or similar. Rather than track what OSS makes it into which firmware builds for which SKUs, they just make a list of all OSS that gets too close to their build system, and put that one list in all products. But I dunno 🤷
Boring joke deflator: afaict it's just Garmin's standard wording so that they can splat in all licenses to everything involved in any of their products, rather than have to generate license compliance text specific to individual firmware builds. But also, lol
How to tell your OSS is ridiculously popular: people aren't 100% sure they _didn't_ embed it, and tack on the software equivalent of "packaged in a facility where peanuts were also present" to the license list.
This watch contains software, so statistically probably contains at least traces of curl.
@chimera_linux Yup, that is all very fair. A lot of the glibc dependence is self-reinforcing, the longer it's the only implementation the more it makes sense to depend on it deeper. Maybe this was fixable 10y ago, but I agree that it's not likely to change now.
@chimera_linux@valpackett@nogweii@bitprophet The section on non-portability is an accurate description of current reality, but maybe also misrepresents why. systemd+musl comes up on systemd-devel@ periodically, and the position is consistently that systemd uses posix APIs where possible. But if glibc provides something useful and generic (an old example from my email is parse_printf_format()), they're not going to implement their own, that should be on musl or some 3p shim.
@valpackett@nogweii@bitprophet@chimera_linux Yeah I wasn't sure about the atomic fedoras, but I think toolbox/distrobox is what's going to make me give them a try for at least some time. It captures some of the ways I like to run my computers reasonably well, and combined with Flatpak for apps I think I can run a computer like that.
Chimera is super interesting, but a lot of its design decisions make it very alien for non-free linux software, and I need a break from that for a while :)
@valpackett@nogweii@bitprophet@chimera_linux I don't love it, but realistically the linux target companies build for is ubuntu, so any system that doesn't look like ubuntu at the most basic layers (gcc, glibc, FHS layout etc.) is swimming upstream to get that stuff working. I've lived with that swimming upstream for several years, and my arms are tired 😂
Atomic Fedora with flatpak/toolbox feels like a better balance for me, because I can drop into near vanilla ubuntu when needed.
@chimera_linux@valpackett@nogweii@bitprophet Huh, I'm honestly surprised! I expected LLVM+musl to be a too different ABI to make app distribution stuff work right. Either there's less implicit dependency on gcc+glibc in the world than I thought, or y'all have done a lot of work make the worlds meet. Either way, it's very nice to hear :)
Chimera makes other choices that are very reasonable, but that I disagree with. So I think it's still not for me, but I'm glad it exists ❤️
@chimera_linux@valpackett@nogweii@bitprophet (in particular, I'm a huge fan of systemd, and so distros that don't use it are off the table. Chimera has a whole FAQ about it, so I won't relitigate in detail. I think it still perpetuates some unhelpful myths about systemd, but ignoring those small parts, I think Chimera's analysis is very reasonable, and what you ended up doing is a very valid point in the design space. I will definitely watch how it develops, but for now it's not for me)
The section about unrelated components (IMO) implies that you are forced to use all or nothing, which is one of the most commonly repeated myths about systemd (see also 1, 6, 12 in http://0pointer.de/blog/projects/the-biggest-myths.html). Maybe I'm reading too much between the lines, but I read that and think "oh the conflation of monorepo source organization and monolithic output again".
I do agree about various components being hit and miss though.
@bitprophet Genuinely exhausting. I'm picking my next OS in part based on whether I've ever heard _anything_ about it, on the theory that it means it has its house in order and isn't trying to sell me religion. That sounds like a nice place to be, for a while.
It's all over my feed already, but in case I get to give you good news: VOYAGER ONE LIVES! Its incredible team managed to work around the damaged region of memory, and they're getting engineering data back again!
So I guess a little orientation: there are 3 computer systems on Voyager, each one dual redundant.
The CCS (Computer Command System) is the probe's brainstem, it runs the overall show, afaict it's the one receiving and routing commands. It's an adapted CCS from the Viking program, and built to last. Notably, it uses plated wire memory. Similar to magnetic core memory, slower and low density by today's standards, but non-volatile and unbothered by harsh space weather.
@anymaw@dave_andersen Yeah, these feature checks usually work by compiling (and maybe running) a test program, to check that everything required is present. The original malicious commit that added this check explained that on some systems the header files for Landlock are present but Landlock doesn't actually work, so the configuration builds a test program to check if it actually works.
And yes, any failure is interpreted as the feature being unavailable :/
The poor original maintainer of xz is on it now, and has already found another "fun" thing: https://git.tukaani.org/?p=xz.git;a=commitdiff;h=f9cf4c05edd14dedfe63833f8ccbe41b55823b00 . The configure check for enabling the Landlock sandboxing facility was subtly broken, so that Landlock support would never get enabled. The original malicious commit landed around the same timeframe as the main backdoor, also at an abnormal time of day compared to the new maintainer's historical activity pattern.
Software developer by day, other kinds of nerd the rest of the time. ADHD says current hobbies are 3D printers, building CNC machines, old computers in space, and general shitposting on whatever grabs my interest.Nazis, TERFs, other terrible people: please go away, there's nothing for you here.