Sponsored Content
Full Discussion: My UnixWare SCO Server
Operating Systems SCO My UnixWare SCO Server Post 302598920 by Corona688 on Wednesday 15th of February 2012 05:28:59 PM
Old 02-15-2012
Quote:
Originally Posted by DGPickett
Most x86 LINUX/UNIX code used to be portable, but I haven't checked if x86_64 systems run old 32 bit coff/elf executables and files.
ELF ought to work given matching libraries, but ELF was 1995 and later. There's still options for ECOFF in the Linux kernel, but they might need to be built-in custom; I can't imagine a standard kernel having them enabled.

Whether a program from 1992 will work without its corresponding libraries is another question. I have no idea how shared libraries would need to be set up for COFF. I doubt the standard ld.so system would touch them.
 

8 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. UNIX for Dummies Questions & Answers

SCO Unixware 7 download

According to this thread: https://www.unix.com/showthread.php?t=1 one guy says However, I cannot find any sco unixware7 iso download link in their download section (http://wdb1.sco.com/clbk_web/owa/dwn_customer), is it really for free, and if that is true, where can I download it? Thanks, (2 Replies)
Discussion started by: phalcos
2 Replies

3. SCO

Samba 3.0.24 in SCO UnixWare 7.1.4

Please help me in troubleshooting my problem in Samba? I tried to instal Samba 3.0.24 in our SCO UnixWare 7.1.4 but after installing the nmbd daemon is not running. When i check the syslog from /var/adm, the following error appears: Sep 30 13:04:22 unixeei nmbd: bind failed on port 137... (0 Replies)
Discussion started by: eric_hing
0 Replies

4. SCO

sco unixware + oracle 8.0.5

hi, anybody can give procedure for how to install oracle 8.0.5 in sco unixware 7.1.4. (0 Replies)
Discussion started by: prakrithi
0 Replies

5. SCO

Noob needs help with Sco Unixware 7.1

We are retiring a Unixware 7.1 server that has custom applications on it. It has Raid 5 and we would like to use the machine for other things. Is there a way we can image/clone to virtual machine file and run that VM within say Virtual PC 2007 or VMware? I am not aware of anything to do this. I... (20 Replies)
Discussion started by: ccd1977
20 Replies

6. SCO

Install GRUB on SCO Unixware 7.1.1

Hi, I am trying to install the linux boot loader (GRUB) on a non-linux machine (Unixware 7.1.1). The thing is I want to boot the linux kernel (vmlinuz) and the linux ram disk (initrd.img) from unixware and boot the machine with it. Does anyone have a good way to do this? (10 Replies)
Discussion started by: teen_racer19
10 Replies

7. SCO

SCO Unixware 7.1.1 Install - Need help

(sorry my English, is really poor). I have a SCO Unixware 7.1.1 and I need install in ML350 G3. Reading in google and HP web, make a floppy disks for install, but the options that I have is for network or floppy disk. How install from CD with patch for HP smart array 532 ?? or How... (5 Replies)
Discussion started by: xplertor
5 Replies

8. SCO

Need Help with installtion of SCO UNIXware 7.0.1

Hi, I need help to install SCO Unixware 7.0.1. Can any one help with any documentation or installation notes for SCO Unixware 7.0.1. Thank you (1 Reply)
Discussion started by: farhandalvi
1 Replies
LDCONFIG(8)						    BSD System Manager's Manual 					       LDCONFIG(8)

NAME
ldconfig -- configure the shared library cache SYNOPSIS
ldconfig [-32] [-aout | -elf] [-Rimrsv] [-f hints_file] [directory | file ...] DESCRIPTION
The ldconfig utility is used to prepare a set of ``hints'' for use by the dynamic linker to facilitate quick lookup of shared libraries available in multiple directories. It scans a set of built-in system directories and any directories specified on the command line (in the given order) looking for shared libraries and stores the results in a system file to forestall the overhead that would otherwise result from the directory search operations the dynamic linker would have to perform to load the required shared libraries. Files named on the command line are expected to contain directories to scan for shared libraries. Each directory's pathname must start on a new line. Blank lines and lines starting with the comment character '#' are ignored. Filenames must conform to the lib*.so.[0-9] pattern in order to be added to the hints file. For security reasons, directories which are world or group-writable or which are not owned by root produce warning messages and are skipped, unless the -i option is present. The shared libraries which are found will be automatically available for loading if needed by the program being prepared for execution. This obviates the need for storing search paths within the executable. The LD_LIBRARY_PATH environment variable can be used to override the use of directories (or the order thereof) from the cache or to specify additional directories where shared libraries might be found. LD_LIBRARY_PATH is a ':' separated list of directory paths which are searched by the dynamic linker when it needs to load a shared library. It can be viewed as the run-time equivalent of the -L switch of ld(1). The ldconfig utility is typically run as part of the boot sequence. The following options are recognized by ldconfig: -32 Generate the hints for 32-bit ABI shared libraries on 64-bit systems that support running 32-bit binaries. -aout Generate the hints for a.out format shared libraries. -elf Generate the hints for ELF format shared libraries. -R Rescan the previously configured directories. This opens the previous hints file and fetches the directory list from the header. Any additional pathnames on the command line are also processed. This is the default action when no parameters are given. -f hints_file Read and/or update the specified hints file, instead of the standard file. This option is provided primarily for testing. -i Run in insecure mode. The security checks will not be performed. -m Instead of replacing the contents of the hints file with those found in the directories specified, ``merge'' in new entries. Direc- tories recorded in the hints file by previous runs of ldconfig are also rescanned for new shared libraries. -r List the current contents of the hints file on the standard output. The hints file is not modified. The list of directories stored in the hints file is included. -s Do not scan the built-in system directory (``/usr/lib'') for shared libraries. -v Switch on verbose mode. SECURITY
Special care must be taken when loading shared libraries into the address space of set-user-Id programs. Whenever such a program is run by any user except the owner of the program, the dynamic linker will only load shared libraries from the hints file. In particular, the LD_LIBRARY_PATH is not used to search for libraries. Thus, the role of ldconfig is dual. In addition to building a set of hints for quick lookup, it also serves to specify the trusted collection of directories from which shared objects can be safely loaded. FILES
/var/run/ld.so.hints Standard hints file for the a.out dynamic linker. /var/run/ld-elf.so.hints Standard hints file for the ELF dynamic linker. /etc/ld.so.conf Conventional configuration file containing directory names for invocations with -aout. /etc/ld-elf.so.conf Conventional configuration file containing directory names for invocations with -elf. /var/run/ld-elf32.so.hints /var/run/ld32.so.hints Conventional configuration files containing directory names for invocations with -32. SEE ALSO
ld(1), link(5) HISTORY
A ldconfig utility first appeared in SunOS 4.0, it appeared in its current form in FreeBSD 1.1. BUGS
Some security checks (for example, verifying root ownership of added directories) are not performed when -aout is specified. BSD
March 19, 2013 BSD
All times are GMT -4. The time now is 03:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy