Action Retro 
Did anyone order a UNIX pizza?
Kevin Karhan 
@ActionRetro yes...
I want one "MAX IMPACT" please...
https://www.youtube.com/watch?v=ZDxLa6P6exc
SGI Indigo2: An $86,000 Workstation from 1995
Diving into the Silicon Graphics Indigo² desktop workstation computer! This was a beast in 1995, and yes, "it's a UNIX system, I know this!" How do the pros ...
@ActionRetro this reminds me of the scalable Workstation Design I wanted to get off the ground...
Kinda like the #Onyx but woth modern bus systems...
https://www.youtube.com/watch?v=Bo3lUw9GUJA
SGI's $250,000 Graphics Supercomputer from 1993 - Silicon Graphics Onyx RealityEngine²
@kkarhan i want to play with one of these so badly
@ActionRetro sadly #Dodoid went dark for quite some time.
I wounder if David "#8BitGuy" Murray still has some #Sun slabs lying around...
@ActionRetro but be aware that the #RabbitHole for old #Unix is very, very deep.
*points at @ncommander doing #Solaris 7*
https://www.youtube.com/watch?v=sJFxwBfFkyM
Exploring Sun Solaris 7 for SPARC
JessOFC, cuz @ncommander is #based af.
@kkarhan @ActionRetro @ncommander there are three streams I have watched on YouTube, and two of them were the LFS ones
@sataa @ncommander @ActionRetro yeah...
Some people may call this "Cyber-Masochism" in terms of tech but his videos crucially showcase the achilles heels of #unix-alike systems:
- archiving the toolchain and dependencies
- documentation, or lack thereof
- how the #GlibC is an unfixable POS that should not exist since minor updates brick an entire userland and this is absolutely unacceptable for anyone who wants a stable #Linux system!
- how online-dependent distros are.
Grey Matter@kkarhan @sataa @ncommander @ActionRetro
i feel like i'm stepping onto landmines here but, ya know, what's your solution? certainly not windows. in terms of glibc update type issues, isn't this the difference between upstream and downstream solutions? pick what is right for you.
@greymatter @sataa @ncommander @ActionRetro I think that #ChimeraLinux is showing the way by yeeting all the #GNU & #FSF shit out of the system.
The fact that #Win32 is the most stable #API & #ABI on #Linux is a shame and testiment to the lack of fucks given by #glibc and other projects.
#Busybox, #Toybox, #uClinux and #Musl are working solutions espechally in #embedded setups where #GNUtils are seen as unstable #bloat.
@greymatter @sataa @ncommander @ActionRetro interestingly all those "but #SystemD is bloat" cultists turn a blind eye on the clusterfuck thaf is #glibc and rather integrate deprecated stuff like Sun's #SMF which is basically what inspired #LaunchD and thus SystemD....
Sorry if I sound jaded. I just want systems to work and at this point I'm so close to just throw $25 p.a. at #Canonical for @ubuntu #UbuntuLTS /#UbuntuPro w/ #Landscape on-prem.
@kkarhan @sataa @ncommander @ActionRetro @ubuntu
tbh, supporting multi-platforms is a pain in the fucking ass. what is the market share of solaris in 2023? is it primarily legacy systems? serious question.
@greymatter @sataa @ncommander @ActionRetro @ubuntu *nodds in agreement*
With #Oracle basically killing #OpenSolaris and chasing away all the #Sun-era #FLOSS #devs and #projects, it's basically a statistical anomaly, not even a "rounding error"...
@kkarhan @sataa @ncommander @ActionRetro @ubuntu
one thing i will give them credit to is that they have done a solid job of trying to keep up with the times. installation, package management, etc has severely become more user friendly and comprehensive. but -- and i am happy to be correct / out of touch -- i just don't understand why someone is deploying solaris in 2023.
@greymatter @sataa @ncommander @ActionRetro @ubuntu I know why someone would still deploy & maintain #Solaris and I'd love to go into details, but do keep to #NDA's...
What I can say however is that said systems are completely airgapped in a bunker and I would've not been able to ever bring a phone or anything with a camera even on the same premises...
And no, it's not some govt. thing...
@kkarhan
@sataa @ncommander @ActionRetro @ubuntu
we still support solaris and have a couple boxes but we also still develop 32-bit versions of our software sooo yeah.
@greymatter @sataa @ncommander @ActionRetro @ubuntu
But to go back at your original question:
https://rap.social/@greymatter/110546111879490017
The solution is to make statical linking the norm.
https://github.com/OS-1337/spm#why-no-dependency-checking
I mean we already have that - tho in a 3D Chess version aka. #Docker, #Snap, #Flatpak and #AppImage...
And for my current project this is the way to go in order to make easy updates, revisions and fixes without breaking shit.
https://github.com/OS-1337/OS1337
@greymatter @sataa @ncommander @ActionRetro @ubuntu
And yes, I call it OS/1337...
NCommander@kkarhan @greymatter @sataa @ActionRetro @ubuntu static linking sounds great until you have a major CVE in a common library
@ncommander @greymatter @sataa @ActionRetro @ubuntu
OFC it comes with that drawback, but then again for an #embedded & #minimalist distro, swapping out the statically executeables is worth it, espechally since we're still wrhin Kilobytes...
@kkarhan @greymatter @sataa @ActionRetro @ubuntu
Actually, static linked hurts unless you lack a MMU since you then have multiple versions of the libraries loaded into memory instead of a single version of the library loaded that can be paged into all instances. It also increases overall storage.
(this was one of the big reasons while DLLs were a very big deal on Windows)
@ncommander OFC, that is a concern if RAM is a limiting factor...
And I do know that most distros like @ubuntu will zse shared libraries as they have way more programs needing them at the same time, so I don't think that's bad on their part.
Whereas in my case of OS/1337 the #Floppy version (1440kB) literally only contains #Linux as Kernel, #toybox as Userland and #Dropbear as SSH-Client and nothing else.
It's basically turning a machine into a "SSH-Terminal" and that's it.
@ncommander Granted that's not common for #Distros to do so, and my goal with #OS1337 was to make something more practical than #Floppinux which can barely output some text on screen - at least connect to somethng else that is useful.
OFC I'll release it once tested and satisfactory in useability for what I want to achieve with it.
But yeah, there isn't much beyond #musl being shared among those processes, so it's mostly a tradeoff that'll cost storage or RAM in more extensive setups...