@lavxnews point is: "reinventing the wheel" is rarely easy nor worth the effort.

• Shure one can design their own OS or Kernel but the cost of doing so rarely makes sense.

That's why I use #Linux, #toybox and #musl for
OS/1337 ...

• Same reason why noone spins their own #encryption, except here it's a matter if #ITsec and thus #InfoSec, #CopSec & #OpSec!

@bagder Problem with that is (besides occasional bugfixes), most people including myself would see #curl to be functionally complete and anything "nice to have" would be considered not worth the balooning in #complexity and #size.

• I mean, does curl need to be able to do #BitTorrent (magnet:), #IPFS (ipfs://) or god forbid #blockchain (i.e. #EVM) support?

• Do you really want to integrate @torproject / #Tor support natively into curl when using #HTTP (localhost:8118) and #SOCKS5 (localhost:9050) #proxy allows for the same and doesn't necessitate having to handle and ingest Tor arguments as well??

In fact if #toybox didn't have a #wget implementation that I could use for OS/1337 I would've merely chosen tiny-curl -o as a global alias or if #tinycurl wasn't an option, curl -o instead.

• Maybe someone who wants to have said functionality like tor support built-in will go and IDK make i.e. #neocurl or sth. along those lines or build something like #ethcurl or #torcurlor #ipfscurl or whatever...

That being said I am glad curl isn't solely maintained by you but has other contributors (give them a shoutout!) but I also am glad you maintain that vital software that most "#TechIlliterate #Normies" most likely never heard of but propably use on a daily basis as part of all the #tech they use to #consume media with...

• I consider curl to be "the #vim of downloaders" (tho that's kinda insulting and limiting since curl is more than just a downloader and more intuitive than vim) with wget being "the #vi of downloaders" (tho wget is even simpler to use than vi)...

Either way, curl is awesome...

@dalias @eniko Personally, I'll sooner or later have to engange the whole #ARMv5 / #ARM11r7 / #RaspberryPi architecture anyway with OS/1337.

• Tho given it's a minimalist Linux merely booting an initramfs and never doing any writes, there should be no indurance issues.

But I know a #readonly - OS isn't practical and where it is people already use #iPXE & #iSCSI for #diskless setups!

• THO AFAICT there should be an option to basically partition the system and only keep /boot on an SD card, and the rest could be on any USB mass storage device (i.e. SSD or even HDD)...

That being said Raspberry Pi do have the key advantage of being by far the best in terms of #documentation.

@nixCraft cool...

Personally I'd propably make a "screenless" #NUCbook down the lane and use that as an #AiO similar to those that @vwestlife seemingly likes...

• Sadly I couldn't find that #WintelK3 at reasonable prices anymore when I first saw it...

Would've been the ideal testing system for OS/1337 ....

@OS1337

Anyway, the short-term solution would be to setup some #iPXE "Internet Boot Server" on boot.os1337.com to download @OS1337 into RAM and boot that...

Cuz that may be a quick and dirty option to get the latest version at boot...

@mdhughes personally I want a sleek #toybox + #musl / #Linux distro that embraces the #TUI...

I call it OS/1337: @OS1337

@ariadne makes sense espechally if you don't want to delegate that to tools like #curl or #wget to handle...

• In fact, were it not for the minimalist wget in #toybox [without #HTTPS!] I would've to figure out a different way to make the package manager for OS/1337, #spm, work.

OFC it's not operational yet but I know that #KissPrinciple is good...
And I do intent @OS1337 to do that with as well...

@nixCraft Similar reason why I'm sticking with #bash...

It just works!

- Okay, I'd love to use #fish more but that sadly doesn't get used in @OS1337 at all...

@hspmauli @meerschweinchen83
Bei einem System das nur 80*25 Zeichen Text ausgibt sollte dem aber so sein...

Ich wünschte ich hätte Budget um jemensch für entsprechendes #AccessibilityTesting von #OS1337 zu bezahlen, weil das schließlich auch #Arbyte ist die nicht einfach ist...

In der Theorie sollte es gut funktionieren aber ich konnte es bisher noch nicht verifizieren.

Da aber eine serielle Konsole unterstützt wird sollten allerdings theoretisch alle Ein- und Ausgaben implementierbar sein.

@rory So think of #OS1337 like a new attempt at #tomsrtbt in terms of simplicity...
https://infosec.exchange/@rory/111630432435153899

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

https://github.com/OS-1337/OS1337
https://github.com/orgs/OS-1337/projects/1/views/1

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 Well, for #OS1337 I took inspiration from @w84death 's #Floppinux and took his #documentation and went full "chimp banging rocks together" on it, but swapping #BusyBox for @landley 's #toybox since I prefer #bash over #ash and wanted something really basic that would do more than cat text files but provide i.e. a portable #SSH #client on a FDD.
Something that could serve as a foundation or rather plain "slate for my other projects in lieu of a THICC distro that is not practically auditable

@bagder same reason for #Linux I guess and same reason why I do all the #OS1337 code in #bash with only .config makefiles where needed:

Readable and thus easy to #audit code allows for #transparency, which is vital for #maintainability and #security...

After all, mistakes do happen and I'd rather have it easy find and fix than optimize every bit at the cost of unmaintainable code.

@ExpiredPopsicle giess what #Kernel version I want to use for the 0.1 release of OS/1337
@OS1337 ?