Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instead of hardcoding paths, look for them in the most obvious places #2367

Closed
wants to merge 1 commit into from

Conversation

FransUrbo
Copy link
Contributor

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})...

@behlendorf
Copy link
Contributor

@FransUrbo sorry I lost track of this. When you get a moment could you rebase it on master so it'll run through the buildbot. Since many of the test cases depend on this common functionality we'll learn pretty quickly if this is safe to merge.

@behlendorf
Copy link
Contributor

Yeah, I was afraid of that. @FransUrbo let's not rock the boat here so to speak. This issue only impacted Arch Linux and arguably they can handle that downstream.

@behlendorf behlendorf closed this May 4, 2015
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.

/sbin/lsmod: No such file or directory
2 participants