Upgrade SCO 5.0.2 Host to Enterprise with license Post: 302940601

6 More Discussions You Might Find Interesting

1. IP Networking

QNX host cannot ping SCO host, vice versa

The problem I am facing now is that the QNX host could not ping the SCO host and vice versa. They are in the same domain, ie, 172.20.3.xx. As I am very new to Unix, I guess I must have missed out some important steps. Pls help... Thanx alot

2. UNIX for Dummies Questions & Answers

Upgrade SCO openserver

Hi guys i have a unix server SCO 5.0.4 and i'm trying to install and intel pro 100 and for some reason it wont see it , i tried to install a 3 com card and same thing. I know that if i had 5.0.6 it will see any of those cards.my questions is ( if i upgrade to 5.0.6 i have a computone card...

3. SCO

SCO OpenServer 6.0.0 License for Testing

SCO OpenServer 6.0.0 License is required for testing purpose. If anyone have, please help me at the earliest.

4. Shell Programming and Scripting

to check the Linux upgrade in the host

Hi, how to check when was the linux upgrade has been done to this host. below command show the RHEL version. cat /etc/redhat-release Red Hat Enterprise Linux AS release 3 (Taroon Update 6) i want to know when it was upgraded.. is there any command available for that ? or anywhere we...

5. Shell Programming and Scripting

Updating the license tag in XML file with new license

Hi All, I have a XML file : System.xml in which I want to update the license tag with the new data from file licence.xml. The content of files is in following format: System.xml: <?xml version="1.0"?> <!DOCTYPE Configuration SYSTEM "SystemVariables.dtd"> <usageConfiguration...

6. SCO

Looking to Buy SCO Merge 5.3 License

Xinuos (SCO) discontinued Merge 5.3 on 1.31.16. I'm looking to buy from someone their Merge license. Please contact 1234567@optonline.net

LEARN ABOUT LINUX

relup

relup(5)							       Files								  relup(5)

NAME

       relup - Release upgrade file

DESCRIPTION

       The release upgrade file describes how a release is upgraded in a running system.

       This file is automatically generated by systools:make_relup/3,4 , using a release resource file ( .rel ), application resource files ( .app
       ) and application upgrade files ( .appup ) as input.

FILE SYNTAX

       In a target system, the release upgrade file should be located in the OTP_ROOT/erts-EVsn/Vsn directory.

       The relup file contains one single Erlang term, which defines the instructions used to upgrade the release. The file has the following syn-
       tax:

       {Vsn,
	 [{UpFromVsn, Descr, Instructions}, ...],
	 [{DownToVsn, Descr, Instructions}, ...]}.

	 * Vsn = string() is the current version of the release.

	 * UpFromVsn = string() is an earlier version of the release to upgrade from.

	 * Descr  =  term()  is  a user defined parameter passed from the systools:make_relup/3,4 function. It will be used in the return value of
	   release_handler:install_release/1,2 .

	 * Instructions is a list of low-level release upgrade instructions, see appup(5) .

	   It consists of the release upgrade instructions from the respective application upgrade files (high-level instructions  are	translated
	   to low-level instructions), in the same order as in the start script.

	 * DownToVsn = string() is an earlier version of the release to downgrade to.

       When  upgrading	from  UpFromVsn  with  release_handler:install_release/1,2  ,  there  does  not have to be an exact match of versions, but
       UpFromVsn can be a sub-string of the current release version.

SEE ALSO

       app(5), appup(5), rel(5), release_handler(3erl), systools(3erl)

Ericsson AB							   sasl 2.1.9.3 							  relup(5)