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

Allow to select no driver (auto) #958

Merged
merged 4 commits into from Sep 16, 2019

Conversation

imobachgs
Copy link
Contributor

@imobachgs imobachgs commented Sep 13, 2019

In my tests I ended in this scenario: let's say that I select a custom driver for a given interface, which caused a udev rule to be written. The next time that I open the hardware dialog again, I can only switch between the custom and the virtio_net driver. But, in both cases, a udev rule will be written (or updated). But what I want to do is to not force any driver at all. The only option is to manually delete the file.

As a solution, I have extended the drivers dialog to support an auto option, in which case no udev rule is written (and the kernel will decide which module to use).

driver-auto

@imobachgs imobachgs marked this pull request as ready for review September 16, 2019 05:23
@@ -70,6 +70,7 @@ def initialize(name, params = "")
# @param other [Driver] Driver to compare with
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please document that it can accept also non Driver

subject.save
end

it "does not update any driver" do
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we want not update or explicit udev rule delete?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is about setting the Driver options.

@imobachgs imobachgs merged commit 8aea8b7 into network-ng Sep 16, 2019
@imobachgs imobachgs deleted the network-ng-fix_custom_driver_assignment branch September 16, 2019 08:28
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.05%) to 66.561% when pulling 90a5425 on network-ng-fix_custom_driver_assignment into 8b183bf on network-ng.

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.

None yet

3 participants