@gettie @chesheer Sadly not even #AdelieLinux, which @ActionRetro uses all the time...

I am working on an #i486 distro ( @OS1337) but for #i386 the support in terms of Linux ended with Versions 3.4.99 LTS & 3.6.9 respectably, and my #userland & #toolchain (#toybox & #musl-cross) doesn't support that at all, and I'd propably have more success convincing @landley to join #OS1337 than to support i386 even if I could pay him for that!

@FandaSin @cleverboi @BrodieOnLinux @neal I think #i486 is a good baseline because that's the furthest some systems can go!

• And supporting #i386 is out of the question for @OS1337 - unless someone wants to also abckport #toybox and #musl!

https://infosec.space/@kkarhan/114738983433662865

@cleverboi @FandaSin @BrodieOnLinux @neal as for #i386 I understood why cuz it was more and more painful m, but the problem with #i486 is that in several #embedded and #industrial setups there are still newly deloyed systems based off it.

I.e. #Vortex86 #SoC's cuz #MSDOS and shit still gets used in #industrial equipment.

• And #Linux is kinda necessary to keep that rollin'...

Linux stopped supporting i386 with versions 3.4.99 (longterm) & 3.6.9 respectably.

• And unlike with i386 where none of the toolchain (#musl) and utilities (#toybox) supoort it, i486 is still supported there.

And I really want to continue developing a minimalist "rescue" distro that can handle such legacy hardware because it may be the only option to ddrescue stuff from certain systems or to properly & reproduceably backup & restore them!

@landley @mrmasterkeyboard nodds in agreement

Granted the #IETF also accepts proprietary standards like #HSRP which resulted in #CARP being developed.

• In the end, I think #toybox is "Praxis" as in "Just build it!"...

@mrmasterkeyboard I mean, that's why I chose #musl for @OS1337...

Shoutout again to @landley for making this super easy by releasing the musl-cross - toolchain used for #toybox, making it super easy to just build against that.

@landley @mrmasterkeyboard yeah.

Personally, if "producing paper" wasn't undesireable you'd propably consider just taking the subsets of #POSIX and #LSB you're implementing and standardizing that as a sorf-of "#TINYNIX" (MININIX may be confused with Minix, MICRONIX and NANONIX already exist) standard.

• Simply because you've propably taken a look at every userland-tool you want to include or have included in #toybox and asked if it's necessary to make a self-hosting OS.

I just tend to ask what are the comfort features and tools that I use and want if I have to use "my little distro" for my daily job as linux sysadmin.

@mrmasterkeyboard @landley glad I could get you guys connected then...

I'm convinced #toybox is a good #userland to get a basic OS up and running and on it's feet. If it's good enough for #Android then it's certainly gonna be good enough for #embedded stuff as well...

• After all that seems to be the main goal of it: Allowing "self-hosting" as in building itself under itself if not deliver under the same OS...

I don't leverage that capability with #OS1337 (at least for now) but that's because I treat it more akin to how #VxWorks and #WindRiverLinux is being developed and deployed...