Sponsored Content
Operating Systems SCO Migrating Digi PortServer TS 16 Post 302501469 by Eclectic Wave on Thursday 3rd of March 2011 03:32:46 PM
Old 03-03-2011
Be sure to use the UNIXWARE 7.14 Digi Drivers

Remember that SCO 6 is a Unixware kerneal with a SCO 5 overlay on it. For did drivers you must use the Unixware drivers and not the sco 5.07 drivers.
 

8 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

mini digi-cam

hey guys! I am on a fedora core2 i686 with gui and I have a miniture cool-cam which is digital.. it connects through regular usb.. the system recognizes it and the when I go into the desktop peripheral and go to camera it gives name and tells test was successful.. it also says that the camera has... (0 Replies)
Discussion started by: moxxx68
0 Replies

2. UNIX for Dummies Questions & Answers

Migrating from HP to Solaris

My company is considering migrating from HP unix to Solaris just to get two more years of support for a particular software product. My question is just how much of an effort is it to do this migration? Are you aware of any migration tools to assist us in this migration? Thanks (1 Reply)
Discussion started by: jkuchar747
1 Replies

3. HP-UX

When migrating from HP-UX 11.0 to HP-UX 11.i

Hi to all, I am migrating HP-UX 11.0 to HP-UX 11.i, The following list are the components which i used in HP-UX 11.0, Whether I can use this same components in HP-UX 11.i or I should upgrade any of software version with respect to HP-UX 11.i. Oracle 8.1.7 Tuxedo 8.0 BEA Message queue... (0 Replies)
Discussion started by: sweta
0 Replies

4. HP-UX

Migrating from HP-UX 11 to HP-UX 11.i?

Hi, I want to Migrate my machine from HP-UX 11 to HP-UX 11.i, regarding this i would like to know the difference and the advances b/w these two. If anyone have cookbook HP-UX 11 to HP-UX 11.i, then provide the link to me. Thanks in Advance. Sarwan (3 Replies)
Discussion started by: sarwan
3 Replies

5. AIX

Printer issue on a Digi

Ok, Im a new network admin to the AIX environment. Im in the AIX console as we speak and I don't understand this issue with the print server. It's not a standard print server that I'm used to seeing and was wondering if any of you have any experiences with a Dev_Wait issue on a Digital to Serial... (0 Replies)
Discussion started by: Itsaboutme
0 Replies

6. SCO

Digi 8e memory window not available in mpi

In setting up an 8e on 5.0.5 I couldn't find a memory window that worked using mpi (3 versions). The memory search program (DOS based) indicated E800 was available but mpi only listed E000. I resolved my immediate problem by changing the window value in /etc/conf/pack.d/pcxx/space.c prior to... (2 Replies)
Discussion started by: edfair
2 Replies

7. AIX

Setup 1 Digi PortServer II with 5 x AIX boxes

Hi everyone, My latest challenge sees me assisting with the setup of one of our classroom labs. We are trying to configure the lab so that the (5) IBM 9115-505 servers (all running AIX7.1) have their serial 0 ports connected to a Digi PortServer II, which is on the classroom LAN, along with the... (4 Replies)
Discussion started by: richardsantink
4 Replies

8. UNIX for Beginners Questions & Answers

Migrating to UNIX

I am looking for a stable, reliable system to replace my current Windows systems in the home. These are simple systems that I purchased from the local Big Box store. I have heard many good things about Unix and it's various children and it sounds like a good option to me. I have worked... (2 Replies)
Discussion started by: donschurter
2 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 10:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy