add support for coreutils compiled with --enable-single-binary #128
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When coreutils is compiled with the
--enable-single-binaryoption, all the individual commands are just symlinks to a larger single binary named "coreutils", the same way that a typical busybox binary works. In this situation,progressgets back the name "coreutils" instead of, for example, "dd" when reading/proc/[pid]/exe.Unfortunately this means that, on systems with single-binary coreutils, all of your running commands will show up as "coreutils" instead of the command you actually typed.