home.social

#busybox — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #busybox, aggregated by home.social.

  1. Just finished a PoC if i could bootstrap pkgsrc on my self-assembled minimal docker container.

    Ingredients: skarnet-musl-toolchain. busybox-static, toybox-static, gawk, gsed, gtar, gmake, libz, libexpat, libxcrypt, libbsd, libmd, musl-{bsdcompat,fts,obstack,rpmatch}, and finally pkgsrc from netbsd.

    after a few ins and outs, and learning the ropes, bootstrapping worked flawlessly.

    shout out for the developers for their good work!

    #docker #toybox #busybox #LFS #LFN #pkgsrc #linux #musl

  2. Just finished a PoC if i could bootstrap pkgsrc on my self-assembled minimal docker container.

    Ingredients: skarnet-musl-toolchain. busybox-static, toybox-static, gawk, gsed, gtar, gmake, libz, libexpat, libxcrypt, libbsd, libmd, musl-{bsdcompat,fts,obstack,rpmatch}, and finally pkgsrc from netbsd.

    after a few ins and outs, and learning the ropes, bootstrapping worked flawlessly.

    shout out for the developers for their good work!

    #docker #toybox #busybox #LFS #LFN #pkgsrc #linux #musl

  3. Just finished a PoC if i could bootstrap pkgsrc on my self-assembled minimal docker container.

    Ingredients: skarnet-musl-toolchain. busybox-static, toybox-static, gawk, gsed, gtar, gmake, libz, libexpat, libxcrypt, libbsd, libmd, musl-{bsdcompat,fts,obstack,rpmatch}, and finally pkgsrc from netbsd.

    after a few ins and outs, and learning the ropes, bootstrapping worked flawlessly.

    shout out for the developers for their good work!

    #docker #toybox #busybox #LFS #LFN #pkgsrc #linux #musl

  4. Just finished a PoC if i could bootstrap pkgsrc on my self-assembled minimal docker container.

    Ingredients: skarnet-musl-toolchain. busybox-static, toybox-static, gawk, gsed, gtar, gmake, libz, libexpat, libxcrypt, libbsd, libmd, musl-{bsdcompat,fts,obstack,rpmatch}, and finally pkgsrc from netbsd.

    after a few ins and outs, and learning the ropes, bootstrapping worked flawlessly.

    shout out for the developers for their good work!

    #docker #toybox #busybox #LFS #LFN #pkgsrc #linux #musl

  5. Just finished a PoC if i could bootstrap pkgsrc on my self-assembled minimal docker container.

    Ingredients: skarnet-musl-toolchain. busybox-static, toybox-static, gawk, gsed, gtar, gmake, libz, libexpat, libxcrypt, libbsd, libmd, musl-{bsdcompat,fts,obstack,rpmatch}, and finally pkgsrc from netbsd.

    after a few ins and outs, and learning the ropes, bootstrapping worked flawlessly.

    shout out for the developers for their good work!

    #docker #toybox #busybox #LFS #LFN #pkgsrc #linux #musl

  6. Naty S @eclecticpassions ·

    After discovering from @jbaty, I went ahead to give (lightweight TW fork) a spin as a personal bin. I really like how it’s just a HTML file at 58kb!

    Using , it failed due to Android Storage Access Framework (#SAF) limitations. I ended using the amazing once again to run , automate the whole process of opening, serving & saving back to my…

    Full note: burgeonlab.com/notes/2026/0325
    Syndicated by

  7. After discovering #TiddlyWiki from @jbaty, I went ahead to give #FeatherWiki (lightweight TW fork) a spin as a personal #braindump bin. I really like how it’s just a HTML file at 58kb!

    Using #Android, it failed due to Android Storage Access Framework (#SAF) limitations. I ended using the amazing #Termux once again to run #Busybox #httpd, automate the whole process of opening, serving & saving back to my…

    Full note: burgeonlab.com/notes/2026/0325
    Syndicated by #Indiekit

    #syncthing #bash #wiki #FOSS

  8. Varastossa makaa pari hyvin vanhaa QNAP’n NAS palvelinta ja siellä olisi terakaupalla hyvää tilaa esim. perheen kuville, puhelinten varmuuskopioiden ja kuvagallerialle. En vaan ole varma saako niistä enää mitään käyttöön, kun QNAPin tuki NASin Busybox distrolle taitaa olla loppunut vuosia sitten.

    #qnap #nas #backup #homeautomation #busybox #linux

  9. Varastossa makaa pari hyvin vanhaa QNAP’n NAS palvelinta ja siellä olisi terakaupalla hyvää tilaa esim. perheen kuville, puhelinten varmuuskopioiden ja kuvagallerialle. En vaan ole varma saako niistä enää mitään käyttöön, kun QNAPin tuki NASin Busybox distrolle taitaa olla loppunut vuosia sitten.

    #qnap #nas #backup #homeautomation #busybox #linux

  10. make your filesystem eventful using inotify cmds,
    the REACT for filesystems ❤

    ```
    $ inotifyd ./myscript /dir /dir/sub/dir &

    $ touch /dir/foo.json
    myscript: w /dir/foo.json

    $ touch /dir/sub/dir/bar.json
    myscript: w /dir/sub/dir/bar.json
    ```

    #hack #eventdriven #busybox #toybox

  11. make your filesystem eventful using inotify cmds,
    the REACT for filesystems ❤

    ```
    $ inotifyd ./myscript /dir /dir/sub/dir &

    $ touch /dir/foo.json
    myscript: w /dir/foo.json

    $ touch /dir/sub/dir/bar.json
    myscript: w /dir/sub/dir/bar.json
    ```

    #hack #eventdriven #busybox #toybox

  12. make your filesystem eventful using inotify cmds,
    the REACT for filesystems ❤

    ```
    $ inotifyd ./myscript /dir /dir/sub/dir &

    $ touch /dir/foo.json
    myscript: w /dir/foo.json

    $ touch /dir/sub/dir/bar.json
    myscript: w /dir/sub/dir/bar.json
    ```

    #hack #eventdriven #busybox #toybox

  13. [Перевод] Собираем и запускаем минимальное ядро Linux

    Однажды на работе техлид порекомендовал мне проштудировать книгу Understanding the Linux Kernel Бове и Чезати. В ней рассмотрена версия Linux 2.6, сильно не дотягивающая до более современной версии 6.0. Но в ней явно ещё много ценной информации. Книга толстая, поэтому на её изучение мне потребовалось немало времени. Занимаясь по ней, я решил настроить такую среду разработки, в которой я мог бы просматривать и изменять новейшую версию ядра Linux — чтобы было ещё интереснее. Есть и другие статьи, в которых рассказано, как собрать ядро Linux. Но в этой статье я немного иначе организую и подаю информацию.

    habr.com/ru/companies/timeweb/

    #timeweb_статьи_перевод #linux #ядро_linux #kgdb #qemu #busybox #vim #cd #ifplugd #install

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

    #BusyBox #ToyBox #runit

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

    #BusyBox #ToyBox #runit

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

    #BusyBox #ToyBox #runit

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

    #BusyBox #ToyBox #runit

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

    #BusyBox #ToyBox #runit

  19. @hexaheximal case in point:
    #Copyleft doesn't work in terms of getting #contributions or actual improvements.

    One can not really force people to do intellectual labour nor get them to share it!

    But don't take my word for it, because @landley has been there and done that as the fmr. maintainer of #BusyBox and nowadays maintains a competing project (#toybox) licensed under #0BSD...

    ---

    TBH I'm not against the #GPL, not even #GPLv3 because when you want to commit #AssetDenial it does that fine and I use it for that...

    But sadly #FLOSS doesn't exist in a vacuum and as much as I wished #CCSS to never have existed in the first place, it sadly does and worse people often depend on that shite...

    ---

    So I do aim to #DoBetter instead...

  20. @hexaheximal case in point:
    #Copyleft doesn't work in terms of getting #contributions or actual improvements.

    One can not really force people to do intellectual labour nor get them to share it!

    But don't take my word for it, because @landley has been there and done that as the fmr. maintainer of #BusyBox and nowadays maintains a competing project (#toybox) licensed under #0BSD...

    ---

    TBH I'm not against the #GPL, not even #GPLv3 because wgen you want to commit #AssetDenial it does that fine and I use it for that...

    But sadly #FLOSS doesn't exist in a vacuum and as much as I wished #CCSS to never have existed in the first place, it sadly does and worse people often depend on that shite...

    ---

    So I do aim to #DoBetter instead...

  21. Tangents aside, people are free to create forks and even branches that include #SystemD or use #BusyBox:

    That is the #Freedom of #FLOSS and in fact for anything outside the 1440kB target we'd accept #SystemD since it works and solves a lot of issues...
    youtube.com/watch?v=o_AIw9bGog

    Granted OS/1337 isn't a #demo first but rather tries to take the concept of #tomsrtbt and @w84death 's #Floppinux and tries to make it something that is useable and can be extended to arbitrary complexity if one desires to...

    It's about making a tiny #Linux distro that is #reproduceable and #auditable...

    It won't replace @ubuntu or any other big distro, likely it won't even replace #mkroot from #toybox but it should be a clean and level foundation for small #IoT and #EmbeddedSystems projects and products...

    Something that is easy to build and customize and port to other platforms...

    And we're open for contributions:
    github.com/OS-1337/OS1337/blob

  22. Tangents aside, people are free to create forks and even branches that include #SystemD or use #BusyBox:

    That is the #Freedom of #FLOSS and in fact for anything outside the 1440kB target we'd accept #SystemD since it works and solves a lot of issues...
    youtube.com/watch?v=o_AIw9bGog

    Granted OS/1337 isn't a #demo first but rather tries to take the concept of #tomsrtbt and @w84death 's #Floppinux and tries to make it something that is useable and can be extended to arbitrary complexity if one desires to...

    It's about making a tiny #Linux distro that is #reproduceable and #auditable...

    It won't replace @ubuntu or any other big distro, likely it won't even replace #mkroot from #toybox but it should be a clean and level foundation for small #IoT and #EmbeddedSystems projects and products...

    Something that is easy to build and customize and port to other platforms...

    And we're open for contributions:
    github.com/OS-1337/OS1337/blob

  23. Someone asked "Why don't you use BusyBox?

    Let me answer this simply...

    1. #BusyBox's #Licensing page kinda makes them look #toxic...
    busybox.net/license.html

    And @landley went into great detail on why the whole "enforcement" backfired very hard:
    youtube.com/watch?v=MkJkyMuBm3

    2. #toybox on the other hand is very much a drop-in replacement and it's #0BSD licensed, so much less headaches...
    landley.net/toybox/license.htm

    So it was chosen for OS/1337:
    github.com/OS-1337/OS1337/blob

    3. We use unmodified source code as of today and thus can just link to the original sources and attribute them properly:
    github.com/OS-1337/OS1337/blob

    #NotLegalAdvice but AFAICS this is sufficient for compliance.

    I

  24. Someone asked "Why don't you use BusyBox?

    Let me answer this simply...

    1. #BusyBox's #Licensing page kinda makes them look #toxic...
    busybox.net/license.html

    And @landley went into great detail on why the whole "enforcement" backfired very hard:
    youtube.com/watch?v=MkJkyMuBm3

    2. #toybox on the other hand is very much a drop-in replacement and it's #0BSD licensed, so much less headaches...
    landley.net/toybox/license.htm

    So it was chosen for OS/1337:
    github.com/OS-1337/OS1337/blob

    3. We use unmodified source code as of today and thus can just link to the original sources and attribute them properly:
    github.com/OS-1337/OS1337/blob

    #NotLegalAdvice but AFAICS this is sufficient for compliance.

    I

  25. @DavittoKun Actually, I've not come that long and have been quite #lazy and #halfassing things way too much.

    I just took @w84death 's #Floppinux Manual, a current #Linux Kernel, yeeted #BusyBox for @landley 's #toybox and hammered enough keys with my monkey brain to get a console working.

    @SweetAIBelle them beautified and streamlined the list of scripts I used to build it and provided ample of feedback and suggestions.

    In fact, I think everyone should read that Floppinux manual which is also a nice writeup to get started at the surface of it.
    archive.org/details/floppinux-

    It's an ongoing process and ideally it'll get modest success for those that look for #OpenBSD-alike security but with the ease and simplicity of "how do I get this running on my [weird] box?" since basically every SoC today can boot Linux more or less straightforward to some degree.

    I do OFC value and welcome feedback and support on that matter, as I can't even remotely claim to know everything without ridiculing myself with such a baseless statement.
    github.com/OS-1337

    Does it seem redundant to #mkroot?
    Yeah, but that's expected since mkroot's goal is to showcase toybox's self-reproduceability and using it's built-in gzip instead of xz is just one of the many concessions this will inevitably demand...

    Do I want OS/1337 to be 'self-hosting'?
    Yes, but it's not the prime goal and thus currently out of focus for testing...

    A lot of things will develop over time...

  26. @DavittoKun Actually, I've not come that long and have been quite #lazy and #halfassing things way too much.

    I just took @w84death 's #Floppinux Manual, a current #Linux Kernel, yeeted #BusyBox for @landley 's #toybox and hammered enough keys with my monkey brain to get a console working.

    @SweetAIBelle them beautified and streamlined the list of scripts I used to build it and provided ample of feedback and suggestions.

    In fact, I think everyone should read that Floppinux manual which is also a nice writeup to get started at the surface of it.
    archive.org/details/floppinux-

    It's an ongoing process and ideally it'll get modest success where one looks for #OpenBSD-alike security but with the ease and simplicity of "how do I get this running on my [weird] box?" since basically every SoC today can boot Linux more or less straightforward.

    I do OFC value and welcome feedback and support on that matter, as I can't even remotely claim to know everything without ridiculing myself with such a baseless statement.
    github.com/OS-1337

    Does it seem redundant to #mkroot?
    Yeah, but that's expected since mkroot's goal is to showcase toybox's self-reproduceability and using it's built-in gzip instead of xz is just one of the many concessions this will inevitably demand...

    Do I want OS/1337 to be 'self-hosting'?
    Yes, but it's not the prime goal and thus currently out of focus for testing...

    A lot of things will develop over time...

  27. @geraldew @RTP @linux @torvalds

    Being a "universal donor license" would be a reason.

    But don't take my word for it, ask @landley on why he left #BusyBox and started #toybox under #0BSD.

    TLDW: #Copyleft backfired and made BusyBox notoriously hostile to vendors as well as kinda hurt everyone.
    youtube.com/watch?v=MkJkyMuBm3

    The reason why no "applianced" Console runs #Linux is the #GPL, because #PlayStation since the #PS2 and #Nintendo since the #WiiU run #FreeBSD as #Copyleft would be incompatible with their #DRM and subsequent #NDA's as well as contractual secrecy per their vendors & subcontractors...

    #Valve and the #SteamDeck aren't compareable to i.e. the #NintendoSwitch because they see it as a tool to increase revenue per #Steam User, not as a means to increase their market share from de-facto to de-jure #monopoly whilst facing stiff competition like #XboxGamePass on the #PC and #Chromebooks as well as #ChromeOS flex running #Android #Games!

  28. @geraldew @RTP @linux @torvalds

    Being a "universal donor license" would be a reason.

    But don't take my word for it, ask @landley on why he left #BusyBox and started #toybox under #0BSD.

    TLDW: #Copyleft backfired and made BusyBox notoriously hostile to vendors...
    youtube.com/watch?v=MkJkyMuBm3

  29. @BrodieOnLinux @fuchsiii OFC not - and not because they don't want to [tho I'd also nope ransomware groups' demands] but also because #nvidia can't legally do that in many cases, as they too are #licensees of #patents and are bound to #NDA's.

    So #GPLv3 and #AGPLv3 are impossible to comply with and even #GPLv2 would be hard to.

    Kinda like the shitshow #BusyBox did (gojng GPLv3 and sueing the crap out of license violators), so @landley left that project and started #toybox from the ground up.

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

  31. Updated #FreshTomato #firmware on my #Netgear #R7000 #router and #ASUS RT-N66U that I use as a switch + WiFi AP.

    For some reason it was a pain to get the WAN working again. Rebooting the cable modem and R7000 eventually cleared it up?

    Noticed that #busybox #ntpd on the firmware doesn't respond to ntpq queries and is rather config-limited, so I installed the #entware version on the R7000's USB stick.

    Also uninstalled #avahi because it's now built into the firmware - neat! Now do #wsdd2 please!

  32. Updated #FreshTomato #firmware on my #Netgear #R7000 #router and #ASUS RT-N66U that I use as a switch + WiFi AP.

    For some reason it was a pain to get the WAN working again. Rebooting the cable modem and R7000 eventually cleared it up?

    Noticed that #busybox #ntpd on the firmware doesn't respond to ntpq queries and is rather config-limited, so I installed the #entware version on the R7000's USB stick.

    Also uninstalled #avahi because it's now built into the firmware - neat! Now do #wsdd2 please!

  33. Updated #FreshTomato #firmware on my #Netgear #R7000 #router and #ASUS RT-N66U that I use as a switch + WiFi AP.

    For some reason it was a pain to get the WAN working again. Rebooting the cable modem and R7000 eventually cleared it up?

    Noticed that #busybox #ntpd on the firmware doesn't respond to ntpq queries and is rather config-limited, so I installed the #entware version on the R7000's USB stick.

    Also uninstalled #avahi because it's now built into the firmware - neat! Now do #wsdd2 please!