Hi This is going slightly off topic. However, while I agree with "go with what works", I disagree with the implication that coolstack is always going to be behind blastwave. at the moment Coolstack 1.3 (RC1) contains php 5.2.6 which my university requires for any externally accessible web server using php, blastwave is still using 5.2.4 http://www.blastwave.org/packages.php
One of the advantages of coolstack being outside Solaris is that it decouples updates of the AMP stack from the OS. I do use blastwave for thing that are not in coolstack and very good it is too. It would be nice if they could both be reworked so that the configuration files and data files where under /etc/ and /var so that they worked better with sparse zones. Cheers Anthony Worrall > -----Original Message----- > > > When it comes to taking care of the customer I suggest that you go > with what works and you know that you can get it anywhere and there is > a community behind it at all times. > > The stable tree at blastwave.org is very well tested and you can not > go too far wrong there. The basic coolstack stuff from Sun is fine > also but don't expect updates too often. Of course, you can always > build it all yourself but that would be painful. > > With anything from Solaris 8 upwards ( containers also ) I go with the > stable tree from Blastwave.org and sometimes the unstable tree : > > see http://pluto.blastwave.org/ > > and > > http://www.sun.com/customers/software/blastwave.xml > > I'm pretty serious about using Solaris and OpenSolaris and I support > the open source needs of the Solaris customer. > > Dennis Clarke > _______________________________________________ > > > webstack-discuss mailing list > webstack-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/webstack-discuss
