Sponsored Content
Full Discussion: SCO UNIX to Linux migration
Top Forums Shell Programming and Scripting SCO UNIX to Linux migration Post 66494 by vickey on Tuesday 15th of March 2005 01:24:36 AM
Old 03-15-2005
Question SCO UNIX to Linux migration

hi all
i m working in a company ...and i have to migrate a C application running on SCO-UNIX to Red hat linux.
can anybody tell me what is the difference between C commands and shell scripting on SCO-UNIX and LINUX.

best regards

harsh
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

How can i get start both sco unix and turbo linux?

I think and believe that i could start both the two OS from HardDisk until i installed Turbo Linux after the SCO unix . If I do anything ,Ican only start Turbo,but if i run "fdisk /mbr",the SCO unix can normally start,but the Turbo Linux could not start with unless you insert the bootdisket,which... (4 Replies)
Discussion started by: sensir163
4 Replies

2. Shell Programming and Scripting

I/ps pls for migration of oraboot & orabackup files from Tru64 Unix to Linux 3.0

Hi, I have 2 Files - oraboot and orabackup, which are correct Files in Tru64 Environment and I am trying to check whether the Files are running properly in my current Linux 3.0. (basically trying to migrate them from Tru64 to Linux 3.0). The files are neither Shell nor Perl, and just have the... (1 Reply)
Discussion started by: marconi
1 Replies

3. Linux

I/ps pls for migration of oraboot & orabackup files from Tru64 Unix to Linux 3.0

Hi, I have 2 Files - oraboot and orabackup, which are correct Files in Tru64 Environment and I am trying to check whether the Files are running properly in my current Linux 3.0. (basically trying to migrate them from Tru64 to Linux 3.0). The files are neither Shell nor Perl, and just have the... (2 Replies)
Discussion started by: marconi
2 Replies

4. Shell Programming and Scripting

Regarding migration (from Tru64 Unix to Linux 3.0) of Files :- oraboot and orabackup

Hi, I have 2 Files - oraboot and orabackup, which are correct Files in Tru64 Environment and I am trying to check whether the Files are running properly in my current Linux 3.0. (basically trying to migrate them from Tru64 to Linux 3.0). The files are neither Shell nor Perl, and just have the... (1 Reply)
Discussion started by: marconi
1 Replies

5. SuSE

Telnet to SCO UNIX from SUSE Linux Workstation

Hi i am new to Linux, i am trying to connect SCO Unix from SUSE LINUX Workstation but i am unable to define the terminal type. i have also downloaded terminal softwares but function keys (f1, f2....) and some other keys are displaying code instead of working the correct function. is there... (2 Replies)
Discussion started by: aafflatoon
2 Replies

6. Red Hat

tool for migration from HP Tru64 UNIX to Linux Red Hat 5

Hi, We are going to migrate our Dataware House system from HP Tru64 UNIX to Red Hat Linux 5. There are more than 500 shell scripts which are written in ksh. The schedule is very tight. So, I want to learn whether there is a tool that can help us find the incompatible shell scripts in... (2 Replies)
Discussion started by: franksubramania
2 Replies

7. Shell Programming and Scripting

Shell scripts migration from HP-Unix 11 to Red Hat Linux

We are changing our OS from HP-Unix 11 to Linux Red Hat. We have few k- shell, c - shell and sql scripts which are currently running under HP-Unix 11. Will these scripts work on LINUX as it is? or we need to do any code changes?IS there anyone who have done this kind of migration before?Thanks for... (2 Replies)
Discussion started by: Phoenix2
2 Replies

8. Shell Programming and Scripting

AIX UNIX (kshell) to Linux Shell Script Migration.

Hi, Could you please let me know what kind of changes/issues commonly occurs at Scripting /command level during AIX Unix (kshell) to Linux shell script migration. (24 Replies)
Discussion started by: Raghuraman.R
24 Replies

9. Shell Programming and Scripting

UNIX to Linux Migration

We have certain number of scripts that run on AIX server using ksh. Now that we migrate these scripts to Linux servers. We need to know what are the changes that we have to perform in script to make it compatible to run on Linux. Say like in our Unix -AIX "print" command worked. But that did... (6 Replies)
Discussion started by: SIva81
6 Replies

10. Shell Programming and Scripting

Need advice for project UNIX to Linux migration

I am working on UNIX AIX to Linux migration. Does anybody know the good site for doing this? Thanks for contribution (4 Replies)
Discussion started by: digioleg54
4 Replies
COMPAT_IBCS2(8) 					    BSD System Manager's Manual 					   COMPAT_IBCS2(8)

NAME
compat_ibcs2 -- setup procedure for running iBCS2 binaries DESCRIPTION
NetBSD supports running Intel Binary Compatibility Standard 2 (iBCS2) binaries. This only applies to i386 systems for now. Binaries are supported from SCO UNIX and other systems derived from AT&T System V Release 3 UNIX. iBCS2 support is only well tested using SCO binaries. XENIX binaries are also supported although not as well tested. SVR4 binaries are supported by the COMPAT_SVR4 option. iBCS2 supports COFF, ELF, and x.out (XENIX) binary formats. Binaries from SCO OpenServer (version 5.x) are the only ELF binaries that have been tested. Most programs should work, but not ones that use or depend on: kernel internal data structures STREAMS drivers (other than TCP/IP sockets) local X displays (uses a STREAMS pipe) virtual 8086 mode The iBCS2 compatibility feature is active for kernels compiled with the COMPAT_IBCS2 option enabled. If support for iBCS2 ELF executables is desired, the EXEC_ELF32 option should be enabled in addition to COMPAT_IBCS2. Many COFF-format programs and most ELF-format programs are dynamically linked. This means that you will also need the shared libraries that the program depends on. Also, you will need to create a ``shadow root'' directory for iBCS2 binaries on your NetBSD system. This directory is named /emul/ibcs2. Any file operations done by iBCS2 programs run under NetBSD will look in this directory first. So, if an iBCS2 pro- gram opens, for example, /etc/passwd, NetBSD will first try to open /emul/ibcs2/etc/passwd, and if that does not exist open the 'real' /etc/passwd file. It is recommended that you install iBCS2 packages that include configuration files, etc. under /emul/ibcs2, to avoid nam- ing conflicts with possible NetBSD counterparts. Shared libraries should also be installed in the shadow tree. Generally, you will need to look for the shared libraries that iBCS2 binaries depend on only the first few times that you install an iBCS2 program on your NetBSD system. After a while, you will have a sufficient set of iBCS2 shared libraries on your system to be able to run newly imported iBCS2 binaries without any extra work. Setting up shared libraries How to get to know which shared libraries iBCS2 binaries need, and where to get them? Depending on the file type of the executable, there are different possibilities (when following these instructions: you will need to be root on your NetBSD system to do the necessary installation steps). COFF binaries You can simply copy all of the available shared libraries since they are fairly small in size. The COFF shared libraries are typically found in /shlib and can be obtained from the following sources: SCO UNIX version 3.x (aka ODT) SCO UNIX version 5.x (aka OpenServer) SCO UnixWare Many versions of SVR4.2/x86 After copying the shared libraries, you should have at least the following files on your system: /emul/ibcs2/shlib/libc_s /emul/ibcs2/shlib/libnsl_s /emul/ibcs2/shlib/protlib_s ELF binaries You can simply copy all of the available shared libraries from the source system or distribution or use ldd(1) to determine the libraries required by a specific binary. After copying the shared libraries, you should have at least the following files on your system: /emul/ibcs2/usr/lib/libc.so.1 /emul/ibcs2/usr/lib/libcrypt.so /emul/ibcs2/usr/lib/libndbm.so /emul/ibcs2/usr/lib/libsocket.so.1 If you don't have access to a SCO system, you will need to get the extra files you need from a SCO distribution. As of January 1998, SCO sells a copy of SCO OpenServer (iBCS2) and/or SCO UnixWare (SVR4) for personal/non-commercial use for only the cost of shipping (about $20US). The distribution comes on an ISO9660-format CDROM which can be mounted and used to copy the necessary files. Run the following script to copy the basic set of files from a SCO distribution directory mounted somewhere locally: /usr/share/examples/emul/ibcs2/ibcs2-setup [directory] You should now be set up for SCO binaries which only need standard shared libs. BUGS
The information about SCO distributions may become outdated. Attempting to a use a nameserver on the local host does not currently work due to an absurd shortcut taken by the iBCS2 network code (remem- ber that there are no kernel sockets). 16/32/64 bit offsets may not be handled correctly in all cases. BSD
February 8, 1998 BSD
All times are GMT -4. The time now is 04:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy