Re: SuSe and Oracle11- why SLES9 is notsupported while RHEL4 (and OL4) are supported?

"Arun Singh" <[email protected]>
Newsgroups gmane.linux.suse.oracle.general
Message-ID <[email protected]>
>>> On 8/11/2007 at 7:50 AM, Tom Sightler <[email protected]> wrote:
> On Fri, 2007-08-10 at 15:33 -0700, Alexei_Roudnev wrote:
>> Sysadmins are not dumb - seen all this, they select RHEL4 or UL4 - these 2 
>> systems are well compatible with all Oracle versions (I can even run 
>> Oracle8i on RHEL4, with some hacks) and are rock-solid.
> 
> Your right, sysadmins are not dumb, unfortunately, software companies
> are dumb.  They seem to be pushing shorter and shorter product
> lifecycles and have forgone "stable" products for simply "current"
> products.  Last time I looked Novell's official lifecycle for SLES9 was
> five years.  Oracle's support for their database products is not much
> better, although at least you can pay extra.
...
> My guess is that this is what lead to RHEL4 being certified while SLES9
> is not.  Redhat has a 7 year lifecycle on it's products, but Novell only
> officially guarantees 5 years (as far as I know anyway).  That means
> that SLES9 is scheduled to be desupported on August 2009 only two years
> from now, and it already feels abandoned.
> 
> RHEL4 on the other hand, will be supported until Feb 2012, nearly 4 1/2
> years from now, even though it's initial release only trailed the SLES9
> release by 6 months.  Those two years might not seem like much, but they

Just for the benefits of all list members. Now, Novell/SUSE support cycle (http://support.novell.com/lifecycle/) is 7 years (It was 5).

For exacts dates, etc. Please refer: http://support.novell.com/lifecycle/lcSearchResults.jsp?st=SUSE&x=0&y=0&sl=-1&sg=-1&pid=1000

-Arun


-- 
To unsubscribe, email: [email protected]
For additional commands, email: [email protected]
Please see http://www.suse.com/oracle/ before posting
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.