Hi, the local yum tool does not implement any limitations. There was no reason for that as RHN does this on the channel side and we'd expect people who have their own yum-based setups to be careful.
The differentiation is on a repository level, not per package and the
repositories on the CD correlate with that. So it should be easy to map
that to a yum setup... The easiest way to to see what repositories are
included in your subscription is to run
python /usr/lib/python2.4/site-packages/instnum.py <IN>
And please don't misunderstand: you are allowed whatever software you
like. It's all Free Software as long as it is not on the Supplementary
CD. The difference is what packages you receive maintenance (Security
and Bugfixes, Updates) and Support for (from Red Hat)!
The mapping basically is:
RHEL (Server) HPC: /Server
RHEL (Default Server, replacing ES):
/Server, /VT
RHEL Advanced Platform (replacing AS):
/Server, /VT, /Cluster, /ClusterSotrage
RHEL Desktop (replacing Red Hat Desktop):
/Client
RHEL Desktop + Workstation (Replacing WS):
/Client, /Workstation
RHEL Desktop + MultiOS: /Client, /VT
RHEL Desktop + Workstation + MultiOS:
/Client, /Workstation, /VT
If you have an AS Subscription you currently get RHEL (so /Server, /VT)
but starting in May you can get AP by calling Red Hat Customer Service.
Regards,
Daniel
On Mon, 2007-04-09 at 11:44 +0200, Jan-Frode Myklebust wrote:
> On 2007-04-08, Daniel Riek <[EMAIL PROTECTED]> wrote:
> >
> > A result of this is that customers need a simple way to extract the
> > components/products to which they have subscribed from the media kit.
> >
> > The Installation Number does this for them. Simply enter the number and
> > everything that you are being offered for installation, you can be sure
> > to get support and bugfixes for. Simple. In the future the Installation
> > Number could be encoded to extract other optional products from the
> > media kit (think
> > JBoss, Directory Server, or even partner products).=20
>
> We've dumped the RHEL5 cd's into mrepo maintained repositories,
> which is basicly one yum repository for the installation CDs (RPMS.os/),
> and one yum repository for the updates (RPMS.updates/). Will the local
> yum command still be smart enough to deny us features/packages not
> allowed by the installation number ?
>
> Otherwise it would be great to know exactly which packages we're not
> allowed to use, so that we could exclude them in the yum config..
>
>
> -jf
>
> _______________________________________________
> rhelv5-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/rhelv5-list
--
Daniel Riek, Product Manager Red Hat Enterprise Linux, Red Hat Inc.
E-Mail: [EMAIL PROTECTED], http://www.redhat.com/
Key-FP: 3DD7 C376 C3E0 1917 9A63 6343 5A26 2C59 6C07 6F32
signature.asc
Description: This is a digitally signed message part
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
