Sponsored Content
Full Discussion: Ip change SCO UNIX 3.2.4.2
Top Forums UNIX for Beginners Questions & Answers Ip change SCO UNIX 3.2.4.2 Post 303031008 by jgt on Wednesday 20th of February 2019 10:54:32 AM
Old 02-20-2019
You don't have a gateway address.
Add a script to /etc/rc2.d that executes after S85tcp that contains:
Code:
route add default 192.168.1.x

or edit the/etc/default/tcp so that GATEWAY has a value.

--- Post updated at 10:54 AM ---

The scripts in /etc/rc2.d execute in alphabetical order.
This User Gave Thanks to jgt For This Post:
 

9 More Discussions You Might Find Interesting

1. 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

2. SCO

pswd change on sco GUI login

Can i change the password on the SCO GUI interface login page and if so how? When I try to login it just goes right back to the login screen. If anyone has any suggestions, please reply. :confused: (3 Replies)
Discussion started by: qphillips
3 Replies

3. Filesystems, Disks and Memory

Unix Sco Open Server, Windows Computers Problem Access Unix Shared Files Help!!!!!

Hello Moto I hope someone can help We's here at work, have a unix box with sco openserver 5 on it, so it has a nice gui interface.. and also a fair few windows computers.. a system admin guy b4 me, has set up a user called neil, which can, when u try to access the unix box using windows... (2 Replies)
Discussion started by: haggo
2 Replies

4. 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

5. SCO

load sco xenix and sco unix binary ?

Hi I have some sco xenix object, bin and archive files that operate in sco unix 5.0.7. I know that sco unix kernel can support sco xenix binary. I want to know how can I link xenix and unix archives together? (0 Replies)
Discussion started by: javad1_maroofi
0 Replies

6. SCO

change NetBIOS name of SCO 5.0.6

hi Howto change NetBIOS name of SCO 5.0.6? Is it enough just to edit /etc/hosts file? (1 Reply)
Discussion started by: ccc
1 Replies

7. SCO

Change SCO - GUI or Desktop interface to DOS based interface

Hi all I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface? If you have any ideas, please tell me then. Thank you (2 Replies)
Discussion started by: TinhNhi
2 Replies

8. SCO

Change Disk controller in SCO 6.0.0

So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller. First, I downloaded the megasas driver from SCO and installed it on the old system. Then I created a new Microlite Edge emergency boot cd with the new driver on it. I... (2 Replies)
Discussion started by: jgt
2 Replies

9. 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
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)

Featured Tech Videos

All times are GMT -4. The time now is 02:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy