home.social

#busybox — Public Fediverse posts

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

  1. PSA: In #debian unstable, "copy_exec /bin/lsblk" stopped working when used in an initramfs-tools hook. Why? The #busybox 1.38.0 upload enabled the lsblk applet and (to my surprise) the "copy_exec" function will not overwrite the destination file if it already exists. Since busybox lsblk does not support any command line flags, my initramfs scripts which expected lsblk from util-linux failed in funny and non-obvious ways. Time to make these scripts more robust. :)

  2. PSA: In #debian unstable, "copy_exec /bin/lsblk" stopped working when used in an initramfs-tools hook. Why? The #busybox 1.38.0 upload enabled the lsblk applet and (to my surprise) the "copy_exec" function will not overwrite the destination file if it already exists. Since busybox lsblk does not support any command line flags, my initramfs scripts which expected lsblk from util-linux failed in funny and non-obvious ways. Time to make these scripts more robust. :)

  3. PSA: In #debian unstable, "copy_exec /bin/lsblk" stopped working when used in an initramfs-tools hook. Why? The #busybox 1.38.0 upload enabled the lsblk applet and (to my surprise) the "copy_exec" function will not overwrite the destination file if it already exists. Since busybox lsblk does not support any command line flags, my initramfs scripts which expected lsblk from util-linux failed in funny and non-obvious ways. Time to make these scripts more robust. :)

  4. PSA: In #debian unstable, "copy_exec /bin/lsblk" stopped working when used in an initramfs-tools hook. Why? The #busybox 1.38.0 upload enabled the lsblk applet and (to my surprise) the "copy_exec" function will not overwrite the destination file if it already exists. Since busybox lsblk does not support any command line flags, my initramfs scripts which expected lsblk from util-linux failed in funny and non-obvious ways. Time to make these scripts more robust. :)

  5. PSA: In #debian unstable, "copy_exec /bin/lsblk" stopped working when used in an initramfs-tools hook. Why? The #busybox 1.38.0 upload enabled the lsblk applet and (to my surprise) the "copy_exec" function will not overwrite the destination file if it already exists. Since busybox lsblk does not support any command line flags, my initramfs scripts which expected lsblk from util-linux failed in funny and non-obvious ways. Time to make these scripts more robust. :)

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

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

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

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

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

  11. Ten years ago, I built a #WebSocket server using nothing but #UNIX shell and #BusyBox tools. 🛠️

    Looking back at `websocket.sh` today, it's just a fun, interesting project that shows how far you can stretch basic tools.

    Read the original post: meefik.dev/2016/08/04/websocke

    #Linux #Bash #Coding #Throwback

  12. Ten years ago, I built a #WebSocket server using nothing but #UNIX shell and #BusyBox tools. 🛠️

    Looking back at `websocket.sh` today, it's just a fun, interesting project that shows how far you can stretch basic tools.

    Read the original post: meefik.dev/2016/08/04/websocke

    #Linux #Bash #Coding #Throwback

  13. Ten years ago, I built a #WebSocket server using nothing but #UNIX shell and #BusyBox tools. 🛠️

    Looking back at `websocket.sh` today, it's just a fun, interesting project that shows how far you can stretch basic tools.

    Read the original post: meefik.dev/2016/08/04/websocke

    #Linux #Bash #Coding #Throwback

  14. Ten years ago, I built a #WebSocket server using nothing but #UNIX shell and #BusyBox tools. 🛠️

    Looking back at `websocket.sh` today, it's just a fun, interesting project that shows how far you can stretch basic tools.

    Read the original post: meefik.dev/2016/08/04/websocke

    #Linux #Bash #Coding #Throwback

  15. Ten years ago, I built a #WebSocket server using nothing but #UNIX shell and #BusyBox tools. 🛠️

    Looking back at `websocket.sh` today, it's just a fun, interesting project that shows how far you can stretch basic tools.

    Read the original post: meefik.dev/2016/08/04/websocke

    #Linux #Bash #Coding #Throwback

  16. Following on from my #kindle hacking - I haven't yet got a custom kernel booting but I did use the bootargs to drop into a simple #busybox shell which meant I could root the device by changing the password:

    1. Connected up serial lines (1.8v)
    2. Drop into u-boot
    3. `setenv bootargs setenv bootargs root=/dev/mmcblk0p1 earlyprintk console=ttymxc0,115200 init=/bin/sh`
    4. `boot`
    5. Once it drops into the busybox shell do `mount -o remount, rw /` to remount the as rw
    6. `passwd`
    7. Set a new password
    8. `reboot now` and this time let it fully boot up
    9. Login in via serial using `root` and your password

  17. Following on from my hacking - I haven't yet got a custom kernel booting but I did use the bootargs to drop into a simple shell which meant I could root the device by changing the password:

    1. Connected up serial lines (1.8v)
    2. Drop into u-boot
    3. `setenv bootargs setenv bootargs root=/dev/mmcblk0p1 earlyprintk console=ttymxc0,115200 init=/bin/sh`
    4. `boot`
    5. Once it drops into the busybox shell do `mount -o remount, rw /` to remount the as rw
    6. `passwd`
    7. Set a new password
    8. `reboot now` and this time let it fully boot up
    9. Login in via serial using `root` and your password

  18. Following on from my #kindle hacking - I haven't yet got a custom kernel booting but I did use the bootargs to drop into a simple #busybox shell which meant I could root the device by changing the password:

    1. Connected up serial lines (1.8v)
    2. Drop into u-boot
    3. `setenv bootargs setenv bootargs root=/dev/mmcblk0p1 earlyprintk console=ttymxc0,115200 init=/bin/sh`
    4. `boot`
    5. Once it drops into the busybox shell do `mount -o remount, rw /` to remount the as rw
    6. `passwd`
    7. Set a new password
    8. `reboot now` and this time let it fully boot up
    9. Login in via serial using `root` and your password

  19. Following on from my #kindle hacking - I haven't yet got a custom kernel booting but I did use the bootargs to drop into a simple #busybox shell which meant I could root the device by changing the password:

    1. Connected up serial lines (1.8v)
    2. Drop into u-boot
    3. `setenv bootargs setenv bootargs root=/dev/mmcblk0p1 earlyprintk console=ttymxc0,115200 init=/bin/sh`
    4. `boot`
    5. Once it drops into the busybox shell do `mount -o remount, rw /` to remount the as rw
    6. `passwd`
    7. Set a new password
    8. `reboot now` and this time let it fully boot up
    9. Login in via serial using `root` and your password

  20. Following on from my #kindle hacking - I haven't yet got a custom kernel booting but I did use the bootargs to drop into a simple #busybox shell which meant I could root the device by changing the password:

    1. Connected up serial lines (1.8v)
    2. Drop into u-boot
    3. `setenv bootargs setenv bootargs root=/dev/mmcblk0p1 earlyprintk console=ttymxc0,115200 init=/bin/sh`
    4. `boot`
    5. Once it drops into the busybox shell do `mount -o remount, rw /` to remount the as rw
    6. `passwd`
    7. Set a new password
    8. `reboot now` and this time let it fully boot up
    9. Login in via serial using `root` and your password

  21. @jpmens

    In the spirit of there always being 1 more #vi clone than one thinks, notice that @lpar 's list is lacking Ali Gholami Rudi's #neatvi which is packaged in #pkgsrc and about a decade old now.

    pkgsrc.se/editors/neatvi

    And even then the rule still applies. There's 1 more clone: Sterling Huxley's and Brent Roman's #viless, a quarter of a century old and what #BusyBox supplies.

    github.com/brentr/viless

    #NetBSD #OmniOS

  22. @jpmens

    In the spirit of there always being 1 more #vi clone than one thinks, notice that @lpar 's list is lacking Ali Gholami Rudi's #neatvi which is packaged in #pkgsrc and about a decade old now.

    pkgsrc.se/editors/neatvi

    And even then the rule still applies. There's 1 more clone: Sterling Huxley's and Brent Roman's #viless, a quarter of a century old and what #BusyBox supplies.

    github.com/brentr/viless

    #NetBSD #OmniOS

  23. @jpmens

    In the spirit of there always being 1 more #vi clone than one thinks, notice that @lpar 's list is lacking Ali Gholami Rudi's #neatvi which is packaged in #pkgsrc and about a decade old now.

    pkgsrc.se/editors/neatvi

    And even then the rule still applies. There's 1 more clone: Sterling Huxley's and Brent Roman's #viless, a quarter of a century old and what #BusyBox supplies.

    github.com/brentr/viless

    #NetBSD #OmniOS

  24. @jpmens

    In the spirit of there always being 1 more #vi clone than one thinks, notice that @lpar 's list is lacking Ali Gholami Rudi's #neatvi which is packaged in #pkgsrc and about a decade old now.

    pkgsrc.se/editors/neatvi

    And even then the rule still applies. There's 1 more clone: Sterling Huxley's and Brent Roman's #viless, a quarter of a century old and what #BusyBox supplies.

    github.com/brentr/viless

    #NetBSD #OmniOS

  25. @jpmens

    In the spirit of there always being 1 more #vi clone than one thinks, notice that @lpar 's list is lacking Ali Gholami Rudi's #neatvi which is packaged in #pkgsrc and about a decade old now.

    pkgsrc.se/editors/neatvi

    And even then the rule still applies. There's 1 more clone: Sterling Huxley's and Brent Roman's #viless, a quarter of a century old and what #BusyBox supplies.

    github.com/brentr/viless

    #NetBSD #OmniOS

  26. Randomly wondering: Does anyone know what's going on with #Busybox? The last release is a year and half old, there has been development in Git, including bugfixes (including ones that may be relevant for security, like 3fb6b31c716669e12f75a2accd31bb7685b1a1cb), but there's no sign of a new release. The mailing list is mostly people complaining gitweb doesn't work, and a fix for httpd I sent early this month didn't get any response… ​:neocat_think:​

  27. Randomly wondering: Does anyone know what's going on with #Busybox? The last release is a year and half old, there has been development in Git, including bugfixes (including ones that may be relevant for security, like 3fb6b31c716669e12f75a2accd31bb7685b1a1cb), but there's no sign of a new release. The mailing list is mostly people complaining gitweb doesn't work, and a fix for httpd I sent early this month didn't get any response… ​:neocat_think:​