> 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. 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). 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" ? -- This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
