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
uname(1)							   User Commands							  uname(1)

NAME
uname - print name of current system SYNOPSIS
uname [-aimnprsvX] uname [-S system_name] DESCRIPTION
The uname utility prints information about the current system on the standard output. When options are specified, symbols representing one or more system characteristics will be written to the standard output. If no options are specified, uname prints the current operating sys- tem's name. The options print selected information returned by uname(2), sysinfo(2), or both. OPTIONS
The following options are supported: -a Prints basic information currently available from the system. -i Prints the name of the platform. -m Prints the machine hardware name (class). Use of this option is discouraged. Use uname -p instead. See NOTES section below. -n Prints the nodename (the nodename is the name by which the system is known to a communications network). -p Prints the current host's ISA or processor type. -r Prints the operating system release level. -s Prints the name of the operating system. This is the default. -S system_name The nodename may be changed by specifying a system name argument. The system name argument is restricted to SYS_NMLN char- acters. SYS_NMLN is an implementation specific value defined in <sys/utsname.h>. Only the super-user is allowed this capa- bility. This change does not persist across reboots of the system. Use sys-unconfig(1M) to change a host's name perma- nently. -v Prints the operating system version. -X Prints expanded system information, one information element per line, as expected by SCO UNIX. The displayed information includes: o system name, node, release, version, machine, and number of CPUs. o BusType, Serial, and Users (set to "unknown" in Solaris) o OEM# and Origin# (set to 0 and 1, respectively) EXAMPLES
Example 1: Printing the OS name and release level The following command: example% uname -sr prints the operating system name and release level, separated by one <SPACE> character. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of uname: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. SYSV3 This variable is used to override the default behavior of uname. This is necessary to make it possible for some INTERACTIVE UNIX Systems and SCO UNIX programs and scripts to work properly. Many scripts use uname to determine the SYSV3 type or the version of the OS to ensure software is compatible with that OS. Setting SYSV3 to an empty string will make uname print the following default values: nodename nodename 3.2 2 i386 The individual elements that uname displays can also be modified by setting SYSV3 in the following format: os,sysname,node,rel,ver,mach os Operating system (IUS or SCO). sysname System name. node Nodename as displayed by the -n option. rel Release level as displayed by the -r option. ver Version number as displayed by the -v option. mach Machine name as displayed by -m option. Do not put spaces between the elements. If an element is omitted, the current system value will be used. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
arch(1), isalist(1), sys-unconfig(1M), sysinfo(2), uname(2), nodename(4), attributes(5), environ(5), standards(5) NOTES
Independent software vendors (ISVs) and others who need to determine detailed characteristics of the platform on which their software is either being installed or executed should use the uname command. To determine the operating system name and release level, use uname -sr. To determine only the operating system release level, use uname -r. Notice that operating system release levels are not guaranteed to be in x.y format (such as 5.3, 5.4, 5.5, and so forth); future releases could be in the x.y.z format (such as 5.3.1, 5.3.2, 5.4.1, and so forth). In SunOS 4.x releases, the arch(1) command was often used to obtain information similar to that obtained by using the uname command. The arch(1) command output "sun4" was often incorrectly interpreted to signify a SunOS SPARC system. If hardware platform information is desired, use uname -sp. The arch -k and uname -m commands return equivalent values; however, the use of either of these commands by third party programs is dis- couraged, as is the use of the arch command in general. To determine the machine's Instruction Set Architecture (ISA or processor type), use uname with the -p option. SunOS 5.10 17 Sep 2003 uname(1)
All times are GMT -4. The time now is 01:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy