From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Several issues with busybox-1.30
Date: Wed, 09 Nov 2022 03:13:33 +0100 [thread overview]
Message-ID: <20221109021333.sD1-lLF8gq-ux_PAADQGtEgzp-Yqe3QmRCX6x2HXjEY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11263@inbox.vuxu.org>
[-- 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
next prev parent reply other threads:[~2022-11-09 2:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11263@inbox.vuxu.org>
2019-05-05 0:24 ` voidlinux-github
2021-01-30 2:07 ` ericonr
2021-01-30 2:07 ` ericonr
2021-01-30 23:42 ` ericonr
2022-04-15 0:52 ` github-actions
2022-04-15 11:09 ` Toromino
2022-07-15 2:14 ` github-actions
2022-07-17 20:24 ` ericonr
2022-07-26 19:23 ` kehak
2022-10-25 2:14 ` github-actions
2022-11-09 2:13 ` github-actions [this message]
2024-04-16 23:46 ` xplshn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221109021333.sD1-lLF8gq-ux_PAADQGtEgzp-Yqe3QmRCX6x2HXjEY@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).