Sponsored Content
Operating Systems SCO UNIX SCO based Healthcare system Post 59649 by Docboyeee on Monday 27th of December 2004 09:51:45 PM
Old 12-27-2004
Conversion

I deal with these sorts of coversions all the time. I sell Medical Practice Management Software so I am often converting data from one system to another. It might be necessary for you to create a disk printer for unix and print your data out of the application into disk print files that you should then be capable of getting the data you desire. If you wish to contact me you may do so
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SCO UNIX System V/386, Release 3.2

I was just wondering if there is a way to recursive grep for something in this version of UNIX... so that I don't have to do it a directory at a time? (1 Reply)
Discussion started by: PBNOSGT
1 Replies

2. Filesystems, Disks and Memory

SCO TCP/IP runtime System for SCO Unix

Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
Discussion started by: Cerberus
0 Replies

3. UNIX for Dummies Questions & Answers

Limit number of user accessing to SCO UNIX System

Hi, In my company, we are using SCO UNIX system and Informix database. Recently, there have been a lot of users accessing to server and sometimes it has made server run very slow. So, I intend to limit number of users of 30 only. Although I have tried to search on the Internet for several days,... (1 Reply)
Discussion started by: trinhnguyen
1 Replies

4. UNIX for Dummies Questions & Answers

ASP.net in unix based system

Hi Guys, i am new to the fourms.. i have one doubt related to unix.. i was developed one application in asp.net under windows platfrom. i want to run this application in sun one web server under unix environment.. Its possible or not .. please calrify my doubt. Thanks and Regards... (1 Reply)
Discussion started by: ksathiya76
1 Replies

5. Windows & DOS: Issues & Discussions

ASP.net in unix based system. Someone Help Me

Hi Guys, i am new to the fourms.. i have one doubt related to unix.. i was developed one application in asp.net under windows platfrom. i want to run this application in sun one web server under unix environment.. Its possible or not .. please calrify my doubt. Thanks and Regards... (4 Replies)
Discussion started by: ksathiya76
4 Replies

6. UNIX for Dummies Questions & Answers

unix system v release 3.2 (sco-unix?)

another unix printing issue. our client based pc's used to print some form's to our hp printer. as of the moment they can not print. i have checked & did the ff: #lpstat -r (scheduler is running) i dunno if i need to restart the whole unix box via shutdown or just checking at... (15 Replies)
Discussion started by: jedimaster
15 Replies

7. SCO

Sco Unix HFS file system error

HI, I have sco unix server currently i am trying to boot its not booting and giving error as HTFS error message contains - Warning : can not identify block 496 for i number 438 on HTFS dev hd (1/42). Warning : exit - /etc/init (PID 1) died, status 0x0000008B server is not getting boot... (0 Replies)
Discussion started by: islamsk
0 Replies

8. UNIX for Dummies Questions & Answers

Error UNIX: UNIX SCO release 5.05 system does not boot

UNIX sco release 5.05 system does not boot:cannot open device hd(40)/boot stage 1 boot failure: error loading hd(40)/bootWhat to do? (2 Replies)
Discussion started by: Joaoalpande
2 Replies

9. SCO

UNIX SCO release 5.05 system does not boot

UNIX sco release 5.05 system does not boot: cannot open device hd(40)/boot stage 1 boot failure: error loading hd(40)/boot what to do? (1 Reply)
Discussion started by: Joaoalpande
1 Replies

10. UNIX for Advanced & Expert Users

UNIX SCO release 5.05 system does not boot

UNIX sco release 5.05 system does not boot: cannot open device hd(40)/boot stage 1 boot failure: error loading hd(40)/boot what to do? (5 Replies)
Discussion started by: Joaoalpande
5 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 characters. SYS_NMLN is an implementation specific value defined in <sys/utsname.h>. Only the super-user is allowed this capability. This change does not persist across reboots of the system. Use sys-unconfig(1M) to change a host's name per- manently. -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.11 17 Sep 2003 uname(1)
All times are GMT -4. The time now is 12:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy