Shakedown Social

1 post1 participant0 posts today

SourcewareThe next GNU Tools Cauldron, taking place in Porto, Portugal, on September 26-28, 2025.<a href="https://inbox.sourceware.org/gcc/87o6ubhn4j.fsf@oracle.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://inbox.sourceware.org/gcc/87o6ubhn4j.fsf@oracle.com/</a> <a href="https://gcc.gnu.org/wiki/cauldron2025" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gcc.gnu.org/wiki/cauldron2025</a> <a href="https://gnu-tools-cauldron.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gnu-tools-cauldron.org/</a>Some <a href="https://fosstodon.org/tags/Sourceware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Sourceware</a> Project Leadership Committee members and <a href="https://social.sfconservancy.org/users/conservancy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@conservancy</a> staff should also be there.<a href="https://fosstodon.org/tags/GCC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GCC</a> <a href="https://fosstodon.org/tags/GDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GDB</a> <a href="https://fosstodon.org/tags/binutils" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#binutils</a> <a href="https://fosstodon.org/tags/CGEN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CGEN</a> <a href="https://fosstodon.org/tags/DejaGnu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DejaGnu</a> <a href="https://fosstodon.org/tags/newlib" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#newlib</a> <a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://fosstodon.org/tags/poke" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#poke</a> <a href="https://fosstodon.org/tags/libabigail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libabigail</a> <a href="https://fosstodon.org/tags/elfutils" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#elfutils</a>

Kevin Karhan :verified:<a href="https://cuties.cloud/@ULTROS_PROFESSIONAL" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ULTROS_PROFESSIONAL</a> <a href="https://studio8502.ca/@mos_8502" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mos_8502</a> yeah. <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GlibC</a> randomly bricks shit at minor version updates.Their response: "JuSt ReCoMpIlE!"

Kevin Karhan :verified:<a href="https://mastodon.social/@mrmasterkeyboard" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mrmasterkeyboard</a> <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> My choice of <a href="https://social.treehouse.systems/@musl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@musl</a> for <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a> is because I want my stuff to be statically linked and not every minor update to have the risk to brick shit, because <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GlibC</a> is notorious for that since the <a href="https://infosec.space/tags/GNU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNU</a> project are nonchalantly thinking "just recompile it" is a valid excuse.<ul><li>Espechally since (for better or worse) not everything is (A)GPL(v3)-licensed and prople may need to deal with <a href="https://infosec.space/tags/binaries" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#binaries</a> and/or <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCSS</a> because in many cases patents and licensing are not allowing the distribution of it.</li></ul>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 <a href="https://en.wikipedia.org/wiki/Mixed-excitation_linear_prediction" rel="nofollow noopener noreferrer" target="_blank">MELP</a>, <a href="https://en.wikipedia.org/wiki/Multi-Band_Excitation" rel="nofollow noopener noreferrer" target="_blank">AMBE</a> or <a href="https://twelp.pro" rel="nofollow noopener noreferrer" target="_blank">TWELP</a> 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"...

Kevin Karhan :verified:<a href="https://fosstodon.org/@lmemsm" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lmemsm</a> basically the Idea behind <a href="https://infosec.space/@OS1337" rel="nofollow noopener noreferrer" target="_blank">it</a> is to be a brutally simple <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toybox</a> + <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#musl</a> / <a href="https://infosec.space/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> distro that grew out of the necessity for me to actually think about <a href="https://infosec.space/tags/firmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#firmware</a> for some projects. <ul><li>And lets just say I did saw <a href="https://fosstodon.org/@w84death" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@w84death</a> 's <a href="https://infosec.space/tags/Floppynux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Floppynux</a> and <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> did present <a href="https://www.youtube.com/watch?v=SGmtP5Lg_t0" rel="nofollow noopener noreferrer" target="_blank">a</a> <a href="https://www.youtube.com/watch?v=MkJkyMuBm3g" rel="nofollow noopener noreferrer" target="_blank">lot</a> of convincing arguments <a href="https://www.youtube.com/watch?v=Sk9TatW9ino" rel="nofollow noopener noreferrer" target="_blank">alongside a literal walktrough</a> to get started.</li></ul>Basically I want something that is so simple and auditable that it's practical to make it pass any <a href="https://infosec.space/tags/verification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#verification</a> demands for <a href="https://infosec.space/tags/SecureTerminal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecureTerminal</a>|s in <a href="https://infosec.space/tags/CriticalInfrastructure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CriticalInfrastructure</a> and <a href="https://infosec.space/tags/Communications" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Communications</a>. <ul><li>OFC one may point at my other projects and say: "Why don't you just put <a href="https://infosec.space/tags/RaspberryPiOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RaspberryPiOS</a> on a <a href="https://infosec.space/tags/microSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#microSD</a>?" ignoring that the smallest image is >330MB in size and that seems kinda overkill for essentially my demands for a minimalist <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> with very few programs in userspace. </li></ul>Not to mention a <a href="https://infosec.space/tags/GNUfree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNUfree</a> - <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> distro is the way to go if I want that thing to not get bricked constantly by minor <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GlibC</a>-changes... <ul><li>End goal is something akin to <a href="https://infosec.space/tags/MSDOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MSDOS</a> in it's brutal simplicity, but way more extendable.</li></ul> I hope that answers your question...<ul><li>Sorry for the delay.</li></ul>

datenwolfAll I want is just a collection of <a href="https://chaos.social/tags/binutils" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#binutils</a>, <a href="https://chaos.social/tags/GCC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GCC</a>, <a href="https://chaos.social/tags/llvm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#llvm</a>+<a href="https://chaos.social/tags/clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clang</a>, <a href="https://chaos.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> and <a href="https://chaos.social/tags/musl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#musl</a> that are "free standing" / relocatable, which I can pack into a <a href="https://chaos.social/tags/squashfs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#squashfs</a> 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

Felix Palmen :freebsd: :c64:Solved! 🥳 This was a pretty "interesting" bug. Remember when I invented a way to implement <a href="https://mastodon.bsd.cafe/tags/async" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#async</a> / <a href="https://mastodon.bsd.cafe/tags/await" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#await</a> in <a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a>, 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 <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>, and I finally understood the reason for this was that I was using <a href="https://mastodon.bsd.cafe/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TLS</a> (thread-local storage) to find the context to restore.Well, most architectures store a pointer to the current thread metadata in a register. <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#POSIX</a> user <a href="https://mastodon.bsd.cafe/tags/context" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#context</a> <a href="https://mastodon.bsd.cafe/tags/switching" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#switching</a> saves and restores registers. I found a source claiming that the <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> (<a href="https://mastodon.bsd.cafe/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a>) implementation explicitly does NOT include the register holding a thread pointer. Obviously, <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>'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. 🤯

Aho<a href="https://social.linux.pizza/@MichaelRoss" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@MichaelRoss</a> something I have been trying to look for is a <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/ls" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ls</a> that isn't depending on <a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> or another <a href="https://mastodon.social/tags/libc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libc</a> 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.

Freexian :debian: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: <a href="https://www.freexian.com/blog/debian-lts-report-2025-04/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.freexian.com/blog/debian-lts-report-2025-04/</a>This work is funded by Freexian's Debian LTS offering.Your organization too can sponsor the Debian LTS (<a href="https://www.freexian.com/lts/debian/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.freexian.com/lts/debian/</a>) and join the esteemed list of sponsors in the monthly report.<a href="https://hachyderm.io/tags/debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debian</a> <a href="https://hachyderm.io/tags/debianlts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debianlts</a> <a href="https://hachyderm.io/tags/freexian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freexian</a> <a href="https://hachyderm.io/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#infosec</a> <a href="https://hachyderm.io/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a>

jbz⚠️ 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 ｣<a href="https://linuxiac.com/steam-will-stop-working-on-outdated-linux-systems-this-august/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://linuxiac.com/steam-will-stop-working-on-outdated-linux-systems-this-august/</a><a href="https://indieweb.social/tags/steam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#steam</a> <a href="https://indieweb.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://indieweb.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://indieweb.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a>

Tuckers Nuts Resist! 🇺🇦 <a href="https://mastodon.social/@cleverboi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cleverboi</a> Boi, I'm not knowledgeable about glibc, but I do use and like Pop!_Os, so I'm boosting your twt in an effort to secure you an answer. I don't know your use case, so I have no clue why you'd be having this software issue with Pop!_Os! Hope someone else can be of actual assistance. <a href="https://mstdn.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://mstdn.social/tags/GLIBC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GLIBC</a> <a href="https://mstdn.social/tags/Pop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pop</a>!_Os <a href="https://mstdn.social/tags/PopOs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PopOs</a>

you╭👺+300╭🐈x5╭⁂+3╭(Ⓐ+a<a href="https://mastodon.social/tags/tek" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tek</a> 0.2.0 out now: <a href="https://codeberg.org/unspeaker/tek/releases/tag/0.2.0" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/unspeaker/tek/releases/tag/0.2.0</a>it's buggy as hell, and about half the features i've showcased previously are disabled for now. but, more importantly, i've managed to build it as a single binary that you should be able to run on any <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> with <a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> and <a href="https://mastodon.social/tags/jack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jack</a>... let me know what happens!<a href="https://mastodon.social/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a> <a href="https://mastodon.social/tags/tui" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tui</a> <a href="https://mastodon.social/tags/daw" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#daw</a>

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> <a href="https://todon.nl/@burnoutqueen" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@burnoutqueen</a> Yeah...<a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> is a desaster as it's 99% ideology and 1% license text and alongside <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> completely ignores the reality of how <a href="https://infosec.space/tags/licensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#licensing</a> and <a href="https://infosec.space/tags/patents" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#patents</a> and <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IP</a> works.<ul><li>Not that I like the status-quo, but we'd rather see businesses steer clear of anything GPLv2+ or GPLv3 or worse.</li></ul>And on the flipside we basically get "source available" stuff like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> which only serves as a means to commit <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssetDenial</a> and monopolize commercial offerings...<ul><li>I think <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> being <a href="https://infosec.space/tags/GPLv2only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv2only</a> is a good compromise and my personal gripes with <a href="https://infosec.space/tags/FSF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> & <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNUtils</a> as well as <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GlibC</a> are something different...</li></ul>

Kevin Karhan :verified:<a href="https://kitsunes.club/@Jessica" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Jessica</a> <a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BrodieOnLinux</a> +9001%The reason I don't use <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GlibC</a> on <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a> is because it's <a href="https://infosec.space/@kkarhan/114175034719920644" rel="nofollow noopener noreferrer" target="_blank">constantly breaking userspace</a>…

Liam @ GamingOnLinux 🐧🎮The glibc 2.41 update has been causing problems for Linux gaming <a href="https://www.gamingonlinux.com/2025/02/the-glibc-2-41-update-has-been-causing-problems-for-linux-gaming/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.gamingonlinux.com/2025/02/the-glibc-2-41-update-has-been-causing-problems-for-linux-gaming/</a><a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://mastodon.social/tags/LinuxGaming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxGaming</a>

Kevin Karhan :verified:<a href="https://tech.lgbt/@krishean" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@krishean</a> that's not how <a href="https://infosec.space/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> works.SystemD was created because <a href="https://infosec.space/tags/SysVinit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SysVinit</a> was shit and noone fixed it or made something better.<ul><li>Same with <a href="https://infosec.space/tags/PipeWire" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PipeWire</a>: <a href="https://infosec.space/tags/ALSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ALSA</a> & <a href="https://infosec.space/tags/OSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSS</a> are really janky!</li></ul><a href="https://infosec.space/tags/Wayland" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Wayland</a> is the future as <a href="https://infosec.space/tags/Xorg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Xorg</a> is being <a href="https://infosec.space/tags/EoL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EoL</a>'d.<ul><li><a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> as a Kernel works fine, so no reason to replace it.</li></ul>For the shitty <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GlibC</a> we have alternatives like <a href="https://infosec.space/tags/bionic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bionic</a> and espechally <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#musl</a>! <a href="https://www.youtube.com/watch?v=o_AIw9bGogo" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.youtube.com/watch?v=o_AIw9bGogo</a>

Kevin Karhan :verified:<a href="https://social.treehouse.systems/@mgorny" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mgorny</a> that's because <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GlibC</a> is garbage and maintained by <a href="https://infosec.space/tags/Stallmanist" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Stallmanist</a>|is assholes that proudly brick userspace with minor version updates and tell people to "just recompile from source" as a valid strategy...

Kevin Karhan :verified:<a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dalias</a> <a href="https://mastodon.transneptune.net/@owen" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@owen</a> <a href="https://woof.group/@aphyr" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@aphyr</a> nodds in agreement I want stuff to be portable and reproduceable!<ul><li>And that means actually including - or at the very least declaring - ALL dependencies...</li></ul>The whole <a href="https://infosec.space/tags/PainAndFrustration" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PainAndFrustration</a> with <a href="https://infosec.space/tags/LinuxFromScratch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxFromScratch</a>, bloated <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNUtils</a> and <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GlibC</a> constantly breaking shit (among other things) is why I started <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a> …

Kevin Karhan :verified:<a href="https://hespere.de/@hllizi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@hllizi</a> <a href="https://types.pl/@haskal" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@haskal</a> that's one way to put it, but it completely ignores how to get devs to support an OS:<ul><li>Being able to get some MVP run quickly and dirty to showcase sth.</li></ul>This (slongside with <a href="https://infosec.space/tags/GLibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GLibC</a> messing up everything with every minor update is the reason why <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> failed on the <a href="https://infosec.space/tags/Desktop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Desktop</a> for so long:<ul><li>Compare that to <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> and <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows</a> where one can write a simple game or app and it'll likely still run as it did 10 years ago...</li></ul>

Kevin Karhan :verified:<a href="https://mk.absturztau.be/@enigmatico" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@enigmatico</a> <a href="https://plasmatrap.com/@privateger" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@privateger</a> there's a reason I work on <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a> and why it's intended to be a <a href="https://infosec.space/tags/GNU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNU</a>-free <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toybox</a>+<a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#musl</a> / <a href="https://infosec.space/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> distro:<ul><li><a href="https://infosec.space/tags/GLibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GLibC</a> is a shitshow maintained by nonchalant assholes that constantly brick systems with minor updates whilst denying the right to exist to <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCSS</a> and who think "recompile it yourself" is an acceptable answer even outside of <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> projects.</li></ul>The only <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNUtils</a> part that neither <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> nor I were able to replace is the <a href="https://infosec.space/tags/GCC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GCC</a> because AFAIK Linux just won't compile under <a href="https://infosec.space/tags/Clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Clang</a> / <a href="https://infosec.space/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a>...<ul><li>The moment that isn't the case anymore I')( happily ditch tht too, cuz GNU / <a href="https://infosec.space/tags/FSF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> are just bad and the only recourse I have aggainst them is to <a href="https://infosec.space/tags/boycott" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#boycott</a> them into irrelevancy...</li></ul>Shall all those people at the FSF complain at <a href="https://infosec.space/tags/RMS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RMS</a> for <a href="https://youtu.be/R2SKenHRhMg" rel="nofollow noopener noreferrer" target="_blank">alienating people and harming FLOSS in general</a> or as <a href="https://social.restless.systems/@ncommander" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ncommander</a> once said: ' […] <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> thrives not hecause but in spite of <a href="https://infosec.space/tags/Stallman" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Stallman</a> […]' cuz being a visionary predicting <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Enshittification</a> like <a href="https://infosec.space/tags/DRM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DRM</a> doesn't make him a less unlikeable character to be polite...

Recent searches

Search options

Administered by:

Server stats:

#glibc