Bug 101450 - Missing products in RHEL AS / WS
Summary: Missing products in RHEL AS / WS
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: redhat-release
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: dff
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-01 07:51 UTC by Winfrid Tschiedel
Modified: 2007-11-30 22:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-10-11 15:25:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Winfrid Tschiedel 2003-08-01 07:51:48 UTC
Description of problem:

I have compared the contents of the first CD of RHEL AS with RHEL WS
for IA64 and X86_64, and I found that you miss some components, if 
you install either versions.

In case of usage in our company, RHEL WS would be a good solution for
most of our compute nodes, but we need at least rsh-server to installed
on all nodes, because we run parallel applications using mpi ( lam-mpi, mpich ).

In case of using RHEL AS, we would miss rpms like, lam, blas, lapack, ...


Version-Release number of selected component (if applicable):
RHEL 3.0 Beta 1

How reproducible:
Compare available rpms for RHEL AS withe RHEL WS

Steps to Reproduce:
1.
2.
3.
    
Actual results:
-

Expected results:
Provide at least rsh-server for RHEL WS
All products from RHEL WS should be part of RHEL AS

Additional info:

Comment 1 Jeremy Katz 2003-08-20 22:07:59 UTC
This is reflected in our current internal trees

Comment 2 Jay Turner 2003-08-21 02:26:26 UTC
All of the WS packages are now part of AS, but rsh-server still isn't a part of
WS, so reopening this.  Need to decide if we are making that change as well.

Comment 3 Jeremy Katz 2003-09-16 23:42:45 UTC
rsh-server now in a WS near you

Comment 4 Bill Nottingham 2004-10-11 15:25:14 UTC
Closing MODIFIED bugs as fixed. Please reopen if the problem perists.


Note You need to log in before you can comment on or make changes to this bug.