MiniBox, ultra small busybox without uncommon options | Hacker News Reader

MiniBox, ultra small busybox without uncommon options

github.com

Would this compile to WASM for use as a terminal in JupyterLite? Though, busybox has the ash shell instead of bash. https://github.com/jupyterlite/jupyterlite/issues/949

It could with a few tweaks, but it lacks features when compared to bash and busybox ash. For example, it doesn't support shell scripting, configuration file initialization, etc. I wouldn't recommended it right now though since it doesn't have most features of a standard shell but if you want to test it out, give it a try.

RustyBox is a c2rust port/rewrite of BusyBox to Rust; though it doesn't look like anyone has contributed fixes to the unsafe parts in awhile.

So, no SysV /etc/init.d because no shell scripting, and no systemd because embedded environment resource constraints? There must be a process to init and respawn processes on events like boot (and reboot, if there's a writeable filesystem)

Yes, you are right, I am trying to create a smaller version of sysvinit compatible with busybox's init. There is still no shell scripting yet, but I do promise to make the shell fully compatible with other shells with shell scripting in a future version.

What happened to RustyBox? c2rust is way easier than doing it manually, then why is it abandoned?

Same question about rustybox. Maybe they're helping with cosmos-de or coreutils or something.

OpenWRT has procd instead of systemd, but it does source a library of shell functions and run [somewhat haphazard] /etc/init.d scripts instead of parsing systemd unit configuration files to eliminate shell scripting errors when spawning processes as root.

https://westurner.github.io/hnlog/ Ctrl-F procd, busd

(This re: bootloaders, multiple images, and boot integrity verification: https://news.ycombinator.com/item?id=41022352 )

Systemd is great for many applications.

Alternatives to systemd: https://without-systemd.org/wiki/index_php/Alternatives_to_s...

There are advantages to systemd unit files instead of scripts. Porting packages between distros is less work with unit files. Systemd respawns processes consistently and with standard retry/backoff functionality. Systemd+journals produces indexable logs with consistent datetimes.

There's a pypi:SystemdUnitParser.

docker-systemctl-replacement > systemctl3.py parses and schedules processes defined in systemd unit files: https://github.com/gdraheim/docker-systemctl-replacement/blo...

Reply on news.ycombinator.com