Sponsored Content
Operating Systems SCO SCO 5.0.6 application compatibility w/ Linux? Post 302191328 by stay0ut on Friday 2nd of May 2008 07:48:52 AM
Old 05-02-2008
Quote:
Originally Posted by fabtagon
But is maintainance of one old SCO system really that work-intensive? What about e.g. putting it into a VMware?
VMware is what it looks like. . . I just don't have a lot of experience with it. Does VMware allow for direct access to serial ports? and will it run despite the hardware it's on? in other words, does vmware supply a generic set of hardware in the VM that connects to the actual hardware?

Thanks For the Input!
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Linux & Unix Compatibility

I am looking for a dual XEON or any dual CPU motherboard that can support Linux and Solaris at the same time. Does anyone have any idea? I am now looking at the TYAN S2507T / TYAN S2505T / TYAN S2720, you guys have any clue?:confused: (6 Replies)
Discussion started by: doyho
6 Replies

2. Linux

Linux-laptop compatibility debate

Hey guys, i use my mac laptop and i love it, but i have decided its time to break the mold and use linux, and since linux on macs suck, i need to know what kind of pc to build... I want to know what kind of motherboard, wireless cards, hard drives, laptops, video cards, and etc. people have had... (3 Replies)
Discussion started by: mesaynaysayer
3 Replies

3. Hardware

Linux Hardware Compatibility Guide (2007 HOWTO)

Before posting questions about Linux hardware, it is a good idea to check the Linux Hardware HOWTO guide (Last Update: 2007-05-22) However, this HOWTO has not been maintained since 2007 and it out-of-date. (0 Replies)
Discussion started by: Neo
0 Replies

4. SCO

SCO unix binary compatibility problem

Hi I am looking for sco xenix binary compatibility utility "cvtomf",(convert omf object to COFF object) Would you please help me ? tnx (3 Replies)
Discussion started by: javad1_maroofi
3 Replies

5. SCO

sco unix backward compatibility on "max open file per process"

Hi How to increase maximum number of open file in "sco xenix binary" running in "sco unix openserver 5.0.7" ? I have changed "NOFILES" kernel parameter to 512, but xenix binray can't open more than 60. tnx (4 Replies)
Discussion started by: javad1_maroofi
4 Replies

6. SCO

SCO Unix 5.0.6 SATA in compatibility mode

I am very new to SCO Unix so I apologize if this is a easy or dumb question. I have a 160GB SATA hard drive and SATA CD-ROM drive connected to one of my systems. I have both the drives running in compatibility mode. I also have the hard drive set as a primary master and the CD-ROM drive set as... (10 Replies)
Discussion started by: NPIGuy
10 Replies

7. BSD

OpenBSD fdisk - Linux fdisk compatibility ?

Hello, MBR partition table made by linux fdisk looks certainly not correct when printed by openbsd fdisk: Partition table created on linux (centos 6.3): # fdisk -l /dev/sdc Disk /dev/sdc: 10.7 GB, 10737418240 bytes 255 heads, 63 sectors/track, 1305 cylinders Units = cylinders of 16065 *... (2 Replies)
Discussion started by: vilius
2 Replies

8. Shell Programming and Scripting

Linux Compatibility

Hi all. I'm in the process of migrating existing script on UNIX server to the LINUX platform. One of the script that have issues is this one: cd /home/edwh_test/S13018/EDWH-DMT03/stgdata/RPT/ # GIANT # rm -f INPUT_GIANT.csv filename=INPUT_GIANT_*csv GIANT_MONYYYY=$(echo $filename | awk... (9 Replies)
Discussion started by: aimy
9 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 11:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy