Sponsored Content
Operating Systems SCO Set NIC correctly , but the network does not work Post 302875555 by jgt on Tuesday 19th of November 2013 08:24:51 PM
Old 11-19-2013
If you have a valid serial number and activation key, you can/should upgrade to 5.0.6. You can do this before making the image file and as an update install so no data should be lost.
When Intel introduced the Pentium 4, they moved control of the processor temperature from the CMOS/microcode to the operating system. SCO did not incorporate this change into any releases older than 5.0.6.
In 5.0.4 SCO made a change to the custom file format. Any VOL.000.000 files that work with 5.0.4 and newer will not work with 5.0.0 thru 5.0.3. This fact will make finding drivers much more difficult.
This User Gave Thanks to jgt For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

why the PATH can not be set correctly?

I'm using Linux-Mandrake 8.0 in my laptop. After I logged in as a "root", I added a new path in my .bashrc file (I use bash shell). Then I can observe it has been set correctly by typing echo $PATH. But, when I log in again as a personal account, not "root", then I open my bash shell, and type... (5 Replies)
Discussion started by: yishen
5 Replies

2. UNIX for Dummies Questions & Answers

Couldn't set locale correctly

When a user connects via ssh to one of out Sun V120 boxes the following message is displayed. "couldn't set locale correctly" The .profile has the following line # @(#)local.profile 1.6 98/02/06 SMI stty istrip stty erase ^H So I put a set -x in the .profile and re sourced it and... (1 Reply)
Discussion started by: mattd
1 Replies

3. SuSE

vsft doesn't work correctly

I install vsftpd server on 2 SUSE 10.2 servers. The first works perfectly, but the second doesn't work how I expect. The second works only over local network and doesn't over internet. The vsftpd.conf and ../xinetd.d/vsftpd are the same in 2 servers. The only different was when I threw to log in... (1 Reply)
Discussion started by: zhivko.neychev
1 Replies

4. Solaris

Couldn't set locale correctly

hi All, I'm using sun OS 5.10. All locales are set to en_US.ISO8859-1 in /etc/profile/init file. I'm using one functional user.When I tried to "sesu - functionalUser",its giving me error like "Couldn't set locale correctly".In functional user profile i'm tring to set locales to en_US.After... (1 Reply)
Discussion started by: Kathraji
1 Replies

5. Solaris

Couldn't set locale correctly

Hello, I have a recently configured machine that when log into it as a user or remotely as root it displays "Couldn't set locale correctly" When I type locale it displays the below which is wrong compared to other machines LC_CTYPE="C" LC_NUMERIC="C" LC_TIME="C" LC_COLLATE="C"... (7 Replies)
Discussion started by: Mr Pink
7 Replies

6. Programming

Cannot get dbx to work correctly with a running process

Hi everyone, I've been struggling with this for a few weeks now. I'm trying to debug a running process with dbx on an AIX box. The command I'm using is 'dbx -a <pid> core' There is a function I can perform in my application that crashes this process, but it does not show up as crashed in... (0 Replies)
Discussion started by: ctote
0 Replies

7. Solaris

LC_ALL & LANG are set OK, but others couldn't set locale correctly.

Hi, I have a Solaris (SunOS 5.10) installed, by default with the en_AU.UTF-8 locale. I want to change it to en_US.UTF-8 With AU, I have no issues whatsoever, so I installed the language package and now locale -a shows "en_US.UTF-8". Problem is even with LC_ALL set in etc/default/init, the... (2 Replies)
Discussion started by: asdfg
2 Replies

8. UNIX for Advanced & Expert Users

Libvirt does not work correctly anymore on my gentoo

Hi, Since a year my libvirtd does not work anymore on my Gentoodesktop. In the meantime a used virtualbox. But I would like to have back libvirt. The problem was after libvirt should not only work with root privileges. I deinstalled all things with libvirt an kvm. I removed all things from /var... (4 Replies)
Discussion started by: darktux
4 Replies

9. Gentoo

LDAP-Auth does not work correctly with systemd

Hi, since the upgrade to Gnome 3.6 (now i have 3.8) the authentication over LDAP stops working. The whole machine does not start anymore. The machine boot, but no gdm and no X. I can login, with root, but then the tty hangs. When i look at ttyF12 i see a lot of systemd service the runs random,... (1 Reply)
Discussion started by: darktux
1 Replies

10. Shell Programming and Scripting

Why does this awk script not work correctly?

I have a large database with English on the left hand side and Indic words on the left hand. It so happens that since the Indic words have been entered by hand, there are duplicates in the entries. The structure is as under: English headword=Indic gloss,Indic gloss A small sample will... (6 Replies)
Discussion started by: gimley
6 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 03:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy