Paul,
If you are planning on using up2date to do this include the "--dry-run" feature and see what happens? Up2date also has a few more options that you might need like: --installall=<channel-label>, --show-channels, --upgrade-to-release
Upgrade to the channel specified
>Message: 12
>Date: Tue, 06 Apr 2010 20:19:56 -0400 (EDT)
>From: Paul Robertson <probertson@xxxxxxxxxxx>
>To: redhat-list@xxxxxxxxxx
>Subject: Convert Redhat 4 ES to AS?
>Message-ID:
> <Pine.LNX.4.61.1004062007270.29150@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>We installed a third-party application onto a Redhat 4 ES server
>recently. Due to some unfortunate application issues, we'd like to
>upgrade to the next version of the application, but the vendor claims
>the next version is supported only on Redhat 4 AS.
>Is there a supported process to "convert" an existing Redhat 4 ES server
>to AS? Alternatively, it appears that there are just a few differences:
>>
> http://kb.mit.edu/confluence/pages/viewpage.action?pageId=4259963
>Is it as simple as replacing the three ES RPMS with their AS equivalents
>and then re-entitling the server at RHN with an AS license?
>Cheers,
>Paul
>
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
