Skip to content

Conversation

@clintharrison
Copy link

Scripts currently run without PATH set at all.
This works somewhat okay for things directly launched within these scripts, because busybox defaults to PATH=/sbin:/usr/sbin:/bin:/usr/bin (source) for anything run in the script -- it's not set as an environment variable though, so it doesn't propagate to subprocesses.

This means directly running sh, eips, etc. will work fine, but any processes started (e.g. a daemon like utild) will have an unexpectedly empty PATH.

This changes sh to be invoked with -l (--login), which will execute /etc/profile and set the usual PATH.

clintharrison and others added 2 commits October 7, 2025 18:12
Scripts currently run without `PATH` set at all.
This works somewhat okay for things directly launched within these
scripts, because busybox defaults to PATH=/sbin:/usr/sbin:/bin:/usr/bin
for anything run in the script -- it's not set as an environment
variable though, so it doesn't propagate to subprocesses.

This means directly running sh, eips, etc. will work fine, but any
processes started (e.g. a daemon like utild) will have an unexpectedly
empty PATH.

This changes `sh` to be invoked with `-l` (`--login`), which will
execute `/etc/profile` and set the usual PATH.
@ThatHackerDudeFromCyberspace
Copy link
Member

Tests pass, LGTM

@ThatHackerDudeFromCyberspace ThatHackerDudeFromCyberspace merged commit 71aec3c into KindleModding:master Oct 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants