--- On Wed, 8/12/09, Anon Y Mous <[email protected]> wrote:

> From: Anon Y Mous <[email protected]>
> Subject: Re: [osol-discuss] Oracle 10g on OpenSolaris (Solaris 5.11)
> To: [email protected]
> Date: Wednesday, August 12, 2009, 8:20 PM
> > Please don't spread FUD.> 
> 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. 
> 
>
> 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. 

Not so much that. The issue you discussed was basically part of the design
originality of Project Indiana - a CORE distro versus the "meat and potatoes" 
bigger distro known as SXCE.

So it is moreso a "user expectation" error in not knowing (i.e. forgetting) the 
intent of the project distros at that time as OSOL 2008.05-2009.06 were mini 
distros of SXCE so of course parts were missing to squeeze the distro to fit on 
a CD.

Now the emancipation project and other toolsets were getting placed in IPS
to make them available to people or admins were told to pull files from SXCE. 
Really, it was kinda that simple between the two distros and it
still is that way today for some things. Some things were closed source or 
nonredistributable on SXCE, but these were all known factors being discussed 
with community members willing to listen.

So any app not running on OSOL Live CDs were to be reported so that 
libs/commands could be brought over to fill the void - yet still trying to keep 
the space on CD/DVD small enough.

Sun mentioned they wanted to stick all of the bulk of thngs into IPS (or 
something else in the future) and only keep key pieces on the CD/DVD.
You don't want to have to keep up with app development changes on a core
OS CD (see Sun Studio, StarOffice, NetBeans). A larger distro can be made that 
has all that (which would be nice) but I think Sun wanted a mini install 
CD/DVD, so admins could get servers up and running, and only install what they 
need for a Oracle install or dedicated Subversion server. Or, a developer could 
setup up a dev box without installing hundreds of unnecessary drivers or cruft 
on the HD.

Most ISPs will take something like OSOL 2009.06 and test it with their core ISP 
services to make sure it will handle them. If a major app, then you'd probably 
want certification or assurance from the vendor that it will work (or you just 
get your admins/engineers to validate it). So, it
is really up to the customer to do a bit of "due diligence" before
risking themselves and know what the purpose of the OS distro intends to 
provide.

My penny..times two..
~ Ken Mays


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to