03-04-2015
You can build the new distribution on a new set of disks (or disk partitions) and still use the same hardware..
Or you can use new hardware (with same chipset, etc) to build new system then move over to original hardware.
You have a number of migration options.
This User Gave Thanks to Neo For This Post:
7 More Discussions You Might Find Interesting
1. Red Hat
Hi,
I heard a command that can collect all RHEL 5 log in a single compress file before I forget.
Does any body know...What the command is ?
Thanks. (4 Replies)
Discussion started by: nnnnnnine
4 Replies
2. Red Hat
Hi,
We have RHEL 5.3 beta as a current OS, but planning to upgrade to RHEL 5.6 GA. After the upgrade do i need to rebuild the server. ?
I'm looking for all the possiblities to avoid redoing of install software and configurations.
Please let me know. :)
Thanks in advance,
Vasu (3 Replies)
Discussion started by: vasukv
3 Replies
3. Red Hat
Hi all,
Im studying rhcsa as of now, so yum installation and dependencies are messing me to not workit out.
i have dual os, win 7 & rhel 6.
i have tried this installation of vsftpd package with rhel 6 dvd in VM rhel 6 in win 7 as well as host rhel 6.still the same issue.
below error... (6 Replies)
Discussion started by: redhatlbug
6 Replies
4. Red Hat
I going to be updating a few of our rhel5.5 servers this weekend to rhel5.10. I'll be making a checklist for pre & post maintenance comparisions.
so far I'll be checking,
services running
filesystems
netstat
ifconfig
uname
oracleasm
multipath
just basic stuff
if it were you what... (5 Replies)
Discussion started by: mkeyes001
5 Replies
5. Red Hat
Hello all, I am having a bit of an issue on my Spacewalk installation. Some amplifying information is that it is Spacewalk 2.3 installed on a RHEL 6 machine and I am attempting to install/update a RHEL 5 channel/repository. I am fairly new to Spacewalk so I am still learning but this is what I... (3 Replies)
Discussion started by: jstone4646
3 Replies
6. UNIX for Dummies Questions & Answers
I know this question might have been asked a lot but couldn't find anything that worked. From a windows machine 'A' I can only SSH into Linux server 'B' from where I can SSH into another Linux server 'C'. I need to be able to run GUI interfaces on server C which run on my Windows machine. I... (3 Replies)
Discussion started by: hr.prasan
3 Replies
7. Red Hat
Hi
We have RHEL 6.7 on an HP physical server and want to install RHEL 7 (not upgrade) on top of it by means of virtualization. Is it possible to install/configure RHEV/KVM virtualization on base RHEL 6.7 OS instance and then install RHEL 7 as a VM guest on it? If yes, could you please guide me... (1 Reply)
Discussion started by: magnus29
1 Replies
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)