Sponsored Content
Operating Systems Linux Red Hat RHEL 7 distribution compatibility Post 303028910 by Peasant on Friday 18th of January 2019 12:51:27 AM
Old 01-18-2019
To be sure install a Centos 7 (which is identical to RHEL) and give it shot.
Do not upgrade your operating system to next major release, without running tests of your software and tools.

Hope that helps
Regards
Peasant.
 

10 More Discussions You Might Find Interesting

1. Red Hat

Difference between RHEL 3 AND RHEL 4

Anybody, let me know major differences between RHEL 3 & 4 . (2 Replies)
Discussion started by: sakthi_13
2 Replies

2. Solaris

Disks compatibility

Hi all, I am trying to isntall veritas replicator on 2 DA 3000 storage , But with little luck . I am running a solaris 10 and vsf 4.1, Veritas Volume Replicator Option 4.1 My question is that : when i got the array i had 2 disks missing , So we had to replace them , but I found out that... (0 Replies)
Discussion started by: ppass
0 Replies

3. Solaris

Solaris 10 - HW compatibility

Sorry, if this isn't the right forum for this question. I would like to compile an executable with gcc/g++ under Solaris 10 on the following OLDER SPARC-machine and then run this executable on the NEW SPARC-machine (see description down in this post). I'm wondering if it would be possible or if... (4 Replies)
Discussion started by: sunfire
4 Replies

4. Red Hat

cannot ssh (use NFS) on RHEL box, but can mount external & ssh out of RHEL box

Ok, Im trying to get NFS working on my RHEL 5 box, apparently i can use the box as a client, but not as a server. If it helps i cant ssh into the box (server), but as a client ssh works fine. Ive configured server: /etc/hosts.allow: all : all all :all@all setup my /etc/exports file... (4 Replies)
Discussion started by: drs.grid
4 Replies

5. Red Hat

Does RHEL 5 provide a command to collect RHEL system log in single compress file?

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

6. Red Hat

Error throwing while installing vsftpd package in rhel 6. using rhel 6 dvd.

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

7. Red Hat

RHEL 6, Spacewalk 2.3 unable to download RHEL 5 repo data

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

8. UNIX for Dummies Questions & Answers

Windows->RHEL->RHEL X11 Forwarding?

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

9. Red Hat

Is it possible to install RHEL 7 on top of RHEL 6?

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

10. Shell Programming and Scripting

Cut command on RHEL 6.8 compatibility issues

We have a lot of scripts using cut as : cut -c 0-8 --works for cut (GNU coreutils) 5.97, but does not work for cut (GNU coreutils) 8.4. Gives error - cut: fields and positions are numbered from 1 Try `cut --help' for more information. The position needs to start with 1 for later... (6 Replies)
Discussion started by: Vikram Jain
6 Replies
versw(8)						      System Manager's Manual							  versw(8)

NAME
versw - Manages the transition from the active version of the operating system to a new version SYNOPSIS
/usr/sbin/versw [option...] OPTIONS
Checks whether a version switch is pending. The versw utility returns a 1 if a version switch is pending (the active and new versions dif- fer), a 0 if a version switch is not pending (the active and new versions are the same). Sets the versw_transition attribute in the generic kernel subsystem of the member-specific /etc/sysconfigtab file to 0 (zero). Prints the old (previously active), active, and new version IDs, the version transition state, and the version switch state. If a version switch is in progress, the version switch state is the member ID of the cluster member running the versw utility plus 100. Otherwise, the version switch state is 0. Unconditionally sets the active version ID to the new version ID in the generic kernel subsystem of the member-specific /etc/sysconfigtab file and in the member's running kernel. Specifies a directory path to an alternative /etc/sysconfigtab file. By default, the member-specific /etc/sysconfigtab file is used. Sets the new version ID in the generic kernel subsystem of the member-specific /etc/sysconfigtab file and in the running kernel. The installation of the Tru64 UNIX operating system and the cluster software automatically sets these values. Sets the versw_tran- sition attribute in the generic kernel subsystem of the member-specific /etc/sysconfigtab file to 1. When run with the -switch option, the versw utility automatically sets this attribute. Attempts to set the active version ID to the new version ID on a standalone system or on all currently active cluster members. When you install Tru64 UNIX on a standalone system, the installation procedure concludes by using a versw -switch command to set the active version to the new version. When you complete a cluster rolling upgrade, by issuing a clu_upgrade -switch, clu_upgrade automatically issues the versw -switch command to set the active and new versions consistently on all cluster members. Checks the return value from the versw() function. See versw(3) for a description of this function. DESCRIPTION
The versw utility manages the transition from the active version of the operating system to a new version. You must be root to use this utility. The active and new operating system versions are recorded in the act_vers and new_vers attributes, respectively, in the generic kernel sub- system of the /etc/sysconfigtab file (or each member's /etc/sysconfigtab file in a cluster). When you install a new version of the Tru64 UNIX operating system or cluster software, the installation procedure automatically issues the versw -setnew command to establish the new version ID in the /etc/sysconfigtab file and in the running kernel. At installation time, the new version ID must always be higher than the active version ID. When installation completes on a standalone system, the active and new versions will be identical. When you install Tru64 UNIX on a stand- alone system, the installation procedure concludes by using a versw -switch command to set the active version to the new version. During a rolling upgrade of a cluster, the active and new versions will not be the same on each cluster member until the rolling upgrade completes. When you conclude the rolling upgrade, by issuing the clu_upgrade -switch command, clu_upgrade automatically issues the versw -switch command to set the active and new versions equal on all cluster members. After all cluster members have been rebooted with the new active version, all features of the new operating system and cluster software are enabled across all cluster members. When called by the clu_upgrade -switch command in a cluster, the versw utility performs the following operations: Compares the active and new version IDs in each member's running kernel. If new versions of the operating system and cluster software have been installed, the new version ID will be higher than the active version ID. If the IDs are identical or the new version ID is less than that of the active ver- sion, the utility issues a warning and exits. Checks that each member's /etc/sysconfigtab file is accessible. If not, the utility issues a warning and exits. Checks that all members have booted with the new version. If not, the utility issues a warning and you must either reboot the members or run versw -forcesw to continue. Use the clu_get_info command to determine which systems are running at or below their installed version. Checks for blocking conditions. If any exist, the the versw utility prints an error message and exits. If the new soft- ware has introduced a change or enhancement that is incompatible with the active version, the component sets up a condition that blocks the rolling upgrade. Such incompatibilities usually involve changes to configuration files, on-disk structures, or local or remote interface protocols. Operating system components establish a blocking condition by placing files in the /var/adm/versw directory. These text files provide instructions for manually restoring compatibility between installed and new versions: for instance, by editing a configuration file or running a data conversion script. You must follow the directions in these files to proceed with the upgrade. Moving these files to another directory removes the blocking condition. Determines whether all running members are capable of the switch this member is propos- ing. If not, it displays an error and exits. Sets the versw_transition attribute in the generic kernel subsystem in each member's /etc/sysconfigtab file (and in each member's running kernel) to 1. Requests that the connection manager stop new members from joining the cluster until the completion of the version switch. Sets the active version to the new version in the generic kernel subsystem of each cluster member's /etc/sysconfigtab file. Note that, if a member goes down during this stage, the versw utility exits with an error message. All running members clear their versw_transition attributes and restore their /etc/sysconfigtab copies. Sets the versw_transition attribute in the generic kernel subsubsystem of each member's /etc/sysconfigtab file to 0. Sends a clusterwide clu.versw EVM event to sig- nify that the version switch was successful. EXAMPLE
The following example shows how a script might use the versw -check command to enable new features on a cluster member that has completed a version switch: #!/usr/bin/ksh -p # Script example usage of versw command switch # if versw -check ; then echo "Enable new version features" else echo "Disable new version features" fi The following command shows the output of the versw -dump command on a cluster that has completed a roll: # versw -dump Old version = ( 0 , 0 ) Active version = ( 14000800009a1700 , 3b88 ) New version = ( 14000800009a1700 , 3b88 ) Version transition state = 0 Version switch state = 0 FILES
Specifies the command path. Configurable subsystem definition database file, as specified to the -mount option of the versw utility. By default, the /etc/sysconfigtab file is used. In a cluster, /etc/sysconfigtab is a context-dependent symbolic link (CDSL) that references the sysconfigtab file for a member. Rolling upgrade blocking conditions directory. SEE ALSO
Functions: versw(3), clu_is_member(3), clu_get_info(3) versw(8)
All times are GMT -4. The time now is 06:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy