Re:The button went RED and he updated. Oops- MIsta
Posted by: Anonymous Coward
on March 01, 2006 01:19 AM
I understand what you are saying but, I still must argue. You took a distribution and replaced some of its files with non-distro files in order to play back DVD's. The files share the same name so when the update runs it overwrites those files.
This is almost exactly the type of thing that happens on Windows with files like MSVCRT40.DLL or VBRUN600.DLL ALL THE FRICKING TIME! Some application overwrites the file with an older/different version and all sorts of applications puke! Some crap application requires a "specially modified" version of MSVCRT40.DLL, Windows updates to the latest official Microsoft version and the application dumps.
It is a problem, I agree. It could be improved upon, I agree. But, it is not a problem that is unique to Linux or SuSE. Had you installed the modified Xine packages in a different location or using a different file name, the problem would not have occurred. Additionally, if you had not replaced SuSE files with non-SuSE files, there would not have been any breakage.
The odd thing is that Microsoft is excused of its problems, such as this. Everyone knows it is a problem and simply accepts it and sets to working around the problem. But, when any other OS hickups, it is completely unacceptable! I see the same thing in the hardware world. Some Cisco kit fails and it's perfectly OK but, if it's 3Com or Juniper or Nortel then it's a totally unacceptable failure and people start talking about ripping everything out and replacing it with Cisco.
Learn about Linux
Download Linux
Get Linux help
Re:The button went RED and he updated. Oops- MIsta
Posted by: Anonymous Coward on March 01, 2006 01:19 AMThis is almost exactly the type of thing that happens on Windows with files like MSVCRT40.DLL or VBRUN600.DLL ALL THE FRICKING TIME! Some application overwrites the file with an older/different version and all sorts of applications puke! Some crap application requires a "specially modified" version of MSVCRT40.DLL, Windows updates to the latest official Microsoft version and the application dumps.
It is a problem, I agree. It could be improved upon, I agree. But, it is not a problem that is unique to Linux or SuSE. Had you installed the modified Xine packages in a different location or using a different file name, the problem would not have occurred. Additionally, if you had not replaced SuSE files with non-SuSE files, there would not have been any breakage.
The odd thing is that Microsoft is excused of its problems, such as this. Everyone knows it is a problem and simply accepts it and sets to working around the problem. But, when any other OS hickups, it is completely unacceptable! I see the same thing in the hardware world. Some Cisco kit fails and it's perfectly OK but, if it's 3Com or Juniper or Nortel then it's a totally unacceptable failure and people start talking about ripping everything out and replacing it with Cisco.
#