Sponsored Content
Full Discussion: license info
Operating Systems SCO license info Post 302142346 by rm -r * on Thursday 25th of October 2007 03:44:41 PM
Old 10-25-2007
It's been a while since I've used SCO OpenServer, but does the following command:

# scoadmin license

...take you where you need to go?
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

License Expired

Hi: I´m working with a SCO system and during a reboot i accidentally change the date system. Now when i try to establish a telnet session the system reject me saying that the license has expired. Is there any way to solve this problem? Thanks (1 Reply)
Discussion started by: Tavo23
1 Replies

2. UNIX for Dummies Questions & Answers

License with demo???

I'm trying to setup a test environment to test upgrading to Solaris 8 or 9. Though when I go to install the demo version of Sun1 (forte/sun workshop as named before) it'll still ask for a 20 hexidecminal password for just a demo. huh? Ok so I added a 20 character thing in there it passed... (2 Replies)
Discussion started by: merlin
2 Replies

3. UNIX for Dummies Questions & Answers

license info

Help, I need to find info for the following: 1. Applications that are running 2. application(s) info, i.e. , version, etc 3. License info (if applicable) 4. expiration dates of licenses. I would like to create a perl script to gather this info from my servers. I am teaching myself... (3 Replies)
Discussion started by: antalexi
3 Replies

4. UNIX for Dummies Questions & Answers

Which Unix license should I go for?

I'm thinking about getting the Network and Admin licenses for Solaris 9. But some people say Red Hat Linux license is just as good. And there is also IBM's Linux license. Is Solaris still very popular in the corperate world? Looking for a Unix Admin job, which license do you suggest I try... (3 Replies)
Discussion started by: CapsuleCorpJX
3 Replies

5. AIX

license trouble

Hi, we currently use a valisys licence : it is based on a server (serv1) it is reached only by one workstation (cam1) In all licence files there is line with cam1 et serv1 We want to use cam22 (new workstation) instead of cam1 I made a copy the licences files with remplacing cam1 by cam22... (0 Replies)
Discussion started by: cadmanager
0 Replies

6. UNIX and Linux Applications

License

Dear Expert, Let say i have already Build Any Application under UNIX platform. Then i want to sell that application for Free. But buyer have to Buy the License for running my application. Somebody knows if there is an any kind of tools or another technique for Generate that License ? ... (1 Reply)
Discussion started by: tpx99
1 Replies

7. Solaris

License expired

Hi I am working with Solaris 4.1.3 The system uses CMIS protocol to communicate with other system. The Live server is working properly. The fall back system says Licese CMIS expired. all the files are exactly similar on both the systems now if i change the... (4 Replies)
Discussion started by: asalman.qazi
4 Replies

8. Programming

License error

All, When I am trying to complie a c code, I am getting the following error below. Anyone please tell me where to fix it. #cc -o hello.exe hello.c License Error : Cannot find the license server (au1144s) in the network database for product(Sun WorkShop Compiler C SPARC) Cannot... (2 Replies)
Discussion started by: thana
2 Replies

9. Shell Programming and Scripting

Updating the license tag in XML file with new license

Hi All, I have a XML file : System.xml in which I want to update the license tag with the new data from file licence.xml. The content of files is in following format: System.xml: <?xml version="1.0"?> <!DOCTYPE Configuration SYSTEM "SystemVariables.dtd"> <usageConfiguration... (2 Replies)
Discussion started by: Pramod_T
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 07:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy