* Anon Y Mous ([email protected]) wrote: > > Please don't spread FUD. OpenSolaris ships with the exact same > > userland as Solaris Express (with some exceptions such as > > technologies which are being replaced, live upgrade for one). > > The only difference is the inclusion of GNU tools prepended > > to the default user's path. > > I'm not spreading F.U.D. His question- Why won't Oracle install on > OpenSolaris Indiana build 111, is a legitimate question and my answer- > start troubleshooting by first installing it successfully on SXCE and > / or Solaris 10 is a legitimate answer to his question. If it installs > on SXCE for the same build and won't install on Indiana, then there > might be a difference in his $PATH variable that confuses the Oracle > installer or there might be some library that his Oracle install needs > that is bundled with SXCE but isn't included with his Indiana build.
The problem with suggesting SXCE as a troubleshooting step is that you didn't state that it was meant purely as a troubleshooting step in your response. So, the unknowing person (ie someone new to OpenSolaris) would take what you suggested as "Oracle doesn't work on OpenSolaris so I need to use SXCE because that's what someone told me on a forum when I asked". Then when SXCE is no longer available they're now upset because they've invested time into SXCE which ends up being wasted effort. SXCE is a dead-end. It's been a de-facto dead end for some time and became officially so with the official announcement that it's going to be discontinued in the near term. Investing any effort in it (in particular by new users) is just not worth the time. Move to OpenSolaris and file bugs. It'll make the transition once SXCE really isn't available any more that much easier for everyone involved. > I'm an immigrant to OpenSolaris from Debian, *BSD, and Red Hat Linux, > so I'm no stranger to the GNU toolchain and I've been using Indiana > religiously as a desktop OS since 2008.05 first came out and you have > no idea how many times I've been bitten in the May 2008 to February > 2009 time period by missing files / missing libraries / missing man > pages not being there that I had to copy over from a friend's SXCE > installation DVD. Most of these missing pieces are actually now > included in the latest Indiana builds (good job btw), but the > experience of having to go for a one year long treasure hunt / easter > egg hunt to go find the missing pieces of my OpenSolaris OS has given > me a good troubleshooting methodology for these type of situations > which I will outline below: > > The best way to determine if it's a missing file / missing library or > a $PATH error that's causing the problem (and not something else) > would be to try installing it on SXCE build 111 (i.e. the SXCE > equivalent of his Indiana). If it doesn't install on the SXCE version > that is the same build as his Indiana build, then it's probably NOT a > missing library that's causing the problem and the problem is probably > some peculiarity that is specific to build 111 (or, perhaps, something > unique to his particular OpenSolaris build 111 installation if he > changed or customized some feature or setting that broke Oracle). Except as I said, offering SXCE for anything at this point sets the wrong expectation. OpenSolaris is the official distribution that Sun is going to continue to provide to the community (I'm not talking about Solaris Next which Sun will provide and will be *based*, based on OpenSolaris but not just be OpenSolaris as it ships today). The real way to troubleshoot this stuff is to do so on the platform that you're going to roll it out on. Having to install an entire OS just to compare is just way too much trouble imo (coming from a prior career in tech support) and doesn't buy you much. There's no reason that people familiar with Oracle couldn't tell you what is missing on OpenSolaris if the proper details of a failure are given imo. I don't know Oracle so can't offer anything to the OP's original question. > If it fails to install on both SXCE 111 and Indiana 111, then do a > regression test and try Solaris 10 and earlier builds of SXCE and then > look at the changes made between the older build that worked and the > newer build that didn't work and figure out which one of the changes > is causing the problem. > > Since when does looking for regressions in new software spread "Fear > Uncertainty Doubt" ? It's spread "Fear, Uncertainty and Doubt" when you say things like: > I suspect Oracle products run better on Solaris Express than they do > on OpenSolaris Indiana because Solaris Express has a user-land that is > more traditional, like Solaris 10. The advantage of using SXCE over > Solaris 10 is that SXCE has most of the same new cutting features that > OpenSolaris Indiana has (Crossbow, etc.) while maintaining better > backwards compatibility with Solaris 10 than OpenSolaris Indiana does: You've stated that OpenSolaris isn't as good as Solaris Express (in not so many words). You've further set an expectation that the user should use SXCE since it has the 'same new cutting features that OpenSolaris has'. This sets the wrong expectation as I've outlined above. At least, that's certainly how I interpreted what you wrote. I think what people are missing in this whole SXCE going away thing is that OpenSolaris is the development distribution going forward at Sun. We can't afford to run two (OpenSolaris and SXCE). We'll have a Solaris Next release coming out at some point which will be the successor to Solaris 10 and it will be based on OpenSolaris and by extension SXCE (again, see my comment above about how OpenSolaris is derived from the same sources as SXCE). So, we'll have OpenSolaris for the 'cutting-edge' crew or those who want shiny new things and are willing to test out new ideas/concepts and then Solaris for the 'I want to set this up and leave it alone for a few years' type of crowd. Just like other OpenSource vendor offerings from say RedHat or Ubuntu etc that have development releases and enterprise releases. That's probably more than .02 at this point. -- Glenn _______________________________________________ opensolaris-discuss mailing list [email protected]
