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

dkms: always use read_conf_or_die #354

Merged
merged 1 commit into from
Oct 21, 2023
Merged

Conversation

evelikov
Copy link
Collaborator

Currently dkms status and by extension dkms autoinstall use read_conf, which prints an error yet results in the commands succeeding.

Browsing across Arch and Debian, this can only happen on user error. As such lets flip it to the fatal "_or_die" variant, like all the other instances in the codebase.


See #352 for context.

/cc @scaronni @anbe42 @C0rn3j do shout if you think this is a bad idea, thanks in advance.

Currently dkms status and by extension dkms autoinstall use read_conf,
which prints an error yet results in the commands succeeding.

Browsing across Arch and Debian, this can only happen on user error. As
such lets flip it to the fatal "_or_die" variant, like all the other
instances in the codebase.

Signed-off-by: Emil Velikov <[email protected]>
@scaronni scaronni merged commit c0004f0 into dell:master Oct 21, 2023
@evelikov evelikov deleted the fatal-conf branch October 21, 2023 19:58
@evelikov evelikov mentioned this pull request Oct 24, 2023
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.

2 participants