@mrmasterkeyboard @landley I mean, that's why I use #toybox for @OS1337, because I can't be assed to deal with the convoluted mess of #GNUtils and I do want to make a #GNU-free, minimalist distro that I can use as a baseline for #Firmware.

@mrmasterkeyboard If that #kernel is mostly #POSIX-compatible it should be possible to port #toybox over there (alongside any other software one may want to get running on @OS1337), but that's as far as I know.

Not shure if @landley has the time and spoons beyond testing toybox against #Linux as he does aim to make it a better alternative to #BusyBox & #GNUtils.

@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...

• I think #Linux being #GPLv2only is a good compromise and my personal gripes with #FSF & #GNUtils as well as #GlibC are something different...

And OFC #toybox is a good baseline in terms of #userland - espechally when I want a #GNU-free #Linux distro because there are very good reasons beyond #GNUtils being a bloated mess...

@dalias @owen @aphyr nodds in agreement

I want stuff to be portable and reproduceable!

• And that means actually including - or at the very least declaring - ALL dependencies...

The whole #PainAndFrustration with #LinuxFromScratch, bloated #GNUtils and #GlibC constantly breaking shit (among other things) is why I started @OS1337 …

@enigmatico @privateger there's a reason I work on @OS1337 and why it's intended to be a #GNU-free #toybox+#musl / #linux distro:

• #GLibC is a shitshow maintained by nonchalant assholes that constantly brick systems with minor updates whilst denying the right to exist to #CCSS and who think "recompile it yourself" is an acceptable answer even outside of #FLOSS projects.

The only #GNUtils part that neither @landley nor I were able to replace is the #GCC because AFAIK Linux just won't compile under #Clang / #LLVM...

• The moment that isn't the case anymore I')( happily ditch tht too, cuz GNU / #FSF are just bad and the only recourse I have aggainst them is to #boycott them into irrelevancy...

Shall all those people at the FSF complain at #RMS for alienating people and harming FLOSS in general or as @ncommander once said:
' […] #OpenSource thrives not hecause but in spite of #Stallman […]' cuz being a visionary predicting #Enshittification like #DRM doesn't make him a less unlikeable character to be polite...

@SweetAIBelle @OS1337 shure.

I'm convinced that a fully-fledged image of that would be similar to #toybox's #mkroot, which is @landley 's reference implementation for a toxbox + #musl / #linux system.

• Last time I checked it came out just below 4 MB, but that was the premade image using only the stuff toybox included [and linux & being statically compiled against musl] like #gzip instead of #xz for compression, so there already is room to shave a few hundred kB without reducing functionality out of the get-go as I've seen with my build tests of #kernel666...

Either way, we're close to his reference matterial AFAICT and I do think that OS/1337 can become a good and solid foundation for #minimalist & #embedded systems.

For comparison:

• #YoctoLinux is quite #THICC in comparison (using LSB & #GNUtils for the most part!) and stuff like #OpenADK seems to be overly complex...

  • tho #Viprinet hasn't updated their stuff in like 8 years and I sincerely hope that's just them loginwalling access to #SourceCode like #grsecurity to paying customers only and not them such old Kernels.

Speaking of #grsec, I wounder if Bruce Perens actually sued them for allegedly violating #GPLv2 when in fact said license allows #paywalling aka. restricting access to buyers of the product it contains.

@nuintari I disagree.

#SystemD is a "necessary evil" because what existed previously was bad for anything that isn't a "build once never change" server that never gets changed much...
https://www.youtube.com/watch?v=o_AIw9bGogo

• Most #unix-esque OSes already used something like it way before @pid_eins even did #Linux: Like #SMF on #Solaris and espechally #LaunchD which is basically what inspired systemd.

The only reason I "cut" systemd from @OS1337 as of now is because I can't make it - or the #GNUtils that preceded it - fit within the few hundred kB on a 1.440 kB FDD I can spare.

Noone wants to go back to #SysVinit when even the fastest systems took longer to boot that most peoole need to make a shitty coffee or dump ass on the toilet.

• Amd dumping SysVinit - just like #Linux dumping #i386 - is somewhat inevitable given the amount of work it took to keep it workable at all...

@ncommander nodds in agreement

Espechally since #Zones are a built-in containerization and isolation feature of #illumos nee #OpenSolaris and it would be a good match for hat exact scenario...

That being said, it reminds me why I did start my own:

Because #Viprinux's #OpenADK is an unworkable mess even cringier than the #GNUtils toolchain...
https://www.viprinet.com/en/support/downloads
https://github.com/OS-1337/OS1337

@thelinuxcast @fuchsiii yes, a #0day affecting all versions since 1993.

Because #GlibC is a mess that constantly bricks stuff for no good reason - just like the #GNUtils

There's a reason why OS/1337 uses @musl and @landley 's #toybox.

Because #KISS principle rules!

@beforewisdom @Yehuda @fsf exactly.

As for the #GNUtils like #bash, I do work on getting rid of them as well where I can.

I am currently working on a #minimalist #embedded distro based off #toybox / #Linux + #musl, because #Glibc is a shitty mess that bricks stuff at random in minor version updates for no good reason!
http://os1337.com