Hi, BandiPat schrieb:
I did managed to get it installed, as I mentioned in my original email, but not without a bit of frustration and disappointment in 10.1. You say there is a fix, but how is that going to help a new user I've passed a copy of 10.1 on CD too? When will the fix be released? Will it be a security/bug update or?
Yes, it is already part of a set of updates which can be tested by the general public at ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/ and will be released to all users as YOU in the near future, so the crash will no longer happen in installed systems. But: It doesn't help those people who are experiencing this crash during the installation because the CDs are already mastered. Feedback, including disappointment, is of course OK, but it doesn't really help now - the problem cannot be fixed any more. Actually there is a way to fix such problems for released products - a driver update - but "someone" from the community would have to convince "someone" at SUSE that it's severe enough to be worth a driver update, this will not be easy...
As many have mentioned already, these things don't do much for the integrity of SUSE as a seasoned Linux product and unless they sent us all a new copy of the "fixed" CDs and DVD, it serves very little purpose to new installers trying to install SUSE.
I doubt that fixed CDs and DVDs will be sent to customers. If there will be a fix, it would have to be a driver update. This is a cdrom or floppy image that can be used to update the installation system right during the installation. But, as already mentioned, I'm not aware of any plans to create such a driver update - it's just an idea of a solution that would theoretically work. With some technical knowledge of how these driver updates work, even someone from the community could create it, but unfortunately I don't have this knowledge and I don't know where to look for documentation. It might be worth asking.
Would have been better for them to listen to the yells about when it will come out then release such poor stuff too early.
Well, the problem with this crash during installation (#173291) is actually exactly one bug, I wouldn't call a product poor stuff because of one bug. But of course you're right, a bug that almost prevents installation is definitely a valid reason for being disappointed. This bug you were experiencing during installation (#173291) is a classical example of "bad luck": - It was detected very, very late - The original, initial report referred to a less critical situation that could be worked around, so it was decided to fix the problem after the release via YOU instead of delaying the release even more for everyone - The bug was therefore underestimated About "would have been better": It's difficult to say that. While there are many duplicate reports of this problem in Bugzilla, there are probably even more people out there who didn't experience crashes during the installation. And, there are many people giving feedback that the 10.1 release is disappointing, but there were also countless complaints before the release about the delays being unacceptable. What I'm trying to explain is that decisions about priorities had to be made, that some decisions of this kind are difficult enough to be always wrong and that legitimate feedback cannot undo problems that are technically not fixable after the release has beed made. There is a reference to a driver update in the original report, but I don't know if it's "officially" considered. I think the report is kept open because of the upcoming YOU. Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org