For more information about this certification and to see the latest list
of UNIX registered products, please go to the Open Brand Register at
[link]http://www.opengroup.org/openbrand/register|| ||Registration[/link]
For more information on UNIX 03, see
[link]http://www.UNIX.org/unix03.html|| ||UNIX 03[/link]
To follow the UNIX 40th anniversary world tour, see
[link]http://www.flickr.com/groups/unix/|| ||UNIX Plate World Tour[/link]
Post a Comment
Linux and *BSD aren't UNIX 2003 compliant; it is about conforming to a set of specifications. I wish more vendors were UNIX 2003 compliant, even if it doesn't have the certification the compliance would be great - then we wouldn't have situations of GNOME compiling on Linux but needing huge numbers of patches to get it to compile on *BSD or OpenSolaris.
If *BSD and Linux were at least 100% UNIX 2003 compliant and GNOME was developed for compliancy with the specification then there wouldn't be the ifdef's and patches left, right and centre to the point that it is a mess to get any desktop compiling cleanly.
The one thing I'd love to know is whether the UNIX 2003 test suite is available and free of charge? because if it at least conforms to the test suite then it would go along way to improving the cross platform nature of GNOME and KDE.
I can't see that happening personally.
Partly down to cost and partly down to inconvenience because each version (including CPU architecture) would have to be separately certified and paid for.
Plus it's not like Linux's lack of UNIX certification has harmed it's server market share.
In fact, if anything, Linux has steadily gained market share from businesses that were perviously running UNIX systems.
I do not think that being certified or not as compatible to the UNIX 03 (or any other standard), can dissuade or attract a customer. Yet, I do believe that the standardization procedure is important. Small deviations from the standards cause no harm, so you have to envisage the hole thing in a more diffuse context. There are lots of people involved in the Austin group, and just by looking in the mailing lists archives you can immediately see that market needs are not the main driver. I would say that it is mostly a technical working group. Compiler standards are very important to programmers. OS standards bare the same importance for ISVs and end users. I can only view portability across different OSes as a good thing.
And that is a valid point for the desktop and hobbyist crowd. But there is no way that a CTO will install non-certified HW in the server room. There are too many other factors in that sort of decision. WHO built it who can fix it? Is it the same as the server in the branch office? Is there a HW warrantee so that the vendor will bring me one that is exactly the same as the other one? It is not like I am concerned about what 'desktop' the SAN is running. It is good to have something - anything to say about Apple, But this is a BSD Unix. And it does work.
if I was going to get a new certification would I go for a certified track or some 'johnny faith healer' certification? If you were hiring some one would you pick a candidate that met your criteria / could do your job on your day off OR someone who was kind of as good as. And then that makes it easy for the Board of Directors (bean counters) to pick a server OS that is Certified, so YES UNIX 03 is 100% Marketing. But I do not think that it is marketing for the kind of person who can #make /make clean /make dep / make install AND if it is broken then patch it.
BTW I have compiled KDE in 10.2 and every version of the OS since. I suspect that I could be done real swift like on an XServe, what would the benefit be?
UNIX certification is a software standard, not a hardware one.
Plus, given that BSD and Linux massively outnumber OS X on servers, I think that your comment about CTOs not willing to run non-certified technology is inaccurate.
CTOs are more concerned about knowing there's support for the product than certifications they don't understand.




