https://bugzilla.novell.com/show_bug.cgi?id=219456 ------- Comment #37 from eich@novell.com 2007-01-08 03:35 MST ------- (In reply to comment #35)
Also if we can get SaX2 to unload the driver module (using some 'flag' that's been set up by the installation procedure) it can do with the link anything it likes. Sure, but we are talking about the situation, where it isn't possible to unload the module, because it runs on top of a NVIDIA Xserver.
This would only be the case if SaX was running inside the X session where the installation took place. Why would the user do that? Anyway if Marcus was willing to touch SaX2 there are two ways to remedy the problem. 1. SaX2 detects the situation and refuses to run - opening a window telling the user to restart X first. 2. SaX2 would detect the situation and do something smart about the link ie. changing the backup copy of the installer link - which could cause problems if multiple stacked backup copies existed or better assume the link is correct and leave it alone. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.