Aside from the IFUNC mechanism (which #musl doesn't and won't support, btw), the one way for libraries that get linked but not used to run code is as global constructors.
Wouldn't it be nice if distros could just audit for which libs have global ctors, and apply greater scrutiny to pulling ones that do into sensitive programs?
#musl web infrastructure has now been switched entirely over to tipidee (https://skarnet.org/software/tipidee/) thanks to range request support that was added a while back, and to fix some breakage introduced with split backends. Thanks @ska for writing it, help setting up, and feature additions to meet site needs!
To get that “full desktop” experience I am reinstalling #VoidLinux with the @xfce iso. I am still staying with #musl. I will probably install #Cinnamon too.
#Gnome was okay, but the inability to easily install the extensions was a no bueno for me. My gnome needs to have some spice; vanilla doesn’t cut it 🌶️
I've been re-reconverting a lot of my "stuff" to the BSDs (Free, Open, Net). It's refreshing. The Linux every-tool-has-to-be-a-swiss-army-knife ethos is exhausting after a while. The relative simplicity and clean organization of *BSD (especially OpenBSD) re-affirms my fondness for UNIX-y things.
You might think there's not that much difference but, in many cases, I'd rather admin a BSD box. Try it, you'll see.
Also, NetBSD is soo lean, it has made my old Pentium III almost useful again. Even with 333Mhz and 128 MB of RAM 🙃
@rory Since then @SweetAIBelle and I have worked on OS/1337 and whilst we have some booting prereleases, I want to iron it out into something that works and that is easily extensible and "build from source yourself"...
Tho #OS1337 is not to be confused with @landley 's reference implementation of a #toybox + #musl / #Linux distro that is #mkroot, which is close to but not identical to the foundation of #Android, but exceeds my space requirements.
@rory That being said, Contributions and Feedback is welcome and as per it's #0BSD license you could even go so far as to fork it and put a #NetBSDor any other #unix-esque #Kernel under it if you so please.
My quest is to see if something like #tomsrtbt can be done with modern versions of #Linux & #toybox.
I know #mkroot is meant to show a full #musl + toybox / linux system for each supported architecture without sacrificing features and drivers along the way whilst retaining readability and reproduceability.
Alors, c’est comme ça ? Je vais devoir en passer par là (ou par Lagrange, voire Amfora) pour pouvoir lire les articles de Numerama sans devoir passer par leur site ?
C’était plus simple via FrogFind!, mais il ne veut plus afficher les articles de ce site depuis hier après-midi (et @ActionRetro ne répond pas…)… ;__;
@HopelessDemigod The current goal is to get a 0.1 release that fits on a 1.400kB 3,5" FDD and includes #Linux (ideally 6.6.6 for maximum meme factor) #Toybox and #dbclient (#Dropbear#SSH as SSH-Client only) compiled against #musl-cross and bootable on any #i486 and up.
also: call me weird but I'd rather integrate #SystemD into #OS1337 than using #glibc for OS/1337:
In fact I'd rather statically link #musl with every binary to maximize portability of applications...
If #Glibc wasn't a piece of shit that knowingly and willingly bricks #Userspace all the time #Docker would neither have a right to exist nor legitimate reason to be used.
I hope #Linux will migrate to #musl sooner than later...
Just when I feel like I'm ready to throw in the towel with email, I discover a solution that actually sounds sensible:
« #mxclient is not a normal MTA. Rather, it's a minimalist client for sending mail direct to the recipient's MX, or mail exchanger, in contrast to the widespread practice of sending through a "smarthost" or "outgoing mail server".
In combination with sufficient cryptographic measures, this ensures that no one outside the receiving domain's mail system can intercept or alter the contents of the message, making mxclient suitable for:
Private bi-directional communication between individuals (with personal domains) or organizations that mutually implement this kind of delivery.
Delivery of sensitive data like account access or password reset tokens without them passing through third party mailer systems.
Avoiding dragnet surveillance of outgoing mail in otherwise conventional mail setups.
mxclient is not an outgoing mail queue. It delivers mail synchronously, to a single recipient, reporting success, temporary failure, or permanent failure via the exit status (using sysexits.h codes). It can be used as the backend for the separate queuing frontend to yield a full "sendmail" command for use by MUAs or scripts that expect asynchronous delivery.
Ability to send mail directly to the recipient's MX depends on having unblocked outgoing port 25 (many residential and mobile ISPs firewall it) and on not being on one of several "dialup"/residential IP address lists that many sites' mail systems use to block likely spammers. To get around this while still maintaining the security and privacy properties of interfacing directly with the recipient's MX, future versions of mxclient will support performing the actual TCP connection through a (SOCKS5 or ssh -W child process) proxy while keeping the actual TLS endpoint local. »
Should I install #AlpineLinux on my Laptop with #ArchLinux? Are all the usual programs (like Firefox, Thunderbird/Evolution, Nextcloud clients) compilable with #musl#libc?
Great example of Fork Considered Harmful just came up on #musl: a program that spawns children via fork+exec spending inordinate time in kernelspace (accounted as minor page faults) slowing down computation.
@thegibson Setting up #Debian on #musl#voidlinux to #chroot into for installing #leapmotion software to control my new hand/motion tracker/controller, only for the software to spit out this:
Error: Missing Dependency: glibc
Thought I could cheat the system. Long story short, installed the GLIBC variant of Void on a USB, booted into it, and redid the process of converting and installing (guide coming soon).