Hi Nigel, for Sun customers the fix is available nearly immediately, based on their call to support. Yes, the fix wasn't released to sunsolve yet.
And your declaration "the fix has been known for months/years & is relatively trivial." is truth only partially. If you look at the source code you will discover that the original fix wasn't correct (and contains also unrelevant changes). Fixing mistake by new mistake is not good idea in products I believe. And as you wrote in the last paragraph yourself, Nevada fixes can introduce really bad regressions so we are evaluating every fix carefully if it should be backported or not and when it should be backported. Best regards, Milan Nigel Smith pÃÅ¡e v Ät 22. 05. 2008 v 11:08 -0700: > It was disappointing that the fix for this bug did not make it into Update 4. > Even more disappointing if it's not fixed in Update 5! > > It seems that Sun's policy is to wait for the customers with a support > contract to complain before they will back port a fix, even if > the fix has been know for months/years & is relatively trivial. > > This seems crazy to me, but hey, it's Sun product and they can choose > to do as they like with it. > > I would guess that a lot of potential customers are just using Nevada / > OpenSolaris and cannot be bothered to go through the support process. > > So if you do not want to pay for a support contract, then you may well be > better to switch to a Nevada build or OpenSolaris (aka Indiana). > > Many of the iscsi target bugs have been fixed recently. > But with Nevada there is always the chance that a bad bug may be introduced > which may cause you to have a really bad day :-(. > Regards > Nigel Smith >
_______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
