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

modules.d/35network-manager/nm-run.sh uses basename but does not require it #537

Closed
devurandom opened this issue Feb 12, 2019 · 2 comments
Closed

Comments

@devurandom
Copy link
Contributor

devurandom commented Feb 12, 2019

modules.d/35network-manager/nm-run.sh uses basename, but the accompanying module-setup.sh does not require it.

How to reproduce: On my system, sometimes bcache activation hangs forever, which will make 99-nm-run.sh start before the new rootfs is online. The console will then log lots of lines similar to: basename - no such file or directory.

Attached patch should fix this. (Applies cleanly, not yet tested)

dracut-049-network-manager-dependencies.patch.txt

See-Also: https://bugs.gentoo.org/677788

@mmokrejs
Copy link

Supposedly same patch will also fix for me:

/lib/dracut/hooks/initqueue/settled/99-nm-run.sh: line 13: basename: command not found

@danimo
Copy link
Contributor

danimo commented Oct 29, 2019

Issue is obsolete due to 4c216b1 of PR #578 in master.

@danimo danimo closed this as completed Oct 29, 2019
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 a pull request may close this issue.

3 participants