shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

267
active users

#glibc

2 posts2 participants0 posts today
Replied in thread

@static @Noisecolor personally I think that every package should come statically compiled with it's own dependencies since #GlibC tends to constantly brick shit with minor.version updates and nonchalantly tell people to "just recompile"...

That's why I want statically-linked binaries for @OS1337 because that removes headaches...

Replied in thread

@mrmasterkeyboard @landley My choice of @musl for @OS1337 is because I want my stuff to be statically linked and not every minor update to have the risk to brick shit, because #GlibC is notorious for that since the #GNU project are nonchalantly thinking "just recompile it" is a valid excuse.

  • Espechally since (for better or worse) not everything is (A)GPL(v3)-licensed and prople may need to deal with #binaries and/or #CCSS because in many cases patents and licensing are not allowing the distribution of it.

I mean, we all 'loved' to live in a world where this wasn't the case but if I were to like deal with a vocoder for MELP, AMBE or TWELP I'm pretty shure I'd never ever be allowed to distribute it's source code, even for "clients exempted from the need to obtain licensing"...

en.wikipedia.orgMixed-excitation linear prediction - Wikipedia
Replied in thread

@lmemsm basically the Idea behind it is to be a brutally simple #toybox + #musl / #linux distro that grew out of the necessity for me to actually think about #firmware for some projects.

Basically I want something that is so simple and auditable that it's practical to make it pass any #verification demands for #SecureTerminal|s in #CriticalInfrastructure and #Communications.

  • OFC one may point at my other projects and say: "Why don't you just put #RaspberryPiOS on a #microSD?" ignoring that the smallest image is >330MB in size and that seems kinda overkill for essentially my demands for a minimalist #Linux with very few programs in userspace.

Not to mention a #GNUfree - #Linux distro is the way to go if I want that thing to not get bricked constantly by minor #GlibC-changes...

  • End goal is something akin to #MSDOS in it's brutal simplicity, but way more extendable.

I hope that answers your question...

  • Sorry for the delay.
Infosec.SpaceOS/1337 (@OS1337@infosec.space)1.38K Posts, 42 Following, 192 Followers · A minimalist musl + toybox/Linux Distribution focussed on being the bare minimum of a useable desktop whilst making most of the space it does. like/star ≠ endorsement, but acknowledgement of being read.

All I want is just a collection of #binutils, #GCC, #llvm+#clang, #glibc and #musl that are "free standing" / relocatable, which I can pack into a #squashfs image to carry around to my various development machines.

You'd think that for something as fundamental as compiler infrastructure with over 60 years of knowledge, the whole bootstrapping and bringup process would have been super streamlined, or at least mostly pain free by now.

Yeah, about that. IYKYK

Continued thread

Solved! 🥳

This was a pretty "interesting" bug. Remember when I invented a way to implement #async / #await in #C, for jobs running on a threadpool. Back then I said it only works when completion of the task resumes execution on the *same* pool thread.

Trying to improve overall performance, I found the complex logic to identify the thread job to put on a pool thread a real deal-breaker. Just having one single MPMC queue with a single semaphore for all pool threads to wait on is a lot more efficient. But then, a job continued after an awaited task will resume on a "random" thread.

It theoretically works by making sure to restore the CORRECT context (the original one of the pool thread) every time after executing a job, whether partially (up to the next await) or completely.

Only it didn't, at least here on #FreeBSD, and I finally understood the reason for this was that I was using #TLS (thread-local storage) to find the context to restore.

Well, most architectures store a pointer to the current thread metadata in a register. #POSIX user #context #switching saves and restores registers. I found a source claiming that the #Linux (#glibc) implementation explicitly does NOT include the register holding a thread pointer. Obviously, #FreeBSD's implementation DOES include it. POSIX doesn't have to say anything about that.

In short, avoiding TLS accesses when running with a custom context solved the crash. 🤯

Replied in thread

@MichaelRoss something I have been trying to look for is a #Linux #ls that isn't depending on #glibc or another #libc implementation, the reason is there was some malware that attached itself to glibc and prevented you to see the directories and files it used and also the process directory in /proc
Had you a ls that wasn't built with glibc, then all the files and directories would be listed.

Debian LTS contributors released 46 Debian LTS Advisories about security updates for various packages in April 2025.

These include critical security bug fixes for jetty9, zabbix and glibc and more. Also several LTS contributors prepared packages for the recent point release of current stable Debian 12, with many prepared in conjunction with related LTS updates of the same packages.

Read more about this in our monthly report for April here: freexian.com/blog/debian-lts-r

This work is funded by Freexian's Debian LTS offering.

Your organization too can sponsor the Debian LTS (freexian.com/lts/debian/) and join the esteemed list of sponsors in the monthly report.

Freexian · Monthly report about Debian Long Term Support, April 2025Like each month, have a look at the work funded by Freexian’s Debian LTS offering. Debian LTS contributors In April, 22 contributors have been paid to work on Debian LTS, their reports are available: Adrian Bunk did 56.25h (out of 56.25h assigned). Andreas Henriksson did 15.0h (out of 20.0h assigned), thus carrying over 5.0h to the next month. Andrej Shadura did 10.0h (out of 6.0h assigned and 4.0h from previous period).

⚠️ Steam Will Stop Working on Outdated Linux Systems This August | Linuxiac

「 According to a recent announcement, the Steam client will no longer run on any distribution with a GNU C Library (glibc) version older than 2.31 starting August 15, 2025.

Users who stay on an outdated toolchain will find not only Steam but also any purchased games unable to launch until the underlying operating system is upgraded 」

linuxiac.com/steam-will-stop-w

Linuxiac · Steam Will Stop Working on Outdated Linux Systems This AugustStarting August 15, 2025, Steam will no longer work on Linux systems using glibc older than version 2.31.
#steam#glibc#linux
Replied in thread

@landley @burnoutqueen Yeah...

#GPLv3 is a desaster as it's 99% ideology and 1% license text and alongside #AGPLv3 completely ignores the reality of how #licensing and #patents and #IP works.

  • Not that I like the status-quo, but we'd rather see businesses steer clear of anything GPLv2+ or GPLv3 or worse.

And on the flipside we basically get "source available" stuff like #SSPL which only serves as a means to commit #AssetDenial and monopolize commercial offerings...

Replied in thread

@krishean that's not how #systemd works.

SystemD was created because #SysVinit was shit and noone fixed it or made something better.

#Wayland is the future as #Xorg is being #EoL'd.

  • #Linux as a Kernel works fine, so no reason to replace it.

For the shitty #GlibC we have alternatives like #bionic and espechally #musl!

youtube.com/watch?v=o_AIw9bGogo