Busybox automatically uses builtin commands, ignoring ones in $PATH
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 4.8k
- Forks
- 381
- PR merge metrics
- No merged PRs in 30d
Description
I've compiled GNU grep and sed and replaced the Busybox ones in my path, but calling them from the shell will always call the Busybox version unless I specify an absolute path.
Would it be possible to make Busybox give priority to executables in the path rather than its own builtins?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported shell behavior with GNU grep and sed earlier in PATH than the BusyBox commands, then trace how bare command names are resolved between built-ins and PATH. Done means PATH executables are selected when present, while normal built-in command behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100