|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST doesn´t delete udev settings and sysconfig files when deleting a device | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Michael Stather <kontakt> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Michael Stather
2006-01-23 22:19:58 UTC
I just experiented a bit and read the documentation and it seems YaST does remove the sysconfig files. The files in my folder were some leftovers from old or buggy versions of YaST. But the udev rules thing still applies. When I also forgot is that the information in /var/lib/hardware should also be set to "not configured", so that the hardware is re-detected as new when inserted again (and the notification pops up). Or perhaps it´s even better to delete the /var/lib/hardware file, so that there aren´t leftovers for old devices (I´ve plenty of them on my system, e.g. for old graphics cards). Michael: Can you reference your reports here? Please notice that from 10.1+ the removable network devices are handled by NetworkManager and therefore the mechanism will change completely, hence bugreports made for 10.0 will not be applicable for 10.1 here. If you find something wrong with the behaviour of how 10.1 Beta1 handles this, please be specific about this. I'm not sure if you're actually using Beta1? Unfortunately all versions greater than 10.1 A3 don´t run on my systems. I filed a bug for 10.0 about this issue here and somebody said it´s a thing for 10.1, so I filed this bug report. I´ll try beta2 when it´s out. If there aren´t any udev rules which get automatically created (like it used to be) then you´re right, if they´re still there this still applies. What I said in comment #1 about the information /var/lib/hardware should also still apply since it´s not specific to network devices but to all devices and PCI cards. Kay: Please comment on this. Udev itself does not create any device specific files. And if YaST should remove files or the corresponding lines for the assigned persistent network names, I really can't tell, sorry. (Adding Christian for the network part.) The udev rules for persistent interface names are created automatically. Would be nice could remove them. But afaik it still does not do that. I don't know if YaST removes hwcfg files. Let's ask Martin. I tested it out with 10.0 and YaST does remove the hwcfg files but do4esn´t remove the udev rules and /var/lib/hardware infos. So will this change in 10.1? Why don´t you reply to this bug??? You said that you´ll honor bug reports from the userbase, so please do it! This is a major design issue, so why don´t you read the report and think about it? I really doubt whether I should continue to submit bug reports, I´ve filed so much of them and I get no response for months. Sorry, I was busy with other things and bugs with higher severity. You can always just "ping" in a bug to get my attention. I will have a look. Cool :) Reassigning to the new maintainer of yast2-network. *** Bug 133300 has been marked as a duplicate of this bug. *** This will be implemented for 10.3 Sorry, it was postponed, but implemented in 11.0: http://en.opensuse.org/index.php?title=YaST/Network/11.0-new_features |