Re: Several issues with busybox-1.30

Re: Several issues with busybox-1.30

[voidlinux-github]

[-- Attachment #1: Type: text/plain, Size: 220 bytes --]

New comment by CameronNemo on void-packages repository

https://github.com/void-linux/void-packages/issues/11263#issuecomment-489375894
Comment:
Anything else of interest? Working on this now, hoping to have a PR later.

Re: Several issues with busybox-1.30

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 286 bytes --]

New comment by ericonr on void-packages repository

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

Comment:
SUID'ing or otherwise adding caps to busybox seems bad. IIRC Alpine carries a patch that moves things around in ping to not require privileges.

Re: Several issues with busybox-1.30

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 286 bytes --]

New comment by ericonr on void-packages repository

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

Comment:
SUID'ing or otherwise adding caps to busybox seems bad. IIRC Alpine carries a patch that moves things around in ping to not require privileges.

Re: Several issues with busybox-1.30

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 286 bytes --]

New comment by ericonr on void-packages repository

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

Comment:
SUID'ing or otherwise adding caps to busybox seems bad. IIRC Alpine carries a patch that moves things around in ping to not require privileges.

Re: Several issues with busybox-1.30

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

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

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: Several issues with busybox-1.30

[Toromino]

[-- Attachment #1: Type: text/plain, Size: 556 bytes --]

New comment by Toromino on void-packages repository

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

Comment:
> Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.

The issues are still present. :woozy_face: 

We could probably copy over the patches that Alpine, Adelie and other Linux distros use.
https://git.adelielinux.org/ska/packages/-/tree/master/legacy/busybox
https://git.alpinelinux.org/aports/tree/main/busybox?h=master

Re: Several issues with busybox-1.30

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

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

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: Several issues with busybox-1.30

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 227 bytes --]

New comment by ericonr on void-packages repository

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

Comment:
At that point they might just as well fork busybox.... That's way too many patches.

Re: Several issues with busybox-1.30

[kehak]

[-- Attachment #1: Type: text/plain, Size: 273 bytes --]

New comment by kehak on void-packages repository

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

Comment:
Many of those patches should actually be merged upstream. And those which aren't bugfixes should be allowed to be built as options.

Re: Several issues with busybox-1.30

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

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

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: [ISSUE] [CLOSED] Several issues with busybox-1.30

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]

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

Re: Several issues with busybox-1.30

[xplshn]

[-- Attachment #1: Type: text/plain, Size: 454 bytes --]

New comment by xplshn on void-packages repository

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

Comment:
Seems like the way to go would be to create a PR... Busybox is already provided, we should be alright using all the patches from Alpine, which are small tweaks to make Busybox suitable for general systems and not embedded ones. Also, the busybox package should provide "alternatives" like the `ip` command, etc.