mastodon.ie

HoldMyTypefolks who do smart things with multiprocessing models like Go and Chromium usually don't want C libraries potentially stepping on their toes. Oh gosh threads. The day I figure out how to do those, will be day the whole world will want to use this thing. But I want people who use Cosmopolitan <a href="https://mathstodon.xyz/tags/Libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#Libc</a> to know what value it's providing them. I think the best way to do that is by raising awareness of the systems engineering fundamentals like this. Because that's something you're right to point out that the <a href="https://mathstodon.xyz/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> community leadership has room for improvement on. <a href="https://news.ycombinator.com/item?id=26290723" rel="nofollow noopener" translate="no" target="_blank">https://news.ycombinator.com/item?id=26290723</a>

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

Root MooseI kind of wish there was a version of Alpine that was libc based - just for desktop NVIDIA support really.<a href="https://root.moose.ca/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://root.moose.ca/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> <a href="https://root.moose.ca/tags/Alpine" class="mention hashtag" rel="nofollow noopener" target="_blank">#Alpine</a> <a href="https://root.moose.ca/tags/NVIDIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#NVIDIA</a> <a href="https://root.moose.ca/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a> <a href="https://root.moose.ca/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a>

unixbhaskarUmmm 🤔<a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> <a href="https://fosstodon.org/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a> <a href="https://fosstodon.org/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://fosstodon.org/tags/binary" class="mention hashtag" rel="nofollow noopener" target="_blank">#binary</a> <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://jangafx.com/insights/linux-binary-compatibility" rel="nofollow noopener" translate="no" target="_blank">https://jangafx.com/insights/linux-binary-compatibility</a>

Khionu S :trans_furr_white:Something I would like to make in <a href="https://hachyderm.io/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> is a <a href="https://hachyderm.io/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a> wrapper that uses type-level contracts and optional (maybe debug-by-default) runtime checks. I like Rustix, but I'd like to make something that you can use with magnitudes less footguns.If you know of a company/team that would be willing to fund such work, I'd be eager to get connected!<a href="https://hachyderm.io/tags/FediHire" class="mention hashtag" rel="nofollow noopener" target="_blank">#FediHire</a> <a href="https://hachyderm.io/tags/contracting" class="mention hashtag" rel="nofollow noopener" target="_blank">#contracting</a> (Please reply with suggested hashtags, I'm not the greatest at these xD)

CassandrichExciting easy win I'd been meaning to do for a long time for broadening the scope of libc-test: 45 LoC (including include directives) to dive into a user+mount+net namespace where resolv.conf points to localhost and you have your own localhost you can bind to port 53 on (so resolver can be tested or even fuzzed). Non <a href="https://hachyderm.io/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> specific; like all of libc-test, should work for any <a href="https://hachyderm.io/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a>.

Neustradamus :xmpp: :linux:<a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> 2.40 has been released (<a href="https://mastodon.social/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> / <a href="https://mastodon.social/tags/GNUC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUC</a> / <a href="https://mastodon.social/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a> / <a href="https://mastodon.social/tags/LIBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#LIBC</a>) <a href="https://gnu.org/software/libc/" rel="nofollow noopener" translate="no" target="_blank">https://gnu.org/software/libc/</a>

0mp at FreeBSD<a href="https://mastodon.social/@mntmn" class="u-url mention" rel="nofollow noopener" target="_blank">@mntmn</a> From what I understand though, it is rarely the best approach. Here's an interesting comment by <a href="https://infosec.exchange/@david_chisnall" class="u-url mention" rel="nofollow noopener" target="_blank">@david_chisnall</a> about the recent addition of some <a href="https://mastodon.social/tags/assembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#assembly</a> bits to <a href="https://mastodon.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://mastodon.social/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a>: <a href="https://lobste.rs/s/uhdxcb/freebsd_14_1_release_announcement#c_jdakn8" rel="nofollow noopener" translate="no" target="_blank">https://lobste.rs/s/uhdxcb/freebsd_14_1_release_announcement#c_jdakn8</a>

Khionu S :trans_furr_white:I've got an odd <a href="https://hachyderm.io/tags/posix" class="mention hashtag" rel="nofollow noopener" target="_blank">#posix</a> <a href="https://hachyderm.io/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a> issue I could use help digging into.I'm using `posix_spawnp`, and getting an errno of ECHILD. According to man7 and two other sources, `posix_spawnp` should only error as `clone`, `fork`, or `vfork` might, and none of them list ECHILD as a possible errno.I'm using the Rust libc crate directly, fwiw, which is unabstracted bindings to libc. This error message compares directly against `libc::ECHILD`.Thoughts?

Some Bits: Nelson's Linkblogpollyfill-glibc: Hackery to let new binaries run on old Linux systems. The docs directory has a bunch of interesting technical info on linker tricks <a href="https://github.com/corsix/polyfill-glibc/tree/main" rel="nofollow noopener" translate="no" target="_blank">https://github.com/corsix/polyfill-glibc/tree/main</a> <a href="https://tech.lgbt/tags/compatibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#compatibility</a> <a href="https://tech.lgbt/tags/via" class="mention hashtag" rel="nofollow noopener" target="_blank">#via</a>:lobsters <a href="https://tech.lgbt/tags/pollyfill" class="mention hashtag" rel="nofollow noopener" target="_blank">#pollyfill</a> <a href="https://tech.lgbt/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://tech.lgbt/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> <a href="https://tech.lgbt/tags/hack" class="mention hashtag" rel="nofollow noopener" target="_blank">#hack</a> <a href="https://tech.lgbt/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a> #+

Bo MorganCross-platform native C executables? Sweet."Cosmopolitan Libc makes C a build-once run-anywhere language, like Java, except it doesn't need an interpreter or virtual machine. Instead, it reconfigures stock GCC and Clang to output a POSIX-approved polyglot format that runs natively on Linux + Mac + Windows + FreeBSD + OpenBSD + NetBSD + BIOS with the best possible performance and the tiniest footprint imaginable."<a href="https://github.com/jart/cosmopolitan" rel="nofollow noopener" translate="no" target="_blank">https://github.com/jart/cosmopolitan</a><a href="https://kolektiva.social/tags/c" class="mention hashtag" rel="nofollow noopener" target="_blank">#c</a> <a href="https://kolektiva.social/tags/gcc" class="mention hashtag" rel="nofollow noopener" target="_blank">#gcc</a> <a href="https://kolektiva.social/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#clang</a> <a href="https://kolektiva.social/tags/polyglot" class="mention hashtag" rel="nofollow noopener" target="_blank">#polyglot</a> <a href="https://kolektiva.social/tags/posix" class="mention hashtag" rel="nofollow noopener" target="_blank">#posix</a> <a href="https://kolektiva.social/tags/crossplatform" class="mention hashtag" rel="nofollow noopener" target="_blank">#crossplatform</a> <a href="https://kolektiva.social/tags/cosmocc" class="mention hashtag" rel="nofollow noopener" target="_blank">#cosmocc</a> <a href="https://kolektiva.social/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a> <a href="https://kolektiva.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://kolektiva.social/tags/windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#windows</a> <a href="https://kolektiva.social/tags/mac" class="mention hashtag" rel="nofollow noopener" target="_blank">#mac</a> <a href="https://kolektiva.social/tags/macos" class="mention hashtag" rel="nofollow noopener" target="_blank">#macos</a> <a href="https://kolektiva.social/tags/netbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#netbsd</a> <a href="https://kolektiva.social/tags/bios" class="mention hashtag" rel="nofollow noopener" target="_blank">#bios</a>

sebschCould we have a moment for how amazingly thin and well defined nix' layer for the libc is?<a href="https://chaos.social/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> <a href="https://chaos.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://chaos.social/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a> <a href="https://docs.rs/nix/latest/nix/" rel="nofollow noopener" translate="no" target="_blank">https://docs.rs/nix/latest/nix/</a>

Mike Rochefort :fedora:<a href="https://mstdn.ca/@agierscher" class="u-url mention" rel="nofollow noopener" target="_blank">@agierscher</a> In agreement here. The way I usually look at it is as a suggestion to consider the language for two types of <a href="https://fosstodon.org/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a> projects:a) it is a new(ish) codebase, or b) the project is leaning towards a rewrite anyways.Until developers stop authoring new C code and/or relying on the C <a href="https://fosstodon.org/tags/FFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#FFI</a> and C <a href="https://fosstodon.org/tags/ABI" class="mention hashtag" rel="nofollow noopener" target="_blank">#ABI</a>, we can't really escape C code. And as <a href="https://fosstodon.org/@snonux" class="u-url mention" rel="nofollow noopener" target="_blank">@snonux</a> mentioned, rewrites aren't the answer here. But other implementations of the <a href="https://fosstodon.org/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a>'s <a href="https://fosstodon.org/tags/syscalls" class="mention hashtag" rel="nofollow noopener" target="_blank">#syscalls</a> can be made, avoiding a link to <a href="https://fosstodon.org/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a>.

jouniLLMs as local offline tools like grep? llamafile combines model + binaries into one single file and it is easy to run as part of your bash script as grep or sed is. <a href="https://github.com/mozilla-Ocho/llamafile" rel="nofollow noopener" translate="no" target="_blank">https://github.com/mozilla-Ocho/llamafile</a> Interesting thing is that the same binary runs natively on Linux + Mac + Windows + FreeBSD + OpenBSD + NetBSD + BIOS on AMD64 and ARM64 with the best possible performance. Because of this project: <a href="https://justine.lol/cosmopolitan/index.html" rel="nofollow noopener" translate="no" target="_blank">https://justine.lol/cosmopolitan/index.html</a><a href="https://sauna.social/tags/llm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llm</a> <a href="https://sauna.social/tags/llama" class="mention hashtag" rel="nofollow noopener" target="_blank">#llama</a> <a href="https://sauna.social/tags/llava" class="mention hashtag" rel="nofollow noopener" target="_blank">#llava</a> <a href="https://sauna.social/tags/genai" class="mention hashtag" rel="nofollow noopener" target="_blank">#genai</a> <a href="https://sauna.social/tags/cosmopolitanlibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#cosmopolitanlibc</a> <a href="https://sauna.social/tags/cosmopolitan" class="mention hashtag" rel="nofollow noopener" target="_blank">#cosmopolitan</a> <a href="https://sauna.social/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a>

Kaitobuild once run anywhere c

MysticBasil 🇺🇦This. Is. Huge. 🎉 <a href="https://mastodon.online/tags/cosmopolitan" class="mention hashtag" rel="nofollow noopener" target="_blank">#cosmopolitan</a> <a href="https://mastodon.online/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a> <a href="https://justine.lol/cosmo3/" rel="nofollow noopener" translate="no" target="_blank">https://justine.lol/cosmo3/</a>

Thomas Frans 🇺🇦C developers: "Rust's memory safety is not a 'feature' of your program. It doesn't automatically make it better."CVE-2023-4911: "Well hello there!"I don't know about others but security is a pretty big feature in my books!<a href="https://social.linux.pizza/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> <a href="https://social.linux.pizza/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://social.linux.pizza/tags/cve20234911" class="mention hashtag" rel="nofollow noopener" target="_blank">#cve20234911</a> <a href="https://social.linux.pizza/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a> <a href="https://social.linux.pizza/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> <a href="https://social.linux.pizza/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> <a href="https://social.linux.pizza/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a> <a href="https://social.linux.pizza/tags/MemorySafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#MemorySafety</a>

das_menschyShould I install <a href="https://toot.bike/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> on my Laptop with <a href="https://toot.bike/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArchLinux</a>? Are all the usual programs (like Firefox, Thunderbird/Evolution, Nextcloud clients) compilable with <a href="https://toot.bike/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> <a href="https://toot.bike/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a>?

Kevin Karhan :verified:<a href="https://mas.to/@bitpirate" class="u-url mention" rel="nofollow noopener" target="_blank">@bitpirate</a> <a href="https://mastodon.social/@gamingonlinux" class="u-url mention" rel="nofollow noopener" target="_blank">@gamingonlinux</a> and as much as I'd love to see every game getting updated, it's illusional that publishers and devs will invest the time to do so on one-time-purchase titles that are over 2 years old, don't sell any significant numbers or don't get any other revenue to pay for workarounding the shit that <a href="https://mstdn.social/tags/flibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#flibc</a> does.Other <a href="https://mstdn.social/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a>'s like <a href="https://mstdn.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> don't do that.

Kevin Karhan :verified:<a href="https://blahaj.zone/@lunaa" class="u-url mention" rel="nofollow noopener" target="_blank">@lunaa</a> <a href="https://udongein.xyz/users/yura" class="u-url mention" rel="nofollow noopener" target="_blank">@yura</a> <a href="https://social.kernel.org/users/torvalds" class="u-url mention" rel="nofollow noopener" target="_blank">@torvalds</a> I know...There's a reason Distros like <a href="https://mstdn.social/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a>, <a href="https://mstdn.social/tags/ChimeraLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChimeraLinux</a> and almost all <a href="https://mstdn.social/tags/embedded" class="mention hashtag" rel="nofollow noopener" target="_blank">#embedded</a> systems using <a href="https://mstdn.social/tags/Busybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Busybox</a> or <a href="https://mstdn.social/tags/Toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Toybox</a> want to get rid of <a href="https://mstdn.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> if not replace it with something like <a href="https://mstdn.social/tags/uClinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#uClinux</a>, <a href="https://mstdn.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a>,or another <a href="https://mstdn.social/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a>... Because glibc bricking stuff with minor updates kills any <a href="https://mstdn.social/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> and any non-<a href="https://mstdn.social/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> that can't be recompiled.And what RMS et. al. may see as intentional, I think is the biggest issie that prevents <a href="https://mstdn.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> from dominating <a href="https://mstdn.social/tags/Desktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#Desktop</a>|s!

Recent searches

Search options

Administered by:

Server stats:

#libc