Sponsored Content
Operating Systems SCO Migrating Digi PortServer TS 16 Post 302467625 by atish0 on Saturday 30th of October 2010 10:24:30 AM
Old 10-30-2010
Migrating Digi PortServer TS 16

Hi

I am migrating from SCO 5.05 to SCO 6. The SCO 5.05 is on old hardware.

I have installed SCO 6.0 on a new Dell server. I am manualy migrating the users, printer config and profiles.

When I finsh migrating I plan to switch the IP address from the old server to new server, and shut down the old server.
By doing this I will not have have re-configure the digiport divices, print servers.

Digi port devices are new for me and I dont want to make any change on the devices ( this is to minimize the down time, as these devices are geographically spread)

Can you please advise me what files contain the Digi Portserver 16 configuration in SCO 5.05, that I can copy to the new server. or if copy is not possible then find out the config and re create on the new server.

TIA

TIA
 

8 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

mini digi-cam

hey guys! I am on a fedora core2 i686 with gui and I have a miniture cool-cam which is digital.. it connects through regular usb.. the system recognizes it and the when I go into the desktop peripheral and go to camera it gives name and tells test was successful.. it also says that the camera has... (0 Replies)
Discussion started by: moxxx68
0 Replies

2. UNIX for Dummies Questions & Answers

Migrating from HP to Solaris

My company is considering migrating from HP unix to Solaris just to get two more years of support for a particular software product. My question is just how much of an effort is it to do this migration? Are you aware of any migration tools to assist us in this migration? Thanks (1 Reply)
Discussion started by: jkuchar747
1 Replies

3. HP-UX

When migrating from HP-UX 11.0 to HP-UX 11.i

Hi to all, I am migrating HP-UX 11.0 to HP-UX 11.i, The following list are the components which i used in HP-UX 11.0, Whether I can use this same components in HP-UX 11.i or I should upgrade any of software version with respect to HP-UX 11.i. Oracle 8.1.7 Tuxedo 8.0 BEA Message queue... (0 Replies)
Discussion started by: sweta
0 Replies

4. HP-UX

Migrating from HP-UX 11 to HP-UX 11.i?

Hi, I want to Migrate my machine from HP-UX 11 to HP-UX 11.i, regarding this i would like to know the difference and the advances b/w these two. If anyone have cookbook HP-UX 11 to HP-UX 11.i, then provide the link to me. Thanks in Advance. Sarwan (3 Replies)
Discussion started by: sarwan
3 Replies

5. AIX

Printer issue on a Digi

Ok, Im a new network admin to the AIX environment. Im in the AIX console as we speak and I don't understand this issue with the print server. It's not a standard print server that I'm used to seeing and was wondering if any of you have any experiences with a Dev_Wait issue on a Digital to Serial... (0 Replies)
Discussion started by: Itsaboutme
0 Replies

6. SCO

Digi 8e memory window not available in mpi

In setting up an 8e on 5.0.5 I couldn't find a memory window that worked using mpi (3 versions). The memory search program (DOS based) indicated E800 was available but mpi only listed E000. I resolved my immediate problem by changing the window value in /etc/conf/pack.d/pcxx/space.c prior to... (2 Replies)
Discussion started by: edfair
2 Replies

7. AIX

Setup 1 Digi PortServer II with 5 x AIX boxes

Hi everyone, My latest challenge sees me assisting with the setup of one of our classroom labs. We are trying to configure the lab so that the (5) IBM 9115-505 servers (all running AIX7.1) have their serial 0 ports connected to a Digi PortServer II, which is on the classroom LAN, along with the... (4 Replies)
Discussion started by: richardsantink
4 Replies

8. UNIX for Beginners Questions & Answers

Migrating to UNIX

I am looking for a stable, reliable system to replace my current Windows systems in the home. These are simple systems that I purchased from the local Big Box store. I have heard many good things about Unix and it's various children and it sounds like a good option to me. I have worked... (2 Replies)
Discussion started by: donschurter
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)
All times are GMT -4. The time now is 01:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy