[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Thu Mar 24 15:28:19 2005 -->
- <!--x-from-r13: uoof ng pbzpnfg.arg (Xrss Vhoof) -->
- <!--x-message-id: 1111695741.10214.25.camel@angel -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] SMP support for CentOS 4.0 i386 -->
- <li><em>date</em>: Thu Mar 24 15:28:19 2005</li>
- <li><em>from</em>: hbbs at comcast.net (Jeff Hubbs)</li>
- <li><em>in-reply-to</em>: <<a href="msg00437.html">[email protected]</a>></li>
- <li><em>references</em>: <<a href="msg00437.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] SMP support for CentOS 4.0 i386</li>
Jeff
On Thu, 2005-03-24 at 15:11 -0500, Yu, Jerry wrote:
> if so, <= 2-way restriction for 'RHEL ES' is probably just marketing/sales gimmicks to force you to buy pricier AS version for >=3-way servers.
>
> # -----Original Message-----
> # From: ale-bounces at ale.org [<a rel="nofollow" href="mailto:ale-bounces">mailto:ale-bounces</a> at ale.org]
> # Sent: Thursday, March 24, 2005 2:31 PM
> # To: Atlanta Linux Enthusiasts
> # Subject: Re: [ale] SMP support for CentOS 4.0 i386
> #
> #
> # CentOS is compiled from RHEL source. That source is still
> # GPL. I can't
> # see how RH can enforce something like that on the license. It
> # could be
> # possible that Redhat has changed the kernel code in such a
> # way, to only
> # use at most twoCPUs, but if that were the case nothing would
> # prevent you
> # from changing it back. I know the guys over at
> <a rel="nofollow" href="http://www.openfiler.org">http://www.openfiler.org</a>
> use CentOS as there base distribution for the OpenFiler project, you may
> want to ask those guys this question, they would probably know.
>
> Denny
>
> Yu, Jerry wrote:
>
> > anybody know how many CPU can CentOS 4.0 support? Its redhat
> > counterpart "RHEL 4.0 ES" supports only 2. I'd assume it is
> > restriction of RHEL license instead of 'feature lock' in the kernel,
> > right?
> >
> > This email and any attached files herein contain information that is
> > intended only for the use of the individual or entity to whom it is
> > addressed and may contain information that is legally privileged,
> > confidential or otherwise exempt from disclosure under applicable
> > laws. If the reader of this message is not the recipient, any
> > disclosure, dissemination, distribution, copying or other use or
> > retention of this communication or its substance is prohibited.
> >
> >------------------------------------------------------------------------
> >
> >_______________________________________________
> >Ale mailing list
> >Ale at ale.org
> ><a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
> >
>
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00439" href="msg00439.html">[ale] SMP support for CentOS 4.0 i386</a></strong>
<ul><li><em>From:</em> cfowler at outpostsentinel.com (Christopher Fowler)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00437" href="msg00437.html">[ale] SMP support for CentOS 4.0 i386</a></strong>
<ul><li><em>From:</em> Jerry.Yu at Voicecom.com (Yu, Jerry)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00437.html">[ale] SMP support for CentOS 4.0 i386</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00439.html">[ale] SMP support for CentOS 4.0 i386</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00437.html">[ale] SMP support for CentOS 4.0 i386</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00439.html">[ale] SMP support for CentOS 4.0 i386</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00438"><strong>Date</strong></a></li>
<li><a href="threads.html#00438"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>