Instead of hardcoding paths, look for them in the most obvious places #2367
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.
Closes: #460
I know this is somewhat ugly, but I think it's better than hardcoding paths (which, as I've said elsewhere, I really, really hate! :).
To support the old behavior (setting the variable in the shell before calling), I first check to make sure the variable is empty, THEN check for it's existance...
The issue mentioned only talks about lsmod, but I figure since I do this, I could just as well do it for all the commands (including the udev{trigger,settle})...