|
Blue Forest http://www.lslnet.com at 11:08 on July 8, 2006
 S CO OPENSERVER OS
INTRODUCTION 9
SCO OpenServer systems outlined in paragraph l Chapter 11
Rather, company profiles 11
SCO UNIX 12
12 1.1 System Configuration
SCO OpenServer 1.1.1 System 12
12 1.1.2 Media
1.1.3 Document 13
Additional permits and products 1.2 1.3
13 1.2.1 license and registration terms
SCO visit online information services 14 1.3
Chapter 2 of the installation and upgrading 14
2.1 installation and upgrading checklist 14
The installation and upgrading of 230 18
2.5 After installation mistake! Bookmark not defined.
2.6 upgrade choice of 20 channels
2.6.1 upgrade installed on 21 types
2.6.2 Preserve hard disk option on 22
2.6.3 installed option on 22 interactive Hard Disk
2.6.4 installed on the hard disk of 23 other option
2.7 various upgrading 23
2.7.1 restore user accounts 23
24 2.7.2 user configuration files and directories
2.7.3 upgrade the main hard disk-25
2.7.4 upgrade a third party driver 26
SCO OpenServer 2.7.5 Development System 26 upgrade
Upgrade from version 2.8 5.0 26
2.8.1 lost 26 documents created by users
2.8.2 third-party products and systems serial number 27
Desktop 2.8.3 or upgrade to Enterprise from the Host Configuration 27
Upgrade from version 2.9 3.0 27
2.9.1 upgrade SCO Merge 27
Upgrade from version 2.0 2.10 28
Chapter 3 of 28 floppy disks to create emergency guide
28 emergency allocation of 3.1 disk
3.2 increase in the root system diskette 29 documents
3.3 increase in root disk Network File 29
3.4 diskette test group of 30 emergency guide
Backup 3.5 capturing 30
3.6 31 from the hard disk boot
Chapter 4 with the permission of SCO products registered 31
Interface Manager 4.1 Licnese 31
31 4.2 product license
4.2.1 permit other users and CPU 32
4.2.2 products permission to delete 32
32 products registered 4.3
4.4 product licensing and registration of fault diagnosis 34
Manager 4.4.1 license is not registered 34
4.4.2 License Information Manager is not permitted to accept 34
4.4.3 OpenServer license had expired 34
OpenServer 4.4.4 check the license expiration date 35 products
Computer users were not found in 4.4.5 license 35
4.4.7 LOGIN : ERROR initialization policy management process -- not 36
4.4.7.1 /etc/ifor_pmd binary file has been lost or interrupted 36
4.4.7.4 There is no user license, permit or no more 36
4.4.7.5 STREAMS resources system has exceeded 37
Chapter 5 of the installation of fault diagnosis 37
5.1 installation problems in the course of 37
5.1.1 installation process can not lead in 38
5.1.2 disk read errors 39
5.1.3 installation of equipment used SCSI errors 39
5.1.4 from the disk channel guide or suggested in its space from 39 Boot :
5.1.5 system hardware configuration screen GUI starting 39
Hardware self-stop 40 of 147 centers in 1985
Panama guidance system from the hard drive 40
After the installation of 41 5.2
5.2.1 consoles display abnormal 41
5.2.2 tty02 in the graphics display abnormal scologin 41
5.2.3 hardware can work 41
5.2.4 unable to work 41 DOS
5.2.5 system software is not permitted or not registered 42
5.2.6 no mistake : the process of creating sub-42
5.2.7 error : ERROR 42 X TOOLKIT
5.2.8 General information system resources mistake 42
5.3 The document did not address the installation of 43
43 hardware and operating system 5.3.1
5.3.2 identified 43
540 for help before 44
5.4.1 Description of the 44
5.4.2 System Configuration 45
Chapter 6 SCO and the use of other operating systems 46
District 46 installed OS/2, or Windows NT 6.1
Creating and formatting a physical DOS 6.2 46
47 6.2.1 DOS zoning restrictions
6.2.2 procedures for the use of low-level formatted 47
6.2.3 digital conversion fdisk 48
6.3 classified disk using fdisk (interactive installation) 48
Table 6.3.1 shows the current District 49
Switching OS 6.4 49
6.4.1 guide DOS 49
6.4.2 guide arbitrary District 50
6.4.3 from the disk to guide dos 50
District 51 in DOS 6.5 installed UNIX
6.6 operating system from one hard disk to delete 51
SCO management system 51 Chapter 7
Understand basic knowledge 7.1 52
52 What is the management system 7.1.1
7.1.2 reservation system day to forget 52
7.1.3 super user accounts 53
7.1.4 multi-screen display running in a number of procedures 53
SCOadmin management systems use 53 7.2
7.2. 1 command line started SCOadmin 54
7.2.2 update data on Display 54
7.2.3 using 55 points for help
7.2.4 using a tool column 55
7.2.5 in text mode using SCOadmin 55
7.2.6 SCOadmin fault diagnosis 56
Summary 58 7.3 system management tasks
The system was activated and 59 Chapter 8
Start-up System 59 8.1
8.1.1 operating system installed 59
5.4 Storage / delete system memory image 60
File System 8.1.3 cleared 60
8.1.4 selection system operated 61
8.1.5 launch time and date installed 61
Shall be elected for a five-normal operating time and date installed 62
8.1.7 change the system time zone 62
63 8.1.8 database security checks
The system 65 8.2
8.2.1 shutdown command line using 66
8.2.2 use haltsys orders 66
83,000 registered users in the Super 67
8.4 understanding of the hardware information guide, indicate 67
Start to change 8.5 69
8.5.1 change the system to restart option 69
8.5.2 change tacit guide series (DEFBOOTSTR) 70
8.5.3 old guide core 70
8.6 The fault diagnosis system activated 70
8.6.1 loss or damage to the system documentation 71
8.6.2 restore key security database documents 71
8.6.3 guidance system failure or that the "NO OS" news 72
8.6.4 boot found 72 documents
UNIX 8.6.5 found 73 documents
8.6.6 floating point simulation program can load 74
8.6.7 : No such documents or unable to perform list /bin/login 74
8.6.8 unable to break /etc/inittab 75
8.6.9 /etc/initscript:/bin/sulogin not find 76 :
8.6.10 /etc/initscript:/etc/bcheckrc not find 76 :
8.6.11 no utmp items from the lowest level registered 76 -sh
8.6.12 failure of the process of creating a temporary void resources : 77
8.6.13 guidance system in effect at 77 GUI
Console 8.6.14 good keyboard lock 78
Console 8.6.15 not registered 79
Chapter 9, the start of 79 customized graphical environment
9.1 graphical environment for dialogue initiated 80
Operation scologin 80 64 9.2
Scologin allocation of the electromagnetic launch 81
9.1.1.2 dialogue definition x 81 server
7.1.1 off from the 81 scologin
Script 7.1.3 operating procedures startx 81
9.2.1 customization scologin 82
82 scripted using scologin management might affect her health or that of her child
9.2.3 the number of monitors on the allocation of 83 scologin
Chapter 10 increased 83 Disk
Support the distribution of the hard disk 10.1 83
Add a second hard disk 10.2 84
SCSI hard disk configuration 10.3 84
Installation Disk 10.4 85
10.4.1 tacit approval to change the use of the disk parameters dkinit 86
10.4.2 to disk using fdisk District 87
10.4.3 using disk scanning errors badtrk 87
10.4.4 Percentage of the use of disk divvy put into a regional district 88
89 10.5 overcome restrictions BIOS
10.5.1 definition in the BIOS and IDE disk geometry ESDI 90
10.5.2 so stored in the root of disk geometry parameters invalid BIos中 90
10.5.3 write a new master boot block 91
10.5.4 cylindrical disk BIOS supports more than 1,024 91
IDE disk controller and disk configuration 10.6 91
Disk replacement root 10.7 92
Disk allocation root 10.7.1 93
Disk fault diagnosis 10.8 93
10.8.1 complex repair the hard disk and bad bad cylinder block 93
10.8.2 installed hard disk partition factor 94
94 10.8.3 formatted hard disk
Chapter 11 increased 94 serial terminal
Serial terminals installed 94 11.1
Link 95 terminals 11.2 tests
11.3 acquiescence to change the terminal characteristics of 96 lines
1.2.2.4 change /etc/gettydefs registered items 96
11.3.2 check terminals installed 97
Serial changes in operating line 108 11.4 97
11.4 provision for the registration of 98 types of terminal
11.4.1 installed automatic terminal type 99
11.5 removed terminal 99
Serial consoles installed 99 11.6
Fault diagnosis of terminal 100 11.7
11.7.1 did not resume work on the terminal 100
11.7.2 repair the terminal complex GUI Qi 101
11.7.3 repair the terminal complex and chaotic 101
11.7.4 good lift lock on the terminal 102
11.7.5 back without significant terminal complex repair 102
Chapter 12 Equipment Management 102
102 documents and equipment 12.1
104 12.2 equipment configuration
Chapter 13 system-level fault diagnosis 107
13.1 10.7 Other Documents Fault Diagnosis
To 13.2 from 10.7 in preparation for resuming save stomach
13.2.1 108 record, the layout of hard disk root
13.3 restore damaged root file system 108
13.4 110 collapse
13.4.1 from the emergency system were restored 111
13.4.2 after the restart to restore 113
13.4.3 automatic channel 113
113 13.5 System Fault Analysis
13.5.1 still, fault and unusual 113
Available Console emergency urgent letter 114
13.5.3 access EIP Radio 114
13.5.4 115 inspections wrong information
13.5.5 115 historical mistakes in the document inspection system
13.5.6 115 inspection system configuration
13.6 use crash (ADM) memory dump 117 inspection orders
Research emergency 117 13.6.1
13.6.3 help from the SCO more empty 118
13.7 118 questions within the scope of the usual system
13.8 cron, at the fault diagnosis and solvents 119
13.8.1 cron process is not running 119 Stars
13.8.2 can not change operations at 119 orders failure :
13.9 out of 119 in the process
Chapter 14, with the core system performance parameters 120
System performance monitoring 120 14.1
14.2 core of the system parameters 121
14.3 122 exchange zone management
14.4. Dynamic Core 123
Chapter 15 of the document management system 123
15.1 Filesystem Manager (document management procedures) 124 interface
15.2 File System on 124
15.2.1 124 document types
Niger to increase support for 125 different types of documents
Delete the configuration and installation of 125 additional 15.3
Installation and Configuration File System 126 15.4 Laws
15.4.1 amend HTFS, EAFS, AFS S51K other types of root file system and the installation of 127 distribution
15.4.2 amendments consist of 127 types of root file system configured
15.4.3 authorized users to install 128 File System
15.4.4 installed option File System (HTFS, EAFS, AFS, S51K) 128
15.4.4.1 installing temporary File System 129
15.4.4.2 File System checkpoint 129
15.4.4.3 Log File System Services 129
15.4.4.4 complex and the original purchase documents (that can recover deleted) 130
15.4.5 installed option File System (consist) 130
15.4.5.1 131 Data Compression
15.4.5.2 mandatory writes data on the disk 131
15.4.6 installed option File System (DOS) 132
15.5 File System installation and unloaded 132
15.5.1 installed on the DOS File System 132
15.5.1.1 DOS file system and permission to visit 133
15.5.1.2 133 DOS file system restrictions
15.6 create documents on diskette 134
15.7 134 File System inspection and repair complex
135 option puts inspection and repair complex
15.7.2 File System inspection phase (HTFS, EAFS, AFS, S51K) 136
15.7.3 File System inspection phase (consist) 137
15.7.4 UNIX file system and how to preserve documents 137
15.8 safeguard the free space 138 File System
15.8.1 shows the list of documents and the use of statistics 139
140 15.8.2 position paper
15.8.3 find temporary documents 141
15.8.3.1 find on the implementation of export orders 141
15.8.3.2 inspection and removal system log files 142
15.8.3.3 using the system log management procedures 142
15.8.3.4 command line clearing system log files 143
15.8.3.5 remove log files 143
15.8.4 increased disk space and 143 File System Reconstruction
144 15.9 maintaining the validity of documents
15.9.1 reduce debris disk 144
15.9.2 144 surveillance and restrictions on the size of Contents
15.9.3 delete air shafts 145 list
Chapter 16 user account management 146
16.1 Account Manager (account management procedures) 146 interface
16.1.1 147 on the choice of the default values
Increase and modify user accounts 147 16.2
16.2.1 use of account templates 147
16.2.2 or delete user accounts idle 148
16.2.3 149 user accounts in the use of idle
16.2.4 set up and modify user and group ID (UID/GID) 149
16.2.5 to change the document is null and void main UID/GID 150
Section 16.2.6 150 registered users change
151 16.2.7 change user group members
16.2.8 change shl1 151 registered users
16.2.9 151 registered shell
16.2.10 limited she11 152
16.2.11 change in the initial list of 152 users
16.2.12 152 types of users change
16.2.13 users to change the priority level 153
16.2.14 registered an increase of 153 shells and environmental documents
Management User Group 154 16.3
16.3.1 User Group 154
16.3.2 add to or amend Section 154
16.3.3 delete User Group 155
16.3.4 page document was created in the Group ID 155
16.3.5 users to change the restriction on the number of members eligible 155
Password management 155 16.4
16.4.1 installed or change user password 156
16.4.2 156 expired password control
Password control options 16.4.3 157
16.4.3.1 not allow account access code 157
16.4.3.2 prohibit users change the password 157
16.4.3.3 allows users to password generated 158
16.4.3.4 restrictions obvious password 158
User-defined password checks 16.4.3.5 159
16.4.3.6 160 installed password length
16.4.4 installed 160 dial-up password
Installed 161 registered 16.5 restrictions
16.5.1 setting restrictions on the registration of 161
Restrictions on the registration of 161 terminals installed 16.5.2
16.5.3 lock unlocking user accounts or 162
16.5.4 or unlocking locked terminal 162
Limit distribution 16.6 163 users
16.1.1 163 power distribution subsystems
16.6.1.1 basic competence 163
16.6.4 allow ordinary users to implement orders 164 super users
16.6.5 using su (C) visit other accounts 164
16.6.5.1 record su (C) 165 usage
165 16.7 complicated system user accounts
16.7.1 user account complex system of non-SCO UNIX System 166
16.7.2 complex systems from SCO UNIX or SCO XENIX System 166 user accounts
16.7.2.1 166 different UNIX system password compatibility
Fault Diagnosis 167 16.8 Account Management
Responsibilities user or group of illegal attribute set 167
Remote management of the 167 16.8.2
16.8.3 lost or damaged database file 167
Chapter 17 agreement TCP 168
Introduction to TCP 168 17.1
17.2 169 IP addresses
17.3 start / TCP 171 closed
171 17.4 standard network configuration file
17.5 posted distant mainframe 172
Host equivalence 172 17.6
Equivalent 17.7 173 users
17.8 distant mainframe document duplication 173
17.9 routers (Router) 174
Domain Name System and the provision of section 174 of chapter 18
Table 18.1 IP addresses and NIS 175
176 18.2 DNS system summary
18.2.1 176 hierarchical structure of DNS
18.2.2 The action principle DNS 177
18.2.3 DNS service classifier 177
18.2.4 domain name service data files 178
For 18.2.5 configuration : 180
182 NFS Network File Chapter 19
NFS concept 19.1 182
NFS Network File Allocation 182 19.2
Chapter 20 PPP 184
Appendix A to use SCO Shell 191
Shell launched SCO 191 1.1
1.2 document management using 191 SCO Shell
Appendix B UNIX directories and special equipment to document 192
1. KAN 192 list
Contents 192 2./dev
3./etc/conf 193 main-menu system configuration
Appendix C:SCO UNIX 2000 193
1.SCO issues outlined in the UNIX 2000 193
2. SCO UNIX solutions to the problems of 193 in 2000
1). 194 adopts the solution
2). 194 SCO OpenServer 3.0 solution
3). OpenServer upgrade to version 5.04 or 5.05 195
3. 195 issues need attention
Preamble
UNIX systems since 1969 has been nearly 30 years since the world into the computer. Although the market faces some operations
System (Windows NT) strong competition, but it will still be a notebook computer, PC, PC servers, SMEs
, Workstation, and large Supercomputer clusters and SMP, and the entire series on the overall MPP operating system, a system which can, at least so far, has not undertake this important task. But its form the basis of the open system standards (POSIX) so far
The only operating system standard, or even its competitors still remaining dedicated hardware systems (some of the company's large and medium-sized aircraft or special hardware), the operating system, follow the POSIX interface is the standard UNIX or other categories. In this sense, the UNIX operating system is not just a special name, and became a synonym for the current open system. Do you not see many companies "open system" UNIX in the world instead of the banner and pop open a trend, voluntarily or not to hold? UNIX denied on this point. In the early 1980s, he said the following : UNIX computer world in the name may disappear, but its spirit will last forever, and today they still do.
UNIX is a turning point in 1972 to 1974, with C language for Unix, portability as a main
To the design objectives. After opening Software Foundation, founded in 1988, Unix has gone through a brilliant course. Thousands of application software development and implementation of the Unix system for virtually every application. Unix became the world's most widely used operating system overall. Unix has greatly promoted the development of computer systems and software technology, in a sense, the development of Unix to promote the progress of the whole society also play an important role.
Advances in technology and products is becoming richer and fierce competition in the market today, we hope that each and every one of the fastest and
Abreast of the latest technologies and effectively applied to the actual work. And the multitude of scientific and technological knowledge, has always chosen according to need
Optional learn UNIX system should do so as well.
In addition to specific clusters, the large SMP and MPP system, the rest of the hardware platform used by UNIX
Current system is divided into two parts. UNIX is part of the basic system hardware manufacturers and related standards under development and distribution
Preparation of different platforms in the system, representatives of IBM AIX, HP UH, the RAS NCR, the Soralis SUN
; Another part of the system is to provide professional software manufacturers, and representatives of SCO UNIX. SCO UNIX is currently in InteI
Chip hardware platforms running UNIX most widespread. AT8LT UNIX System V in 1989 launched
Release 4 (SVR4), after the AT & T UNIX System and put a trademark to sell Novell, Novell opened this basis
Made a UnixWare. After again Novell sold SCO UnixWare, SCO XENIX as the foundation of its previous UNIX版本 in 1997 and the development of a new UNIX System V Release 5 (SVR5).
Integrated the former OpenServer and UnixWare, SCO OpenServer introduced a 5.0 version. So
OpenServer5.0 is now the most popular is the latest in the market value of the system. Because of Intel chips
CPU PC, PC servers, notebook computer and other extremely popular in the market, to learn these computer Carrier
SCO UNIX System OpenServer5.0 master knowledge becomes the most convenient way.
UNIX is currently the world generally use a far-reaching impact on the mainstream operating system. In the UNIX world, SCO
UNIX has its roots in Intel平台, closer to the public and features renowned the world over. This is the latest products
SCO OpenServer the series, which is in the face of this series of books you want to introduce to you the contents. International
Data Group (opened) statistics, in 1996, SCO UNIX in the global market share of 35% of the UNIX market. 1997
, SCO UNIX market share increased to 40%. This is the most SCO OpenServer products.
UNIX from birth to now have nearly 30 years of history. In the course of these 30 years, it had UNIX
The pit, and it, too, it's brilliant. In the 20th century draws to a close, once again facing the UNIX market test. Competition from other operating system products, a lot of people have doubts and misunderstanding, and we spent months bristles at the word as "erroneous
District. " When you start reading these books, I think it is necessary to clarify these misconceptions, in order to avoid the learning process should also consider why you should learn UNIX.
Misunderstanding : one of the core UNIX system is only applicable to large and medium-sized
Although the clustering, SMP, or MPP is the only area of the UNIX operating system is a basic, but also is the only UNIX operating in a notebook computer, PC, PC server, the server and the operating system were made. Opened can be seen from the above statistics, 40% of the UNIX system is SCO UNIX, SCO UNIX is the only operating in InteI platform. With the other types of UNIX, it can be said that most of the world's PC UNIX system is in operation. Today, the SCO UNIX also have the ability to support clusters and SMP.
UNIX core can support multi-user systems, while also supporting distributed network system. The network will support UNIX
Enough is the key to long-term development. The phrase "the network is the computer" behind the famous words, UNIX denied. With UNIX, and have TCP before the Internet. Understand the UNIX, you will be able to more deeply understand their essence.
Misunderstanding No. 2 : UNIX has nothing to do with our daily lives
Although UNIX is not like Windows will see in each office. But your life is inseparable from UNIX
The. As far as China is concerned, most of the key business operations in the UNIX platform. This includes banks, security
Insurance, taxation, postal services and telecommunications, railways, customs, meteorological and government organizations. All of this in your side. I believe that many people who have had personal experiences to understand SCO UNIX. Most of the key sectors of high technology application and management staff knew how to UNIX or UNIX experts. If you want to become a qualified Information Manager (CIO), you may be required to UNIX programs.
Misunderstanding number three : Since spring snow UNIX is difficult to learn without the use of the Jordan school
UNIX high technological content, the experts said that the majority of today's computer software technology from the technology
UNIX find their sources and shadows. It is for this reason, that has such a high performance UNIX, reliability, stability
, Security, interoperability, availability, scalability and so on. It is for this reason that the UNIX to learn more than other things. Meanwhile, we should also recognize, due to historical reasons. UNIX enough friendly user interface. However, this situation has now greatly improved. Later, you can see that the SCO has become a very friendly interface OpenServer; system.
Learn UNIX, you will feel leaving a new realm, which is not satisfied with this level of software technology shallow taste
Instead, a smattering of people can be achieved.
UNIX has not been met without the use of a great deal of study. Are encountered on UNIX laments, "only when used to hate books
Less. " Not even see the shelving used to buy a UNIX system, although such a situation for many other products and
See. If you are a software engineer recruitment advertisement carefully, you will find the number is not necessary to understand UNIX?
No 4 : UNIX development Mistakes
UNIX Ever since its birth, has never stopped since the development. We can only understand in recent years.
One in 1995, the new standard UNIX 'birth 95
One in 1996, the two groups X/Open UNIX and OSF merged into "open group"
One in 1997, the new core UNIX SVR5 (UNIX system; . Version; ) In the completion of SCO
One in 1998, based on the comprehensive SCR5 version of the OpenServer and UnixWare from UnixWare7
SCO launched, and plans to introduce OpenServer 5.0.5 version
These new standards in product development and integration of new technologies, have enabled them to provide their customers with more powerful function and performance to customers more friendly, more closely integrated with the Internet. That is why UNIX is still much beloved by Intel, the vast majority of software and hardware manufacturers including IBM, HP, Compaq, SUN, NCR as a standard operating system platforms and other reasons.
5 : Errors in other UNIX operating system will be replaced
If we are talking about a product or a technology will be replaced by other products or technologies, or simply
It will vanish, then I think there must be two prerequisites : one is the technology or products can not meet market demand
To, belong to be eliminated; Second, there is a better than and more advanced technologies or products developed. However, a careful study
UNIX, no prerequisite for the existence of these two. In addition, the technology so far is not UNIX
Can be compared to any one operating system, but the large number of applications based on UNIX, is incalculable Choi
Fu. UNIX will be a considerable length of time and other operating systems coexist, but two years ago to talk about the demise of Unix will be "
Introduction home "in the face of the current development of UNIX have kept silent, now predicted UXIX soon will be replaced by a shock!
The same words in the face of history, the jokes become leisure.
SCO OpenServer systems outlined in the first chapter 1
Rather, company profiles
SCO is referred to the Santa Cruz Operation. Rather, the company is the world's leading PC computer based on Intel processors and the Unix System Windows/Unix integrated product suppliers. The company was founded in 1979 and in 1993 became publicly listed companies. IDC statistics show that 40% of SCO UNIX share of the global market
SCO has adopted a series of important measures :
1979 to 1981, was jointly developed by Microsoft and SCO XENIX (a subset of UNIX), intended to be used
Intel-based PC operating system.
SCO acquired in 1987 by Microsoft adopts copyright.
IXI acquisition in 1993, and Windows Friendly program
VisionWare acquired in 1994 and developed a series of integrated products client.
Novell acquired the business in 1995 UnixWare
1995 authorization to purchase UNIX source code, and announced a series of development plans.
SCO OpenServer Release 5 of the 1995 launch
1996 SCO Unix and HP jointly issued a new plan
Launched in July 1997 SCO OpenServer Release 5.0.4
1998 introduced a 64-bit SCO's Unix operating system unixware 7
SCO is an innovative company, it is :
Intel put a transplanted to UNIX servers;
The first independent software vendors and users to provide real binary-compatible products;
Windows Friendly's first multi-client strategy and provide integrated tools;
Multi-processor Unix operating system to provide first;
The first well-known by many hardware manufacturers certification standards for enterprise-class server systems.
SCO UNIX
Unix is a multi-user computer system only. Multi-process. Multi-task operating system. SCO Unix is SCO Set
System of the heart, it has 32-bit processing capability, based on the 386. 486 and Pentium processors running on the computer. Unix machines can be easily with other servers. Minicomputer or Mainframe link constitute efficient network environment.
Rather, the company quickly issued based on the Intel 386. Intel's Unix System 486 product. From its version of its Unix
3.2.0, Unix 3.2.2.0, 3.2.2.2 Unix, Unix 3.2.4.0, 3.2.4.2 until the latest Unix Unix, SCO OpenServer product line is a software products and license additional products and the composition of the family. These software products are designed to permit additional products can meet and work together.
1.1 System Configuration
SCO provides a set of software products, software and additional media published documents, users can be grouped according to need.
SCO OpenServer 1.1.1 System
SCO OpenServer series includes three operating system and a set of system development. Detailed information can be read on the latter
SCO System 0penServer Developolent of files.
Host System (Host System)
The only product to a central mainframe applications without the need for networking low cost, high reliability solutions and key
Application design tasks. In addition to providing many of the characteristics can improve performance and reliability, the product also provides End
The entire graphics support, including 0SF/Motif and system management tools based on the characters that SCOadmin. Host System
SCO also includes senior documents and print server (SCO Advanced File and Print Sever), the software directly
Windows documents and then print documents stored the result list NetBEUI network.
Enterprise System (Enterprise System)
The product includes all the functions of the mainframe system and the integrity of web-based tools, including the installation of the network, TCP (with
TCP operation in the SCO senior documents and print server), NIS, IPX/SPX, sco Gateway for
Netware, LAN Manager CIient, Netscape Navigator Gold and Netscape FastTrack server.
This shows that the product series is the most powerful and comprehensive server.
Desktop system (Desktop System)
The products are designed for single-user workstations, which provides full network connectivity and integrated graphics support. Desktop system
Including Netscape Navigator
1.1.2 Media
All depositors SCO OpenServer products available to users on a CD-ROM disk. In addition, customers may also need to provide 150MB 3.5-inch floppy disk or tape software packages.
1.1.3 Documents
"<Release Notes>;>; ;>; and" <SCO OpenServer System Handbook, "published by the system software and file formats, together with the provision of SCO OpenServer, Meanwhile "<SCO OpenServer manuals)) and some other form of manual also provide online manuals, online manuals published by the majority of vendors can be manual is divided into two parts, the part of all users and administrators, including guidance and the other including all the reference manual (hard Volume).
Additional permits and 120 products
These additional permits and the purchase of products together with the SCO OPenServer system :
SC0 Open Server User Licenses (10,25,100,500 subscribers or an unlimited number) (permit only)
Lisense SCO SMP (symmetric multi-processing) (permit only)
SCO VirtuaI Disk Mamager (only permits)
SC0 Merge (Permits and files)
SCO OpenServer Development System (Permits and files)
SCO Advanced file and Print Server (license, and media files)
SCO ARCserver/Open from Cheyeme (licensing, documentation and media)
SCO Doctor (license, and media files)
SCO Visionfs (license, and media files)
Netscape Proxy Server (license, and media files)
NetscaPe Enterprise Server (license, and media files)
SCO to Netware Internet Gateway (license, and media files)
SCO XVision (license, and media files)
Apart from the last two, the rest are kept in the medium with SCO OpenServer systems, can only buy permits to install and use :
1.2.1 license and registration terms
Now three in the "permission and authorization certificate" is a user of the item on the "license" and always tie together :
Permit No. : No. The only marking each SCO products.
: Product activation code permits the code permits.
Permit data :
Additional permits required for the activation of certain product information. Each field is not in the "permission and authorization certificate) have, but each permit is not needed.
End of software installation and after permission should be registered. See the SCO OpenServer systems together with the "<SCO software Registration>;>; booklet.
SCO registered a product, users must provide :
Rather, the ID system
SCO OpenServer installed for the sole ID markings, the SCO OpenServer installed when students in each grade
%. Therefore, if the re-installation of a new generation of SCO OpenServer systems SCO System ID.
License Manager, SCO operating system in the ID shown.
Keyword registration
From the user-key registration centers to register their products from SCO registration centers. For every user registration
Products (from licensing its logo) will receive a registration key-users. Will display a warning message system to prompt the user
Re-install the system should be re-registered SCO SCO OpenServer products.
SCO visit online information services 1.3
If your machine and Internet connection and a browser (such as Netscapepe Navigator), the following URL
(Uniform resource locator), the home page will take you to SCO :
Http://www. Sco. Www.centamap.com/
Shoot "Supportt" SCO support services can visit detailed information.
Chapter 2 of the installation and system upgrade
Chapter describes how to install and upgrade computer SCO OpenServer systems, and specifically include the following chapter
:
Gathering the information necessary to install the system
Software installation
The upgrading of choice
Installation in the past, we should pay attention to :
Reading "Release Notes and the No. 1 chapter, which describes the different versions of SCO OpenServer systems hardware
And disk space requirements, should read "Release Notes and of other chapters devoted to hardware and software.
Collection of "installation list" of the information needed.
Rather, the software includes a series of "SCO Hardwre ComPatibilily Hanldbook> compatible hardware or SCO website
(Http://Scaffold.sco.com/chwp/owa/hch_search_form), the hardware driver. If you use
Rather, but not by the driver and equipment provided by other businesses, and your suppliers and confirming these Flooding
The latest action procedures and whether SCO OpenServer software compatibility. If the driver is not compatible operating system and related
External equipment will not work.
If you are a first time installation or can not identify the hardware requirements, please read the attached hard disk and computer manuals.
In addition, the operation of computer hardware designated operator guidance system of self procedure can detect hardware problems.
Read license agreements.
If you move from 1.1 to 1.0 or SCO IntemetFastStart SCO OpenServer, please refer to the "SCO
The OpenServer lntemet Services> "version of Notes and migration," a chapter, which will help to preserve your handbook.
Ppp and server configuration, not all of the reconfiguration.
2.1 installation and upgrading checklist
Users with the information needed to answer the questions the installation process. If at the beginning of installation, you did not record
Some information may be forced to suspend the installation and start anew.
After installation, and please send a copy of the list "system log" together.
(L) the need to guide people Driver BTLD installed? I see no need
Document Set BTLD software vendors. I need key people who package :
___________________
___________________
___________________
(2) the installation CD-ROM media mouth ATAPI/EIDE
If the use is the main driver, who is self procedure may fill IDE controller
Correct driver. At the "first or second SCO Hardware Compatibility :
Handbook> or SCO website compatible hardware equipment were identified. Properties or secondary disk
I SCSI CD-ROM
SCSI adapter types :
Main SCSI adapter :
SCSI ID :
SCSI LUN:0
(SCO provided for by the driver always 0)
SCSI BUS :
(3) the keyboard language _______________
(For example : UK English-- British English)
(4) Permit No. _______________
The answer from the 4th, 5th and 6th and permits authorized book reproduces.
(5) permit code _______________
(6) permit data (the upgrade version appeared only in certain fields. ) _______________
(7) Fresh installation type I
Upgrade options will keep your existing file system, but I can not provide Upgrade (if appropriate systems)
Fresh安装中所有的新功能(有些系统不能升级)
(8)系统名 _______________
系统名必须是唯一的，以字母开始，并且只能使用
小写字母和数字(最多不能超过8个字符)。
(9)域名 ________________
(10)安全级别
Hight用于有内部信息和大量用户的系统， 口 High (高级) C2以上
Improved用于有共享信息的用户的系统， 口Improved (增强) C2
Traditional用于维护与配有系统的 UNIX系统， 口Traditional (传统)
Low用于不是大范围的或公共的访问系统。 口 Low（低级）
( l l)时区 大陆或地区：
________________
时区名：
________________
是否采用夏时制？
口 是
口 否
(12)语言 ________________
如果你所运行的是非美国英语产品(如法语或德语)
(13)初始化系统文件 口Shandard System(标准系统)
Standard Enterprise(标准企业版)安装除
Microsoft LAN Manager CIient、SCO Gateway和 口Lightweight Character terminal
PC-Interface Server外的所有软件。 Lightweight (简易字符终端)
Character terminal (简易字符终端)不安装 Xl l服 口Database service (数据库服
务器和前端、图形管理工具和IPX／SPX运行系统 务)(加到标准系统或简易
程序。Database service(数据库服务) 则要加上为 字符终端系统)
大型数据库产品配的suds驱动程序。
(14)硬盘设置，第一硬盘 口 Preserve (保持)
Preserve维持当前的硬盘分区(有些系统不能保 口Use Whole disk for UNIX
存)。Use Whole disk for UNIX 配置为默认的硬 （整个硬盘只装UNIX）
盘分区；Customize则让用户自己创建和分配分 口Customize layout
区 Interactive 调用fdisk(ADM)与divvy(ADM)来 (自定义布局)
更精确地配置硬盘；customize or Interactive 口 Interactive fdisk/divvy
layout (对文件系统类型的描述请参见《Release (交互式fdisk/divvy)
Notes》)。
UNIX分区大小(MB) ______________
DOS分区大小(MB) ______________
其它分区大小(MB) ______________
引导文件系统大小(MB) ______________
交换区大小(MB) ______________
(建议采用RAM的1．5倍到2倍的大小)
根文件系统大小(MB) ______________
(新的文件系统类型不再要求小的根文件系统)
其它文件系统大小(MB) ______________
(15)坏道／坏块，第一硬盘
Thorough/destructive(彻底的／破坏性的)确保最
高的硬盘完整性，但需要较长的时间。不彻底的
选项会因磁盘上的坏道而增加安装失败的危险。
(16)硬盘设置，第二硬盘(如果有)
Customize layout (自定义布局)
UNIX分区大小(MB) ______________
DOS分区大小(MB) ______________
其它分区大小(MB) ______________
引导文件系统大小(MB) ______________
交换区大小(MB) ______________
根文件系统大小(MB) ______________
其它文件系统大小(MB) ______________
(18) 软件的组成部分 口 操作系统
你可以安装全部或任意组合的部分软件包(对于 口 图形环境
硬盘空间的要求，详见＜Release Notes＞)。初始 口 连接
安装完毕后，还可以增加或删除软件包。 口 联机文档
(19) 网络卡
如果系统能自动检测网卡或你打算暂缓配置网 厂商和型号：
络，那么就不需要这些信息(如果要使用的网络 ____________
卡地址没有出现在有效地址的表中，在系统安装 中断向量 IRQ：
完毕之前，暂缓网络的配置)，更详尽的信息请参 _____________
见硬件文档。 I／O基地址(如果适用)：
_____________
ROM地址(如果适用)：
_____________
DMA(如果适用)：
_____________
RAM基地址(如果适用)：
_____________
RAM大小(如果适用)：
_____________
本地环广播(只用于令牌环网)：
_____________
插槽号(如果适用)：
_____________
电缆类型(如果适用)：
_____________
（20）IP地址 _____________
四个由句点分开的十进制数(例如：168．160．80．9)。
如果你还没有 IP地址，请暂缓网络配置。
(21) 网络掩码 _____________
如果不准备配置子网，请接受默认值。
(22)广播地址 _____________
(23)显示卡 _____________
详见《SCO Handware Compatibility handbook》或 SCO
兼容硬件网页。
(24)显示模式 _____________
(25)显示器 _____________
(26)图形界面注册 口开
如果你打算使用图形环境，保留图形注册界面。 口关
(27)鼠标 口类型(厂商)：
请查阅你的硬件文档。 ____________
对总线鼠标，要设定中断向量。对串行鼠标，只 口总线鼠标
能使用 COMl端口。若串行鼠标已连接在 COM2 ·IRQ2 (INTR2)
上，也应设成 COM1，在安装后，重新装配鼠标。 ·IRQ2 (INTR2)
·IRQ2 (INTR2)
口串行鼠标：com1
(不支持 COM2)
口键盘鼠标
·低分辨率
·高分辨率
2.3安装和升级的过程
按下面的步骤，记住回答每个提问后要按＜Enter＞键：
(1)请认真填写“安装和升级检查清单”。
这一点非常重要。如果事先没有收集好这些信息，就有可能被迫中止安装并再次从头
开始。
(2)如果硬盘有多个分区，确保 UNIX分区是活动的，安装程序将把 SCO OpenServer 系统复制到活动分区中。
(3)在任何安装和升级前，确信你已备份了系统中的当前数据，在安装中有的选项覆盖掉硬盘上的所有数据，包括用户数据和 DOS分区。
(4)在关掉电源或在“Press any key to reboot”的提示符下，将引导盘插入驱动器。
如果有多个软盘驱动器，使用主驱动器(也叫引导驱动器)。如果不能确定哪个是主软
盘驱动器，请查阅计算机硬件手册。
(5)打开电源(或在haltsys下按任意键)，等待出现 Boot：提示符。
注意：在任何时候，若想要重新安装，插入引导盘，在Boot:下按<Enter>;,系统将再次从头开始安装。如果要使用BTLD 实用程序，并需要重新安装，插入引导盘，在Boot:提示符下键入restartlink =pkg1 (其中pkg1 是软件包的名字，所需要的BTLD 驱动程序就是从该包中抽取出来)
(6)在 Boot：提示符下：
·如果你不打算安装引导时可装如入的驱动程序，那么按＜Enter＞从软盘开始引导。
·如果你要引导时安装BTLD，在Boot ：提示符下键入link 并按<Enter>; 或 使用link= 引导串实参。如果是直接调用link ,会提示输入要装入的软件包的名字：
what packages do you need linked into the system
or q to quit?: pkg1 pkg2
系统开始检查当前配置有哪些硬件，硬件是否有问题，每一步检测显示一个从 D到 M
之间的字母。每个字母的含义参见附录 G‘核心初始化检测字母”中的解释。
在这些核心初始化字母后将出现受限的权限说明。
(7)当出现提问时，提供你的 CD-ROM驱动器的有关信息，插入 CD-ROM，按＜Enter＞键。
(8)根据每一屏显示的操作，按照事先记录在 “安装和升级检查清单’’中的信息，填写信息字段。在屏幕底下的两行给出填写每个字段的简明操作。若想要得到更详细的求
助。请按＜ FI＞。按＜ Space＞将列出可以选择的选项或显示第二组提示。
注意：如果安装类型字段自动填入了Fresh, 而又不能将亮条移动到该区域，那么就说明系统不能进行升级。完成并确保具备所有必需的信息，然后继续进行fresh 安装。
(9)当出现提示时，设置 root(超级用户或系统管理员)口令。
不要忘记 root用户口令。要恢复一个忘记的root用户口令，必须向技术支持人员求助：
(10)如果你选择Interactive fdisk／divvy磁盘设置选项，安装程序提示你初始化硬盘。
提醒： 不要将所有的可用空间分配给可选的／u文件系统，这样就没有给根文件统留下足够的空间。而一旦根文件系统没有足够的空间，安装就会失败。
若在此处遇到错误，重启系统，从头开始重新安装。不要企图通过安装屏幕回翻。
(11)如果选择该选项，则接着运行 badtrk ( ADM)实用程序。若在 badtrk命令执行过程中遇
到错误，则需要重新引导系统并重新进行安装。
(12)在磁盘设置和检查坏道完成后，就开始装载软件。这是安装过程中最费时的阶段。但
能无须干预地装入。
在把选中的软件安装到硬盘的过程中。会看到如下的信息：
Installing： SCO UNIX System V Operating system ( Ver5．0．4Bg)
Installing Phase： Copying files from the media
Installation Status： Copying file
这些消息记录在 custon的日志文件／var／opt／K／SCO／SoftMgr／*／custom．log，以备
以后查阅。
软件装载完毕后，将要重新构造系统核心(／stand／unix)，这一步需要几分钟。安装程序还将在／stand另建两个可引导的核心，以便在 uinx不能引导的情况下使用。 Unix.safe和 unix一样，但删除了所有第三方的驱动程序；而 unix．install是安装过程中使用的核心，它包含了大部分驱动程序.
(13)如果在引导时链接了 BTID，那么会看见己安装到硬盘上的软件包的列表。键如入要安
装的BTLD软件包名，或按＜ Enter＞键安装默认软件包。
(14)系统关闭时，会看到： Press any key to reboot。从驱动器中取出软盘，然后接任意键。
(15)在出现 Boot：提示符时，接＜ Enter＞ 。
(16)如想进行下列操作，在见到 INIT： SINGLE USER MODE：时，键人 root口令，进入
系统维护方式(即单用户方式)：
．设置一个串行鼠标
．安装附加软件或删除软件
．配置网络
如果你有一个不是安装在 COMl上的串行鼠标，应该现在配置它，
若想安装或删除软件。
如果在初始安装中已安装了联网组件并暂缓网络的配置，现在也可以进行网络配置。
(17)要进入多用户方式，可在 INIT： SINGLE USER MODE提示下按＜ Ctrl＞ D(或者，在
单用户方式的 # 提示符下，按＜ Ctrl＞ D，会看见 INIT： SINGLE USER NODE，
再按＜Ctrl＞ D 键.
(18)若显示的时间是正确的，按＜Enter＞键。若时间不正确，键人当前时间。
在系统的启动过程中，会看到版权信息，之后是各软件组件的启动信息。当在 tty02 看
到scologin图形屏幕，或在 tty01看到 login：提示时，系统准备就绪了。
(19)要启动桌面系统，在tty02的图形界面scologin屏幕上以 root注册(如果当前屏幕不是
图形界面，按＜ Ctrl＞＜ AIt＞＜ F2＞)。
要从字符界面上注册，＜ CbI＞＜ AIt＞＜ Fn＞可以从当前图形界面切换到字符界面
(这里， n是与另一个tty相关联的功能键，如＜ Fl＞)。然后以 root注册
(20)这时，你能：
·增加用户账号。安装过程自动建立root账号，这个账号应该只用于完成系统维护
任务。为维护系统的安全，必须为每个用户建立单独的账号( Upgrade(升级)安装
将保持所有账号和数据)。
·增加本地打印机(直接和系统相连的打印机)。
·安装基于 DOS的应用程序。
·在系统中增加硬盘。
·配置邮件系统。
·在硬盘上建立另外的分区(如果事先留有空间)。
·在硬盘上创建附加的文件系统(若事先留有空间)。
(21)为系统做一个完整的备份，
如果系统受到损坏，那么可以使用该备份和下一步创建的应急引导盘组来恢复它，而
无需重新彻底的安装。
提醒：为文件系统定期做备份，这样，一旦系统毁坏，可用最近的备份恢复系统。
(22)为系统创建应急引导软盘组。
如果系统严重损坏不能从硬盘引导时，这些软盘可帮你很快地恢复根文件系统。创建
应急引导软盘的操作请参见第5章“创建应急引导软盘组”。然后测试这些应急软盘．
(23)登记你的软件。
在安装了系统后，建立用户账号，安装附加的硬件或软件，并运行所有必要的配置，做一个系统的完整备份。
2.6选择升级途径
在开始系统升级前，详细阅读本节和随后的关于系统升级的章节，它们描述：
·如果你正在运行 SCO 操作系统,你所能选择的不同的安装类型
·为使原系统中的某些软件在系统升级后能继续工作，在安装前和安装后所必须采取
的步骤。
警告： 在开始任何安装和升级以前，确信当前系统所有数据都有最新的备份。在安装过 程中，有些选项将覆盖硬盘上所有的数据，包用户数据和DOS 分区 建议使用cpio (C) 格式来备份系统，并每个磁带只备份一个文件系统。
如果现在运行的是较早版本的 SCO UNIX 操作系统，下面一种或多种方法可使之升级
到 SCO OpenServer5．0．5版。阅读相关章节和(Release Notes＞后决定适合你的系统的最佳方法，
．选择 Upgrade安装 ，
．选择 Fresh安装，设置硬盘时选择 Preserve选项
．选择 Fresh安装，然后运行 lnteractive fdisk／divvy 来重建当前硬盘的设置
．选择 Fresh安装，选 Use while disk for UNIX或Customize选项来设置硬盘，然后
从备份中恢复数据。
2.6.1关于升级安装的类型
如果原先安装的是 SCO OpenServer 5.0或5.02 ,5.04；并且硬盘有足够的空间来安装
SCO OpenServer5．0．5系统(参见＜Release Notes＞对硬盘空间的要求和有关Upgrade选项的其它信息)，那么就可使用 Upgrade选项。这个选项将保持所有的非根文件系统和分区的原来面貌，但要清除掉旧的根文件系统，并安装所有旧软件包的新版本。 Upgrade选项在安装开始不久就出现在 Installatin type的安装提示符下。
如果升级失败，安装程序将试图恢复原系统。依照升级失效的阶段，程序将显示该系
统预期状态的消息并指导你检测是否需要从备份上恢复系统：
下面是 Upgrade安装的可选途径：
要升级的旧版本号： 能升级到的新版本：
SCO OpenServer5.0.0 Host/ Desktop/ Enterprise SCO OpenServer 5.0.5 Host/ Desktop/ Enterprise
SCO OpenServer5.0.2 Host/ Desktop/ Enterprise SCO OpenServer 5.0.5 Host/ Desktop/ Enterprise
SCO OpenServer5.0.4 Host/ Desktop/ Enterprise SCO OpenServer 5.0.5 Host/ Desktop/ Enterprise
注意： Upgrade的安装类型并不是必须与所购买的 SCO OpenServer系统升级版相联系。这里只是简单描述了一种安装软件可以遵循的途径，它还取决于升级前的系统配置。例如，如果当前运行的是 SCO OpenServer Release5.0.0系统，即使你购买的是标准安装版，也可以选择 Upgrade安装类型。相反，如果你购买的是 SCO Open DesktopRelease3．0的升级版，那么就必须选择 Fresh安装类型，然后在 Hard disk setup设置的选项下，选择最合适的升级方法——可能是 Preserve.
由于 SCO OpenServer Release5.0.5系统的默认配置要比 SCO OpenServer Release5.0.0或5.0.2大得多，原先主硬盘上的根文件系统也许不够大，不能容纳升级系统。请查看＜Release
Notes＞中对空间的要求。如果选择 Upgrade选项，而根文件系统又不能容纳新版本，有三种方法解决：
·通过重新配置硬盘增加根文件系统的空间；
·安装一个更大的主硬盘；
·将新系统的组件安装到非根文件系统中。如果硬盘总空间足够大，并且具备可用的
分区，安装过程会提示把组件放置到其它文件系统(包括在非主硬盘中的文件系统)。
同样，也不要寄希望于在重新定位的文件系统上放置额外的数据(如用户账号)。重新
定位程序将使用所选的文件系统上几乎全部的空间，以便建立一个有空闲空间的根文件系统。
只有在／etc／default／filesys 上的文件系统才可用于放置组件。如果想把组件重新定位到在安装这一步没有显示出来的文件系统，那么就需要中止安装，重新启动原先的系统，运行mkdev fs把文件系统放到／etc／default／filesys上。
升级安装时能保存的数据
在根文件系统中能保存的用户数据包括：
·起始目录
·用户创建的文件和目录
·用户ID
·组 ID
·口令
·文件许可权
·邮箱
在根文件系统中能保存的系统数据包括：
·系统配置文件
·作业调度文件
·文件系统
·文件系统节点
·安装点
·终端控制数据库
·审计参数
·文件控制数据库
·系统默认值
·邮件别名
非根文件系统和非根盘保持不变，除非用它们来接受重定位的组件。
2.6.2关于Preserve硬盘选项
如果系统具有一个活动的、并带有干净的根文件系统购 UNIX分区和一个有效的／etc／default／filesys文件(参见filesys(F))， Preserve选项就有效。这个选项将保持原先安装的文件系统的布局和类型(根文件系统除外)。该选项删除根文件系统中的所有数据，然后安装新的系统，而其它所有数据都不改变。要进人 Preserve选项，先在 Preparing your disk and choosing software窗口的 Hard disk setup项下按＜ Space＞键，在随后出现的 Partitions & filesystems下再按＜ Space＞ 。
如果硬盘设置选项表中并不包括 Preserve，说明安装程序没有找到具有有效根文件系统的活动的 UNIX分区和／etc／default／filesys 文件。为保存当前的分区和文件系统，参见 “关于交互式硬盘设置选项”。
Preserve选项同样适合第二硬盘。参见 “升级非主硬盘”。
2.6.3关于交互式硬盘设置选项
提醒：用 lnteractive fdisk／divvy 选项去保存先前分区与划分，则在新的安装开始前 必须从原系统中搜集硬盘布局信息。
硬盘设置选项中 Interactive fdisk／divvy 对任何 Fresh(而不是 Upgrade)安装类型都有效。 lnterative fdisk／divvy暂缓硬盘设置，直到安装提示结束。然后安装程序交互地运行实用程序fdisk( ADM)和divvy(ADM)。如要在新系统中保存原先的分区，必须在新安装以前．搜集好原系统中硬盘布局的信息(包括原先存在的 DOS分区)。具体步骤如下：
( l)首先，运行fdisk并选择选项 1，记录文件系统的分区数，然后退出fdisk。
(2)接着对每个分区运行 divvy.
提醒：请不要在divvy 中选择c。这样做将会破坏所选的文件系统的内容。只能在确实有该文件系统的完整备份，而希望重新把文件系统划分成不同格式的情况下，选择c,在安装后还必须恢复该文件系统的所有文件。
(3)把屏幕上出现的信息抄录到表2—l中
表2—l 主硬盘文件系统
名字 类型 新的FS # 起始块 终止块
主硬盘文件系统
(4)退出 divvy。
(5)在新安装fdisk和 divvy过程中，键入以上信息，重建原先的硬盘布局。
divvy调用mkdev hd时，在其中再对 SCSI和非 SCSI硬盘都运行badtrk。在mkdev
hd中， badtrk将按默认值显示当前坏道表的大小。必须接受这个默认值，因为改变
badtrk表的大小会破坏分区的内容。
要调用 Interactive fdisk／divvy 选项，在 Preparing your disk and choosing software窗
口的 Hard disk setup下按＜ Space＞键，随后在 Partitions & filesystems下再按
＜ Space＞ .
lnteractive fdisk/divvy选项对第二个硬盘无效。参见 “升级非主硬盘”。
2.6.4关于硬盘设置的其它选项
在 Partitions ＆ filesystems中可用的其它硬盘设置选项(在 Hard disk setup下)有
Use whole disk for UNIX和 Customize。 Use whole disk for UNlX将清除该硬盘现存的
全部分区，建立一个默认的不能更改的 UNIX分区。 customize也将建立一个同样的
认布局的 UNIX分区，但允许用新的分区修改。这两个选项都不能保存原先的数据和硬
盘设置。如果选择了 Use whole disks for UNIX分区或 Customize，必须在安装完毕后从
备份上恢复数据。
Use whole disk for UNIX和 Customize这两个选项对第二硬盘也有效。参见
“升级非主硬盘”。
2.7 各种升级问题
无论从哪种SCO系统升级或安装何种配置的 SCO OpenServer5.0.5系统，都可能遇到的问题。
2.7.1 恢复用户帐号
如果选择的升级途径不能保留系统中的用户账号资料，可以使用 ap(ADM)命令来保存
用户帐号资料。
在开始安装以前，运行命令：
ap –dg>;filename
该命令把口令文件中所有用户的帐号资料，包括组成员信息都复制到文件filename 中，
然后备份该文件。系统安装完毕后，把文件filename 复制到新系统中，运行命令：
ap –ro –f filename
该命令恢复每个用户的帐号资料，并复写现有的相同名字的账号资料，其中包括 root
帐号。
2.7.2用户配置文件和目录
下面是一张通常配置的文件和目录的清单，它们在安装新的 SCO系统后可能会发生改
变，因而需要恢复(Upgrade安装类型试图保存可配置的文件)。这张清单并不能包括所有要保存的文件，也并不是所有列在该清单上的文件都会改变。这张清单的一个简单出发点是用于确定哪些文件有重要的用户特定信息和系统特定信息。
通常配置的文件
／etc／checklist /etc/inittab
／etc／default／* / etc / mscreencap
／etc／conf/init.d／* / etc / passwd
／etc／cshrc / etc / profile
／etc／date ／etc／rc
／etc／dialups ／etc／systemid
／etc／d_passwd ／etc／termcap
／etc／motd ／etc／ttys
／etc／gettydefs ／etc／ttytye
／etc／group ／etc／wtmp
／usr目录下的用户起始目录
／usr／adm / hwconfig
／usr／adm／messages
／usr／adm / pacct
／usr／lib／mail / aliases
／usr／lib／mail /aliases. hash
／usr／lib／maiI／faliases
／usr／lib／mailases
／usr／lib / malirc
／usr／Iib／mkuser／ *
／usr／lib／uucp／ *
／usr／1ib／Xll／app_defaults／*
／usr／lib／XIl／Mosaic／*
／usr／lib／Xll／scologin／Xservers
／usr／Iib／Xl1／system.mwmrc
／usr／lib／XlI／sys.startrc
／usr／man／cat.LOCAL(本地手册页)
／usr／man／man.LOCAL(本地手册页)
／usr／mmdf / mmdftailor
／usr／mmdf / table／*.dom(mmdf配置)
／usr／mndf／table／*. chn(mmdf配置)
／usr／mmdf／table／alias* (mmdf配置)
／usr／spool／cron／clontabs (cron作业)
／usr／spool／lp / admins／interfaces／* (打印机脚本)
／usr／spool／lp / pstatus
／usr／spool／lp / qstatus
／usr／spool／mail／*
／var / opt／httpd／htdocs／ *
／．probfile
2.7.3升级非主硬盘
只要选择Upgrade 安装类型或在配置第二硬盘时选择Preserve选项，就能保护非主硬盘中的任何文件系统。如果这两个选项都无效，或者没有选择其中的一个，在安装过程中选择
Defer硬盘设置选项或在开始安装以前，把附加的硬盘拆掉。
如果为第二硬盘选择了 Preserve选项，必须在安装完毕后对那个磁盘运行divvy。在divvy中，选择 n，命名保存的分区，然后退出。接着按第4步描述，运行mkdev fs
提醒： 请不要在divvy 中选择c。这样做将会破坏所选的文件系统的内容。只能在确实有该文件系统的完整备份，而希望重新把文件系统划分成不同格式的情况下，选择c,在安装后还必须恢复该文件系统的所有文件。
对于任何打算在安装前拆掉、或者打算选择 Defer硬盘设置选项的非主硬盘，按本节下列步骤的次序操作：
( l)在安装前，对每个受影响的硬盘运行fdisk(ADM)。例如，对第二硬盘，键人：
fdisk –f ／dev／rhd10
在fdisk主菜单中键人 1。记下含有 unix文件系统的fdisk分区数，然后退出fdisk。
（2）同样在安装前，对每个受影响的分区运行 divvy(ADM)并记录信息。例如，对第二
硬盘的活动分区，键人：
／etc／divvy／dev／hd1a
把屏幕上出现的信息抄录到表2．2中
表2—2 第二个硬盘文件系统
名字 类型 新的FS # 起始块 终止块
然后，退出divvy.
(3) 在安装了 SCO OpenServer5.0.4系统后，按“增加硬盘’’中的指导使用 mkdev hd
(mkdev hd运行fdisk和 divvy)。在mkdev hd中，确信：
·接受了babdtrk表默认的大小；
·fdisk分区表中的分区数和安装前记录的一样；
·记录在表2—2“第二个硬盘文件系统”中的信息写到了新的 divvy表中。选择 n
并给每个文件系统命名；
·选择 n和每个文件系统的名字(如果这些分区的设备节点不存在， divvy就创建
它们，因此，你必须修改由 divvy生成的名字，以便与原来的相一致)。
(4) 对每个受影响的文件系统，键入：
mkdev fs
选择选项 l增加一个新的文件系统。按照提示，键入从／dev开始的设备全路径名：
例如，要增加一个名为uj的文件系统，键入／dev／u。
按照提示，键入该文件系统安装位置的目录名。例如，一个名为 u的文件系统通常
安装在目录／u上。
设定在系统进入多用户方式时，如何安装该文件系统：
·在系统启动时，自动安装(选择 1)
·只在系统管理员要求时才安装(选择2)
·在系统启动时，显示安装选择(选择3)
当询问是否允许用户安装该文件系统时，出于安全原因一般回答 n(在任何情况
下，用户进行备份必须同时具备 sysadmin和backup的权限。
退出divvy fs。
(5) 如果现在就想安装该文件系统，那么键入下面的命令(在本例中使用／u．)：
mount ／dev／u ／u
2.7.4 升级第三方的驱动程序
如果第三方的驱动程序与 SCO OpenServer Release5.0.4不兼容，那么在安装结束时可能
并未链接核心(／stand／unix)。在这种情况下，请链接核心／stand／unix.safe，这里不包含第三方驱动程序。
若根文件硬盘控制器的驱动程序是第三方的，则unix.safe可能引导不了。此时用 SCO
OpenServer系统引导时可装人的驱动程序( BTLD)引导，然后从核心中删掉旧的驱动程序，并用installpkg( ADM)安装 BTLD，
2.7.5升级 SCO OpenServer开发系统
当升级到 SCO OpenServer Release5．0．4时，我们建议也升级到 SCO OPenServer
Development System Release5．0．4版。 SCO OpenServer系统不支持 SCO开发系统的早期版本，运行早期版本可能会发生不可预期的结果。
当 SCO OpenServer系统升级时开发系统并不能自动升级：完成操作系统的升级后用
Software Manager去安装开发系统的新版本。
若选择运行早期版本的开发系统，则在升级到 SCO OpenServer5．0．4时，必须重新激活它。当调用／bin／cc，／bin／rcc或／usr／bin／CC命令时，激活开发系统的指令会显示出来。
2.8 从5．0版升级
本节覆盖从 SCO OpenServer Release5．0．0或5．0．2升级到 SCO0penServer5.0.4时可能遇到的问题。
参见：
·选择升级途径
·各种升级问题
2.8.1丢失了用户创建的文件
Upgrade安装在建立目录级的符号链接时，可能会丢失一些用户创建的文件和目录。
当一个目录directory_name 被移走，则被更名为此directory_name # (如果目录
directory_name # 已存在，那么将在原来的目录名后加上一个#，以保证所创建的目录名是
唯一的，如directory_name # # ) 。例如，如果目录／usr／files／audit中有在升级前用户创建的文件，那么在升级后就不能在这个目录下找到，请检查是否存在名为／usr／files／audit#
的目录。如果有，那么就可以把其中的文件放回到升级前的／usr／files／audit目录中。
2.8.2第三方产品与系统序列号
在系统升级后第三方产品可能会发现其序列号与以前安装的不一样。
在升级过程中，安装程序试图用旧的序列号来重构核心 。若不能成功，请用以下命令：
brand –n old_serial_numer old_activation_ky /etc/conf/pack.d/kernel/os.a
再重新链接核心，并重新引导系统。
2.8.3从Host或Desktop升级到 Enterprise配置
若你购买了以下升级版，则升级要分两步：
·从 SCO OpcnServer5.0.0 Host系统升级到 SCO OpenServdr5．0．4 Enterprise
·从 SCO OpenServer5.0.0 Desktop系统升级到 SCO OPenServer5．0．4 Enterprise
·从 SCO OpenServer5.0.2 Host系统升级到 SCO OpenServer5．0．4 Enterprise
·从 SCO OpenServer5.0.2 Desktop系统升级到 SCO OpenServer5．0．4 Enterprise
第一步把系统在同样配置下升级到 SCO OpenServer Release5．0．4，第二步再把系统升级到 SCO OpenServer EnterPrise.
第一步当选用 Upgrade安装后自动完成。这一步使用5.0.0或5.0.2的＜许可和授权
证书＞(COIA)信息。
完成第二步时按“安装和管理软件组件”中的指令，调用Software Manager ,安装SCO
OpenServer Enterprise：当出现提问时，按5．0．4提供的＜许可和授权证书＞信息。
当安装完 SCO OpenServer Enterprise后，退出Software Manager并重新引导系统。
升级语言产品
在 SCO OpenServer家族内升级系统（如，从Host 到 Enterprise ）,必须在升级后按通常的方法安装相应的语言产品。
2.9 从3．0版升级
本节内容与“各种升级问题”的内容一起适用于从 SCO Open Desktop Release3．0升级到 SCO OpenServer Release5。
注意： 从3.0 升级必须选择Fresh 安装类型，然后用2.6 节 “选择升级途径”中的方法保存或恢复数据。
2.9.1升级 SCO Merge
当安装 SCO OpenServer Release5．0．4时， SCO OpenServer Release5.0.0或5.0.2下运行 SCO Merge，那么在完成Release 5.0.4 安装后，再用software Manger从Release5.0.4的
CD-R0M上安装SCO Merge 3.2。请使用SCO Merge自己的<许可和授权证书>;上的许可信息。
2.10 从2．0版升级
当从 SCO OpenServer Desktop 2.0升级到 SCO OpenServer Release 5.O.4时，没什么特别需要注意的问题。在开始安装之前，请认真阅读“各种升级问题”和《Release Notes》。“从3.0版升级”和“从5.0版升级”中的内容也可能适用于升级2．0版。
注意： 从2.0 升级请用Fresh 安装类型，然后用“选择升级途径”中的方法保存或恢复数据。
第3章 创建应急引导软盘
当系统发生灾难性的故障时（如无法启动计算机），应急引导软盘组能帮你恢复系统。使用这些软盘可以恢复损坏了root 文件系统，而无需重装系统。
如果有多个系统，应该为每台机器创建一套应急应导软盘，在每套应急软盘上标上机器的名字，并把他们放在计算机附近安全可靠的地方。
下面就是与创建应急应导软盘组相关的任务：
·配置应急软盘
·在根系统软盘上增加文件
·测试应急应导软盘组
·读取备份
·从硬盘应导
3.1 配置应急盘
可以使用两张3．5英寸1．44MB (135道／英寸，每磁道18扇区) 或单张3．5英寸2．88MB(135道／英寸，每磁道36扇区)软盘来建立应急引导软盘组。
( l)用 root注册。
(2)使用 SCOadmin中filesystems目录下的同Floppy Manager ，或键人以下命令：
mkdev fd
(3)在主菜单下，选择2来创建应急引导软盘组。
(4)在紧接着的提问中，选择你所使用的软盘类型;除非使用2．88MB的软盘驱动器，否
则选择2。
(5)如果你有多个软盘驱动器，会提问使用哪个软驱来创建应急盘。0 －代表第一个
软驱， 1－代表第二个软驱。
(6) 当出现选择文件系统类型的菜单时，选择 1 先创建根文件系统盘，如果要创建单
张应导／根系统软盘，选择性3。
(7）回答后，插入一张空盘，按＜Enter＞键。
(8) 当问你是否要格式化软盘时：
· 若该软盘已格式化，则键入n,将立即开始构造文件系统。
· 若该软盘未格式化，则键入y.
(9) 在软盘上建立文件系统之后，将把系统文件复制到RAM 盘上以便压缩，其中包
括将/dev/cmos 复制为／etc/cmos.root。以后可以使用这个文件来恢复CMOS设置.
(10) 当看到如下消息时：
Do you want a shell escape to place extra files on the root filesystem ? (y / n)
如果想在盘上加一些文件，输入y。
注意：应急应导软盘上的空间是有限的，因此只装入关键的实用程序。如果空间允许，附加的实用程序如tar (C) 也可以复制上去。
(11)使用fsck(ADM)检查文件系统，显示的消息与引导时的检查文件系统的消息相似。
当软盘已准备好时，你会得到提示。从驱动器上移开软盘，标上“root”字样和该
台计算机的名字，贴上写保护标签，以免偶然的失误删除了软盘上的信息。
(12) 按＜Enter＞镊继续，返回选择文件系统类型菜单。键人2创建引导软盘。
(13) 对于创建引导软盘，你可以有两种选择：一种是针对特定系统的引导盎，它含有
与当前系统一样的核心，另一种是较小的“通用”核心‘它链接的驱动程序较少。
如果你当前的核心相对你的软盘来说太大，你会得到告诫并只能选择建立一个通
用盘。
(14) 插入软盘并回答提问，就像在插入和格式化根系统软盘时一样。
(15) 在创建引导盘时，你会看到文件复制到软盘上的消息，然后，使用fsck(ADM)检查
文件系统。当全部完成后贴标签，就橡制作根系统软盘时一样。
(16) 按照5．3节“测试应急引导软盘组”中描述的过程检验你是否可以使用引导和根
系统软盘来引导伤的系统和访问备份。
把应急引导软盘组(或单张引导／根系统软盘)保存在安全可靠的地方，确保能够很方便
地取用。在系统损坏或不能引导时需要使用它们。
3.2 在根系统软盘上增加文件
如果在创建系统软盘过程中，对是否转入shell 的提示，回答了得y,你会看到如下信息：
you can copy files into /mnt to customize your root filesystem floppy.
After you finish ,type “exit 0” to continue .
You have n free blocks (512bytes) available on the floppy.
命令提示符是<bootroot>;
如果有足够的空闲空间，你就可以把附加的文件复制到根系统软件盘上。例如，要将文件／usr/pest 复制到软盘上，输入：
cp /usr/pest /mnt/usr
当添加文件完毕后，在<bootroot>; 提示符下输入exit 0。
3.3 在根软盘中增加网络文件
要创建能用于网络的根软盘，以便可以使用rlogin( C)， telnet( C)和 ftp( C)等命令，需要在＜ bootroot＞提示符下用复制命令复制下列文件：
cp／etc／services ／mnt／etc／services
cp／etc／tcp / mnt／etc／tcp
cp／etc／slink ／mnt／etc／slink
cp／etc／ifconfig ／mnt／etc／ifconfig
cp／etc／inconng ／nmt／etc／inconEg
cp／bin／who ／mnt / bin／who
cp／bln／ps ／mnt / bin／ps
cp／usr／bin／telnet ／mnt / usr／bin／telnet
cp／usr／bin／rlogin ／mnt / usr／bin／rlogin
cp／usr／bin／ftp ／nmt／usr／bin／ftp
要使用应急软盘中的网络服务，请打人 tcp start手工启动网络。
3.4 测试应急引导软盘组
当应急引导软盘组建立后：需要检验是否能用它来引导系统．并续取备份。
( l) 用 root (超级用户)注册。
(2) 键人／etc／shutdown 关闭系统。
(3) 在提示重新引导时将你的引导盘插入软盘驱动器。并按＜Enter＞键。
(4) 在 Boot：提示符下按＜ Enter＞，从软盘引导。
(5) 出现要求插入根系统软盘提示时，插入根系统软盘，并按<Enter>; 键。
(6) 当看见系统提示符时，按下一节
3.5 读取备份
在系统安装过程的最后，需要给系统做一份完整的备份。
如果还没有备份系统，应按照《SCO OpenServer 系统管理指南》中的“运行不定期的文件备份”的说明进行。
确认在使用应急引导软盘引导系统后，能访问该备份。
注意：在用应急引导和根系统软盘引导时，除非有第二个软驱器，否则只能从磁带备份上读取文件。
(1) 确保根系统软盘在驱动器。
(2) 列出备份的目录。
cpio -itvcB –I /dev/rct0
(3) 在用应急引导软盘组引导之后，一旦你对备份的读取情况感到满意，键人／etc /
haltsys从硬盘上重新启动系统。
(4) 当看到重新启动的信息时，从驱动器中取出软盘，按＜ Enter＞ o
(5) 在 Boot：提示符下，按＜ Enter＞键从硬盘引导系统。
关于使用应急引导软盘组存取并恢复损坏的 rmc文件系统的信息，请参阅13‘3
节“恢复被破坏的根文件系统”。
3.6 从硬盘引导
如果你用应急引导软盘组引导系统时碰到问题或不能访问备份卷，从硬盘上重新引
系统：
( l) 按计算机上的reset健，或关掉电源，然后再打开。
(2) 在 Boot：提示符下，按＜Enter＞键从硬盘上重新引导。
(3) 如果你的应急引导软盘有问题，请按5．1节“配置应急软盘”中的步骤再做一遍。
第4章 许可与登记SCO 产品
你必须许可证和登记每一种SCO 产品。在安装时，基本操作系统都要得到许可，其它绝大多数SCO 产品在它们的安装过程中都会向你提示此产品的许可信息。
使用License Manager 许可和登记产品。以root 注册，并按照下列步骤执行:
(1) 安装产品
(2) 许可产品
(3) 获得登记关键字
(4) 登记产品
参见：
·许可与登记术语
·许可其他用户和 CPU
·删除产品许可
·产品许可和登记故障诊断
4.1 Licnese Manager界面
使用 License Manager以进行：
·产品许可
·删除许可证
·注册产品
在完成软件产品的安装之后，以 root注册，以下列方式之一启动 License Manager：
·双击桌面上system Administration窗口中的 License Manager图标。
·在命令行上运行 scoadmin命令来启动 scoadmin界面．然后选择 License Manager。
·在命令行上键人 scoadmin license manager (或者缩写scoadmin l)。
注意：scoadmin命令只能识别“Iicense”，而不能识别“Iicence” 。
4.2产品的许可
在License Manager中：
( I) 从已安装的产品中选择你希望许可的产品。
注意：不要选择“OpenServer Software ”，因为它不是可以许可的产品。
(2) 从 license菜单中选择Liecnse Prodduct。
(3) 请确认随软件一起提供的＜许可与授权证书＞是原件，并且它的左边应有SCO全息
防伪标志。从此处输入：
·许可证号
·许可证代码
·许可证数据(如果证书中包括)
(4) 单击License图标。
注意：请记住登记所有的产品，你的系统软件将经常提醒你直到将它们登记为止。
要确定哪一种产品已经许可或登记，请在License Manager 上使用View 菜单。
4.2.1 许可其他用户和CPU
在License Manager 中：
(1) 从License 菜单上选择License Additional User 或License Additional CPU。
(2) 单击 license 。
4.2.2 删除产品许可
为使另一个系统建立能够使用的许可证，或者因其它原因需要删除一个许可证，可以从License Manager列表中选择已许可的产品，然后从 License菜单上选择 Remove License。
如果删除了一个产品的许可，那么其功能就不能在那个系统上使用了。
4.3登记产品
一旦你完成了 SCO产品的安装和许可，应尽快地登记产品以免系统软件经常提醒你进
行登记：
1)、SCO产品注册
1.记下系统上的许可证号（License Number:）,系统号(SCO System ID :)
scoadmin - License Manager – Register
如License Number: 2EK041587
SCO System ID: xqcrkewbso
其系统号是机器安装时产生的。
2.注册方法
可自己上Internet网，直接访问http://www.sco.com站点注册。
或 用电脑将License Number:与SCO System ID :打印后，传真给代理商。
SCO产品注册步骤：
3. 启动Netscape或IE，在Location中键入www.sco.com/ register后回车。
* 输入您的邮编并选择国家。
* 选择您所使用的产品类型。
* 选择以前是否注册过, 如果您注册过选择<1>;, 未注册过选择<2>;。
<1>;按提示填入：
公司的名称
称呼
街道地址
城市/城镇/乡村
国家
电话、传真、电子邮件
填写完毕后单击submit。
<2>;按提示填入：
System ID
License number ( 一次最多可注册六个产品 )
选择注册公司的类别
A. 选择最能说明用户组织活动的行业类别(只能选一项)
B. 选择在SCO基本系统上已经运行和将要运行的应用
C. 在空格内填入相应的数目:
当前使用该系统的最大用户数
在安装场地的全体人员数
在用户组织中的全体人员数
安装该系统的组织
A. 选择安装该系统所用的机器类型（只能选一项）
B. 选择您希望收取关于产品和服务的额外信息
选择完毕后单击 Register Product , 注册成功后将在另
一屏中给出registration key。
2).龙马产品注册
将注册卡及注册号(安装时产生)传真给北京东方龙马总公司 （010-64447559）
注册信息表：
注册名称（unit name）:安装过程中输入的单位名称。
序列号 （ser Number）
活动码 （Act Key）
注册号 （Log Number）
如何获得注册信息表
东方龙字符版：#/usr/bin/draglog disp
东方龙图形版：#/usr/bin/dragxlog disp
天道通信： #/usr/bin/transtlog disp
东方笔： #/usr/bin/xwordlog disp
注册(当得到本公司注册码后)
东方龙字符版：#/usr/bin/draglog log
东方龙图形版：#/usr/bin/dragxlog log
天道通信： #/usr/bin/transtlog log
东方笔： #/usr/bin/xwordlog log
4.4产品许可和登记故障诊断
下面列举了在许可和登记过程中最常遇到的
· license Manager不接受登记关键宇
· license Manager不接受许可信息
· OpenServer许可已经过期
· 在本机中没有发现用户许可
4.4.1 license Manager 不接受登记
关键字无效或不正确，将会出现一个出错消息。确认正确地键入了关键字，并没有错误地将SCO 系统ID 键入，如果继续收到出错消息，请与SCO 登记中心联系，
4.4.2 License Manager 不接受许可信息
请仔细阅读许可证。许可证上偶尔会有一些字符不易辨认。
4.4.3 OpenServer许可已经过期
如果license Manager 提示操作系统许可已经过期，检查系统时钟和 CMOS时钟(计算机中的以电池作动力的硬件时钟)，以保证与现实的年月及时间相符。如果 CMOS时钟设置错了年份，将导致许可过期。使用 date 命令检查系统时间，使用setclock命令检查 CMOS
时钟。如果它们不同步，你可以以root注册，使用如下命令使它们同步：
date MMDDhhmmYY
这里MMDDhhmmYY是月-日-小时-分钟-年格式的正确时间。例如，下面是1997年8月31日上午9：31的格式：
0831093197
当你改变了时钟之后，重新启动系统，开始License Manager，看看许可是否已经由“Expired”改变到“Yes”。操作系统的许可功能均可由许可指定的选项操作。
4.4.4 查看OpenServer产品的许可过期日
使用如下过程可以查看过期日：
( l) 使用brand命令确定操作系统许可 ：
brand -l
这个命令对于每个产品产生两行数据，第2行比第 l行缩进几个字符。产品由第2
行识别。它的输出类似于如下 SCO OpenServer的例子：
____________________________________________________________________________
{
{{ l32}{5．0}{ bif654321} {bdhxyz10z;g0； k255／bif654321； s950502； u5}
{799372800}{3955219199}
{ SCO：odtes }{5．0．4b}{ SCO OpenServer Eterprise System}；{bdhyff00z； g0 ;k；
u5}}
}
____________________________________________________________________________
每个产品许可的起始日期和终止日期是第 l行的最后两个数字。你感兴趣的数字
是终止日期，在例子中以黑体表示。
(2) 用fmtclock(TCL)命令可以将过期日期转化为常用的日期格式，就像以下由用户输
入的黑体：
# tcl
tcl＞fmtclock 3955219199
Mon Jan 18 19：14：07 PST2038
tcl＞
4.4.5 在计算机中没有找到用户许可
如果在机器启动时看到如下消息：
NO user licenses were found on this machine． Please boot
Single user and correct this situation .Licensed software
Will not operate until user licenses are installed.
The License Policy Manager Daemon (ifor_pmd) was unable to start.
This is usually due to a read-only root filesystem,lack of
User licenses or a damaged program image file (/etc/ifor_pmd).
If this is not the case ,please contact your SCO service provider.
这是由于系统时钟日期大大超出许可日期，也有可能因为缺少用户许可或policy 管理程序
精灵进程/etc/ifor_pmd 有相当严重的错误。
4.4.7 LOGIN: ERROR -- 不能初始化policy 管理程序
如果在注册之后看到如下消息
LOGIN：ERROR –failed to initialize policy manager.(IFOR_PM_FATAL)
Login session denied．
或者因为policy管理程序精灵进程／etc／ifor_pmd已经停止工作并且没有重新启动，或因为 policy管理程序注册所需的一些关健性文件丢失或被破坏。
注意：你可能将退出并且不能再注册解决这个问题。另一个错误消息将会出现。如果是这样的话，应该将系统关闭并重新启动。如果错误消息仍出现，请按下列步骤进行。
这里列出了一些导致中断或非正常工作的原因
．／etc／ifor_ pmd二进制文件被中断或丢失
．关键字文件或目录丢失
．根目录文件系统被置为只读
．没有用户许可，或没有更多的许可
．系统已经超出STREAMS资源
4.4.7.1 /etc/ifor_pmd 二进制文件被中断或丢失
policy管理程序(／etc／ifor_pmd)必须存在并且在系统中运行。在softwrae manager中，
选择 Software >;>; Verify Software 并选择 Broken／mssing syvmbolic links。这样，就将检查并修复／etc／ifor_pmd和／opt／K／SCO两层间的链接。也可以按照如下所示单独对 policy管理程序包进行这个操作：
SCO OpcnServer Enteprise System
SCO0penServer Enterpxlse System UNIX
SCO OpenServer Entelprise SysLem Core OS
4.4.7.4没有用户许可存在，或没有更多许可
首先，确认有多少用户已经注册到系统中。一个用户被定义为一个物理键盘或一个网络注册用户。如果一旦用户多于系统可检测的许可用户范围，唯一可以避免错误提示的方法是购买额外的用户许可产品。
如果注册的用户数量没有超过界限，发生错误的原因可能是许可数据库本身工作出现中断。依据以下步骤重新进行用户许可登记。这个步骤的执行前提示用户许可是唯一通过SCO OpenServer企业系统许可及授权认证提供的。如果你已经使用一个独立的用户许可产品许可了另外的用户，请先对那个产品执行下述步骤：
( l) 告知所有用户退出系统。
(2) 当所有用户退出后，启动License Manager，选择 SCO OpenServer Enterprise
System，选择 License>;>;Remove License以删去 SCO OpenServer企业系统许可。
(3) 重新许 |
S CO OPENSERVER操作系统
斑竹，你不觉的贴错地方了吗? |
| |
