Sponsored Content
Full Discussion: UnixWare 2.x needed
Operating Systems SCO UnixWare 2.x needed Post 302528882 by dgux on Wednesday 8th of June 2011 06:50:20 AM
Old 06-08-2011
UnixWare 2.x needed

Anyone here using Unixware 2.x? I want to try some binary testing on this system regarding DG/UX binaries.
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

SCO Unixware 2.1

I am using SCO Unixware 2.1 & some PC clients are connected, suddenly one message appearslike : UX:strintercept error: dropping message this message starts coming repeatedly & agtre some time system hangs.I had to reset the system & now the problem is not there.Please suggest, why this is... (0 Replies)
Discussion started by: paprch
0 Replies

2. IP Networking

Change ip on UnixWare 2.1.2

I changed the IP whit Ifconfig and I used ping to test the conetions the conection is rigth on my LAN (NetA) But, I have two networks for example: NetA route to NetB and vicevers On NetB ping to any machine on NetA, it is respons successfully. but I ping to UNIX server no respons. I... (1 Reply)
Discussion started by: lmena
1 Replies

3. UNIX for Advanced & Expert Users

UnixWare printing

I have a Unixware OS and a HP Business Inkjet printer. I am unable to print from Unixware in landscape mode. I have tried filters and have failed every time. Any advice would be greatly appreciated. (6 Replies)
Discussion started by: sb4best
6 Replies

4. SCO

Performance issue from Unixware 2.1 to Unixware 7

Hello, I am having performance problem when , i ported a c code from Unixware 2.1 to Unixware 7.0.0. My program establishes a synchornous connection with the client in a windows OS and then sends and receives messsages using the recv and send calls. What i hyave noticed is that after a... (0 Replies)
Discussion started by: Amith
0 Replies

5. UNIX for Dummies Questions & Answers

please help me about unixware 7.1.3

msg: vfs_mountroot:cannot mount root %%%%%% system don't start (0 Replies)
Discussion started by: hushboy
0 Replies

6. SCO

unixware 2.0

High, I have a simulator application running on unixware 2.1, there are no original installation CDs for the application. is it possible to copy directories and configuration files, related to the installed application, from unixware 2.1 to other system running Unixware 7.1.1 (replacing Unixware... (0 Replies)
Discussion started by: fareedah
0 Replies

7. SCO

Problem in Unixware 7

Hi, I need help for SCO UNIXWARE 7.1.0. During booting it is detecting the network card (Intel PRO 100B /100+) but it is giving error : "UX:S69inet:error". Hence network is not getting up. I have tried with another network card (D-Link DFE 538TX) but unable to get the proper driver for the... (1 Reply)
Discussion started by: hcl.rajat
1 Replies

8. SCO

Unixware 7.11 cannot telnet

Hi all, I recently re-installed a Unixware 7.1.1 system for a customer. It installed correctly, I can ping the server but I cannot telnet to it. I did check and telnetd is running. Am i missing something in the config? thanks for any help (0 Replies)
Discussion started by: RDP
0 Replies

9. SCO

unixware 7.1.0 boot floppy #2 needed if someone has one.

Hi all, I'm reinstalling unixware 7.1.0 on another machine for a customer that will replace the existing machine that is now in use. When i go to start the install the second floppy is not recognized. These are the original sco floppies. I have recreated the boot floppies from the... (3 Replies)
Discussion started by: RDP
3 Replies

10. News, Links, Events and Announcements

Are the UnixWare 7.1.1 sources available?

So, I was browsing groklaw.net, and I was surprised to read that Pamela Jones was reading the copyright notices in the UnixWare 7.1.1 source code files... Groklaw - Santa Cruz Listed Novell as Owning the Copyrights in 1999 How can that be? Are the UnixWare 7.1.1 sources available to the... (1 Reply)
Discussion started by: pepinox
1 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 06:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy