@katyswain I din't think that #CCSS is good either, but the demands of #GPLv3 are not compatible with the (adnitteldy shitty) reality of how #IP, #Licensing and #Patents work and thus it kneecaps a lot of things.

• GPLv3 caused #Apple to freeze their #bash version and divest into #LLVM and adopt #zsh.

• As @landley showed, enforcing the #GPL(v2) resulted in exactly 0 code being committed to #BusyBox and it only made said project look toxic and litigatious.

• Also i've yet to see anything happen re: #paywalled #SourceCodeAccess for #grsec & #RedHat #Linux. Maybe #GPLv4 will ban #paxwalling and force violators to work on #GNU / #HURD?

I chose #0BSD for _OS/1337 because as with any "intellectual labour", one cannot force others to collaborate and I'd rather have people join in out of the goodness of their hearts instead of just dumping some random git commit that is useless.

@santi @mos_8502 @Wintermute_BBS well, as for #GPLv2 and license enforcement, using #copyleft as a bat to club corporations with isn't effective.

@landley still feels remorse for having started that with #BusyBox.

Not to mention #GPLv3 & #AGPLv3 really is bad unless one wants to commit "asset denial" aka. be an anticompetitive dickhead and at that point it's close to "asshole licensing" of #SSPL & #RSAL!

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

@robpumphrey

I cannot say positively that there exists someone who can *recommend* some. I can point to some, but this does not constitute a recommendation, and you'll have to do some investigation. (-:

https://packages.debian.org/sid/dibbler-server

https://packages.debian.org/sid/dhcpy6d

https://packages.debian.org/sid/kea-dhcp4-server

https://packages.debian.org/sid/kea-dhcp6-server

https://packages.debian.org/sid/udhcpd

https://packages.debian.org/sid/wide-dhcpv6-server

@burnoutqueen the problem is that #enforcing #copyleft doesn't get you a single line of code improvements.

• Ask @landley and his successor(s) that are now maintaining #BusyBox.

In an ideal world it would, but we all know that's not the case.

• Consider #BSD-licensed alternatives a competiton, which is more likely to get contributions back (again, Rob Landley can most likely attest to that) from corporations and see it as a motivation for copyleft-licensed projects to step up their game!

@target

@cstross isn't even joking, I think.

Both BusyBox and ToyBox actually do have an init program, a getty program, and a login program.

BusyBox also has the Almquist shell. ToyBox has a Landley shell. BusyBox even has runit.

It is possible to have a system where even if you are doing various things in a shell you're just invoking the same program image over and over, using all of the same code that is there in process #1.

@notjustbikes precisely!

Only #OpenSource & #OpenStandards can yield #MultiVendor & #MultiProvider systems necessary to prevent #monopolies and #oligopolies and enshure #ITsec, #InfoSec, #OpSec & #ComSec, thus being able to comply with #NatSec & #IntlSec demands.

Guess why #NORAD runs #BusyBox / #Linux?

• Because they demand every single line of code to be audited MANUALLY!

@cas TBH, this actually makes sense in some #CriticalInfrastructure when someone wants to finally replace some #MOS6502-based system and chug a low-end SBC in...

And given it targets #BusyBox, I'd not be surprised if #NORAD is already looking at the code to see if they can use it...

@AugierLe42e I assume that port is fixed to a specific USB Hub / Controller / Port and the button is similarly linked to some GPIO / I²C / PS/2 port...

• What you can do is check lsusb for #USB devices and see if the specific port in question has a USB mass storage device or SATA bridge chip attached to it when said button is pressed.

If #QNAP used #Linux they should've provided those drivers / scripts as part of their #GPLv2 obligations to buyers/owners of said #NAS boxes.

• Just don't expect any of that code to be useable, as @landley can attest from the #BusyBox license enforcement…

Either way if you can reliably identify the port & detect the button presses that should be sufficient to build like a #bash or #python script to basically detect the drive, mount it and cp -r /dev/$DRIVE/ /home/copied_drives/$LABEL/

• It may need some fiddling and will most likely only work reliably on unencrypted drives with ext2-ext4, btrfs, ntfs, fat32, exfat filesystems...

Pretty shure you'll have to tweak a bit unless you want to use /dev/by-uuid/$UUID and the UUIDs of the partitions as name...

@EpicPawt I can recommend to take a look at #TinyCore and #BunsenLabs if you like some #smol #desktop #distro...

TinyCore is a #BusyBox / #Linux and @bunsenlabs is a nifty #Debian derivate which runs even on a #GMA500 / #Poulsbo / #IntelAtom Z-series system like the #VaioP11Z just fine despite using #llvmpipe for rendering...

@notsoloud same with all other #Linux distros.

• Guess why #NORAD used #BusyBox and why I started my own minimalist, #GNUfree #toybox + #musl / #Linux distro: @OS1337 ...

Now granted, #NvChad is basically what happens when #neovim fans want to make a better alternative to #emacs.

• Personally, I only put it ob a #wishlist of sorts because I want to make a 80x25-optimized #TUI #Desktop easier to accomplish.

For most people, using #fish as in fish shell with #tmux and some extras could yield the same...

OFC nothing prevents one from using @OS1337 's basic #toybox + #musl / #Linux basis to generate a #smol and efficient #Linux #Desktop or general-purpose Server distro.

• Similar to #TinyCoreLinux, which is a really nifty #BusyBox - based distro which can manage a #Xorg #desktop in 23MB image size...

@krutonium I can recommend @bunsenlabs / #BunsenLabsLinux which runs smooth in my #Vaio #P11Z with the shitty #GMA500 in #llvmpipe.

• If that's too straining, consider #TinyCore, which us a #BusyBox-based distro - abeit very minimalist.

Those are the options with a fancy #GUI.

• I aim for #i486 with @OS1337 (if #Linux didn't cancel #i386 and #toxbox never bothered with it, I'd aim dir that!) but as of now that isn't useable.

@linuxgal I prefer #toybox tho - less stuff than #BusyBox, but cleaner code!
https://www.youtube.com/watch?v=MkJkyMuBm3g

Sadly the #paywalling of #grsec / #grsecurity also killed more #downstream projects like tor-ramdisk which was a minimalist #busybox / #linux #distro designed to host #OnionServices. It was pretty nifty and the #SourceCode is still online and hosted by @torproject on their #gitlab, abeit seemingly abandoned since 2018...

@SweetAIBelle that's why I started @OS1337 : I looked at #Floppynux by @w84death and while it works with #BusyBox it doesn't do much beyond cat and vi and doesn't even have like drivers to store anything.

OFC #OS1337 isn't much better as of now but I do share the motivation that made @landley start #toybox:

A simple, clean, lean and adaptible, #smol #Linux distro that can be the solid foundation for anything.
https://youtu.be/MkJkyMuBm3g&t=1408
Whilst #mkroot is nice, I think there is some room for improvement and building an actual #distro.

• Also he has made excellent documentation including a live demonstration on how to basically DIY a minimalist linux from scratch with #musl & toybox: https://youtu.be/Sk9TatW9ino

I feel that "Just chug in a #RaspberryPi with the lite Version of #RaspberryPiOS seems quite overkill (it's a 350MiB (!!!) image) for most projects and espechally when it comes to #security-related stuff like #Cryptofon, #PocketCrypto and #LambdaCrypt.

• I think that besides "Don't DIY encryption! There are excellent implementations ready to grab and go!" the #KISS-Principle is key, cuz I'm a shit coder and I want to avoid having to fiddle around and instead make it easy to fix stuff just by updating versions from upstream.