Closed issue by dbrll on void-packages repository

https://github.com/void-linux/void-packages/issues/11263

Description:
I'm migrating my userland from GNU Coreutils to Busybox and have noticed several issues with the Void package.

- `CONFIG_FEATURE_USERNAME_COMPLETION` not set in [.config](https://github.com/void-linux/void-packages/blob/master/srcpkgs/busybox/files/dotconfig).
That means the autocompletion will not work for $HOME, which is annoying when using busybox as a login shell. There is no apparent reason why this flag shouldn't be set.

- If `/bin/ash` doesn't exist, the package should create a symlink /bin/ash -> /bin/busybox and add it to /etc/shells. This needs to be done manually so far.

- "ping" applet doesn't work
Since adding a suid flag on /bin/busybox is out of question, the following should be done instead:
```
setcap cap_net_raw=ep /bin/busybox  # set capability for raw sockets on the binary
sysctl -w net.ipv4.ping_group_range=1 4  # allow GIDs 1 to 4 (wheel) to ping (should be added to /etc/sysctl.conf)
```
- "less" only show the first line of the file. I couldn't figure this one. Building from the upstream sources provides a working applet so this seems specific to the package.

- The static build will most likely be used in the initramfs as a rescue shell, or as the login shell for root (same use case). Setting `CONFIG_FEATURE_SH_STANDALONE` for the static package would probably make sense, so the shell will first use its builtin commands.

* package:  
busybox-1.30.1_1