-
Notifications
You must be signed in to change notification settings - Fork 401
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
Since last update using --conf /dev/null
fails. How do I ignore preexisting config files?
#1835
Comments
You can pass an empty file to |
I was hoping for a solution that doesn't require creating a new file and directory. Especially for automated invocation, I need a stateless approach and cannot rely on the state of the user's filesystem. Is there any rationale behind not allowing /dev/null to disable configuration? It seems like an unnecessary complication from my point of view. |
I don't see why calling
|
Not strictly a technical issue of course, but arguably a usability issue. All classical command-line tools can be used with special files from I hope I could clarify why it seems strange to me, when a tool actively prohibits this type of usage. This is also why I initially expected there to be a technical reason for dracut to disallow it. I'm still not sure if that's the case, but if it isn't, I think it feels like an artificial restriction with no apparent benefit. Of course this is a very minor thing overall, but I'd like to say that I would be happy if dracut could be used as described. :) |
Dracut changed parameter interpretation in a new version, causing this script to error out. To properly fix this, we require a resolution of dracutdevs/dracut#1835. Meanwhile, this is tracked internally by #41.
Excuse my impatience, but I wonder if there has been an update to this issue in the meantime? |
I think this is a behaviour change, as |
If file is not a regular file (test -f), dracut.sh fails, which is unexpected change of behaviour. The workaround would be to create an empty file. Fixes: dracutdevs#1835
If file is not a regular file (test -f), dracut.sh fails, which is unexpected change of behaviour. The workaround would be to create an empty file. Fixes: #1835
See dracutdevs/dracut#1835 (cherry picked from commit 3c86f60)
See dracutdevs/dracut#1835 (cherry picked from commit 3c86f60)
Describe the bug
Since the last major update, invoking dracut with
--conf /dev/null
fails. If I see correctly, this has been introduced as a response to #1136, where it was considered a bug not to reject/dev/null
. I've been using--conf /dev/null --confdir /dev/null
to ignore any existing configuration files, but the linked issue suggests this never worked (?). What is the correct way to make dracut ignore any existing configuration files, now that/dev/null
is invalid?Distribution used
Latest arch LIVE-USB environment
Dracut version
dracut-056
The text was updated successfully, but these errors were encountered: