> > taking a break, so I decided to read some news:-) > > > > RedHat 6 got a new pricing. > > > > > > > http://www.c0t0d0s0.org/archives/7023-New-RedHat-prici > > > ng.html > > Sorry for mistakenly posting under "Help" I meant to > posted it under "discussion" > my bad:-(
Cc'd opensolaris-discuss to get it over there. This is good in one way, and misleading in another. AFAIK, Oracle support is premium only; no standard, let alone patch+SunSolve only. A home user or small business may not be able to afford premium; and some large places may need premium only on their critical systems, and have enough in-house expertise to use something less on everything else. (Yes, that mixed case would need some safeguards against abuse.) Home user or small business (esp. small business where one person does pretty much everything, or everything other than what temporary workers or independent contractors do) needs low three digit per year per system prices, tops. Either of those may one day grow to control a nontrivial IT budget, but they aren't there now, and yet may not want to do without security and reliability patches and troubleshooting information. I've only got two beefs with Oracle, aside from plain old arrogant corporate attitude (the whole corporate culture thing that clearly had something to do with some of the departures; who the heck needs fridge+microwave police? creative people should get _respect_, not be treated like cogs in the machine!): * no basic support plan * delaying public source updates not just until an Express release, but until an FCS release (assuming they stick to what a reasonable person might think they've said, and follow through on that) The latter could arguably be made more palatable by having early source be under a restrictive license (no incorporation into independent distros) _until_ the FCS comes out (at which time it would become CDDL). Understand me: I want to see source, without dropping megabucks, even though I have no interest in creating my own distro (or feeding it to anyone else's). Most particularly, I'd really like to see as much of the source as possible for what I'm actually running, and a straightforward way of keeping my view of the source in sync with what I'm running. This is quite desirable to make best use of DTrace; and for those of us who have been known to get better results (and better understanding than the documentation provides) by doing our own troubleshooting than by filing a support request (or at least, faster resolution if we've done our own homework first). A very old example: the older (say Solaris 2.6 to Solaris 9 or 10) printing system was not the easiest thing to understand; and setting up maximal BSD lpr compatibility was less than clear, in part because the mapping between lp -T content-types and BSD filters wasn't fully spelled out anywhere. The source code made that (and the limitations, like that troff font related options would be ignored) pretty obvious. I've never had any trouble getting that version of the printing system to do whatever I wanted it to; from hooking in ghostscript to drive an inkjet printer up to making man -t, lpr -f, lpr -d, or even lpr -c (found an old cif2ps program for the latter) work. -- This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
