Digital UNIX (formerly DEC OSF/1) Release Notes Order Number: AA-QTLMA-TE March 1996 Product Version: Digital UNIX Version 4.0 This book contains notes on software and documentation restrictions for Digital UNIX Version 4.0 and the bundled layered products that ship on the same CD-ROMs. This book also describes significant new and changed features in this version of the Digital UNIX operating system and lists features and interfaces scheduled for retirement in future releases. __________________________________________________ Digital Equipment Corporation Maynard, Massachusetts Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Copyright Digital Equipment Corporation 1996 All rights reserved. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, Alpha AXP, AlphaGeneration, AlphaServer, AlphaStation, AXP, Bookreader, CDA, DDIS, DEC, DEC Ada, DEC Fortran, DEC FUSE, DECnet, DECstation, DECsystem, DECterm, DECUS, DECwindows, DTIF, MASSBUS, MicroVAX, OpenVMS, POLYCENTER, Q-bus, StorageWorks, TruCluster, TURBOchannel, ULTRIX, ULTRIX Mail Connection, ULTRIX Worksystem Software, UNIBUS, VAX, VAXstation, VMS, XUI, and the DIGITAL logo. COMPAQ is a registered trademark of Compaq Computer Corporation. Netscape Navigator is a trademark of Netscape Communications Corporation. NFS is a registered trademark of Sun Microsystems, Inc. ONC is a trademark of Sun Microsystems, Inc. Open Software Foundation, OSF, OSF/1, OSF/Motif, and Motif are trademarks of the Open Software Foundation, Inc. Adobe, PostScript, and Display PostScript are registered trademarks of Adobe Systems, Inc. Proteon is a trademark of Proteon Associates, Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. X/Open is a trademark of X/Open Company Ltd. All other trademarks and registered trademarks are the property of their respective holders. Contents About This Manual Audience ............................................ xix Organization ........................................ xix Related Documents ................................... xx Reader's Comments ................................... xxi Conventions ......................................... xxii 1 New and Changed Features 1.1 Common Desktop Environment .................... 1-1 1.1.1 The CDE Video Tour ....................... 1-2 1.1.2 CDE Screen Savers ........................ 1-2 1.2 X/Open-Compliant Curses ....................... 1-2 1.3 X11R6 ......................................... 1-3 1.3.1 The X Keyboard Extension for X11R6 (XKB) . 1-3 1.4 DXImageview ................................... 1-4 1.5 Commands and Utilities ........................ 1-4 1.5.1 Changes to Mtools ........................ 1-4 1.5.2 The sendmail Utility Supports Configurable GECOS Fuzzy Matching ....................... 1-5 1.5.3 df Supports Large File Systems ........... 1-5 1.5.4 Compressed Reference Pages ............... 1-5 1.5.5 Enhancements to terminfo ................. 1-5 1.5.6 GNU emacs Version 19.28 .................. 1-6 1.5.7 Netscape Navigator ....................... 1-6 1.5.8 dxterm ................................... 1-6 1.5.9 Performance Manager ...................... 1-7 1.5.10 utilupdate .............................. 1-7 1.5.11 Bootable Tape ........................... 1-7 1.5.12 Partition Overlap Checks Added to Disk Utilities .................................. 1-8 1.5.13 scsimgr Utility for Creating Device Special Files .............................. 1-9 1.6 SysMan System Management Applications ......... 1-9 1.6.1 Installation ............................. 1-10 1.6.1.1 New Installation User Interfaces ... 1-10 1.6.1.2 New Format of Distribution Media ... 1-11 1.6.1.3 Installation Name Changes .......... 1-11 1.6.1.4 Enhancements to the Installation Procedure .............................. 1-11 1.6.1.5 Cloned Installations ............... 1-12 1.6.2 Configuration Applications ............... 1-12 1.6.2.1 Bind Configuration ................. 1-13 1.6.2.2 Disk Configuration ................. 1-14 1.6.2.3 Mail Configuration ................. 1-14 1.6.2.4 Network Configuration .............. 1-14 1.6.2.5 NFS Configuration .................. 1-15 1.6.2.6 Print Configuration ................ 1-16 1.6.2.7 Internationalization Configuration . 1-16 1.6.3 Daily Administration Applications ........ 1-16 1.6.3.1 Account Manager .................... 1-17 1.6.3.2 Archiver ........................... 1-18 1.6.3.3 File Sharing ....................... 1-18 1.6.3.4 Host Manager ....................... 1-19 1.6.3.5 License Manager .................... 1-19 1.6.3.6 Shutdown Manager ................... 1-20 1.6.3.7 System Information ................. 1-20 1.6.3.8 Audit Manager ...................... 1-21 1.6.4 Monitoring and Tuning Applications ....... 1-21 1.6.4.1 Kernel Tuner ....................... 1-21 1.6.5 Storage Management ....................... 1-22 1.6.6 Tools .................................... 1-22 iv Contents 1.7 Standards ..................................... 1-23 1.7.1 Realtime Is Compliant With the Final POSIX 1003.1b Standard Interfaces ................ 1-23 1.7.2 DECthreads is Compliant with the Final POSIX 1003.1c Standard Interfaces .......... 1-23 1.7.3 DEC C Compiler Complies With ISO C 94 .... 1-23 1.8 Development Environment ....................... 1-23 1.8.1 Tcl/Tk Availability ...................... 1-23 1.8.2 DEC C++ .................................. 1-24 1.8.3 Replacement of the pixie Utility ......... 1-25 1.8.4 Software Development Environment Repackaging ................................ 1-26 1.8.5 DEC C Compiler ........................... 1-26 1.8.6 Init Execution Order Modified for Static Executable Files ........................... 1-27 1.8.7 PC-Sample Mode of prof Command ........... 1-27 1.8.8 atom and prof Commands and Threads ....... 1-28 1.8.9 Thread Independent Services (TIS) Interface..1-28 1.8.10 High-Resolution Clock ................... 1-29 1.8.11 POSIX 1003.1b Realtime Signals .......... 1-29 1.8.12 POSIX 1003.1b Synchronized I/O .......... 1-29 1.8.13 POSIX 1003.1b _POSIX_C_SOURCE Symbol .... 1-30 1.8.14 Digital Porting Assistant ............... 1-30 1.9 Networking .................................... 1-31 1.9.1 New Version of the gated Daemon .......... 1-31 1.9.2 Dynamic Host Configuration Protocol (DHCP) . 1-31 1.9.3 Point-to-Point Protocol (PPP) ............ 1-32 1.9.4 NFS over TCP ............................. 1-32 1.9.5 Extensible SNMP .......................... 1-32 1.9.6 SNMP MIB support ......................... 1-33 1.9.7 telnet and mrouted ....................... 1-33 1.9.8 Network Time Protocol (NTP) .............. 1-33 1.10 Enhanced Security ............................ 1-34 1.11 File Systems ................................. 1-34 1.11.1 AdvFS ................................... 1-34 1.11.1.1 New Tuning Parameters for AdvFS ... 1-34 1.11.1.2 AdvFS Now Supports Directory Truncation ............................. 1-35 Contents v 1.11.2 File System Access Control Lists (ACLs) . 1-35 1.11.3 Logical Storage Manager ................. 1-36 1.11.4 Overlap Partition Checking .............. 1-38 1.12 Bootstrap Linking and Kernel Modules ......... 1-38 1.12.1 Defining Modules ........................ 1-38 1.12.2 Bootstrap Linking ....................... 1-39 1.12.3 Related Changes ......................... 1-40 1.13 Internationalization and Language Support .... 1-41 1.13.1 Internationalization (I18N) Configuration Utility for CDE ............................ 1-41 1.13.2 Unicode Support ......................... 1-42 1.13.3 The Worldwide Mail Handler No Longer Exists ..................................... 1-42 1.13.4 Multilingual Emacs (mule) ............... 1-42 1.13.5 Support for Catalan, Lithuanian, and Slovene .................................... 1-43 1.13.6 man Command Supports Codeset Conversion . 1-43 1.14 PCMCIA (PC Card) Support ..................... 1-43 1.14.1 Restrictions ............................ 1-44 1.14.2 Configuring the PCMCIA Adapter Board from the Console ................................ 1-45 1.14.3 Configuring and Using a PCMCIA Modem PC Card ....................................... 1-47 1.14.4 Creating a Device Special File for the Modem Card ................................. 1-48 1.14.5 /etc/remote File ........................ 1-49 1.14.6 Inserting a PCMCIA Modem Card ........... 1-50 1.14.6.1 Possible Error Message ............ 1-50 1.14.7 Removing a PCMCIA Modem Card ............ 1-51 1.15 Dynamic Device Recognition for SCSI Devices .. 1-51 2 Installation Notes 2.1 General Information About Installation ........ 2-1 2.1.1 Kernel Object Files Not Installed ........ 2-1 vi Contents 2.1.2 Installation Procedure may Fail to Detect Disks ...................................... 2-2 2.1.3 Systems Without Graphics Devices ......... 2-2 2.1.4 Worldwide Subsets ........................ 2-3 2.1.5 Invalid Password in Graphical Installation . 2-3 2.1.6 Minimum Version 2.10 for Qlogic Firmware . 2-4 2.1.7 ATI Graphics Controllers ................. 2-4 2.1.8 Incorrect Broken Pipe Messages ........... 2-4 2.2 Layered Product Considerations ................ 2-4 2.2.1 DEC FUSE ................................. 2-5 2.2.2 DECnet/OSI ............................... 2-5 2.2.3 Subset Control Program Methods for Restricting a Product to Digital UNIX ...... 2-6 2.3 Full Installation ............................. 2-6 2.3.1 Full Installation Overwrites /etc/fdmns .. 2-6 2.3.2 Full Installation Overwrites /etc/lvmtab . 2-6 2.3.3 Full Installation Overwrites /etc/vol/volboot ........................... 2-6 2.3.4 Full Installation Overwrites /etc/prestotab..2-7 2.3.5 The Installation Graphical Interface ..... 2-7 2.4 Update Installation ........................... 2-7 2.4.1 Systems Without Graphics Devices ......... 2-7 2.4.2 Disable Lightweight Wiring When Using Granularity Hints .......................... 2-8 2.4.3 Disk Space Requirements for Update Installations .............................. 2-8 2.4.4 Update Install and Enhanced Security ..... 2-9 2.4.5 System Clock may Lose Time ............... 2-10 2.4.6 Message From swapon Utility .............. 2-11 2.4.7 Kernel Object Files Are Deleted .......... 2-11 2.4.8 The installupdate Command May Select the Wrong Device ............................... 2-11 2.5 Server Extensions ............................. 2-12 2.5.1 Error when installing Chinese subsets from RIS server ................................. 2-12 2.6 Disk Space Requirements ....................... 2-13 Contents vii 3 Processor-Specific Notes 3.1 General Notes on Processors ................... 3-1 3.1.1 PCI-based Systems with ATI Mach64 Graphics Controllers ................................ 3-1 3.1.2 PCI Shared Interrupt Support ............. 3-1 3.1.3 Support for RTS/CTS (Hardware) Flow Control..3-2 3.2 Digital AlphaStation 200 and Digital AlphaStation 400 Processors ................... 3-2 3.2.1 Power Management Support for the Digital AlphaStation 255 ........................... 3-2 3.2.2 Monitor Power Management for the Digital AlphaStation 255 ........................... 3-3 3.3 Digital AlphaServer 1000 4/200 Processors ..... 3-3 3.3.1 EISA Configuration Utilty and RIS Installation ............................... 3-3 3.4 Digital AlphaServer 2000, AlphaServer 2100 Processors and Digital Alpha VME 2100 Processors..3-4 3.4.1 SWXCR Raid Configuration Updates ......... 3-4 3.4.2 Digital Alpha VME 2100 ................... 3-4 3.4.2.1 Unpredictable Results When Performing Master Block Transfers ................. 3-4 3.5 KDM70 Disk Controller on DEC 7000 Processors .. 3-4 3.6 Digital AXPvme Single Board Computers ......... 3-4 3.6.1 Hardware Restriction ..................... 3-5 3.6.2 Unpredictable Results When Performing Master Block Transfers ..................... 3-6 3.6.3 IRQs for PCI Options on Digital AXPpci 33 Systems .................................... 3-6 viii Contents 4 Base System Software Notes 4.1 Internationalization .......................... 4-1 4.1.1 Return Values of Functions iswdigit() and iswalnum() Under the Thai Locale ........... 4-1 4.1.2 Printing PostScript Format Files in Asian Languages .................................. 4-1 4.1.3 Line Wrapping in vi ...................... 4-2 4.2 X/Open-compliant Curses ....................... 4-2 4.2.1 Changes in Datatypes, Structures, and Macros ..................................... 4-3 4.2.2 Change in Behavior of cbreak() Function .. 4-4 4.3 Commands and Utilities ........................ 4-5 4.3.1 vdump and vrestore Compatability Problem . 4-5 4.3.2 Security ................................. 4-5 4.3.2.1 Unexpected Command Behaviour with ACLs ................................... 4-5 4.3.2.2 Archive Tools and Security ......... 4-6 4.3.2.3 emacs Can Lose ACL File Settings ... 4-7 4.3.3 Mail and mailx Command Behavior .......... 4-7 4.3.4 Using gendisk on Diskette Devices ........ 4-7 4.3.5 Some emacs Command Line Options Fail ..... 4-9 4.3.6 Directory Tree /usr/opt/sterling Renamed . 4-10 4.3.7 POSIX Shell .............................. 4-10 4.3.8 Sendmail Configurable Maximum Hop Count .. 4-10 4.3.9 cksum Reports Incorrect Values ........... 4-11 4.3.10 df and XPG4 Compliance .................. 4-11 4.3.11 Use of echo -n in Scripts ............... 4-11 4.3.12 awk Linked to nawk ...................... 4-11 4.3.13 Unsupported vmh Command ................. 4-12 4.3.14 Restrictions on the od Command .......... 4-12 4.4 SysMan System Management Graphical User Interface ..................................... 4-12 4.4.1 Restrictions on Using the Disk Configuration Manager ...................... 4-12 4.4.2 Account Manager .......................... 4-13 4.4.2.1 Usage Note ......................... 4-14 Contents ix 4.4.2.2 Account Manager Restrictions ....... 4-14 4.4.2.3 Account Manager Problems ........... 4-15 4.4.2.4 Enhanced Security Account Manager Problems ............................... 4-16 4.4.3 Enhanced Security and Account Manager .... 4-19 4.4.4 Swap Warning in dxsysinfo ................ 4-22 4.4.5 File System Percent Full Values May be Incorrect .................................. 4-22 4.4.6 The dxsysinfo Utility May Display /dev/prf as a Tape Device ........................... 4-22 4.4.7 dxshutdown Does Not Prohibit User Logins . 4-22 4.4.8 Print Configuration Manger ............... 4-22 4.5 System Administration ......................... 4-23 4.5.1 Enhanced Security ........................ 4-23 4.5.1.1 Distribution of Enhanced Security Profiles via NIS ....................... 4-23 4.5.1.2 Enhanced Security and Disaster Recovery ............................... 4-25 4.5.1.3 Username Length Restriction ........ 4-26 4.5.2 Bootable Tape ............................ 4-26 4.5.2.1 Disk Space Issues .................. 4-27 4.5.2.2 Setting Swap Space on a Restored Disk..4-28 4.5.2.3 Setting an Existing File System on a Restored Disk .......................... 4-29 4.5.2.4 Tape Drive Restriction ............. 4-29 4.5.3 Multimedia Services for Digital UNIX V2.0 and V2.0A .................................. 4-29 4.5.4 settime After an Update Installation. .... 4-30 4.5.5 System Clock Loses Time .................. 4-30 4.5.6 Symbolically Linked Kernels .............. 4-30 4.5.7 Usage Note for Adding Swap Devices ....... 4-31 4.5.8 Additional SCSI Disk Informational Entries in Error Log ............................... 4-31 4.5.9 Multiple Queues .......................... 4-32 4.6 Network and Communications .................... 4-32 4.6.1 Using bind on an UNIX Domain (AF_UNIX) Socket ..................................... 4-33 4.6.2 Changes to ATM (Asynchronous Transfer Mode)..4-33 4.6.2.1 Changes to ATM Startup Scripts ..... 4-33 x Contents 4.6.2.2 Digital Gigaswitch Interoperability 4-33 4.6.2.3 Support of NFS Locking over ATM .... 4-34 4.6.2.4 Restriction of Using atmsig down ... 4-34 4.6.3 Large User Stack Limits May Cause a System Panic ...................................... 4-34 4.6.4 SVR4 Streams IFNET paradigm. ............. 4-34 4.6.5 Orderly Release in XTI ................... 4-35 4.6.6 Restarting the Network When Using Interface Aliases .................................... 4-35 4.6.7 Incorrect Error Message Using netsetup and rcinet ..................................... 4-35 4.6.8 CDE's Static Dependency on the Network ... 4-36 4.7 Local Area Transport .......................... 4-36 4.7.1 Duplicate Minor Numbers and latsetup ..... 4-37 4.7.2 CTRL/A Causes LAT tty to Change the Case of Characters ................................. 4-37 4.7.3 Simultaneous llogin Connections .......... 4-37 4.7.4 LAT Kernel Module Is Dynamically Loadable 4-37 4.7.5 Group Codes Are Compatible with Version 2.0 LAT Driver. ................................ 4-37 4.7.6 shutdown Command May Stall ............... 4-38 4.8 File Systems .................................. 4-38 4.8.1 Using ACLs over NFS ...................... 4-38 4.8.2 ACL Size Limitations ..................... 4-39 4.8.3 POLYCENTER Advanced File System .......... 4-39 4.8.3.1 Backward Compatability Problem with vdump and vrestore ..................... 4-40 4.8.3.2 Log Half Full Error ................ 4-40 4.8.3.3 ACL Size Limitations ............... 4-41 4.8.3.4 The vdump and vrestore Commands .... 4-41 4.8.3.5 The verify -F Command Does Not Bypass Recovery ............................... 4-42 4.8.3.6 rmfset Command May Hang ............ 4-42 4.8.3.7 AdvFS Sparse File Save and Restore . 4-42 4.8.3.8 AdvFS Verifies Domain Volume Sizes . 4-42 4.8.3.9 AdvFS Domain Panic ................. 4-43 4.8.3.10 AdvFS Supports UFS Quota Commands . 4-44 4.8.3.11 AdvFS Supports More Mounted Filesets..4-45 4.8.3.12 Possible Check and Repair Failure . 4-45 4.8.3.13 AdvFS Command and Quota Problems .. 4-45 4.8.3.14 Reusing AdvFS Partitions .......... 4-45 4.8.3.15 Data Element Size Limits for Extended Attributes .................... 4-46 Contents xi 4.8.3.16 Increase Metadata Extent Size for Large Number of Files .................. 4-46 4.8.3.17 Mounting UFS File System with AdvFS root ................................... 4-46 4.8.3.18 Disk Usage Information ............ 4-47 4.8.3.19 AdvFS Does Not Support the Hierarchical Storage Manager ........... 4-47 4.8.3.20 Unique File Identifiers ........... 4-47 4.8.3.21 NFS Server May Print Error Message on NFS Client Recovery ................. 4-48 4.8.3.22 AdvFS Panic ....................... 4-48 4.8.4 Logical Volume Manager ................... 4-48 4.8.5 Logical Storage Manager .................. 4-49 4.8.5.1 Possible Problems Accessing Physical Block 0 with LSM ....................... 4-50 4.8.5.2 Using LSM with SWXCR-P(A/B) and SWXCR-E(A/B) RAID Controllers .......... 4-50 4.8.5.3 Enabling LSM After Installation Requires Rebuilding the Kernel ......... 4-50 4.8.5.4 The volrootmir Script Supports Only LUN 0 on HSZ ........................... 4-51 4.8.5.5 Boot Failures May Occur When Using LSM Volume rootvol for the root File System ................................. 4-51 4.8.5.6 Block Change Logging Subdisk Size Recommendation ......................... 4-51 5 Development Environment Notes 5.1 Some C Library Functions Have Two Versions .... 5-1 5.2 Missing Debugger Information .................. 5-1 5.3 DEC Ada Is Not Supported ...................... 5-2 5.4 Init Execution Order Modified ................. 5-2 5.5 Using pixie on Applications Built with -om .... 5-3 5.6 pixie Command Can Fail to Locate atom Command . 5-3 5.7 c89 Command Conforms to Spec1170 .............. 5-3 5.8 Alternate Compiler Suite ...................... 5-4 5.9 DEC C ......................................... 5-4 xii Contents 5.9.1 Remove the DEC C -migrate Switch ......... 5-5 5.9.2 Object File Address Reference Limit ...... 5-6 5.10 DEC C -ifo Switch ............................ 5-6 5.11 XTI and TLI Libraries Are Thread-Safe ........ 5-7 5.12 DECladebug Product Name Change (Ladebug) ..... 5-7 5.13 Analysis Tool with Object Modification (ATOM) 5-7 5.13.1 Profiling Signal Handlers and fork with Multithreaded hiprof ....................... 5-7 5.13.2 Third Degree and hiprof Errors with Multi-threaded Applications ................ 5-8 5.13.3 Atom third Tool (Third Degree) May Not Work Correctly with C++ .................... 5-9 5.13.4 Atom Error with Dynamically Linked Fortran Applications ............................... 5-9 5.14 Change to Static Libraries and Kernel Objects 5-10 5.15 DEC C++ Class Library Fixes .................. 5-10 5.15.1 File Positioning for Bidirectional fstreams Has Been Corrected ................ 5-11 5.15.2 real Function Has Been Corrected ........ 5-11 5.15.3 flush Function Has Been Corrected ....... 5-11 5.15.4 LANG Environment Variable No Longer Cleared .................................... 5-11 5.15.5 Extraction Operator Converting Hexadecimal Values Has Been Corrected .................. 5-11 5.15.6 Segmentation Fault at Image Exit Has Been Corrected .................................. 5-11 5.16 General Programming .......................... 5-12 5.16.1 New Interfaces to the C Runtime Library . 5-12 5.16.2 prof Command Information Messages ....... 5-12 5.16.3 Realtime ................................ 5-12 5.16.3.1 SA_SIGINFO Not Visible Under Certain Namespace Conditions ................... 5-12 5.16.3.2 POSIX 1003.1b Synchronized I/O and File Truncation ........................ 5-13 5.16.3.3 fcntl() and F_GETFL with O_DSYNC File Status. ........................... 5-13 5.16.3.4 Realtime Problems with Asynchronous I/O and Streaming Devices .............. 5-13 Contents xiii 5.16.4 DECthreads (pthreads) ................... 5-13 5.16.4.1 The cc Command Supports the -pthread Option ................................. 5-14 5.16.4.2 Libraries libc and libc_r are Merged..5-14 5.16.4.3 DECthreads Exception Handling ..... 5-14 5.16.4.4 DECThreads Signal Model Incompatibilities in Threaded Applications ........................... 5-15 5.16.4.5 dbx and DECthreads ................ 5-15 5.16.4.6 Threaded Application Coding Errors 5-15 5.16.4.7 Missing Thread Routines ........... 5-15 5.16.4.8 DECthreads Static Libraries ....... 5-16 5.16.4.9 DECthreads System Cancellation Points ................................. 5-16 5.16.4.10 DECthreads and Forking ........... 5-16 5.16.4.11 DECthreads and Realtime .......... 5-16 5.16.4.12 DECthreads and Alpha Firmware Revisions .............................. 5-16 5.16.4.13 DECthreads and Signal Handling ... 5-17 5.16.5 Changes in Kernel Debugging Using dbx ... 5-17 5.16.6 Warnings from sysconfig About Loadable Subsystem Attribute Tables ................. 5-18 5.16.7 Device Driver Example Files ............. 5-19 5.17 Functions and System Calls ................... 5-19 5.17.1 Changes in pipe System Call Behavior .... 5-19 5.17.2 shmat() Fails With Invalid Argument (EINVAL) ................................... 5-19 6 Window System Software Notes 6.1 Hardware Notes and Restrictions ............... 6-1 6.1.1 Calcomp Tablet ........................... 6-1 6.1.1.1 Configuring the CalComp DrawingBoard III Tablet ............................. 6-1 6.1.1.2 Notes and Restrictions ............. 6-4 6.1.2 Qvision Graphics Display Error ........... 6-5 6.2 X Servers ..................................... 6-5 6.2.1 Window System Response and Paging Load ... 6-5 xiv Contents 6.2.2 Limited Multiscreen Display Support With CDE ........................................ 6-8 6.2.3 Keymap Interoperability Problem .......... 6-8 6.2.4 Do Not Modify the keymaps.dir File ....... 6-8 6.2.5 Interleaf Display Problem ................ 6-9 6.3 X Clients ..................................... 6-9 6.3.1 X Window Colormap Resources .............. 6-9 6.3.2 Manual Merge of DXnotepad Resource Definition File ............................ 6-10 6.3.3 Defaults for Locking Mailboxes ........... 6-11 6.3.4 Switching Locales in dxmail .............. 6-11 6.3.5 Clipboard Interoperability Problem ....... 6-11 6.3.6 Hilite Mouse Tracking Disabled by Default in xterm ................................... 6-12 6.3.7 Motif Version 1.1.3 Clients .............. 6-12 6.3.8 Old X Environment ........................ 6-12 6.4 CDE Clients ................................... 6-12 6.4.1 Remote Invocation of CDE File Manager dtfile ..................................... 6-13 6.4.2 Autopause and Enhanced Security .......... 6-13 6.4.3 dtmail and the Environment Variable MAILLOCKING ................................ 6-13 6.4.4 dtmail Disables Tooltalk Locking By Default..6-13 6.4.5 dtmail Row and Column Display ............ 6-14 6.4.6 dtmail Attachments are Not Included ...... 6-14 6.4.7 dtmail Start-up .......................... 6-14 6.4.8 CDE's Static Dependency on the Network ... 6-15 6.4.9 xnlLanguage Resource Can Cause Problems with CDE ................................... 6-15 6.4.10 Possible Failure in the XOpenDisplay Call . 6-15 6.5 Windows Programming ........................... 6-16 6.5.1 X11 Font Problem ......................... 6-16 6.6 Internationalization .......................... 6-16 6.6.1 Using Taiwanese EUC Codeset with Chinese DECterm Software ........................... 6-16 6.6.2 Backspace Key Not Supported in Asian Input . 6-17 6.6.3 Transport Layer In Input Servers ......... 6-17 6.6.4 Asian Multiscreen Support ................ 6-17 Contents xv 6.6.5 Hanyu IM Server Support of EDPC Under zh_TW.big5 Locale .......................... 6-17 6.6.6 String Conversion and the ja_JP.SJIS Locale..6-17 6.6.7 Using Bookreader to Print Chinese and Korean Characters .......................... 6-18 6.6.8 Hebrew Editing Style ..................... 6-18 6.6.8.1 Cut and Paste Operation ............ 6-19 6.6.9 Hebrew CDE Users Should Avoid Using Certain Applications ............................... 6-19 6.6.10 Notepad Window Display and Input Style .. 6-19 6.6.11 Default Keyboard Mapping ................ 6-19 6.6.12 Lithuanian and Slovene Language Support . 6-20 6.6.12.1 Mnemonics in Lithuanian and Slovene DX Applications ........................ 6-20 6.6.12.2 DX Applications Integrated to CDE Desktop (Application Manager) .......... 6-20 6.6.12.3 DX applications not integrated into the CDE desktop (Application Manager) .. 6-21 6.6.12.4 DX Applications Invoked from DXsession .............................. 6-23 6.6.12.5 Lithuanian Language Variant ....... 6-23 7 Documentation Notes 7.1 Release Notes ................................. 7-1 7.2 Media CD-ROMs ................................. 7-1 7.3 General Information About the Documentation ... 7-2 7.3.1 New Manuals .............................. 7-2 7.3.2 Revised Documents ........................ 7-2 7.3.3 List of Available Patches ................ 7-2 7.3.4 Compressed PostScript Files .............. 7-2 7.4 Reference Pages ............................... 7-2 7.4.1 [XPG4_UNIX] Used Incorrectly in Section 1 Reference Pages ............................ 7-3 7.4.2 webman Utility for Netscape .............. 7-3 7.4.3 Modes of UNIX domain in the The bind() Reference Page ............................. 7-4 7.4.4 Nonexistant ACL Interfaces in the acl(4) Reference Page ............................. 7-4 xvi Contents 7.4.5 Property List Reference Pages ............ 7-5 7.4.6 mail_manual_setup Reference Page ......... 7-5 7.4.7 quota and vquota Show Wrong Usage of Options .................................... 7-5 7.5 Device Driver Documentation ................... 7-6 7.5.1 Writing VMEbus Device Drivers ............ 7-6 7.5.2 Device Driver Tutorial ................... 7-13 7.6 Network Administration Manual ................. 7-13 7.6.1 Changes to Section 4.2.2.2, "Verifying PPP Support in the Kernel" ..................... 7-13 7.6.2 Sections 4.2.3.1, 4.2.3.2, and 4.2.3.3 are obsolete ................................... 7-14 7.6.2.1 Establishing a PPP Dial-Out Connection ............................. 7-14 7.6.2.2 Establishing a PPP Dial-In Connection..7-18 7.7 System Administration Manual Instructions for SysMan Applications ........................... 7-19 7.7.1 Accessing the SysMan Tools ............... 7-19 7.8 Technical Overview ............................ 7-21 7.9 Assembly Language Programmer's Guide .......... 7-21 7.10 DEC C Language Reference Manual .............. 7-21 7.11 Guide to Preparing Product Kits .............. 7-21 7.11.1 Guide to Preparing Product Kits is now available on CD-ROM ........................ 7-21 7.11.2 Description of setld .................... 7-22 7.11.2.1 setld Functions ................... 7-22 7.11.2.2 Loading Software .................. 7-22 7.11.2.3 Configuring a Subset .............. 7-24 7.11.2.4 Verifying a Subset ................ 7-24 7.11.2.5 Removing Software ................. 7-24 7.12 Online Help Volumes. ......................... 7-25 Contents xvii 7.12.1 General Problems ........................ 7-26 7.12.2 Integration ............................. 7-27 7.12.3 Help Volumes by Application ............. 7-27 7.13 Online PostScript Format Documentation ....... 7-29 7.13.1 PostScript Manuals Replacing Online or Printed Volumes ............................ 7-34 8 Features and Interfaces Scheduled for Retirement 8.1 Retired in This Release ....................... 8-1 8.2 Nonconforming Curses Library .................. 8-2 8.3 ACC ........................................... 8-2 8.4 Kernel Build Procedures ....................... 8-3 8.5 TURBOchannel Denali Graphics .................. 8-3 8.6 dbx Debugger .................................. 8-4 8.7 Nemacs ........................................ 8-4 8.8 Security Interfaces ........................... 8-5 8.9 Security Windows-Based Administration Utilities . 8-5 8.10 System Management Utilities .................. 8-6 8.11 BSD TTY-NAME ................................. 8-6 8.12 NC and NL Interfaces in the Standard C Library . 8-6 8.13 Desktop Applications ......................... 8-7 8.14 SCSI Device Names ............................ 8-7 8.15 POSIX 1003.4a (draft 4) pthread Routines in DECthreads .................................... 8-8 8.16 DECthreads CMA Interface ..................... 8-8 8.17 Functions Retired from libc .................. 8-8 8.18 AdvFS Quota Commands ......................... 8-8 xviii Contents 8.19 LVM-to-LSM Migration Tools ................... 8-9 8.20 OSF/Motif Version 1.1.3 ...................... 8-9 8.21 XIE Version 3.0 X Client Extension ........... 8-10 8.22 ULTRIX Remote Installation (RIS) Support ..... 8-10 8.23 Disk Space Requirement for Installation ...... 8-10 8.24 MSB Driver ................................... 8-10 8.25 C Library Functions and POSIX P1003.1C ....... 8-11 A Maximum System Limits A.1 Maximum System Limits ......................... A-1 B Additional Notes B.1 Demonstration Program dxmandel ................ B-1 B.2 Additional Bootable Tape Restrictions ......... B-1 B.3 Maximum System Limits ......................... B-2 B.4 Remote Installation Services (RIS) Version Requirement ................................... B-2 B.5 Upsolete Files After an Update Installation ... B-2 Index Tables 2-1: Layered Product Versions ...................... 2-5 6-1: CalComp DrawingBoard III Tablet Configuration Options and Values ............................ 6-2 Contents xix About This Manual This manual contains release notes for Digital UNIX[1] Version 4.0. The release notes are available in both hardcopy and an HTML version you can view with the Netscape Navigator. Digital has changed the name of its UNIX operating system from DEC OSF/1 to Digital UNIX. The new name reflects Digital's commitment to UNIX and its conformance to UNIX standards. This manual also describes significant new and changed features in this version of the Digital UNIX operating system and lists features and interfaces scheduled for retirement in future releases. _A_u_d_i_e_n_c_e These release notes are for the person who installs the product and for anyone using the product following installation. _O_r_g_a_n_i_z_a_t_i_o_n This manual is organized as follows: Chapter 1 Contains an overview of new and changed features. This chapter is also part of the online (HTML) book _N_e_w _a_n_d _C_h_a_n_g_e_d _F_e_a_t_u_r_e_s. Chapter 2 Contains installation notes and subset sizes. Chapter 3 Contains processor-specific information. Chapter 4 Contains information about the base operating system software. Chapter 5 Contains information about the development environment. _________________________ [1] Registered trademark Chapter 6 Contains information about the window system software. Chapter 7 Contains information about the documentation. Chapter 8 Contains information about features scheduled for removal in future versions of Digital UNIX. This chapter is also part of the on-line (HTML) book _N_e_w _a_n_d _C_h_a_n_g_e_d _F_e_a_t_u_r_e_s. Appendix A Contains information about the maximum system limits. Appendix B Contains release notes that arrived after the base level was shipped. These notes are included in the hardcopy version but are not in the online version due to time constraints. _R_e_l_a_t_e_d _D_o_c_u_m_e_n_t_s You should have the following documentation available during the installation of this release. +o The hardware documentation for your system +o The online or hardcopy reference pages +o The Bookreader book files that are provided on the CD-ROM The printed version of the Digital UNIX documentation set is color coded to help specific audiences quickly find the books that meet their needs. (You can order the printed documentation from Digital.) This color coding is reinforced with the use of an icon on the spines of books. The following list describes this convention: _____________________________________________________ Audience Icon Color Code _____________________________________________________ General users G Blue System and network administrators S Red Programmers P Purple Device driver writers D Orange Reference page users R Green xx About This Manual _____________________________________________________ Audience Icon Color Code _____________________________________________________ _____________________________________________________ Some books in the documentation set help meet the needs of several audiences. For example, the information in some system books is also used by programmers. Keep this in mind when searching for information on specific topics. The _D_o_c_u_m_e_n_t_a_t_i_o_n _O_v_e_r_v_i_e_w, _G_l_o_s_s_a_r_y, _a_n_d _M_a_s_t_e_r _I_n_d_e_x provides information on all of the books in the Digital UNIX documentation set. _R_e_a_d_e_r'_s _C_o_m_m_e_n_t_s Digital welcomes any comments and suggestions you have on this and other Digital UNIX manuals. You can send your comments in the following ways: +o Fax: 603-881-0120 Attn: UEG Publications, ZK03- 3/Y32 +o Internet electronic mail: _r_e_a_d_e_r_s__c_o_m_m_e_n_t@_z_k_3._d_e_c._c_o_m A Reader's Comment form is located on your system in the following location: /usr/doc/readers_comment.txt +o Mail: Digital Equipment Corporation UEG Publications Manager ZK03-3/Y32 110 Spit Brook Road Nashua, NH 03062-9987 A Reader's Comment form is located in the back of each printed manual. The form is postage paid if you mail it in the United States. Please include the following information along with your comments: +o The full title of the book and the order number. (The order number is printed on the title page of About This Manual xxi this book and on its back cover.) +o The section numbers and page numbers of the information on which you are commenting. +o The version of Digital UNIX that you are using. +o If known, the type of processor that is running the Digital UNIX software. The Digital UNIX Publications group cannot respond to system problems or technical support inquiries. Please address technical questions to your local system vendor or to the appropriate Digital technical support office. Information provided with the software media explains how to send problem reports to Digital. _C_o_n_v_e_n_t_i_o_n_s The following conventions are used in this guide: % A percent sign represents the C shell $ system prompt. A dollar sign represents the system prompt for the Bourne and Korn shells. # A number sign represents the superuser prompt. % cat Boldface type in interactive examples indicates typed user input. file Italic (slanted) type indicates variable values, placeholders, and function argument names. [ | ] In syntax definitions, brackets { | } indicate items that are optional and braces indicate items that are required. Vertical bars separating items inside brackets or braces indicate that you choose one item from among those listed. . . . In syntax definitions, a horizontal ellipsis indicates that the preceding item can be repeated one or more times. xxii About This Manual _c_a_t(1) A cross-reference to a reference page includes the appropriate section number in parentheses. For example, _c_a_t(1) indicates that you can find information on the _c_a_t command in Section 1 of the reference pages. Ctrl/_x This symbol indicates that you hold down the first named key while pressing the key or mouse button that follows the slash. In examples, this key combination is enclosed in a box (for example, ). About This Manual xxiii New and Changed Features 1 This chapter provides brief descriptions of features that are new to the Digital UNIX system in this release or have changed significantly from previous releases. _1._1 _C_o_m_m_o_n _D_e_s_k_t_o_p _E_n_v_i_r_o_n_m_e_n_t The Common Desktop Environment (CDE) is the new default graphical user interface for Digital UNIX. The CDE environment is designed to provide common services across all UNIX platforms, including a consistent user interface for end users and a consistent development environment for application developers across multiple platforms. CDE on Digital UNIX is based on the X Window System Release 6 (X11R6) and CDE/Motif 1.0 (OSF/Motif 1.2.4), and supplies the following desktop services and applications: +o Desktop Services: Window Management Workspace Management SessionManagement Help Management File Management Style Management Data Typing/Actions Tooltalk Messaging System +o Desktop Applications: Calendar Calculator MIME-capable Mail Text Editor Icon Editor Terminal Emulator Application Integrator Print Queue Manager Windowing ksh Keyboard CDE is provided in seven software subsets that require a total of 57.81 MB of free disk space for installation. See the _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for information on the subset names, contents, and sizes. The CDE kit contains the following migration tools: +o _m_a_i_l_c_v mail conversion This utility converts your _d_x_m_a_i_l folders to the conventional mail format used by CDE _d_t_m_a_i_l. If you plan to use the _m_a_i_l_c_v utility to convert your existing mail folders, back up the folders before converting them. Do not use the -_d option with this version of the _m_a_i_l_c_v utility. +o _d_x_c_a_l_t_o_d_t_c_m calendar conversion This utility converts a DECwindows Calendar, _d_x_c_a_l_e_n_d_a_r, database for use with CDE Calendar, _d_t_c_m. _1._1._1 _T_h_e _C_D_E _V_i_d_e_o _T_o_u_r A brief multimedia tutorial of CDE is located on the Digital UNIX V4.0 Associated Products Volume 1 CD-ROM. Once installed, the video tour can be accessed via the application manager in the "Information" folder. The user simply needs to double click the "CDE Video Tour" icon. _1._1._2 _C_D_E _S_c_r_e_e_n _S_a_v_e_r_s The CDE session manager supports X11R6 screen saver extensions and you can now select animated screen savers instead of a blank screen. This release also enables the automatic locking of screens after a specified idle time. Both features can be modified or disabled from the CDE Style Manager menu. Click on the Screen icon, and select the options you want. _1._2 _X/_O_p_e_n-_C_o_m_p_l_i_a_n_t _C_u_r_s_e_s This release provides a new Curses implementation that incorporates the following sets of programming interfaces: +o X/Open Curses, Issue 4 +o System V Multinational Language Supplement (MNLS) +o Minicurses +o BSD Curses See Section 4.2 for information on usage and 1-2 New and Changed Features restrictions. _1._3 _X_1_1_R_6 This release of Digital UNIX supports Release 6 of the X Window System, Version 11 (X11R6) patchlevel 12. Prior versions of the operating system supported Release 5 (X11R5) patchlevel 26. The Digital UNIX port of X11R6 supports all the features and functionality of previous releases of Digital UNIX. It also supports all X Consortium standard features of X11R6. Included in new features are the following protocol extensions: +o BIG-REQUESTS Gives clients the ability to use requests that are arbitrarily large, rather than being limited to the size restriction of the core protocol. This can result in a significant performance improvement for applications that use large requests. +o DOUBLE-BUFFER Enables double buffering, using the new X Consortium standard. +o XIE (updated) Complete implementation of full XIE 5.0 protocol with a few exceptions. +o XKEYBOARD (Xkb) See the following section. _1._3._1 _T_h_e _X _K_e_y_b_o_a_r_d _E_x_t_e_n_s_i_o_n _f_o_r _X_1_1_R_6 (_X_K_B) The XKB (X Keyboard) server extension is new for X11R6 and for Digital UNIX Version 4.0. XKB enhances control and customization of the keyboard under the X Window System by providing the following: +o Support for the ISO9996 standard for keyboard layouts. +o Compatibility with the core X keyboard handling (no client modifications are required). New and Changed Features 1-3 +o Standard methods for handling keyboard LEDs and locking modifiers such as CapsLock and NumLock. +o Support for keyboard geometry. In addition, the X11R5 AccessX server extension for users with physical impairments has been incorporated into the XKB server extension. X11R5 applied to versions of Digital UNIX that preceded this release. These accessibility features include StickyKeys, SlowKeys, BounceKeys, MouseKeys, and ToggleKeys, and control over the autorepeat delay and rate. Several applications that make use of XKB features are also new with Digital UNIX version 4.0. These applications include _X_d_e_c, _x_k_b_c_o_m_p, _x_k_b_p_r_i_n_t, _x_k_b_d_f_l_t_m_a_p, _d_x_k_b_l_e_d_p_a_n_e_l, _d_x_k_e_y_b_o_a_r_d, and _a_c_c_e_s_s_x. Refer to the reference pages for more information. Note that the final revision of the X Keyboard Extension, XKB Version 1.0, will be different from XKB Version 0.65, which is shipping with this release. Avoid creating code that directly references the XKB API and data structures. Any X clients created with direct references must be recompiled and relinked when XKB Version 1.0 is shipped in a future release. You may also have to modify your source code. _1._4 _D_X_I_m_a_g_e_v_i_e_w DXImageview version 1.0 is an OSF/Motif application for viewing a variety of image file types such as GIF and JPEG. DXImageview supports the Common Desktop Environment (CDE) recommended integration for applications. DXImageview is provided in the subset _O_S_F_C_D_E_A_P_P_S_4_0_0 and is installed as /_u_s_r/_b_i_n/_X_1_1/_d_x_i_m_a_g_e_v_i_e_w. The -_h_e_l_p option displays information on using the application. _1._5 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s The following new or changed commands and utilities are available in this release. _1._5._1 _C_h_a_n_g_e_s _t_o _M_t_o_o_l_s _M_t_o_o_l_s software is included in the _O_S_F_D_O_C_T_O_O_L_S_4_0_0 subset. In prior releases, the software was installed by an optional worldwide support subset. 1-4 New and Changed Features _1._5._2 _T_h_e _s_e_n_d_m_a_i_l _U_t_i_l_i_t_y _S_u_p_p_o_r_t_s _C_o_n_f_i_g_u_r_a_b_l_e _G_E_C_O_S _F_u_z_z_y _M_a_t_c_h_i_n_g The _s_e_n_d_m_a_i_l utility now allows the user to configure the fuzzy logic for mail delivery. Previously, if the recipient's address did not precisely match any of the user names on the host, a best-match algorithm was applied against the GECOS field in the _p_a_s_s_w_d file. If a unique best-match was found, the mail was delivered to this user. This behavior is now run- time configurable using the -_o_G option on the command-line. See _s_e_n_d_m_a_i_l._c_f(4) for more information. _1._5._3 _d_f _S_u_p_p_o_r_t_s _L_a_r_g_e _F_i_l_e _S_y_s_t_e_m_s The field width for the _I_u_s_e_d and _I_f_r_e_e fields in the output of the _d_f command has been increased to accommodate 12 digits when using the -_i switch. This modification was made to support very large file systems where the number of inodes could exceed the field width that was previously set aside for these fields. _1._5._4 _C_o_m_p_r_e_s_s_e_d _R_e_f_e_r_e_n_c_e _P_a_g_e_s To economize on disk space, reference pages are now shipped in compressed format. Compressed files were created with the /_u_s_r/_b_i_n/_g_z_i_p utility. The _m_a_n and _x_m_a_n utilities automatically uncompress the reference pages. If required, you can uncompress reference page files manually with the /_u_s_r/_b_i_n/_g_u_n_z_i_p utility. The _c_a_t_m_a_n command has also been enhanced to work with compressed _c_a_t_m_a_n files. All three commands, _m_a_n, _x_m_a_n and _c_a_t_m_a_n, still provide support for uncompressed manpages. The CDE online help viewer also automatically uncompresses reference pages when they are accessed via a hyperlink in a help volume. For more information, refer to the _m_a_n(5) and the _c_a_t_m_a_n(8) reference pages. _1._5._5 _E_n_h_a_n_c_e_m_e_n_t_s _t_o _t_e_r_m_i_n_f_o Terminal support has been enhanced to support non- Digital terminals. Entries have been added to the _t_e_r_m_i_n_f_o databases and the _t_e_r_m_c_a_p file to enable this support. New tools have also been added to New and Changed Features 1-5 assist users in modifying or porting other _t_e_r_m_c_a_p and _t_e_r_m_i_n_f_o entries to Digital UNIX. These include the following: +o _c_a_p_t_o_i_n_f_o - Converts _t_e_r_m_c_a_p files to _t_e_r_m_i_n_f_o entries. +o _i_n_f_o_c_m_p - Uncompiles and, if required, compares _t_e_r_m_i_n_f_o entries. The _t_p_u_t and _t_i_c utilities have also been enhanced. _1._5._6 _G_N_U _e_m_a_c_s _V_e_r_s_i_o_n _1_9._2_8 GNU emacs has been updated to Version 19.28. This version is not upwardly compatible with GNU emacs Version 18.5, the previous version shipped with Digital UNIX. Refer to the appropriate GNU emacs documentation in /_u_s_r/_l_i_b/_e_m_a_c_s/_e_t_c. _1._5._7 _N_e_t_s_c_a_p_e _N_a_v_i_g_a_t_o_r This release contains Version 1.12I of the Netscape Navigator World Wide Web browsing program. Invoke the Netscape Navigator from a CDE desktop icon, located in the CDE Application Manager's Desktop_Apps group. The Netscape Navigator can be invoked directly from the command line by running /_u_s_r/_b_i_n/_X_1_1/_n_e_t_s_c_a_p_e. You can access detailed help on the Netscape Navigator through the help menus. A Digital UNIX home page can be found in /_u_s_r/_d_o_c/_n_e_t_s_c_a_p_e in the the file named _D_i_g_i_t_a_l__U_N_I_X._h_t_m_l. The home page contains links to helpful documentation, including a local copy of the _N_e_t_s_c_a_p_e _N_a_v_i_g_a_t_o_r _U_s_e_r'_s _H_a_n_d_b_o_o_k (consider adding this link to your list of Netscape bookmarks). The Digital UNIX _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e contains information on how to set up Netscape. See Chapter 6, which covers postinstallation setup tasks. _1._5._8 _d_x_t_e_r_m The _d_x_t_e_r_m terminal utility has the following new features: +o Default resource file naming scheme +o A _l_o_g_i_n_S_h_e_l_l resource 1-6 New and Changed Features +o A _u_s_e_W_M_H_i_n_t_s resource See the _d_x_t_e_r_m(1X) reference page for more information. _1._5._9 _P_e_r_f_o_r_m_a_n_c_e _M_a_n_a_g_e_r Performance Manager is a real-time performance monitor that allows users to detect and correct performance problems. Graphs and charts can show hundreds of different system values, including CPU performance, memory usage, disk transfers, file- system capacity, and network efficiency. Thresholds can be set to alert you to correct a problem when it occurs, commands can be run on multiple nodes from the graphical user interface, and archives of data can be kept for high-speed playback or long-term trend analysis. _1._5._1_0 _u_t_i_l_u_p_d_a_t_e A new utility, _u_t_i_l_u_p_d_a_t_e, updates the _s_e_t_l_d, and optionally _r_i_s and _d_m_u utilities on servers that are running a Version of Digital UNIX prior to Version 4.0. It is necessary to run this utility on the server prior to attempting to serve Digital UNIX Version 4.0 clients. The _s_e_t_l_d, _r_i_s, and _d_m_u utilities have been modified for Version 4.0 to allow them to work with the new format of the distribution media. For more information on the use of this utility, refer to the _S_h_a_r_i_n_g _S_o_f_t_w_a_r_e _o_n _a _L_o_c_a_l _A_r_e_a _N_e_t_w_o_r_k manual. _1._5._1_1 _B_o_o_t_a_b_l_e _T_a_p_e This release introduces the ability to create a standalone bootable tape of the operating system. You can boot from the bootable tape as easily as you can boot from CD-ROM or a RIS area, but without the overhead of selecting or installing subsets. When you restore your system from the bootable tape, you must reconfigure your system using the System Management applications. You will need to adjust system parameters, such as the host name or IP address, The binaries and shell scripts needed to create and restore a bootable tape are installed with the base operating system. The files reside in _O_S_F_B_I_N_C_O_M_4_0_0 and no other subsets are needed. _O_S_F_B_I_N_C_O_M_4_0_0 is the New and Changed Features 1-7 Kernel Header and Common Files (Kernel Build Environment) subset. The files used by the bootable tape utility include: +o /_u_s_r/_l_i_b/_s_a_b_t/_e_t_c/_f_s_t_a_b +o /_u_s_r/_l_i_b/_s_a_b_t/_e_t_c/_i_n_i_t_t_a_b +o /_u_s_r/_l_i_b/_s_a_b_t/_e_t_c/_p_r_o_f_i_l_e +o /_u_s_r/_l_i_b/_s_a_b_t/_s_b_i_n/_f_i_n_d_e_r +o /_u_s_r/_l_i_b/_s_a_b_t/_s_b_i_n/_p_i_c_k_a_p_a_r_t +o /_u_s_r/_s_y_s/_b_i_n/_b_t_c_r_e_a_t_e +o /_u_s_r/_s_y_s/_b_i_n/_b_t_e_x_t_r_a_c_t +o /_u_s_r/_s_y_s/_b_i_n/_f_s_m_r_g +o /_u_s_r/_s_y_s/_b_i_n/_m_k_s_a_s_t_a_p_e +o /_u_s_r/_s_y_s/_b_i_n/_m_k_t_a_p_e +o /_u_s_r/_s_y_s/_b_i_n/_p_m_e_r_g_e +o /_u_s_r/_s_y_s/_b_i_n/_s_b_o_o_t You use the _b_t_c_r_e_a_t_e utility to create a standalone bootable tape. To extract and restore file systems from tape at the single-user level, you use the _b_t_e_x_t_r_a_c_t utility. For more information, see the _b_t_c_r_e_a_t_e(8) and _b_t_e_x_t_r_a_c_t(8) reference pages. See Section 4.5.2 for information on supported systems and current restrictions on use. _1._5._1_2 _P_a_r_t_i_t_i_o_n _O_v_e_r_l_a_p _C_h_e_c_k_s _A_d_d_e_d _t_o _D_i_s_k _U_t_i_l_i_t_i_e_s Partition overlap checks have been enhanced or added to the following commands: newfs ufs_fsck mount addvol rmvol rmfdmn swapon voldisk voldisksetup The checks ensure that partitions will not be overwritten if they are marked in use in the _f_s_t_y_p_e field on the disk label. The overlap checks also ensure that no overlapping partition is marked in 1-8 New and Changed Features use. If a partition or an overlapping partition has an in-use _f_s_t_y_p_e field in the disk label, the following commands inquire interactively if a partition can be overwritten or not: newfs mkfdmn addvol swapon voldisk voldisksetup Refer to the reference pages for more information. Partition overlap checks have been generalized by creating two library functions: _c_h_e_c_k__u_s_a_g_e and _s_e_t__u_s_a_g_e. Two new _f_s_t_y_p_e values have been added: _F_S__R_A_W and _F_S__D_B. For example, the library function _s_e_t__u_s_a_g_e could be used by database applications to set the _f_s_t_y_p_e field of a disk partition that is in use by the database. Similarly, _c_h_e_c_k__u_s_a_g_e can be used to determine the usage of a disk partition or any overlapping partition. _1._5._1_3 _s_c_s_i_m_g_r _U_t_i_l_i_t_y _f_o_r _C_r_e_a_t_i_n_g _D_e_v_i_c_e _S_p_e_c_i_a_l _F_i_l_e_s The _s_c_s_i_m_g_r utility creates device special files for newly attached disk and tape devices. This utility is automatically invoked at system boot time. You can execute the command to add device special files for all disk and tape devices attached to a specified SCSI bus at any time. See the _s_c_s_i_m_g_r(8) reference page for further details. _1._6 _S_y_s_M_a_n _S_y_s_t_e_m _M_a_n_a_g_e_m_e_n_t _A_p_p_l_i_c_a_t_i_o_n_s This release includes a new suite of graphical single system management applications called SysMan. These applications support installation, configuration, daily administration, and monitoring and tuning. Some of the SysMan applications require you to have superuser privileges or offer a restricted interface to non-privileged users. At installation time, you can use the graphical Installation Setup application to select software and configure disks. The graphical applications are integrated into the Common Desktop Environment (CDE). The SysMan applications are available from the CDE front panel by clicking on the Application Manager icon and New and Changed Features 1-9 double clicking on the System_Admin group icon. There are five groups of system management utilities: +o Configuration The configuration applications modify system files that control various aspects of network connectivity and system configuration. +o Daily Administration The daily administration applications manage users, file systems, remote hosts, licenses, and backup; one application assists you in shutting down the system. +o Monitoring and tuning The monitoring and tuning applications monitor processes and tune kernel parameters. +o Storage management The storage management applications manage disk organization and performance. +o Tools The tools provide quick status reports. The following sections list the system management utilities. _1._6._1 _I_n_s_t_a_l_l_a_t_i_o_n This release provides full installations for new systems, and update installations to update systems from Digital UNIX Version 3.2C, Version 3.2D-1, or Version 3.2D-2 to Digital UNIX 4.0. _1._6._1._1 _N_e_w _I_n_s_t_a_l_l_a_t_i_o_n _U_s_e_r _I_n_t_e_r_f_a_c_e_s Two new user interfaces are available for the Digital UNIX full installation process: +o A text-based, menu-driven interface +o A graphical interface The type of interface presented during the full installation is determined automatically based on your hardware. Systems with graphical consoles and 32MB or greater main memory will provide a graphical interface to the installation. Systems with consoles 1-10 New and Changed Features that do not have graphics capabilities or have insufficient memory to support graphical installations provide a text-based interface. _1._6._1._2 _N_e_w _F_o_r_m_a_t _o_f _D_i_s_t_r_i_b_u_t_i_o_n _M_e_d_i_a As in previous releases, there are two types of media to install the Digital UNIX operating system onto your system: +o From a CD-ROM that contains the Digital UNIX base operating system Version 4.0 +o Over a network connection to a remote installation services (RIS) server that is serving Digital UNIX Version 4.0 However, for Version 4.0, the CD-ROM contains file systems that are laid out just as the software would be installed on the system and contains directly accessible _r_o_o_t, /_u_s_r, and /_v_a_r areas. This format makes every operating system command and utility available to the installation process. This means that UNIX commands required for recovery procedures such as restoring corrupt file systems are readily available even if your operating system is not yet fully functional. The new format also eliminates the need for the environment previously known as the Standalone Environment, which was a primitive, limited operating system environment. _1._6._1._3 _I_n_s_t_a_l_l_a_t_i_o_n _N_a_m_e _C_h_a_n_g_e_s In Digital UNIX Version 4.0, you can perform a default or custom full installation. In previous releases, these installation types were called basic and advanced, respectively. The installation procedure still provides access to a UNIX shell that lets you recover from serious system problems such as root file system corruption or to perform general file system or disk maintenance tasks before or during the installation. In previous releases, this option was called the System Management option. In Version 4.0, it is known as the UNIX Shell. _1._6._1._4 _E_n_h_a_n_c_e_m_e_n_t_s _t_o _t_h_e _I_n_s_t_a_l_l_a_t_i_o_n _P_r_o_c_e_d_u_r_e The following enhancements have been made to the installation procedure: New and Changed Features 1-11 +o During Custom installations, dependencies between optional software subsets are checked and the additional software is selected automatically. +o The amount of space remaining in the _r_o_o_t, /_u_s_r, and /_v_a_r areas is displayed as you select each optional software subset. +o If you are using the graphical interface, the custom installation provides access to the graphical disk partitioning utility for you to resize disk partitions. +o Online help is available for text-based and graphical installations. _1._6._1._5 _C_l_o_n_e_d _I_n_s_t_a_l_l_a_t_i_o_n_s The ability to perform a cloned installation is available in this release. A cloned installation enables you to duplicate the file system layout, file system type, and software subset selections from a similar system that has already been installed with Digital UNIX Version 4.0. Installation cloning can only be performed using RIS. If your system is registered to a RIS environment and has a configuration description file (CDF), the installation procedure retrieves the CDF and uses the system configuration information stored in the CDF to configure and install your system. _1._6._2 _C_o_n_f_i_g_u_r_a_t_i_o_n _A_p_p_l_i_c_a_t_i_o_n_s After a full installation, the SysMan Configuration Checklist will be displayed and can be used to configure your system. The order in which the applications are presented is a logical order in which to configure your system. You can skip any applications that are not needed for the current configuration. The following graphical applications are also available in the Configuration group under System_Admin in the Application Manager group once the installation is complete: +o BIND configuration +o Disk configuration +o Mail configuration 1-12 New and Changed Features +o Network configuration +o NFS configuration +o Print configuration +o Internationalization configuration In addition, the CDE Application Manager has a launchpoint for NIS Setup, which is a command-line interface for setting up Network Information Services (NIS), such as centralized password and user group files. Each of the graphical configuration applications has a corresponding setup script that can be used through a character-based interface. _1._6._2._1 _B_i_n_d _C_o_n_f_i_g_u_r_a_t_i_o_n The bind configuration utility, _b_i_n_d_c_o_n_f_i_g, provides streamlined management of BIND and DNS (Domain Name Services) services on a host. Bind configuration supports the creation and management of name service clients and servers and provides the complete range of configurations permitted by BIND. Use this application to: +o Configure the host system as a master name server for one or more zones, as a caching-only name server, or as a name service client. +o Initialize and maintain BIND data files and generate resource records to manage areas such as the host-name-to-address and address-to-host-name mappings, host information, host name aliasing, name servers, mail exchange, and the cache file root server list. +o Manage the BIND boot files including creation of multiple zones of authority, designation of forwarders, indication of slave configurations, specify the BIND database directory, and specify the BIND cache file name. +o Maintain the resolver configuration file, specify queriable name servers, and specify an alternate domain search list. +o Modify the desired services for the hosts database service selection configuration file (/_e_t_c/_s_v_c._c_o_n_f). New and Changed Features 1-13 +o Enable and disable the _n_a_m_e_d daemon. +o Modify the host name of the system by modifying the BIND local domain name of the system. _1._6._2._2 _D_i_s_k _C_o_n_f_i_g_u_r_a_t_i_o_n The disk configuration utility, _d_i_s_k_c_o_n_f_i_g, manages certain disk operations for the base system. Use this application to: +o Modify disk configuration parameters +o Display attribute information for existing disks +o Create file system partitions on a disk +o Add disk alias names _1._6._2._3 _M_a_i_l _C_o_n_f_i_g_u_r_a_t_i_o_n The mail configuration utility, _m_a_i_l_c_o_n_f_i_g, configures the _s_e_n_d_m_a_i_l utility. Use this application to: +o Set up the routing and delivery of mail for any of the following types of workstations: - A standalone computer - A mail client (where mail is handled by another computer) - A mail server that addresses and routes mail to other systems +o Use NFS to share mailboxes across multiple hosts, even standalone systems. _1._6._2._4 _N_e_t_w_o_r_k _C_o_n_f_i_g_u_r_a_t_i_o_n The network configuration utility, _n_e_t_c_o_n_f_i_g, manages network hardware and related services on a host. This application supports the configuration and management of networking adapters on a host, and provides maintenance of network services and related data 1-14 New and Changed Features files. Use this application to: +o Configure network hardware interfaces - Ethernet - FDDI - Token Ring +o Enable and disable the following daemons: - _g_a_t_e_d - _r_o_u_t_e_d - _r_w_h_o_d +o Configure the system as an IP router +o Add, modify and delete entries in the following files: - /_e_t_c/_r_o_u_t_e_s - /_e_t_c/_g_a_t_e_w_a_y_s - /_e_t_c/_h_o_s_t_s - /_e_t_c/_h_o_s_t_s._e_q_u_i_v - /_e_t_c/_n_e_t_w_o_r_k_s _1._6._2._5 _N_F_S _C_o_n_f_i_g_u_r_a_t_i_o_n The NFS configuration utility _n_f_s_c_o_n_f_i_g, manages the Network File System (NFS) and related processes on a host. Use this application to: +o Manage the configuration of the system as an NFS server, NFS client, or both. NFS client daemons are started only if the system is configured as a NFS client. +o Manage remote file systems by accessing the File Sharing application. +o Manage the configuration of the NFS daemons. New and Changed Features 1-15 _1._6._2._6 _P_r_i_n_t _C_o_n_f_i_g_u_r_a_t_i_o_n The print configuration utility, _p_r_i_n_t_c_o_n_f_i_g, manages the _p_r_i_n_t_c_a_p file, print daemon specific directories, and files. Use this application to: +o View lists of configured printers and available printer type definitions +o Select a printer from the list of configured printers +o Modify basic and advanced settings for a selected printer +o Designate a selected printer as the system default printer +o Verify configuration changes and make modifications without leaving the application +o Configure local printers (that is, printers connected from an stty port) and printers served remotely (that is, attached to another Digital UNIX host) +o Configure printers connected to a LAT application port +o Create and configure the LAT device and application port _1._6._2._7 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_z_a_t_i_o_n _C_o_n_f_i_g_u_r_a_t_i_o_n Internationalization configuration is available if the optional worldwide support subsets are installed. See Section 1.13 for more information. _1._6._3 _D_a_i_l_y _A_d_m_i_n_i_s_t_r_a_t_i_o_n _A_p_p_l_i_c_a_t_i_o_n_s There are eight applications for the daily administration of your system: +o Account Manager +o Archiver +o File Sharing 1-16 New and Changed Features +o Host Manager +o License Manager +o Shutdown +o System Information +o Audit Manager +o Display Window +o Power Management _1._6._3._1 _A_c_c_o_u_n_t _M_a_n_a_g_e_r The account manager utility, _d_x_a_c_c_o_u_n_t_s, is used to manage user accounts. It operates on both base security level systems and enhanced security (C2) level systems. You must have root privileges to modify account databases. Use NIS to centrally manage user accounts in a network environment. NIS allows participating systems to share a common set of _p_a_s_s_w_d and _g_r_o_u_p files. The account manager allows you manage both the local and NIS account databases. NIS uses a client-server model. To make changes to the NIS databases, you must run the account manager on the machine designated as the NIS server. The account manager offers views of each of the system databases. By default, the account manager starts by displaying the Local User view showing the contents of the /_e_t_c/_p_a_s_s_w_d file. The supported views are: +o Local Users ( /_e_t_c/_p_a_s_s_w_d) +o Local Groups ( /_e_t_c/_g_r_o_u_p) +o NIS Users ( /_v_a_r/_y_p/_s_r_c/_p_a_s_s_w_d) +o NIS Groups ( /_v_a_r/_y_p/_s_r_c/_g_r_o_u_p_s) Please refer to the account manager online help for more information. New and Changed Features 1-17 _1._6._3._2 _A_r_c_h_i_v_e_r The archiver utility, _d_x_a_r_c_h_i_v_e_r, provides graphical access to the _t_a_r, _c_p_i_o, _p_a_x, and _c_o_m_p_r_e_s_s commands. Use this application to: +o Copy and store multiple files to a single, named archive file or output device such as a tape or floppy disk +o Uncompress incoming archive files and compress newly created files +o Retrieve stored files from an archive. Archiver functions are classified as follows: +o Archiver input and output information The input and output areas provide icon containers and user text areas. You can drag icons that represent files and directories from the CDE File Manager, or icons representing tape and floppy drives from the system information application. Any icon that you can drag can also be dropped into the input icon container. Type the name of a file, directory, or device into the user input text area. +o Default Directory The Archiver requires you to choose whether to use absolute or relative pathnames. The use of absolute pathnames (those written out in full with an initial slash) and relative pathnames (those written without an initial slash) allows the archiver to control the placement of retrieved files. Files in an archive have either absolute or relative paths. Files with relative paths are restored to the current default directory. That is, they are restored to the directory that is displayed in the default directory area. _1._6._3._3 _F_i_l_e _S_h_a_r_i_n_g The file sharing utility, _d_x_f_i_l_e_s_h_a_r_e, allows the importing and exporting of NFS file systems. You can run it with or without superuser permissions. If you are not root, access to system files is restricted so that you can only view, but not modify, locally exported file systems and perform mounts to user directories. 1-18 New and Changed Features Use this application to: +o Display mounted NFS file systems that are exported through NFS from the local machine. +o Display file systems available for mounting from a remote set of hosts. +o Perform mount and unmount operations with the ability to modify valid options. +o Add entries to the /_e_t_c/_f_s_t_a_b file as permanent mount entries. +o Add, change, or delete NFS entries from /_e_t_c/_e_x_p_o_r_t file. _1._6._3._4 _H_o_s_t _M_a_n_a_g_e_r The host manager utility, _d_x_h_o_s_t_s, manages X clients. You can use this application to change X host permissions for hosts and to execute X applications remotely on a host. Other applications in this tool suite use it as a host name resource. Use this application to: +o Drag and drop application icons from the CDE Application Manager onto displayed hosts to execute the application remotely and send the display back to the local screen. +o Double click on a host to execute a default command remotely (defaulted to _x_t_e_r_m ). +o Add or remove a host to or from the _x_h_o_s_t access control list. +o Enable or disable X Window System access for all or selected hosts. _1._6._3._5 _L_i_c_e_n_s_e _M_a_n_a_g_e_r The license manager utility, _d_x_l_i_c_e_n_s_e_s, provides access to Digital's License Management Facility (LMF). This application allows you to: +o Add, delete, issue, and list Digital UNIX licenses New and Changed Features 1-19 +o Load a license from a file _1._6._3._6 _S_h_u_t_d_o_w_n _M_a_n_a_g_e_r The shutdown manager utility, _d_x_s_h_u_t_d_o_w_n, shuts down and optionally reboots your system. The following options are available: +o Halt - halts the system and displays the console prompt +o Single-user mode - brings the system to single- user mode +o Reboot - reboots the system +o Message only - sends a message as if a shutdown was initiated, but a shutdown action does not occur. When the main window expands, the following options are also available: +o Broadcast message - sends a broadcast to NFS Clients. +o Preshutdown script - enables you to specify a script to be run before the system is shut down. +o Fast - shuts down without a broadcast message and without performing file system checks when the system reboots. +o No disk sync - shuts down without flushing the system buffer cache. _1._6._3._7 _S_y_s_t_e_m _I_n_f_o_r_m_a_t_i_o_n The system information utility _d_x_s_y_s_i_n_f_o, displays and monitors system resources on a Digital UNIX system. Use this application to: +o Display the operating system version, amount of random access memory (RAM), and the number of CPUs on a system. +o Select the following views of system resources: 1-20 New and Changed Features - Activity displays the CPU percentage used. - Free Memory displays the current percentage of unused physical memory. - Available Swap shows the swap space available as a percentage of the total space on the swap device or devices. - File/Swap Warning Lights turns on the warning lights for file systems and swap space. - The File System Information area lists the mounted file systems. The user can select whether local, remote, or both local and remote file systems are displayed. For each file system, it shows the percentage of disk space used, the amount of disk space free, and an adjustable limit that triggers a warning light when a file system is full. - The Device Information area displays an icon for each disk drive, CD-ROM drive, tape drive, and floppy disk drive configured on the system. _1._6._3._8 _A_u_d_i_t _M_a_n_a_g_e_r The Audit Manager, _d_x_a_u_d_i_t, allows you to create audit reports. For more information see the _S_e_c_u_r_i_t_y manual and the _d_x_a_u_d_i_t(8) reference page. _1._6._4 _M_o_n_i_t_o_r_i_n_g _a_n_d _T_u_n_i_n_g _A_p_p_l_i_c_a_t_i_o_n_s The applications described in this section help you to monitor and tune your system. _1._6._4._1 _K_e_r_n_e_l _T_u_n_e_r The kernel tuner utility, _d_x_k_e_r_n_e_l_t_u_n_e_r, manages attributes of loadable kernel subsystems. Use the kernel tuner to: +o Display a list of kernel subsystems +o Display boot time and current values of kernel subsystem attributes +o Load values for kernel subsystem attributes from a file New and Changed Features 1-21 +o Modify boot time values of kernel subsystem attributes +o Modify current values of updatable kernel subsystem attributes +o Save values of kernel subsystem attributes to a file _1._6._5 _S_t_o_r_a_g_e _M_a_n_a_g_e_m_e_n_t The CDE Application Manager provides launchpoints for Storage Management applications in the System Admin group. The applications that are available depend on what software you have installed. A launchpoint for the Logical Storage Manager is available with the base operating system. _1._6._6 _T_o_o_l_s The CDE Application Manager provides launchpoints for Tools in the System Admin group. The System Management suite includes four launchpoints in this area. Each runs an output-only command in a window that permits you to repeat the command on demand or at intervals. The launchpoints and their commands are: +o I/O statistics: _i_o_s_t_a_t +o Network statistics: _n_e_t_s_t_a_t +o Virtual Memory statistics: _v_m_s_t_a_t +o Who>? _w +o System Messages: tail -f /var/adm/messages If you want to run another output-only command, you can run one of the commands in this group, then change the current command in the user interface. 1-22 New and Changed Features _1._7 _S_t_a_n_d_a_r_d_s This release complies with many new and changes standards. Refer to the _s_t_a_n_d_a_r_d_s(5) reference page for more information. _1._7._1 _R_e_a_l_t_i_m_e _I_s _C_o_m_p_l_i_a_n_t _W_i_t_h _t_h_e _F_i_n_a_l _P_O_S_I_X _1_0_0_3._1_b _S_t_a_n_d_a_r_d _I_n_t_e_r_f_a_c_e_s As of this release, Digital UNIX completes the implementation of the POSIX 1003.1b standard interface as approved by the IEEE standards board in September 1993 (IEEE Std 1003.1b-1993, Realtime Extension). See the Guide to Realtime Programming for more information. The new features are described in sections Section 1.8.11, Section 1.8.12, and Section 1.8.13. _1._7._2 _D_E_C_t_h_r_e_a_d_s _i_s _C_o_m_p_l_i_a_n_t _w_i_t_h _t_h_e _F_i_n_a_l _P_O_S_I_X _1_0_0_3._1_c _S_t_a_n_d_a_r_d _I_n_t_e_r_f_a_c_e_s As of this release, the DECthreads library _l_i_b_p_t_h_r_e_a_d._s_o implements the POSIX 1003.1c standard interface as approved by the IEEE standards board in June 1995 (IEEE Std 1003.1c-1995, POSIX System Application Program Interface). The new POSIX (pthread) interface supported with DECthreads is the most portable, efficient, and powerful programming interface for a multithreaded environment. These interfaces are defined by _p_t_h_r_e_a_d._h. See the _G_u_i_d_e _t_o _D_E_C_t_h_r_e_a_d_s for more information. _1._7._3 _D_E_C _C _C_o_m_p_i_l_e_r _C_o_m_p_l_i_e_s _W_i_t_h _I_S_O _C _9_4 In this release the DEC C compiler and _l_i_b_c implement the ISO C 94 standard. This behaviour is obtained by calling the DEC C compiler with the -_i_s_o_c_9_4 flag. This feature is not available with the -_o_l_d_c compiler option, which invokes the previous compiler. _1._8 _D_e_v_e_l_o_p_m_e_n_t _E_n_v_i_r_o_n_m_e_n_t This release includes the following enhancements to the development environment. _1._8._1 _T_c_l/_T_k _A_v_a_i_l_a_b_i_l_i_t_y Tcl/Tk is now available as part of the base operating system. Tcl/Tk is a public domain unencumbered New and Changed Features 1-23 scripting language and graphical tool kit. In addition to Tcl/Tk, a popular extension package, TclX is also included. TclX provides many UNIX extensions to the Tcl command language. Tcl version 7.4, Tk version 4.0, and TclX version 7.4 are included in this release. See the _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for information on how to identify and install the appropriate software subsets. The available programs are: +o /_u_s_r/_b_i_n/_t_c_l - A tcl shell with TclX extensions. +o /_u_s_r/_b_i_n/_t_c_l_s_h - A hard link to /_u_s_r/_b_i_n/_t_c_l. +o /_u_s_r/_b_i_n/_w_i_s_h_x - A Tcl/Tk/tclX shell. +o /_u_s_r/_b_i_n/_w_i_s_h - A hard link to /_u_s_r/_b_i_n/_w_i_s_h_x. +o /_u_s_r/_b_i_n/_t_c_l_h_e_l_p - A graphical help browser for tcl help. _1._8._2 _D_E_C _C++ The following changes have beem implemented for DEC C++. +o DEC C++ version 5.3 Class Library is now threadsafe Refer to the _D_E_C _C++ _C_l_a_s_s _L_i_b_r_a_r_y _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l for details on the threadsafe support, including a new Mutex Package. +o Complex division catches divide-by-zero errors The division routines within the Complex Library now catch divide-by-zero errors instead of signaling them. +o Iostream assignment operators For iostream assignment operators, there is no longer a memory leak when you use the *__w_i_t_h_a_s_s_i_g_n assignment operators to initialize an object for which you have called _x_a_l_l_o_c(). Previously, the memory allocated for the object by _x_a_l_l_o_c() was lost. +o String extraction operator The String extraction operator now takes care of dynamically allocating the String to accommodate 1-24 New and Changed Features the input. +o _i_o_s::_a_t_e mode When you open a file specifying _i_o_s::_a_t_e but not _i_o_s::_a_p_p to the _f_i_l_e_b_u_f _o_p_e_n() function, the file is no longer opened in _O__A_P_P_E_N_D mode. This incorrect behavior caused all data to be written to the end of the file, regardless of the current file position. +o Exception handling Various problems with exception handling have been fixed. Also, support for exception handling in DEC C++ version 5.3 has been added. +o Function _e_x_p() returns zero for underflow errors When the Complex Library _e_x_p() function detects an underflow error, the resulting value is now (0,0) instead of (+/- max-float, +/- max-float). +o Use of _c_l_o_g() and C++ Class Library iostream _c_l_o_g A single application is restricted from using both the math library function _c_l_o_g() and the iostream package's _c_l_o_g object. This restriction is due to the fact that _l_i_b_m and _l_i_b_c_x_x each contain a definition for the global symbol _c_l_o_g and those definitions are incompatible. Furthermore, applications which reference one of the _c_l_o_g symbols cannot include both -_l_c_x_x and -_l_m on their _l_d command line. An error will be generated by _l_d because _c_l_o_g is multiply defined. +o _c_a_t_c_h(...)clause The _c_a_t_c_h(...) clause now catches C structured exceptions. +o _f_s_t_r_e_a_m _c_l_o_s_e() clears the error state The _f_s_t_r_e_a_m, _i_f_s_t_r_e_a_m, and _o_f_s_t_r_e_a_m _c_l_o_s_e() member functions now clear the stream's error state when the close succeeds. Call the _c_l_e_a_r() member function after the call to _c_l_o_s_e(). _1._8._3 _R_e_p_l_a_c_e_m_e_n_t _o_f _t_h_e _p_i_x_i_e _U_t_i_l_i_t_y The previous version of the _p_i_x_i_e utility has been relocated to the file /_u_s_r/_o_p_t/_o_b_s_o_l_e_t_e/_u_s_r/_b_i_n/_p_i_x_i_e and is provided as part of the _O_S_F_O_B_S_O_L_E_T_E subset. The previous version of _p_i_x_i_e will be retired in a future release and is replaced with the Atom-based New and Changed Features 1-25 _p_i_x_i_e utility. A driver for the Atom-based _p_i_x_i_e is located in /_u_s_r/_b_i_n/_p_i_x_i_e, for backward compatibility with the previous version. The driver accepts the same switches recognized by the previous version. Refer to the _p_i_x_i_e(1) and _a_t_o_m(1) reference pages for more information on _p_i_x_i_e and general information on the Atom tools. _1._8._4 _S_o_f_t_w_a_r_e _D_e_v_e_l_o_p_m_e_n_t _E_n_v_i_r_o_n_m_e_n_t _R_e_p_a_c_k_a_g_i_n_g The Software Development Environment (SDE) has been repackaged to ease installation, simplify licensing, and create a product identity. The current SDE components have been repackaged into a single, new _O_S_F_S_D_E subset and all of the pieces outside the SDE have been moved into logical subsets, including: +o _O_S_F_I_N_C_L_U_D_E for all include files +o _O_S_F_L_I_B_A for all static libraries +o _O_S_F_P_G_M_R for commands outside the scope of the SDE Because the compiler is needed at installation time, some SDE components have remained in the mandatory _O_S_F_C_M_P_L_R_S subset. The Ladebug debugger subsets have been renamed to the _O_S_F* subset name prefix and can now be installed during a custom installation of Digital UNIX. These changes have been made on the Digital UNIX Operating System Volume 1 CD-ROM. The FUSE Porting Assistant has been added to the Digital UNIX kit on the Digital UNIX Associated Products Volume 1 CD-ROM. This is a tool to help port code to Digital UNIX from a variety of platforms and operating systems. The _O_S_F_S_D_E_C_D_E subset was also added to the Digital UNIX Operating System Volume 1 CD-ROM. It contains the files necessary to access DECladebug and the Porting Assistant from CDE. _1._8._5 _D_E_C _C _C_o_m_p_i_l_e_r The C compilers, _c_c and _c_8_9 on Digital UNIX have changed to Digital's DEC C compiler. The previous default C compiler is still a supported viable option and can be accessed by specifying -_o_l_d_c on the _c_c and _c_8_9 command lines. DEC C uses Digital's back-end compiler (GEM) technology, which has been specifically developed and 1-26 New and Changed Features optimized for use with Alpha systems. Both compilers have full binary compatibility with each other. _1._8._6 _I_n_i_t _E_x_e_c_u_t_i_o_n _O_r_d_e_r _M_o_d_i_f_i_e_d _f_o_r _S_t_a_t_i_c _E_x_e_c_u_t_a_b_l_e _F_i_l_e_s The execution order for _i_n_i_t routines in static executable files has been modified to more closely match the execution order for _i_n_i_t routines in dynamic executable files. The init routines loaded from an archive library will be executed prior to any init routines loaded from objects and archives occurring earlier on the linker command line. Prior to this change, _i_n_i_t routines were executed in the order they were encountered in processing the _l_i_n_k command from left to right. As a result, init order for static executable files was much different than the init order for equivalent shared executable files. For existing applications that rely on the static _i_n_i_to rder used in prior releases of Digital UNIX, the new linker option: -_o_l_d__i_n_i_t__o_r_d_e_r can be used to restore the strict left-to-right execution order for static executable files. _1._8._7 _P_C-_S_a_m_p_l_e _M_o_d_e _o_f _p_r_o_f _C_o_m_m_a_n_d The _p_r_o_f command's pc-sampling mode now supports profiling the shared libraries used by a program. Linking a call-shared program with the _c_c command's -_p switch causes the resulting program to profile both the call-shared executable file and all the shared libraries. The following command displays a combined profile: # _p_r_o_f -_a_l_l New -_a_l_l, -_i_n_c_o_b_j, -_e_x_c_o_b_j, and -_s_t_r_i_d_e switches for the PROFFLAGS environment variable enable you to request per-procedure profiling of the shared libraries or to select particular libraries to profile. Related enhancements are: +o Extended APIs to _m_o_n_i_t_o_r(), _m_o_n_s_t_a_r_t_u_p(), and _p_r_o_f_i_l() +o Use of 32-bit pc-sampling counters instead of 16- bit for _c_c -_p and _c_c -_p_g profiling ( _g_p_r_o_f), New and Changed Features 1-27 except for calls to the traditional _m_o_n_i_t_o_r() API. +o Improved reliability in profiling multithreaded programs, and reference page guidelines for use of _m_o_n_i_t_o_r__s_i_g_n_a_l() with threads. +o _p_r_o_f and _g_p_r_o_f checking. +o Profiling report formats are improved. See the _p_r_o_f(_1) and _m_o_n_i_t_o_r(_3) reference pages for further information. _1._8._8 _a_t_o_m _a_n_d _p_r_o_f _C_o_m_m_a_n_d_s _a_n_d _T_h_r_e_a_d_s The following _a_t_o_m and _p_r_o_f commands now profile the shared libraries used by a program: # _a_t_o_m -_t_o_o_l _p_i_x_i_e -_a_l_l and # _p_r_o_f -_p_i_x_i_e -_a_l_l Also, the _t_h_r_e_a_d_s environment for the_a_t_o_mmakes _p_i_x_i_e tool thread-safe, though per-thread counts are not recorded. See the _a_t_o_m (1), _p_r_o_f (1), and _p_i_x_i_e (5) reference pages for further information. _1._8._9 _T_h_r_e_a_d _I_n_d_e_p_e_n_d_e_n_t _S_e_r_v_i_c_e_s (_T_I_S) _I_n_t_e_r_f_a_c_e Digital UNIX Version 4.0 introduces the Thread Independent Services (TIS) application programming interface in the C run-time library _l_i_b_c. TIS provides services that assist in the development of thread-safe libraries. Thread synchronization may involve significant run- time cost, which is undesirable in the absence of threads. TIS enables thread-safe libraries to be built that are both efficient in the non threaded environment, yet provide the necessary synchronization in the threaded environment. When DECthreads (pthreads) are not active within the process, TIS executes only the minimum steps necessary. Code running in a non threaded environment does not encounter overhead incurred by the run-time synchronization that is necessary when the same code is run in a threaded environment. When 1-28 New and Changed Features DECthreads are active, the TIS functions provide the necessary thread-safe synchronization. _1._8._1_0 _H_i_g_h-_R_e_s_o_l_u_t_i_o_n _C_l_o_c_k Digital UNIX Version 4.0 has an optional high- resolution clock. To enable this option, add the following line to the kernel configuration file and rebuild the kernel: options MICRO_TIME The system clock ( _C_L_O_C_K__R_E_A_L_T_I_M_E) resolution as returned by _c_l_o_c_k__g_e_t_r_e_s will not change. Timer resolution remains the same. However, time as returned by the _c_l_o_c_k__g_e_t_t_i_m_e routine will now be extrapolated between the clock ticks. The granularity of the time returned will now be in microseconds. The time values returned are SMP safe, monotonically increasing, and have 1 microsecond as the apparent resolution. _1._8._1_1 _P_O_S_I_X _1_0_0_3._1_b _R_e_a_l_t_i_m_e _S_i_g_n_a_l_s Realtime signals have been implemented to conform to the POSIX 1003.1b standard. This new feature includes queued signals with optional data delivery, and 16 user-definable realtime signals. The following functions to support realtime signals were implemented: +o _s_i_g_q_u_e_u_e +o _s_i_g_t_i_m_e_d_w_a_i_t +o _s_i_g_w_a_i_t_i_n_f_o +o _t_i_m_e_r__g_e_t_o_v_e_r_r_u_n _1._8._1_2 _P_O_S_I_X _1_0_0_3._1_b _S_y_n_c_h_r_o_n_i_z_e_d _I/_O Synchronized I/O (file synchronization) has been implemented to conform to the POSIX 1003.1b standard. New functions for synchronized I/O under the UFS and ADVFS file systems include: +o _a_i_o__f_s_y_n_c Asynchronously writes changes in a file to permanent storage New and Changed Features 1-29 +o _f_d_a_t_a_s_y_n_c Writes data changes in a file to permanent storage The _o_p_e_n function now takes the following new flags for synchronized I/O: +o _O__D_S_Y_N_C Ensures synchronized I/O data integrity of the file accessed +o _O__R_S_Y_N_C Used for synchronized I/O read operations _1._8._1_3 _P_O_S_I_X _1_0_0_3._1_b __P_O_S_I_X__C__S_O_U_R_C_E _S_y_m_b_o_l For applications conforming to POSIX 1003.1b, the __P_O_S_I_X__4_S_O_U_R_C_E macro is supported for this release, but will be retired with the next release of Digital UNIX. The macro __P_O_S_I_X__4_S_O_U_R_C_E is part of an obsolete draft standard and is supported in this release for compatibility only. When possible, existing applications which use __P_O_S_I_X__4_S_O_U_R_C_E should be modified to use __P_O_S_I_X__C__S_O_U_R_C_E instead. The __P_O_S_I_X__C__S_O_U_R_C_E macro is associated with a value, which allows an application to specify the namespace it requires. However, as a general rule, avoid explicitly defining standards macros when compiling your applications. For most applications, the header file _u_n_i_s_t_d._h provides the standards definitions needed. _1._8._1_4 _D_i_g_i_t_a_l _P_o_r_t_i_n_g _A_s_s_i_s_t_a_n_t The Digital Porting Assistant is a Motif-based tool to help you port your C, C++, and FORTRAN source code to Digital UNIX from other UNIX and proprietary platforms, including OpenVMS. The Porting Assistant provides the following features: +o uncovers 32-bit dependencies +o Checks your makefile commands and options +o Helps find functions that your application needs +o Helps develop code segments specific to Digital UNIX 1-30 New and Changed Features +o Provides additional information on porting your application The Porting Assistant is licensed and provided to you with Digital UNIX Developers' Toolkit but requires separate installation. To install Version 2.0 of the Porting Assistant, install subsets _P_R_T_B_A_S_E_2_0_0 and _P_R_T_M_A_N_2_0_0 (and their dependencies) from the _D_i_g_i_t_a_l _U_N_I_X _A_s_s_o_c_i_a_t_e_d _P_r_o_d_u_c_t_s _V_o_l_u_m_e _1 CD-ROM.. _1._9 _N_e_t_w_o_r_k_i_n_g The following networking enhancements have been implemented. _1._9._1 _N_e_w _V_e_r_s_i_o_n _o_f _t_h_e _g_a_t_e_d _D_a_e_m_o_n This release includes a new version of the _g_a_t_e_d routing daemon. The update installation procedure will detect if your system is configured to run the _g_a_t_e_d routing daemon. If the Digital-supplied _g_a_t_e_d is detected then the /_e_t_c/_g_a_t_e_d._c_o_n_f file is moved to /_e_t_c/_o_g_a_t_e_d._c_o_n_f. Otherwise, if a user supplied or customized _g_a_t_e_d is detected, then both the /_e_t_c/_g_a_t_e_d._c_o_n_f and the /_u_s_r/_s_b_i_n/_g_a_t_e_d are saved with the ._P_r_e_U_P_D suffix. When the system is installed, the new gated R3.5 is the default version in /_u_s_r/_s_b_i_n/_g_a_t_e_d. The old _g_a_t_e_d version 1.9 is supplied in /_u_s_r/_s_b_i_n/_o_g_a_t_e_d. Also, corresponding older _g_a_t_e_d reference pages are saved with an _o prefix. _1._9._2 _D_y_n_a_m_i_c _H_o_s_t _C_o_n_f_i_g_u_r_a_t_i_o_n _P_r_o_t_o_c_o_l (_D_H_C_P) This release contains both a client and a server Dynamic Host Configuration Protocol (DHCP) daemon. For DHCP client configuration, use the _n_e_t_c_o_n_f_i_g utility. For configuration of client parameters on the DHCP server, use the /_u_s_r/_b_i_n/_X_1_1/_x_j_o_i_n utility, which provides a graphical user interface to the /_e_t_c/_b_o_o_t_p_t_a_b file. For more information on DHCP, refer to the _j_o_i_n_c(8) and _j_o_i_n_d(8) reference pages. New and Changed Features 1-31 _1._9._3 _P_o_i_n_t-_t_o-_P_o_i_n_t _P_r_o_t_o_c_o_l (_P_P_P) This release supports Point-to-Point Protocol PPP, including support for BSD-style compression of entire packets. This is a negotiated option. If a foreign peer cannot handle this, it should be gracefully rejected via the _P_r_o_t_o_c_o_l-_R_e_j_e_c_t of LCP. When using PPP with modems doing compression, it may be desirable to force no BSD-style compression. To do this, put -_b_s_d_c_o_m_p in either /_e_t_c/_p_p_p/_o_p_t_i_o_n_s, or on the _p_p_p_d command line. PPP now has a configurable (at boot time) number of interfaces. The default is 1. To specify a higher value, add the following line to the /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b file and reboot the system: ppp:nppp=x PPP documentation is available in the _p_p_p_d(8), _p_p_p_s_t_a_t_s(8), and _c_h_a_t(8), reference pages and in the _N_e_t_w_o_r_k _A_d_m_i_n_i_s_t_r_a_t_i_o_n Guide. _1._9._4 _N_F_S _o_v_e_r _T_C_P This release contains Digital's first implementation of NFS support over the TCP transport. Previously, only the UDP transport was available. UDP is still available and may still be the preferred transport in local area networks. For NFS access over wide area, congested, or lossy networks, TCP may offer better performance. Use the _n_f_s_s_e_t_u_p script or the _n_f_s_c_o_n_f_i_g utility to enable TCP on the NFS server. The _n_f_s_i_o_d daemon has been changed to spawn kernel threads (instead of forking multiple processes as it did previously). Each _n_f_s_i_o_d thread can handle UDP or TCP mounts, so the command _n_f_s_i_o_d still accepts one argument. _1._9._5 _E_x_t_e_n_s_i_b_l_e _S_N_M_P A new SNMP architecture is present in this release. The SNMP daemon, _s_n_m_p_d, is now an extensible master agent. End user programmers can develop subagent programs that communicate with _s_n_m_p_d to implement their MIBs on Digital UNIX systems. 1-32 New and Changed Features The base operating system MIB support is implemented in a subagent program called _o_s__m_i_b_s, which is started/stopped automatically with _s_n_m_p_d. _1._9._6 _S_N_M_P _M_I_B _s_u_p_p_o_r_t This release supports the Host Resources MIB (RFC 1514). The MIB support daemon must query the system's devices to retrieve information required for this MIB. This query occurs when the daemon starts, and subsequently whenever a relevant SNMP request arrives. This device querying is the default behavior, and may be configured off. See the _s_n_m_p_d(8) reference page for more information about configuring the SNMP agent. _1._9._7 _t_e_l_n_e_t _a_n_d _m_r_o_u_t_e_d The following new features were implemented: +o A _N_E_W-_E_N_V_I_R_O_N parameter was added to implement RFCs 1571 and 1572 for _t_e_l_n_e_t +o Version 3.6 of _m_r_o_u_t_e_d was added, including the utilities: - _m_t_r_a_c_e - _m_a_p-_m_b_o_n_e - _m_r_i_n_f_o _1._9._8 _N_e_t_w_o_r_k _T_i_m_e _P_r_o_t_o_c_o_l (_N_T_P) The _x_n_t_p utility has been upgraded to Version 3.0, which is a complete implementation as defined in RFC 1305. Note that the new _n_t_p_d_a_t_e utility requires that the version of the server be specified with the -_o flag. For example: % _n_t_p_d_a_t_e -_o _2 _s_e_r_v_e_r._o_x_o._f_f_f._c_o_m The default version is _3. The new _x_n_t_p_d daemon supports authentication. If you choose to enable this option, note that you only have New and Changed Features 1-33 to provide keys to the servers and peers that also support authentication. You should provide names of three servers during setup with _n_t_p_s_e_t_u_p, choosing the mode _s_e_r_v_e_r and the version option _V_2 (In the case where you are not upgrading the servers). _1._1_0 _E_n_h_a_n_c_e_d _S_e_c_u_r_i_t_y This release provides the following new enhanced security features. +o support for per-user resource limits in user profiles, using _s_e_t_r_l_i_m_i_t +o non-shadowed passwords are allowed, while using other extended profile features. +o The system administrator can control whether the _t_t_y_s database is updated on logins. +o Wildcard support for _t_t_y_s has been extended to X displays. +o User profiles and _t_t_y_s information are stored in database files for faster access and update (resulting in faster logins). +o The new utilities _e_d_a_u_t_h and _c_o_n_v_u_s_e_r are available. See the _S_e_c_u_r_i_t_y manual and the _s_e_t_r_l_i_m_i_t(2), _e_d_a_u_t_h(8), and _c_o_n_v_u_s_e_r(8) reference pages. _1._1_1 _F_i_l_e _S_y_s_t_e_m_s The following file system enhancements have been implemented in this release. _1._1_1._1 _A_d_v_F_S The following new features were introduced for AdvFS. _1._1_1._1._1 _N_e_w _T_u_n_i_n_g _P_a_r_a_m_e_t_e_r_s _f_o_r _A_d_v_F_S There is a new mechanism for limiting the amount of kernel memory that AdvFS uses for its access structures. This may be necessary only for systems with 64 Mb or less memory, and AdvFS as the default 1-34 New and Changed Features file systems. This is applicable to all hardware configurations. There are two new kernel paramaters relevant to AdvFS that can be modified using the _s_y_s_c_o_n_f_i_g or _s_y_s_c_o_n_f_i_g_d_b commands. They are _A_d_v_f_s_A_c_c_e_s_s_M_a_x_P_e_r_c_e_n_t and _A_d_v_f_s_A_c_c_e_s_s_C_l_e_a_n_u_p_P_e_r_c_e_n_t. There is a complete description of these parameters in the _G_u_i_d_e _t_o _F_i_l_e _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n _f_o_r _t_h_e _P_O_L_Y_C_E_N_T_E_R _A_d_v_a_n_c_e_d _F_i_l_e _S_y_s_t_e_m _a_n_d _U_t_i_l_i_t_i_e_s _f_o_r _D_i_g_i_t_a_l _U_N_I_X. _1._1_1._1._2 _A_d_v_F_S _N_o_w _S_u_p_p_o_r_t_s _D_i_r_e_c_t_o_r_y _T_r_u_n_c_a_t_i_o_n Traditionally, AdvFS directories were never truncated, even though many of the files in the directory had been deleted. This created a problem if the directory file became very big. For example, if several hundred thousand files were added to a directory, then the directory file itself grew very large. Even though most of the files in that directory were subsequently deleted, operations that required scanning the directory remained inefficient because the entire directory file still needed to be read. AdvFS now truncates directory files when all of the entries at the end of the directory have been deleted. This truncation is done on 8KB byte boundaries, so the size of a directory is always a multiple of 8192. One ambiguity of directory truncation is that the truncation is done when files are created and not when they are deleted. This is done because of the efficiency of underlying algorithms, and is the same model used by UFS for directory truncation. For example, after most files in a given directory are deleted, the size of the directory file itself will not decrease until a new file is inserted into that directory. _1._1_1._2 _F_i_l_e _S_y_s_t_e_m _A_c_c_e_s_s _C_o_n_t_r_o_l _L_i_s_t_s (_A_C_L_s) ACLs (Access Control Lists) on files and directories are a new feature in this release. They are manipulated with the _g_e_t_a_c_l and _s_e_t_a_c_l commands. See the _S_e_c_u_r_i_t_y manual and the reference pages for more information. New and Changed Features 1-35 _1._1_1._3 _L_o_g_i_c_a_l _S_t_o_r_a_g_e _M_a_n_a_g_e_r Digital UNIX Version 4.0 provides the following new features for the Logical Storage Manager (LSM): +o Two new LSM commands, _v_o_l_s_a_v_e and _v_o_l_r_e_s_t_o_r_e, provide an easy way to back up and restore the LSM configuration database. See the reference pages for these commands. +o The Basic Operations menu in LSM's graphical interface, _d_x_l_s_m, now provides support for disk operations. For example, adding a disk to LSM. +o The LSM limits have increased as follows: - The maximum number of LSM volumes on a system has increased from 256 to 4093. - The maximum number of plexes on a system has increased from 256 to 4096. - The maximum number of subdisks in a plex has increased from 256 to 4096. - The maximum number of disks that can be added to LSM has increased from 128 to 256. - The maximum size of an LSM volume has increased from 128GB to 512GB. The functionality and syntax of the LSM commands used for encapsulation, unencapsulation, and mirroring have changed in this release, as follows: +o The _v_o_l_e_n_c_a_p command now supports the following features and functions. For details, refer to the _v_o_l_e_n_c_a_p(8) reference page. - Allows the initialization of LSM and encapsulation of the system disk in one step. This requires the use of a free partition table entry. - Can be used to encapsulate all partitions on a disk. This requires the temporary use of a free partition table entry if the system disk is being encapsulated. - Can be used to encapsulate only the root and swap partitions. - Automatically creates a new disk group if 1-36 New and Changed Features specified. - Subsumes the functionality of the _v_o_l_a_d_v_d_o_m_e_n_c_a_p command. - Takes multiple arguments. - Uses a simple disk instead of a sliced disk for system disk encapsulation. - For disk label characteristics, assumes that partition _c maps the entire disk, and that an in-use partition has an fstype field other than _U_N_U_S_E_D. (If a partition's fstype field is _U_N_U_S_E_D, then _v_o_l_e_n_c_a_p may allocate that partition table entry for its use.) +o The _v_o_l_r_o_o_t_m_i_r command now supports the following features and functions. For details, refer to the _v_o_l_r_o_o_t_m_i_r(8) reference page. - Can be used to mirror all volumes on the system disk by specifying the -_a option. This option requires the target disk to be of the same type as the source disk. - Can be used to encapsulate only the root or swap partition by omitting the -_a option. This procedure requires that the target root and swap partitions are large enough to hold _r_o_o_t_v_o_l and _s_w_a_p_v_o_l, but the target and source disks need not be of the same type. +o When used with the -_a option, the _v_o_l_u_n_r_o_o_t command unencapsulates all LSM volumes on the system disk, not just _r_o_o_t_v_o_l and _s_w_a_p_v_o_l. The requirements for unencapsulation are: - The partition associated with the volume must have been initialized as a _n_o_p_r_i_v disk. - The volume must map directly to the partition (that is, the volume size must be equivalent to the partition size). - The volume must not be mirrored. For details, refer to the _v_o_l_u_n_r_o_o_t(8) reference page. New and Changed Features 1-37 _1._1_1._4 _O_v_e_r_l_a_p _P_a_r_t_i_t_i_o_n _C_h_e_c_k_i_n_g Two new functions, _c_h_e_c_k__u_s_a_g_e and _s_e_t__u_s_a_g_e3 are available for use by applications. These functions check whether a disk partition is marked for use and set the fstype of the partition in the disk label. See the reference pages for these functions for more information. _1._1_2 _B_o_o_t_s_t_r_a_p _L_i_n_k_i_n_g _a_n_d _K_e_r_n_e_l _M_o_d_u_l_e_s In Digital UNIX 4.0, a new method for configuring and building kernels is in place. It is designed to meet future needs for modularity, configurability, maintainability, scalability, and third-party device installation. Although the internal details of building kernels has changed significantly, the external interface is almost identical. The _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n guide and _W_r_i_t_i_n_g _D_e_v_i_c_e _D_r_i_v_e_r_s: _T_u_t_o_r_i_a_l guide contain more detailed information on this process. For normal operations, a static _v_m_u_n_i_x is recommended. Bootstrap linking is intended to support foreign devices, where support for such devices is not delivered in Digital UNIX. Previously, the Digital UNIX kernel was comprised of over 1000 individual ._o files. The configuration procedure, _d_o_c_o_n_f_i_g, selected among those files, and compiled a static kernel image that was then installed and booted. The ._o files are still available in the base kit and can be loaded separately if required. In this release, the ._o files are grouped into 150- 200 modules, with the suffix ._m_o_d. Each module represents a functional piece of the kernel, such as a device driver or platform support module. These modules are the new form of the original dynamically loadable modules introduced in DEC OSF/1 Version 3.0. Modules are selected by _d_o_c_o_n_f_i_g instead of the individual files previously used. This simplifies the Makefiles, saves considerable disk space, and reduces compilation time. _1._1_2._1 _D_e_f_i_n_i_n_g _M_o_d_u_l_e_s There is a new syntax in the _f_i_l_e_s file for making modules: 1-38 New and Changed Features ____________________________________________ Module Definition Syntax ____________________________________________ ____________________________________________ Module Definition Syntax ____________________________________________ MODULE/[STATIC]/modname optional opt1 .... dir/file1.c module modname dir/file2.c module modname dir/file3.c module modname ____________________________________________ This procedure defines a module: _m_o_d_n_a_m_e._m_o_d (note that ._m_o_d is appended to _m_o_d_n_a_m_e automatically). Each module has three files: _f_i_l_e_1._c, _f_i_l_e_2._c, and _f_i_l_e_3._c. When each file has been compiled, the module is linked together, and is ready to build into a kernel. Optionally, _S_T_A_T_I_C may be specified before the module name. If it is omitted, the object files are merely linked together into a module. If _S_T_A_T_I_C is used, the module is assumed to have a _m_o_d_n_a_m_e__c_o_n_f_i_g_u_r_e() routine and _m_o_d_n_a_m_e__a_t_t_r_i_b_u_t_e_s[] table to make it a configurable and potentially loadable module. Linkages to these routines are made in the kernel's _s_t_a_t_i_c__s_u_b_s_y_s__l_i_s_t[] table, and the configure routines will be called at system startup. See _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n for more information on modules, making modules loadable, and the use of configure routines. If an individual file in _B_I_N_A_R_Y is rebuilt, the module that contains it must also be rebuilt to incorporate the change into the kernel. To help with this, an environment variable _D_O__M_O_D_U_L_E_S is checked. Providing that the value of _D_O__M_O_D_U_L_E_S is the string _A_U_T_O, a module will be automatically relinked whenever an individual file is rebuilt. Kernel developers are encouraged to put their files into modules, and to consider making them loadable if possible. _1._1_2._2 _B_o_o_t_s_t_r_a_p _L_i_n_k_i_n_g To enhance configurability, and help mainstream modules, a new technology called bootstrap linking has been created. This is a way to defer the actual linking of a kernel until boot time. It is provided as an alternative to booting a statically linked New and Changed Features 1-39 kernel. When you run _d_o_c_o_n_f_i_g it builds a static kernel by default. To build a bootlink kernel, the command option -_b must be explicitly specified. A bootstrap linked kernel is actually a set of directives in a _s_y_s_c_o_n_f_i_g_t_a_b file that tell the bootstrap program how to build the kernel in memory. This file is generated using the make _s_c_t_a_b rule, which will be invoked by _d_o_c_o_n_f_i_g. The updated file is placed into /_u_s_r/_s_y_s/_M_A_C_H_I_N_E/_s_y_s_c_o_n_f_i_g_t_a_b. It must be copied into the root file system, and the two machine- specific modules _M_A_C_H_I_N_E._m_o_d and _E_X_T_R_A_S._m_o_d copied into the /_s_y_s/_B_I_N_A_R_Y directory. The _s_y_s_c_o_n_f_i_g_t_a_b file is then given to the bootstrap program instead of _v_m_u_n_i_x to build and boot the new kernel. See also the _d_o_c_o_n_f_i_g (8) and _s_i_z_e_r (8) Reference pages for more information. There is one major restriction when using a bootstrap linked kernel. Because there is no _v_m_u_n_i_x executable file, programs that attempt to search the kernel's symbol table will not find one. This includes _d_b_x and most_n_m,and _n_l_i_s_t library call and pass the name of the booted file will work, even if that file is a _s_y_s_c_o_n_f_i_g_t_a_b file. To avoid this restriction in Digital UNIX 4.0, execute: # _l_d -_o <_f_i_l_e_n_a_m_e> `_s_i_z_e_r -_m` This will generate an exact copy of the currently running kernel complete with symbol table in the file <_f_i_l_e_n_a_m_e>. When building a bootstrap linkable kernel, _d_o_c_o_n_f_i_g first builds a static kernel. If the static kernel fails to build, do not attempt to bootstrap link the _s_y_s_c_o_n_f_i_g_t_a_b file. Note that this static kernel will not be identical to the bootstrap-linked kernel as the kernels may be linked at different addresses. Use the _l_d command if required. _1._1_2._3 _R_e_l_a_t_e_d _C_h_a_n_g_e_s To effect full kernel modularization, several internal changes were made to the _c_o_n_f_i_g program and the compile environment for kernel files. These changes are significant for anyone developing kernel drivers or layered products. 1-40 New and Changed Features +o New linker handling of globals. To make all modules the same, a -_d_c linker switch was added to build modules. This has the effect of forcing a full declaration and storage allocation for all commons (globals). Previously, if two files both declared a global _i_n_t _f_o_o;, the linker would coalesce them into the same symbol when linking the kernel. This still happens within a module, but not across modules. Each module would have its own declaration _f_o_o, resulting in multiple definitions of the same global. Because of the multiple definition, kernel linking would fail. To avoid this, make all but one declaration external, using the _e_x_t_e_r_n. variable declaration +o Binary/NotBinary separation. The _B_I_N_A_R_Y file is no longer configurable. All files that are listed as Binary are compiled, and placed into modules as defined. The _B_I_N_A_R_Y configuration file no longer has any information about hardware configuration (bus, devices or controllers) or most options (such as CDFS or NTP_TIME). Neither are any of these header files built in _B_I_N_A_R_Y. _B_I_N_A_R_Y files that use the #_i_n_c_l_u_d_e statement to include other files, and the substitution statement #_d_e_f_i_n_e, will no longer compile. For example: #_i_n_c_l_u_d_e <_d_e_v_i_c_e._h> #_d_e_f_i_n_e _N_D_E_V_I_C_E _4 This includes files that use the following inclusion statement: #_i_n_c_l_u_d_e <_d_a_t_a/_N_o_t_B_i_n_a_r_y__d_a_t_a._c> See the _d_o_c_o_n_f_i_g(8) and _s_i_z_e_r(8) reference pages for more information. _1._1_3 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_z_a_t_i_o_n _a_n_d _L_a_n_g_u_a_g_e _S_u_p_p_o_r_t The following new features have been implemented to support internationalization. _1._1_3._1 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_z_a_t_i_o_n (_I_1_8_N) _C_o_n_f_i_g_u_r_a_t_i_o_n _U_t_i_l_i_t_y _f_o_r _C_D_E The I18N Configuration Tool, available through the New and Changed Features 1-41 CDE Application Manager, is one of the SysMan system administration configuration tools. The I18N Configuration Tool provides a graphical interface that enables you to configure internationalization- specific settings. It also provides a convenient way to see which countries, locales, fonts, and keymaps are currently supported on your system. Use this tool to remove unused fonts and unrequired country support. _1._1_3._2 _U_n_i_c_o_d_e _S_u_p_p_o_r_t This release provides a new set of locales and codeset convertors that support the Unicode and ISO 10646 standards. The codeset convertor modules enable an application to convert between other supported codesets and UCS-4. Digital UNIX also provides a function called _f_o_l_d__s_t_r_i_n_g__w() that maps one Unicode string to another, performing the specified Unicode character transformations. For more information on the _f_o_l_d__s_t_r_i_n_g__w() function, see the _f_o_l_d__s_t_r_i_n_g__w(3) reference page. For more information on the Unicode support, see the _U_n_i_c_o_d_e(5) reference page. _1._1_3._3 _T_h_e _W_o_r_l_d_w_i_d_e _M_a_i_l _H_a_n_d_l_e_r _N_o _L_o_n_g_e_r _E_x_i_s_t_s Worldwide support subsets no longer install internationalized Mail Handler (MH) software in the /_u_s_r/_I_1_8_N/_b_i_n/_m_h directory. In Digital UNIX Version 4.0, internationalization features have been merged into the default Mail Handler (MH) whose files are located in /_u_s_r/_b_i_n/_m_h. Check the value for the _m_h_p_a_t_h resource used to find the DECwindows Mail application. If necessary, change this value to be /_u_s_r/_b_i_n/_m_h. _1._1_3._4 _M_u_l_t_i_l_i_n_g_u_a_l _E_m_a_c_s (_m_u_l_e) The _m_u_l_e editor is a multilingual version of GNU Emacs and supports the following kinds of characters: +o ASCII (7-bit) +o ISO Latin-1 (8-bit) +o Japanese, Chinese, and Korean (16-bit) as 1-42 New and Changed Features specified by the ISO 2022 standard and its variants (EUC, Compound Text, and so on) +o Chinese in both GB and Big 5 encodings +o Thai as specified by the TIS 620 standard The _I_O_S_W_W_M_U_L_E_4_0_0 subset installs Version 2.3 of the GNU mule editor and associated software. Corresponding sources are available in the _I_O_S_W_W_M_U_L_E_S_R_C_4_0_0 subset. Digital UNIX does not include public domain fonts that you can use with mule. Refer to the _m_u_l_e- _2._3/_R_E_A_D_M_E._M_u_l_e file installed by the _I_O_S_W_W_M_U_L_E_S_R_C_4_0_0 subset to find out how you can obtain public domain fonts. The Digital UNIX software is enhanced with lisp libraries that support the _d_e_c_h_a_n_z_i codeset for Simplified Chinese and the _d_e_c_h_a_n_y_u codeset and tsangchi input method for Traditional Chinese. These libraries are included in the IOSWWMULE400 subset and installed in the /_u_s_r/_i_1_8_n/_m_u_l_e/_l_i_b/_m_u_l_e/_s_i_t_e-_l_i_s_p directory. For more information about mule, see the _m_u_l_e(1) reference page. _1._1_3._5 _S_u_p_p_o_r_t _f_o_r _C_a_t_a_l_a_n, _L_i_t_h_u_a_n_i_a_n, _a_n_d _S_l_o_v_e_n_e Digital UNIX Version 4.0 includes support for the the _C_a_t_a_l_a_n(5), _L_i_t_h_u_a_n_i_a_n(5), and _S_l_o_v_e_n_e(5) reference pages for information about associated codesets, locales, keyboards, and fonts. _1._1_3._6 _m_a_n _C_o_m_m_a_n_d _S_u_p_p_o_r_t_s _C_o_d_e_s_e_t _C_o_n_v_e_r_s_i_o_n The man command can automatically invoke the _i_c_o_n_v utility to perform codeset conversion of reference page files. This allows you to install one set of reference pages to support locales that have the same language and territory but different codesets, thereby reducing file redundancy on the system. For more information, refer to the _m_a_n(1) reference page. _1._1_4 _P_C_M_C_I_A (_P_C _C_a_r_d) _S_u_p_p_o_r_t PCMCIA (PC Card) support is a new feature in this release and is limited to the following capabilities: New and Changed Features 1-43 +o Support of a selected ISA to PCMCIA bridge adapter +o Support on the following platforms: - AlphaStation 255, - AlphaStation 200, - AlphaStation 400, - AlphaStation 600, - AlphaServer 1000 +o 1 modem card, specifically Megahertz XJ2288 (28.8kpbs) +o hot swap capability of PC Cards _1._1_4._1 _R_e_s_t_r_i_c_t_i_o_n_s The following restrictions apply in this release. +o No support for loadable device drivers for PC Cards. +o If the system does not have enough available IRQ (interrupt) numbers to assign to the PCMCIA devices, PCMCIA devices cannot be configured. To support one PCMCIA adapter the system must have at least 3 unused IRQ numbers available. One IRQ is for the adapter and the other two are for each PCMCIA socket. +o Digital UNIX can support 2 PCMCIA adapters in a system provided that the necessary resources are available. In some systems, availability of interrupt lines will prohibit the use of multiple adapters. If you have sufficient resources and are going to support 2 adapters, the second adapter should be configured to use the I/O address 3E2. +o In order to use fax functions in a fax/modem PC Card, a commercial UNIX fax application software is required. +o The Megahertz XJ2288 is the only modem card fully qualified on Digital UNIX. However other modem cards of similar type (both 14.4kpbs and 28.8kpbs) may work. The following is the list of modem cards that are known to work: 1-44 New and Changed Features - card manufacturer: MEGAHERTZ product name: XJ2288 - card manufacturer: MEGAHERTZ product name: XJ1144 - card manufacturer: AT&T Paradyne product name: KeepInTouch Card - card manufacturer: Digital product name: PCMCIA V.32bis 14,400 Fax +o The selected ISA to PCMCIA bridge adapters are from SCM Microsystems, the SWAPBOX CLASSIC X2 ... Model MMCD-D2 which has the following features: - 3.5" Front Access - 2 slots (type II + type III) PC Card socket. - Standard PC-AT 16-bit ISA bus interface - PCMCIA Revision 2.X and ExCA compliant and the SWAPBOX PREMIUM COMBO ... Model MMCD-FC2: - 3.5" 1.44 Mbyte Floppy Drive Support. - One Type I, II or III front-access PC Card socket. - One Type I, II or III rear-access PC Card socket. - Standard PC-AT 16-bit ISA bus interface - PCMCIA Revision 2.X and ExCA compliant However, other ISA to PCMCIA bridge adapters using the Intel i82365SL or compatible chip may also work. _1._1_4._2 _C_o_n_f_i_g_u_r_i_n_g _t_h_e _P_C_M_C_I_A _A_d_a_p_t_e_r _B_o_a_r_d _f_r_o_m _t_h_e _C_o_n_s_o_l_e Before inserting the PCMCIA adapter board into your system, make sure to read the manual that came with the adapter from the adapter vendor and follow the instructions on how to connect the cables and install the board. +o Configuring on an ISA bus system: 1. If the system is an ISA bus system, the "isacfg" utility from the console must be used New and Changed Features 1-45 to configure the PCMCIA adapter. 2. After the PCMCIA adapter board is inserted to an ISA slot in the system, power-on the system. 3. To add an PCMCIA option to the platforms with an ISA bus, issue the following ISA option card configuration command at the console. The following example uses an AlphaStation 200 platform, but the commands should be the same in all 3 ISA bus platforms. >>> _i_s_a_c_f_g -_s_l_o_t _1 -_e_t_y_p _1 -_d_e_v _0 -_m_k -_i_o_b_a_s_e_0 _3_e_0 -_i_r_q_0 _1_4 -_e_n_a_d_e_v _1 -_h_a_n_d_l_e _P_C_I_C-_P_C_M_C_I_A NOTE that if the system is already using slot 1, use other slot number that is not used. 4. The IRQ (interrupt) number must also not conflict with those interrupt numbers that are already assigned to other default devices on the system. The system hardware manual usually indicates which default devices are on the system and which IRQ numbers those default devices use. 5. The recommended IRQ number to be used for the PCMCIA adapter is 14 (decimal). 6. If the number 14 is already used, number 10 should be set if it is not already used by other devices. 7. When you issue the above "isacfg" command, the console should print out the following line or something similar: type >>>init to use these changes 8. After reinitializing the console, you can verify that you configured the PCMCIA adapter correctly, by issuing the following command: >>>isacfg -slot 1 9. You should see the following screen display: ============================================================= handle: PCIC-PCMCIA etyp: 1 slot: 1 dev: 0 enadev: 1 1-46 New and Changed Features totdev: 1 iobase0: 3e0 membase0: 8000000000000000 iobase1: 8000000000000000 memlen0: 8000000000000000 iobase2: 8000000000000000 membase1: 8000000000000000 iobase3: 8000000000000000 memlen1: 8000000000000000 iobase4: 8000000000000000 membase2: 8000000000000000 iobase5: 8000000000000000 memlen2: 8000000000000000 rombase: 8000000000000000 romlen: 8000000000000000 dmamode0/chan0: 80000000 irq0: 14 dmamode1/chan1: 80000000 irq1: 80000000 dmamode2/chan2: 80000000 irq2: 80000000 dmamode3/chan3: 80000000 irq3: 80000000 ============================================================= >>> +o Configuring on an EISA bus system: 1. If the system has an EISA bus, the ECU (EISA Configuration Utility) is used for configuring the PCMCIA adapter. 2. If you are going to use PCMCIA adapter on EISA systems, run the EISA Configuration Utility (ECU), tell it that the PCMCIA adapter is there, and tell it to use the aisa3000.cfg config file. 3. Refer to your system hardware documentation for complete instructions on how to run the ECU program. _1._1_4._3 _C_o_n_f_i_g_u_r_i_n_g _a_n_d _U_s_i_n_g _a _P_C_M_C_I_A _M_o_d_e_m _P_C _C_a_r_d Since a PC Card is a dynamic device (i.e. not a static device that is present all the time in the system hardware), and the serial-line device driver is a static device driver, when the system is installed initially, there will not be a corresponding _a_c_e_x entry created automatically by the _d_o_c_o_n_f_i_g of the target system. This is due to the fact that the system doesn't know when it is being installed that there will be a fax/modem card for PCMCIA since the card is not in the system yet. If you want the system to automatically create the 'acex' entry for your PCMCIA fax/modem card, before you start installing the system, make sure that you have the PCMCIA adapter configured in the console and that the PCMCIA fax/modem card is inserted into the New and Changed Features 1-47 slot. If you have a fax/modem card in the slot 0, for instance, when the system is installed and the target kernel is built, the system kernel configuration file built will have the following entry: controller ace2 at pcmcia0 slot 0 vector aceintr The installation will also create the device special file for this fax/modem card in the directory named /_d_e_v. # _l_s -_g_l _t_t_y_0_2 crw-rw-rw- 1 root system 35, 2 Oct 16 13:22 tty02 If you didn't have the PCMCIA fax/modem card inserted in the slot when the system was installed, then you need to add the following line to your system kernel configuration file, /_s_y_s/_c_o_n_f/_H_O_S_T_N_A_M_E where _H_O_S_T_N_A_M_E is the name of your system. If you are just going to use one PCMCIA fax/modem card: controller ace2 at * slot ? vector aceintr If you plan to use 2 modem cards simultaneously, add the following 2 lines to your system configuration file: controller ace2 at * slot ? vector aceintr controller ace3 at * slot ? vector aceintr Once the system configuration file is modified, use the following command to rebuild the new kernel and reboot the system. # _d_o_c_o_n_f_i_g -_c _1._1_4._4 _C_r_e_a_t_i_n_g _a _D_e_v_i_c_e _S_p_e_c_i_a_l _F_i_l_e _f_o_r _t_h_e _M_o_d_e_m _C_a_r_d Normally the system installation will create the following two default _t_t_y_0_x device special files in the directory /_d_e_v, as the following command shows: # _l_s -_g_l _t_t_y_0* This command produces output similar to the 1-48 New and Changed Features following: crw-rw-rw- 1 root system 35, 0 Oct 16 13:22 tty00 crw-rw-rw- 1 root system 35, 1 Oct 16 13:22 tty01 This is because most systems have 2 imbedded serial lines. If the system has only one, only tty00 entry will be visible in the /_d_e_v directory. Create additional device special files for the PCMCIA modem cards using the _M_A_K_E_D_E_V utility in the /_d_e_v directory. For example, in the /_d_e_vdirectory: # ./_M_A_K_E_D_E_V _a_c_e_2 MAKEDEV: special file(s) for ace2: tty02 The generated special file should look like this: crw-rw-rw- 1 root system 35, 2 Oct 27 14:02 tty02 If you intend to have 2 PCMCIA modem cards working simultaneously, create device special files for the number of cards, in this case, 2. For example, in /dev directory: # ./_M_A_K_E_D_E_V _a_c_e_2 _a_c_e_3 MAKEDEV: special file(s) for ace2: tty02 MAKEDEV: special file(s) for ace3: tty03 The generated special file should look like this: crw-rw-rw- 1 root system 35, 2 Oct 27 14:02 tty02 crw-rw-rw- 1 root system 35, 3 Oct 27 14:02 tty03 _1._1_4._5 /_e_t_c/_r_e_m_o_t_e _F_i_l_e The /_e_t_c/_r_e_m_o_t_e file must be modified to add new access line definitions for the PCMCIA modem cards to be used. If you have a 28.8kpb modem card and will be using the full speed, the baud rate (br) in the /_e_t_c/_r_e_m_o_t_e file should be set to 38400. New and Changed Features 1-49 For example, add the following line to /etc/remote file: line2:dv=/dev/tty02:br#38400:pa=none: Note that in the above line, "line2" can be any name you determine to be used with the "tip" command later on. Once the PCMCIA modem card is inserted correctly and the system configures the card, the card can be used the same as any other modem devices. _1._1_4._6 _I_n_s_e_r_t_i_n_g _a _P_C_M_C_I_A _M_o_d_e_m _C_a_r_d To use a PCMCIA modem card, insert the card to one of the PC Card slots in the PCMCIA adapter. Depending on the adapter type, there may be 2 front access card slots or one front access and one rear access card slot. When you insert the card into the slot 0, you should see the following message on the console terminal (or the Console Log window of the graphics head). # PCMCIA socket 0: card manufacturer: MEGAHERTZ product name: XJ2288 Configured: serial unit 2, type=16550A ace2 at pcmcia0 This example used MegaHertz XJ2288 fax/modem card. _1._1_4._6._1 _P_o_s_s_i_b_l_e _E_r_r_o_r _M_e_s_s_a_g_e When a modem card is inserted, an error message such as the following example may appear on the Console Log window: socket 0: card manufacturer: MEGAHERTZ, unknown modem card inserted Using generic modem driver for this PC Card. PCMCIA socket 0: card manufacturer: MEGAHERTZ product name: XJ1144 socket 0: Couldn't find usable config. for this card. Please eject this PC Card. 1-50 New and Changed Features The error message: Couldn't find usable config. for this card. is generated if the card requires I/O resources that are already in use by other components in the system. If this error message is seen, the card should be ejected since it is not configured. One possible way to correct this situation is to remove some other ISA/EISA devices in the system and reboot the system, thus freeing I/O resources that may be required by this card and trying the card insertion again. _1._1_4._7 _R_e_m_o_v_i_n_g _a _P_C_M_C_I_A _M_o_d_e_m _C_a_r_d Once you are finished using the modem card, push the button next to the card slot to eject the card previously inserted. You should see the following message on the console terminal or console Log window. # stray interrupt on unit=2, intr_id=0 PCMCIA socket 0: PC Card removed Note that you may or may not see the "stray interrupt..." message above when you eject the card. The message is generated by the serial-line driver if the PC Card generated an interrupt when the card got ejected. _1._1_5 _D_y_n_a_m_i_c _D_e_v_i_c_e _R_e_c_o_g_n_i_t_i_o_n _f_o_r _S_C_S_I _D_e_v_i_c_e_s Dynamic Device Recognition (DDR) is a framework for describing the operating parameters and characteristics of SCSI devices to the SCSI CAM I/O subsystem. You can use DDR to include new and changed SCSI devices into your environment without having to reboot the operating system. You do not disrupt user services and processes, as happens with static methods of device recognition. Beginning with Digital UNIX Version 4.0, DDR is preferred over the current, static method for recognizing SCSI devices. The current, static method, as described in _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n, is to edit SCSI device customizations into the /_s_y_s/_d_a_t_a/_c_a_m__d_a_t_a._c data file, reconfigure the kernel, and shut down and reboot the operating system. New and Changed Features 1-51 _N_o_t_e Support for the static method of recognizing SCSI devices will be retired in a future release of Digital UNIX . Digital UNIX Version 4.0 supports both methods of recognizing SCSI devices. Both methods can be employed on the same system, with the restriction that the devices described by each method are exclusive to that method (nothing is doubly-defined). The information DDR provides about SCSI devices is needed by SCSI drivers. You can supply this information using DDR when you add new SCSI devices to the system, or you can use the /_s_y_s/_d_a_t_a/_c_a_m__d_a_t_a._c data file and static configuration methods. The information provided by DDR and the _c_a_m__d_a_t_a._c file have the same objectives. When compared to the static method of providing SCSI device information, DDR minimizes the amount of information that is supplied by the device driver or subsystem to the operating system and maximizes the amount of information that is supplied by the device itself or by defaults specified in the DDR databases. You can also use DDR capabilities to convert customizations in the _c_a_m__d_a_t_a._c file to information in the DDR /_e_t_c/_d_d_r._d_b_a_s_e text database. For more information about DDR, see _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n, _d_d_r__c_o_n_f_i_g(8), and _d_d_r._d_b_a_s_e(4). 1-52 New and Changed Features Installation Notes 2 The notes in this chapter discuss the following topics: +o General information about installation +o Layered product considerations +o Full installation +o Update installation +o Server extensions +o Disk space requirements _N_o_t_e Do not attempt to install Digital UNIX Version 4.0 without first reading in Chapter 3 the notes appropriate to your processor. Failure to read these notes can result in serious installation problems. _2._1 _G_e_n_e_r_a_l _I_n_f_o_r_m_a_t_i_o_n _A_b_o_u_t _I_n_s_t_a_l_l_a_t_i_o_n The following notes apply to the installation process in general. _2._1._1 _K_e_r_n_e_l _O_b_j_e_c_t _F_i_l_e_s _N_o_t _I_n_s_t_a_l_l_e_d In this release, kernel object files are not needed for installation or kernel building. Only kernel modules are needed. See Section 1.12 for more information on these kernel modules. The individual kernel object files are only needed for kernel development work. See Section 2.4.7 for instructions on when and how to load these objects if they are needed. _2._1._2 _I_n_s_t_a_l_l_a_t_i_o_n _P_r_o_c_e_d_u_r_e _m_a_y _F_a_i_l _t_o _D_e_t_e_c_t _D_i_s_k_s The installation procedure automatically detects the disk(s) on a system, and asks you to specify the system (root) disk. If the disk label indicates that the _a partition starts at a non-zero offset, the disk may not be detected by the installation procedure. This problem most commonly occurs with disks which have previously been used by LSM. LSM modifies the _a partition to start at offset 16. If all disks on the system cannot be detected because of this problem, the installation procedure will exit to a shell prompt #. If one or more disks are detected, while others are not, the undetected disks will not be presented to the user as devices where Digital UNIX can be installed. You can correct this problem as follows. If the installation procedure does not automatically exit to the shell prompt, exit manually. In the graphical interface, click the UNIX Shell button, and click "OK" in the dialog box that appears. In the character-cell interface, press CTRL/C. When you see the shell prompt, enter these commands: # _c_d /_d_e_v # ./_M_A_K_E_D_E_V <_d_e_v_i_c_e> where <_d_e_v_i_c_e> is replaced by the actual device name such as _r_z_3. If more than one disk is not detected by the installation procedure, enter a _M_A_K_E_D_E_V command for each undetected disk. Enter the following commands to restart the installation procedure: # _c_d / # _r_e_s_t_a_r_t _2._1._3 _S_y_s_t_e_m_s _W_i_t_h_o_u_t _G_r_a_p_h_i_c_s _D_e_v_i_c_e_s This note applies to all hardware configurations that do not have an attached graphics device. If the _O_S_F_X_C_2_S_E_C_3_5_0 subset is installed on a system that does not have a graphics controller installed on it, 2-2 Installation Notes the following errors may be seen: setld: Error installing "Graphical System Administration Utilities" (OSFXADMIN400) This subset requires following subset(s) to operate correctly: "Graphical Base System Management Utilities" (OSFXSYSMAN400) setld: Please install required subset(s) first. These errors are caused by subset dependency ordering and if the errors occur, the following subsets will not be properly installed onto your system. OSFXC2SEC400 OSFXSYSMAN400 OSFCDEMIN400 OSFXADMIN400 OSFTKBASE400 _2._1._4 _W_o_r_l_d_w_i_d_e _S_u_b_s_e_t_s The following error message may be displayed during the installation of the Worldwide subsets: /usr/sbin/setld: /usr/lbin/depord: arg list too long The installation procedure will abort. This error may happen if the shell has too many environment variables and runs out of memory during installation. This problem can be corrected by starting a new shell and removing the unused environment variables. _2._1._5 _I_n_v_a_l_i_d _P_a_s_s_w_o_r_d _i_n _G_r_a_p_h_i_c_a_l _I_n_s_t_a_l_l_a_t_i_o_n After changing the Install Type field (default to custom, or custom to default) and entering an invalid password, an error dialog box will be displayed but may not be in focus. An invalid password is one which is less than six characters long or contains only lowercase characters. Pressing Return to dismiss the dialog box when it is not in focus may cause you to be temporarily locked out of all editable fields. To avoid this situation after entering an invalid password, ensure the error dialog is in focus and either press Return or click on OK with the mouse to dismiss it. This will correctly clear the error dialog box and allow re-entry of the password. If you encounter this temporary lock-out situation, Installation Notes 2-3 you can work around the problem by setting focus to a non-editable field in the Installation Setup window (i.e., clicking on a menu or button) and then setting focus back to the desired entry field. You can also set focus outside the Installation Setup window and back to it. _2._1._6 _M_i_n_i_m_u_m _V_e_r_s_i_o_n _2._1_0 _f_o_r _Q_l_o_g_i_c _F_i_r_m_w_a_r_e On booting, the Qlogic driver attempts to set the Data Overrun Recovery mode to that supported by Digital UNIX. If the operation fails, the driver will print a warning message on the system console: isp: WARNING - Data Overrun Recover Mode could NOT be set! Where <_n> is the number of the Qlogic controller encountered during system probe. Digital recommends that the Qlogic ISP1020 or ISP1020A firmware be at a minimum revision level of 2.10. This is the minimum revision of Qlogic firmware required to implement reliable data overrun error detection and recovery. _2._1._7 _A_T_I _G_r_a_p_h_i_c_s _C_o_n_t_r_o_l_l_e_r_s An address conflict occurs between ISA serial devices configured as COM4 and ATI Mach64 graphics controllers. Both ISA GX and PCI ATI Mach64 CX/GX/CT products use the address range of 2EC-2EF. This is the same address range assigned to COM4 devices. Consult the hardware documentation for more information. _2._1._8 _I_n_c_o_r_r_e_c_t _B_r_o_k_e_n _P_i_p_e _M_e_s_s_a_g_e_s The installation process displays the following message during the installation of some subsets: Broken Pipe The installation will complete successfully and the message can be ignored. _2._2 _L_a_y_e_r_e_d _P_r_o_d_u_c_t _C_o_n_s_i_d_e_r_a_t_i_o_n_s The versions of the layered products shown in Table 2-4 Installation Notes 2-1 are compatible with, or were specifically developed to take advantage of new Digital UNIX features. They may also provide new hardware support or resolutions to problems. The table shows the correct layered product versions to use with this release. Table 2-1: _L_a_y_e_r_e_d _P_r_o_d_u_c_t _V_e_r_s_i_o_n_s _________________________________________________________________ Layered Digital Digital UNIX Digital UNIX Version Product UNIX Version 3.2C 4.0 Version 3.2 _________________________________________________________________ POLYCENTER Version 3.2 Version 3.2 Version 4.0 AdvFS Utilities DECsafe Version 1.2 Version 1.2A N/A Available Server Logical Version 1.2 Version 1.2 Version 4.0 Storage Manager System V Version 3.2 Version 3.2 Version 4.0 Environment DECnet Version 3.0 Version 3.0 Version 4.0 SNA Peer None Version 1.2 Version 1.2 with ECO 1 _________________________________________________________________ _2._2._1 _D_E_C _F_U_S_E DEC FUSE Version 2.1A and prior versions are not supported under Digital UNIX version 4.0. DEC FUSE Version 3.0 is supported under Digital UNIX version 4.0. _2._2._2 _D_E_C_n_e_t/_O_S_I Digital UNIX Digital UNIX Version 4.0 does not currently support DECnet/OSI. Any existing DECnet/OSI releases will not work with this release of Digital UNIX. Installation Notes 2-5 _2._2._3 _S_u_b_s_e_t _C_o_n_t_r_o_l _P_r_o_g_r_a_m _M_e_t_h_o_d_s _f_o_r _R_e_s_t_r_i_c_t_i_n_g _a _P_r_o_d_u_c_t _t_o _D_i_g_i_t_a_l _U_N_I_X Hardware releases based on Digital UNIX Version 4.0 may not install the _O_S_F_B_A_S_E_4_0_0._l_k file; however, they will install a _O_S_F_B_A_S_E_4??._l_k lock file. If you want to tie your product with Digital UNIX Version 4.0 you should use wildcards to check for the _O_S_F_B_A_S_E_4??._l_k file instead of _O_S_F_B_A_S_E_4_0_0._l_k file. If you hard code the test for the _O_S_F_B_A_S_E_4_0_0._l_k into your subset control programs (SCP) it will fail to find the lock file when run on a system with a Version 4.0-based hardware release installed. This policy has always been in place; however, until now, not following it had not caused any problems. If you wish to restrict your product from installing on Version 4.0-based hardware releases, you can hardcode the _O_S_F_B_A_S_E_4_0_0 string in your SCP. _2._3 _F_u_l_l _I_n_s_t_a_l_l_a_t_i_o_n A installation (default or custom) will overwrite any customization on your system. _2._3._1 _F_u_l_l _I_n_s_t_a_l_l_a_t_i_o_n _O_v_e_r_w_r_i_t_e_s /_e_t_c/_f_d_m_n_s If your system is installed with the AdvFS file system, save a copy of the /_e_t_c/_f_d_m_n_s directory before doing a full installation. The installation process causes this directory to be overwritten, resulting in the potential loss of configuration data contained in the directory. _2._3._2 _F_u_l_l _I_n_s_t_a_l_l_a_t_i_o_n _O_v_e_r_w_r_i_t_e_s /_e_t_c/_l_v_m_t_a_b If your system has Logical Volume Manager (LVM) volumes configured on it, save a copy of the /_e_t_c/_l_v_m_t_a_b file before doing a full installation. The installation process causes this file to be overwritten, resulting in the potential loss of all data under LVM control. _2._3._3 _F_u_l_l _I_n_s_t_a_l_l_a_t_i_o_n _O_v_e_r_w_r_i_t_e_s /_e_t_c/_v_o_l/_v_o_l_b_o_o_t If your system has LSM volumes configured on it, save 2-6 Installation Notes a copy of the /_e_t_c/_v_o_l/_v_o_l_b_o_o_t file before doing a full installation. Doing a full installation overwrites the /_e_t_c/_v_o_l/_v_o_l_b_o_o_t file, resulting in the potential loss of data under LSM control. _2._3._4 _F_u_l_l _I_n_s_t_a_l_l_a_t_i_o_n _O_v_e_r_w_r_i_t_e_s /_e_t_c/_p_r_e_s_t_o_t_a_b If your system has Prestoserve configured on it, save a copy of the /_e_t_c/_p_r_e_s_t_o_t_a_b file before doing a full installation. The installation process causes this file to be overwritten, resulting in the potential loss of configuration data contained in this file. _2._3._5 _T_h_e _I_n_s_t_a_l_l_a_t_i_o_n _G_r_a_p_h_i_c_a_l _I_n_t_e_r_f_a_c_e See Section 4.4.1 for information on restrictions when using the Disk Configuration Manager. _2._4 _U_p_d_a_t_e _I_n_s_t_a_l_l_a_t_i_o_n The following notes apply to the update installation procedure. _2._4._1 _S_y_s_t_e_m_s _W_i_t_h_o_u_t _G_r_a_p_h_i_c_s _D_e_v_i_c_e_s This note applies to all hardware configurations that do not have an attached graphics device. If the _O_S_F_X_C_2_S_E_C_3_5_0 subset is installed on a system that does not have a graphics controller installed on it, the following errors may be seen: setld: Error installing "Graphical System Administration Utilities" (OSFXADMIN400) This subset requires following subset(s) to operate correctly: "Graphical Base System Management Utilities" (OSFXSYSMAN400) setld: Please install required subset(s) first. These errors are caused by subset dependency ordering and if the errors occur, the following subsets will not be properly installed onto your system. OSFXC2SEC400 OSFXSYSMAN400 OSFCDEMIN400 OSFXADMIN400 OSFTKBASE400 Installation Notes 2-7 _2._4._2 _D_i_s_a_b_l_e _L_i_g_h_t_w_e_i_g_h_t _W_i_r_i_n_g _W_h_e_n _U_s_i_n_g _G_r_a_n_u_l_a_r_i_t_y _H_i_n_t_s When lightweight wiring is used with granularity hints, the system can experience the following panic message: panic: lw_remove: light weight wiring(s) found This panic can occur on any hardware configuration, but will generally only occur on large systems using large amounts of shared memory. Before updating your system, remove the line in /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b containing _g_h-_c_h_u_n_k_s. Lightweight wiring is enabled by default in Digital UNIX version 4.0. Removing _g_h-_c_h_u_n_k_s from the /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b file will ensure that granularity hints is disabled after the update installation, and that both granularity hints and lightweight wiring are not enabled simutaneously. If granularity hints is required, lightweight wiring must be disabled by setting _n_e_w-_w_i_r_e-_m_e_t_h_o_d=_0 in /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b. The system must then be rebooted for the change to take effect. _2._4._3 _D_i_s_k _S_p_a_c_e _R_e_q_u_i_r_e_m_e_n_t_s _f_o_r _U_p_d_a_t_e _I_n_s_t_a_l_l_a_t_i_o_n_s Before beginning your update installation from Version 3.2C, Version 3.2D-1, or Version 3.2D-2, you should refer to Appendix F.2 in the Digital UNIX Version 4.0 _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e (supplied with your Version 4.0 software distribution kit). Ensure that your system meets the minimum additional disk capacity requirements to successfully update to Version 4.0. If it does not, you may need to remove some optional software subsets in addition to unnecessary core dump files, kernels, or other unrequired files, prior to starting the update procedure. If you have already begun an update installation that exited due to insufficient additional disk space, the installation procedure will list which file systems require additional space, and how much space is required. To identify base and layered product subsets that are currently installed, execute the following command as 2-8 Installation Notes root: # _s_e_t_l_d -_i | _g_r_e_p _i_n_s_t_a_l_l_e_d This command will list all potential candidates for deletion. The left column lists the subset identifier, and the right column gives a brief text description of the subset. Next, refer to Appendix E of the Version 3.2C Installation Guide. This appendix lists the disk space required per subset for the root, /usr, and /var file system. If you have Version 3.2D-1 or Version 3.2D-2 installed, you will need to add the additional amount of space required per file system that these releases add to Version 3.2C (this information is contained in the Version 3.2D-1 and Version 3.2D-2 release notes). Next, determine which subsets can be removed to satisfy the file system space requirements of the update installation. For example, a Version 3.2C to Version 4.0 update installation exits, requiring an additional 1 MB of space in the root file system. The optional subsets _O_S_F_A_T_M_B_A_S_E_3_5_0, _O_S_F_C_O_M_A_G_E_N_T_3_5_0, and _O_S_F_C_2_S_E_C_3_5_0 are installed but are not being used. Referring to Appendix E in the Version 3.2C Installation Guide, the total of the root file system component (in 512- byte blocks) for these subsets is: OSFATMBASE350 431.76 OSFC2SEC350 1513.77 OSFCOMAGENT350 182.79 -------------- ------ Total 2128.32 (512-byte blocks) Total 1.04 (MB) Therefore, removing these three optional subsets should reclaim enough space for the update procedure to complete: # _s_e_t_l_d -_d _O_S_F_A_T_M_B_A_S_E_3_5_0 _O_S_F_C_2_S_E_C_3_5_0 _O_S_F_C_O_M_A_G_E_N_T_3_5_0 _2._4._4 _U_p_d_a_t_e _I_n_s_t_a_l_l _a_n_d _E_n_h_a_n_c_e_d _S_e_c_u_r_i_t_y The update installation process does not convert the extended user profiles and ttys information to the new database format. This can be done manually after the update installation completes with the following Installation Notes 2-9 command: # /_t_c_b/_b_i_n/_c_o_n_v_a_u_t_h _2._4._5 _S_y_s_t_e_m _C_l_o_c_k _m_a_y _L_o_s_e _T_i_m_e During an update installation, the system clock (TOY, time of year) may lose a short amount of time possibly up to 3 minutes. This may happen when you update your system from any version preceding Version 4.0, to Version 4.0 or later. During the boot process, a message will be printed to the console indicating the condition as follows: over 5 years since last boot - CHECK AND RESET THE DATE Setting time to last shutdown time stamp the alternative message will be: WARNING: preposterous time in TOY -- CHECK AND RESET THE DATE The time will be set to the previous shutdown timestamp. On some systems, similar behavior will occur everytime the systems transition between a version preceding Version 4.0 and version Version 4.0 or later. For example, consider a system which has one disk with Digital UNIX Version 3.2C installed and another disk with Digital UNIX Version 4.0 installed: 1. The time is set while either version is booted. 2. When the system is shut down and booted from the other disk, time will not be maintained by the clock. The time will be set to the previous shutdown time-stamp. The problem will occur on the following systems: DEC_3000 series DEC_8000 DEC_4000 DEC_10000 DEC_7000 AXPVME64 Note that systems running _n_t_p should not be affected by this problem, with the exception that a warning message may be printed to the console as the system boots. Open 3D is not supported for update 2-10 Installation Notes installations in this release. Use the _s_e_t_l_d command to remove all Open 3D subsets before updating your system. _2._4._6 _M_e_s_s_a_g_e _F_r_o_m _s_w_a_p_o_n _U_t_i_l_i_t_y During an update installation, the following message from the system _s_w_a_p_o_n utility may appear at the start of some update installations: swapon: /dev/rz10b: already a swap device The swap device specified in the message may be different than the example. You can ignore this message. _2._4._7 _K_e_r_n_e_l _O_b_j_e_c_t _F_i_l_e_s _A_r_e _D_e_l_e_t_e_d After the Digital UNIX Version 4.0 update installation is complete you can remove kernel object files from your system to reclaim disk space. Kernel object files are only necessary if you are going to perform kernel development work on your system. If your system is not being used for kernel development work and you want to reclaim approximately 25 meg of disk space, use the following command to determine if any of the following subsets are loaded on your system: # _s_e_t_l_d -_i OSFBINOBJECT400 OSFHWBINOBJECT400 OSFADVFSBINOBJECT400 OSFATMBINOBJECT400 OSFLSMBINOBJECT400 Use the following command to delete these subsets to reclaim additional disk space: # _s_e_t_l_d -_d _2._4._8 _T_h_e _i_n_s_t_a_l_l_u_p_d_a_t_e _C_o_m_m_a_n_d _M_a_y _S_e_l_e_c_t _t_h_e _W_r_o_n_g _D_e_v_i_c_e The _i_n_s_t_a_l_l_u_p_d_a_t_e command may select the wrong distribution media when multiple distribution media are mounted on mount points with similar names. For example, if the following devices are mounted prior Installation Notes 2-11 to beginning an update installation and you issue a /_s_b_i_n/_i_n_s_t_a_l_l_u_p_d_a_t_e /_m_n_t command, _i_n_s_t_a_l_l_u_p_d_a_t_e will incorrectly select /_d_e_v/_r_z_4_c as the distribution media: /dev/rz0a on / type ufs (rw) /proc on /proc type procfs (rw) /dev/rz0g on /usr type ufs (rw) /dev/rz4c /mnt1 /dev/rz11c /mnt The workaround for this problem is to mount only the intended distribution media prior to beginning the update. _2._5 _S_e_r_v_e_r _E_x_t_e_n_s_i_o_n_s This section provides information on installing Digital UNIX Server Extensions. _2._5._1 _E_r_r_o_r _w_h_e_n _i_n_s_t_a_l_l_i_n_g _C_h_i_n_e_s_e _s_u_b_s_e_t_s _f_r_o_m _R_I_S _s_e_r_v_e_r If you install the Chinese subsets from a RIS server, the following error may occur: Common Chinese Unicode Support Copying from hanax1 (inet) setld: cannot access server mapping (rcp: ris3.alpha/rp_mapping: No such file or directory) setld: Load from hanax1 failed, subset IOSZHUCSBASE400 Verifying setld: There were verification errors for "Common Chinese Unicode Support (IOSZHUCSBASE400) This error causes the system to abort the installation process. The problem may happen in other Chinese subsets also. The error occurs because of the number of subsets in the Worldwide kit. To avoid this problem, create a RIS area with fewer subsets or Chinese subsets only. To do this, choose option 1 from the following menu when installing subsets to the RIS area: Choose one of the following options: 1) Extract software from [kit location] 2) Create symbolic link to [kit location] 2-12 Installation Notes Enter your choice: _2._6 _D_i_s_k _S_p_a_c_e _R_e_q_u_i_r_e_m_e_n_t_s The subset size tables have been moved to a permanent location in the _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for this release. If you want to add optional subsets after you install Digital UNIX Version 4.0, use the _d_f command to determine free disk space in blocks. Installation Notes 2-13 Processor-Specific Notes 3 This chapter contains notes that apply to processors supported by Digital UNIX Version 4.0: +o General notes on processors +o Digital AlphaStation 200 and Digital AlphaStation 400 Series processors +o Digital AlphaServer 1000 processors +o Digital AlphaServer 2000, AlphaServer 2100 processors and Digital Alpha VME 2100 processors +o DEC 7000 processors +o Digital AXPvme single board computers +o Digital AXPpci 33 processors _3._1 _G_e_n_e_r_a_l _N_o_t_e_s _o_n _P_r_o_c_e_s_s_o_r_s The notes in this section apply to more than one processor type. _3._1._1 _P_C_I-_b_a_s_e_d _S_y_s_t_e_m_s _w_i_t_h _A_T_I _M_a_c_h_6_4 _G_r_a_p_h_i_c_s _C_o_n_t_r_o_l_l_e_r_s On PCI machines that include ATI Mach64 graphics controllers in the configuration, the console environment variable _p_c_i__p_a_r_i_t_y must be set to _o_f_f. Due to a hardware limitation, hardware machine checks will occur if this variable is not turned off. Use the following commands: >>> _s_e_t _p_c_i__p_a_r_i_t_y _o_f_f >>> _i_n_i_t _3._1._2 _P_C_I _S_h_a_r_e_d _I_n_t_e_r_r_u_p_t _S_u_p_p_o_r_t In Digital UNIX Version 3.2D and subsequent releases, PCI-based system and I/O support code is shared interrupt capable. The only exception is the 53C810 (onboard or option) SCSI controller. You can use the following console firmware command to determine if your system has a 53C810 SCSI controller: >>> _s_h_o_w _c_o_n_f_i_g In order to setup your PCI-based system to share interrupts, you must ensure the following: +o The firmware revision for your system supports shared interrupts +o You have placed the option cards in PCI slots that allow sharing Refer to your Digital UNIX Layered Product documentation (for example, for MME or Open3D) for information as to the shared interrupt capabilities of the software. _3._1._3 _S_u_p_p_o_r_t _f_o_r _R_T_S/_C_T_S (_H_a_r_d_w_a_r_e) _F_l_o_w _C_o_n_t_r_o_l Digital UNIX Version 4.0, supports RTS/CTS (hardware) flow control in the serial drivers that are used on the DEC3000 series, DEC2000 series, AlphaStation, and AlphaServer systems. This support can be enabled or disabled using the -_c_r_t_s_c_t_s argument to the _s_t_t_y command. It can also be enabled on logins by specifying the _F_f_l_a_g option _C_R_T_S_C_T_S on the appropriate /_e_t_c/_g_e_t_t_y_d_e_f_s entry. By default, RTS/CTS flow control is disabled. _3._2 _D_i_g_i_t_a_l _A_l_p_h_a_S_t_a_t_i_o_n _2_0_0 _a_n_d _D_i_g_i_t_a_l _A_l_p_h_a_S_t_a_t_i_o_n _4_0_0 _P_r_o_c_e_s_s_o_r_s The following notes apply to the Digital AlphaStation 200 and Digital AlphaStation 400 series processors. _3._2._1 _P_o_w_e_r _M_a_n_a_g_e_m_e_n_t _S_u_p_p_o_r_t _f_o_r _t_h_e _D_i_g_i_t_a_l _A_l_p_h_a_S_t_a_t_i_o_n _2_5_5 This release supports power management for the Digital AlphaStation 255 system. The power management capability allows you to control: +o Disk spindown +o CPU slowdown 3-2 Processor-Specific Notes +o Monitor powerdown (DPMS). The user may control power management settings using a graphical user interface /_u_s_r/_b_i_n/_X_1_1/_d_x_p_o_w_e_r A command line interface _s_y_s_c_o_n_f_i_g_d_b is also available. Specific monitor settings can also be modified using the _x_s_e_t command. See the _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n manual and the _x_s_e_t(1X) and _s_y_s_c_o_n_f_i_g_d_b(8) reference pages for more information. Note that a system (root) disk cannot spin down due to normal system activity. User disks will spin down unless applications are running and the applications require constant access to the user disks. _3._2._2 _M_o_n_i_t_o_r _P_o_w_e_r _M_a_n_a_g_e_m_e_n_t _f_o_r _t_h_e _D_i_g_i_t_a_l _A_l_p_h_a_S_t_a_t_i_o_n _2_5_5 Monitors that do not support DPMS (Display Power Management Signaling) can be damaged by the activation of the DPMS feature. Check your monitor specifications. Monitors that support DPMS and are put in a power savings state will vary in the time it takes to come out of power savings. Users will observe that the longer the monitor is in power-off state, the longer it takes for the display to return as a result of mouse or keyboard activity. This is the result of the monitor phosphor cooling down and the time required to heat it back up, and not a function of the operating system. _3._3 _D_i_g_i_t_a_l _A_l_p_h_a_S_e_r_v_e_r _1_0_0_0 _4/_2_0_0 _P_r_o_c_e_s_s_o_r_s The following notes apply to the Digital AlphaServer Model 1000 4/200 _3._3._1 _E_I_S_A _C_o_n_f_i_g_u_r_a_t_i_o_n _U_t_i_l_t_y _a_n_d _R_I_S _I_n_s_t_a_l_l_a_t_i_o_n When upgrading a AlphaServer 1000 series processor from the firmware CD-ROM, you should boot the firmware file _A_S_1_0_0_0__V_5__1._E_X_E, (version 5.1) and not _A_S_1_0_0_0__V_5__2._E_X_E (version 5.2) as indicated in the _A_l_p_h_a _S_y_s_t_e_m_s _F_i_r_m_w_a_r_e _U_p_d_a_t_e _F_T_1 _R_e_l_e_a_s_e _N_o_t_e_s _O_v_e_r_v_i_e_w If you use version 5.1 instead of version 5.2 you Processor-Specific Notes 3-3 will not be able to perform an installation using RIS. _3._4 _D_i_g_i_t_a_l _A_l_p_h_a_S_e_r_v_e_r _2_0_0_0, _A_l_p_h_a_S_e_r_v_e_r _2_1_0_0 _P_r_o_c_e_s_s_o_r_s _a_n_d _D_i_g_i_t_a_l _A_l_p_h_a _V_M_E _2_1_0_0 _P_r_o_c_e_s_s_o_r_s The notes in this section apply to the AlphaServer 2000, AlphaServer 2100 Server and Digital Alpha VME 2100 series processors. _3._4._1 _S_W_X_C_R _R_a_i_d _C_o_n_f_i_g_u_r_a_t_i_o_n _U_p_d_a_t_e_s Do not perform SWXCR RAID configuration updates with ARC Version 4.2-1 on the AlphaServer 2000 or AlphaServer 2100. _3._4._2 _D_i_g_i_t_a_l _A_l_p_h_a _V_M_E _2_1_0_0 The notes in this section apply to the Digital UNIX software running on the Digital Alpha VME 2100. For information on how to configure the VME subsystem, see the _W_r_i_t_i_n_g _V_M_E_b_u_s _D_e_v_i_c_e _D_r_i_v_e_r_s manual. _3._4._2._1 _U_n_p_r_e_d_i_c_t_a_b_l_e _R_e_s_u_l_t_s _W_h_e_n _P_e_r_f_o_r_m_i_n_g _M_a_s_t_e_r _B_l_o_c_k _T_r_a_n_s_f_e_r_s Performing master block transfers with a data width of D64 can produce unpredictable results. For more information, see Section 3.6.2. _3._5 _K_D_M_7_0 _D_i_s_k _C_o_n_t_r_o_l_l_e_r _o_n _D_E_C _7_0_0_0 _P_r_o_c_e_s_s_o_r_s The KDM70 disk controller is not supported when more than one gigabyte of memory is installed. After running the ECU over a serial line, the cursor will not display. You must change the terminal setup to redisplay the cursor. _3._6 _D_i_g_i_t_a_l _A_X_P_v_m_e _S_i_n_g_l_e _B_o_a_r_d _C_o_m_p_u_t_e_r_s The following notes apply to the Digital UNIX software running on the following single board computers (SBCs): +o Digital AXPvme 64 Single Board Computer 3-4 Processor-Specific Notes +o Digital AXPvme 100 Single Board Computer +o Digital AXPvme 160 Single Board Computer +o Digital AXPvme 230 Single Board Computer For information on how to configure AXPvme single board computers, see the _W_r_i_t_i_n_g _V_M_E_b_u_s _D_e_v_i_c_e _D_r_i_v_e_r_s manual. _3._6._1 _H_a_r_d_w_a_r_e _R_e_s_t_r_i_c_t_i_o_n To install Digital UNIX Version 4.0 on a Digital AXPvme SBC you must have a local disk. To attach to a local disk, a 50-pin IDC SCSI cable is required and must be properly terminated. The exact cable requirements depend on your enclosure, disk mounting, and other factors. This cable is not supplied with the Digital AXPvme 64 SBC. The following cables, specified by Digital part numbers, are examples of cables that may be used for this purpose: +o Part number 17-01244-01, 17-01244-02, or 17- 01244-03 These are, respectively, an 8-, 12-, or 21-inch cable with a 50-pin IDC connector for connection to the AXPvme breakout module, and a female IEEE (Champ) connector for connecting to external drives. +o Part number 17-03459-02 This cable is 40.5 inches long and contains six 50-pin female IDC connectors. A-50 pin IDC SCSI terminator is included. This cable connects the AXPvme breakout module to up to four internal drives with the terminator on the last connector. +o Part number 17-03036-01 This cable is about 87 inches long and contains six 50-pin IDC connectors. This cable connects the AXPvme breakout module to up to four internal drives. It also contains an IEEE (Champ) connector for connection with external drives. A Champ SCSI terminator (part number H8574-A) may be required. Processor-Specific Notes 3-5 _3._6._2 _U_n_p_r_e_d_i_c_t_a_b_l_e _R_e_s_u_l_t_s _W_h_e_n _P_e_r_f_o_r_m_i_n_g _M_a_s_t_e_r _B_l_o_c_k _T_r_a_n_s_f_e_r_s Performing master block transfers with a data width of D64 can produce unpredictable results in the following cases: +o If D64 slave access is performed before memory has been mapped to the VMEbus. +o If memory access does not coincide with the appropriate access mode, such as attempting user access to memory specified as supervisory mode access. +o If the AXPvme SBC is a VME interrupter and is targeted for D64 slave access, the interrupt vector presented by the VME interrupter may not be the vector specified in the _v_b_a__p_o_s_t__i_r_q function. Memory must be mapped to the VMEbus prior to D64 slave access. Access to memory must coincide with the appropriate access mode. If supervisory mode access is specified when memory is mapped, memory accesses must use supervisory mode. If user mode access is specified, both supervisory and user access are allowed. See the _W_r_i_t_i_n_g _V_M_E_b_u_s _D_e_v_i_c_e _D_r_i_v_e_r_s manual for more information on slave and master block transfers. The following notes apply to the Digital AXPpci 33 series processors. _3._6._3 _I_R_Q_s _f_o_r _P_C_I _O_p_t_i_o_n_s _o_n _D_i_g_i_t_a_l _A_X_P_p_c_i _3_3 _S_y_s_t_e_m_s PCI options are assigned IRQs after ISA options are configured. Available IRQs are {5, 9, 10, 15}. The firmware automatically assigns PCI IRQs from this list. IRQ 11 is assigned to the internal SCSI controller. 3-6 Processor-Specific Notes Base System Software Notes 4 This chapter contains notes about issues and known problems with the base operating system and, whenever possible, provides solutions or workarounds to those problems. The following topics are discussed in this chapter: +o Internationalization +o Commands and utilities +o SysMan System Management graphical user interface +o System administration +o Network and communications +o File systems _4._1 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_z_a_t_i_o_n The following notes apply to restrictions on using functions that support internationalization or internationalized components. _4._1._1 _R_e_t_u_r_n _V_a_l_u_e_s _o_f _F_u_n_c_t_i_o_n_s _i_s_w_d_i_g_i_t() _a_n_d _i_s_w_a_l_n_u_m() _U_n_d_e_r _t_h_e _T_h_a_i _L_o_c_a_l_e The return values of the functions _i_s_w_d_i_g_i_t() and _i_s_w_a_l_n_u_m() for Thai digits in the range 0xF0,...,0xF9 are false, even though these values are defined as digits in the _W_o_t_o_t_o _S_t_a_n_d_a_r_d, _V_e_r_s_i_o_n _2._0 relating to the Thai language. _4._1._2 _P_r_i_n_t_i_n_g _P_o_s_t_S_c_r_i_p_t _F_o_r_m_a_t _F_i_l_e_s _i_n _A_s_i_a_n _L_a_n_g_u_a_g_e_s If two or more print jobs are sent to different queues of the same printer within a very short time, it is possible that some jobs will get blocked and cannot be printed. Restart the job using the _l_p_c command. _4._1._3 _L_i_n_e _W_r_a_p_p_i_n_g _i_n _v_i Depending on the composition of the line, the _v_i editor that supports Thai may wrap lines before the right boundary of the screen. For a normal 24x80 screen, a line wraps if more than 80 Thai or ASCII characters are entered, even when the display width of the line is fewer than 80 columns. _4._2 _X/_O_p_e_n-_c_o_m_p_l_i_a_n_t _C_u_r_s_e_s Digital UNIX version 4.0 contains a new curses implementation that incorporates the following sets of programming interfaces: +o X/Open Curses, Issue 4 +o System V Multinational Language Supplement (MNLS) +o Minicurses +o BSD curses These interfaces support the new curses standard and also maintain source compatibility with the curses interfaces found in the previous version of Digital UNIX. However, they do not maintain binary compatibility. Therefore, additional library files are also provided to maintain binary compatibility with existing programs The new curses implementation can be found in these directories: ____________________________________________________ Directory Contents ____________________________________________________ /usr/include curses.h, curshdr.h, term.h, unctrl.h /usr/lib libcurses.a /usr/shlib libcurses.so ____________________________________________________ Libraries supporting the previous curses implementation will be found in the following directories: 4-2 Base System Software Notes _______________________________ Directory Contents _______________________________ /usr/opt/lib libcurses.a /usr/shlib/osf.1 libcurses.so _______________________________ There are no header files provided for the old implementation. All programs that call curses directly will use the new header files when compiling and linking with the new libraries. Existing binary files that were built with the old version of the curses shared library, _l_i_b_c_u_r_s_e_s._s_o, will continue to run without modification. Through the technique called _v_e_r_s_i_o_n_i_n_g old binary files will select the correct shared library. When rebuilding applications that do not call curses directly, but which link with libraries that interface with the old curses implementation, set _L_D__L_I_B_R_A_R_Y__P_A_T_H to the proper directory as indicated in the preceding table, or else specify the complete pathname on the compile command. _4._2._1 _C_h_a_n_g_e_s _i_n _D_a_t_a_t_y_p_e_s, _S_t_r_u_c_t_u_r_e_s, _a_n_d _M_a_c_r_o_s Many functions declared in _c_u_r_s_e_s._h and _t_e_r_m._h are implemented both as routines and macros. In these cases, the default is to compile them as macros which execute more quickly. If you wish to execute the corresponding routines instead of using the macros, add the __N_O_M_A_C_R_O_S compile-time switch. The new curses library provides source compatibility with the old version with respect to function calls, data names, and macro names. However, the implementation of types, variables, structures and macros has changed considerably in some cases. If the existing user code takes advantage of the assumed implementation details of such elements, that program may need to be changed to work with the new curses. Elements whose implementation have changed include: +o datatype: - _c_h_t_y_p_e Base System Software Notes 4-3 +o structures: - __w_i_n__s_t - _W_I_N_D_O_W - _S_C_R_E_E_N - _t_e_r_m +o macros: - _A_* - _A_C_S_* - _K_E_Y_* In previous implementations, the ACS definitions in _c_u_r_s_e_s._h were statically defined constant values. In the new implementation, the definitions are dynamically defined at run time based on the current setting of the _T_E_R_M environment variable. This implementation allows terminals with extra ACS capabilities to make them available to the user while providing a set of default ACS definitions for terminals with lesser capabilities. The implementation changes may cause compile time failures for some programs that depend on the static definitions. For example, the following declaration will not compile when it occurs at the global level: char A = ACS_ULCORNER; The new implementation of the curses library defines the ACS definitions at run time and requires that all assignments be made after the _i_n_i_t_s_c_r() function has been called. _4._2._2 _C_h_a_n_g_e _i_n _B_e_h_a_v_i_o_r _o_f _c_b_r_e_a_k() _F_u_n_c_t_i_o_n The X/Open Curses standard requires that the _c_b_r_e_a_k() function disable the _I_C_R_N_L input processing flag. In the previous Digital UNIX implementation, _c_b_r_e_a_k() did not disable this flag. In applications that relied on this default behavior to advance to new lines, subsequent output lines may now overwrite the last line addressed. Those applications should now set the _I_C_R_N_L flag explicitly after the call to _c_b_r_e_a_k(). Here is a sample code fragment that sets 4-4 Base System Software Notes the _I_C_R_N_L flag: #include struct termios tty; tcgetattr(0, &tty); tty.c_iflag |= ICRNL; tcsetattr(0, TCSANOW, &tty); _4._3 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s The following notes apply to commands and utilities. _4._3._1 _v_d_u_m_p _a_n_d _v_r_e_s_t_o_r_e _C_o_m_p_a_t_a_b_i_l_i_t_y _P_r_o_b_l_e_m _N_o_t_e This is an important note for users of _v_d_u_m_p and _v_r_e_s_t_o_r_e Backups made using _v_d_u_m_p on Digital UNIX Version 4.0 cannot be restored using _v_r_e_s_t_o_r_e on earlier versions of Digital UNIX. Patches will be made available for earlier versions of _v_r_e_s_t_o_r_e to correct this problem. Backups made using _v_d_u_m_p on earlier versions of Digital UNIX can be restored using _v_r_e_s_t_o_r_e under Digital UNIX Version 4.0 without problems. _4._3._2 _S_e_c_u_r_i_t_y The following notes describe problems that may occur when using commands and utilities under certain security settings. _4._3._2._1 _U_n_e_x_p_e_c_t_e_d _C_o_m_m_a_n_d _B_e_h_a_v_i_o_u_r _w_i_t_h _A_C_L_s Programs cannot reliably inspect the permission bits in the _s_t_a_t structure and determine the access that will be granted to a particular user. On local filesystems, read-only mounts and ACLs can both modify the access that will be allowed, On remote filesystems, in addition to read-only mounts and ACLs, there may also be additional controls that can alter the permitted access such as: +o id mapping Base System Software Notes 4-5 +o mandatory access control +o additional authentication requirements Programs which copy files to update them, rather than updating them in place, will often not preserve ACLs. Some programs that have this problem are _g_z_i_p, _c_o_m_p_r_e_s_s, and _e_m_a_c_s. The best solution for programs that need to make access decisions is for the program to use the _a_c_c_e_s_s() call to determine what access will be granted. Note that even this may not work as the access protections of the file could be changed between the _a_c_c_e_s_s() call and the _r_e_a_d, _w_r_i_t_e, or _e_x_e_c_u_t_e operation. For programs which copy files, the command: # _c_p -_p will copy a file preserving ACLs and any other extended attribute (property list). See the _a_c_l(4), and _p_r_o_p_l_i_s_t(4) reference pages for more information. _4._3._2._2 _A_r_c_h_i_v_e _T_o_o_l_s _a_n_d _S_e_c_u_r_i_t_y This note is to clarify the interactions between the archive tools _p_a_x, _t_a_r, and _c_p_i_o, and files containing property lists or Access Control Lists (ACLs). or ACLs alone. When you extract files with the above utilities without using the -_p option, and the following conditions apply: +o you are extracting a tar or cpio archive into a directory that has default ACLs, or +o you are extracting a tar or cpio archive that contains directories with default ACLs, and +o not all of the files on the archive have associated ACLs. Then, when files that do not have an associated ACL them are extracted, they will inherit the default ACL that is in force on the directory in which they are being created. This behavior was selected to allow file extractions to work as expected in as many cases as possible. 4-6 Base System Software Notes For times when the above behavior is not appropriate, an alternative behavior has been associated with the -_p option. If you use the -_p option, any file that is extracted from the archive will be given only the property list, ACL, and file permissions that were stored in the archive with that file. For _t_a_r archives you can use either the -_p option to the _t_a_r command or the -_p _p option to the _p_a_x command. For _c_p_i_o archives you can use the -_p _p option to the cpio command See the _t_a_r(1), _p_a_x(1), _c_p_i_o(1), and _t_a_r(4) reference pages. _4._3._2._3 _e_m_a_c_s _C_a_n _L_o_s_e _A_C_L _F_i_l_e _S_e_t_t_i_n_g_s By default, _e_m_a_c_s will rename the original file, and save the new file as a copy, under the original name. If the original file had an Access Control List (ACL) it will now apply to the backup file. If the directory had a default ACL, the new file (original filename) will now have the default ACL instead of the original ACL. If the directory did not have a default ACL, the new file will be protected only by the file permission bits. The _e_m_a_c_s utility has some user-preference variables which can be set to control which file will retain the original ACL. The relevent EMACS variables are: +o _b_a_c_k_u_p-_b_y-_c_o_p_y_i_n_g +o _b_a_c_k_u_p-_b_y-_c_o_p_y_i_n_g-_w_h_e_n-_m_i_s_m_a_t_c_h +o _b_a_c_k_u_p-_b_y-_c_o_p_y_i_n_g-_w_h_e_n-_l_i_n_k_e_d _4._3._3 _M_a_i_l _a_n_d _m_a_i_l_x _C_o_m_m_a_n_d _B_e_h_a_v_i_o_r Since the _m_a_i_l_x and _M_a_i_l command have become XPG4 compliant, their command behavior has changed. When using a carriage return with no arguments in command mode, you no longer see the next message. A carriage return with no arguments now behaves like the _p_r_i_n_t command and not the _n_e_x_t command. The current message is displayed and the message pointer stays on the current message. _4._3._4 _U_s_i_n_g _g_e_n_d_i_s_k _o_n _D_i_s_k_e_t_t_e _D_e_v_i_c_e_s The _g_e_n_d_i_s_k utility is used to create product media. Base System Software Notes 4-7 There is a problem in using it on FDI diskette devices, the diskette drive found on all non- Turbochannel bus Alpha platforms. The solution involves making some hard links to the diskette device special files using the name of the device that _g_e_n_d_i_s_k will use. 1. Make the hard links as follows: # _c_d /_d_e_v # _l_n _r_f_d_0_c _r_f_l_0_c # _l_n _r_f_d_0_a _r_f_l_0_a # _l_n _f_d_0_a _f_l_0_a # _l_n _f_d_0_c _f_l_0_c 2. Format the diskette disk as follows: # _f_d_d_i_s_k -_f_m_t /_d_e_v/_r_f_d_0_c You will see the following messages: NOTE: Setting interleave factor to ``-i2:4''. Use ``-i[:]'' option to override. Disk type: 3.50 inch, HD (1.44MB) Number of sectors per track: 18 Number of surfaces: 2 Number of cylinders: 80 Sector size: 512 interleave factor: 2:4 Formatting disk... Percentage complete: Format complete, checking... Quick check of disk passes OK. 3. Use _d_i_s_k_l_a_b_e_l to label the diskette: # _d_i_s_k_l_a_b_e_l -_w_r _f_d_0 _r_x_2_3 4. Run _g_e_n_d_i_s_k as follows: _N_o_t_e When running the _g_e_n_d_i_s_k utility on the diskette using these instructions, do not respond _y_e_s to the question asking to clean the disk. The following is an example of a _g_e_n_d_i_s_k command 4-8 Base System Software Notes session: # _g_e_n_d_i_s_k -_d _M_Y_P_R_O_D_U_C_T_4_0_0 /_d_e_v/_r_f_d_0_c Generating MYPRODUCT400 Kit from on /dev/fl0c WARNING: this will remove any information stored in /dev/fl0c. Are you sure you want to do this? (y/n): y Do you want to clean the entire disk first? Note: This will replace your current disk label with a default one. (y/n) [n]: n Preparing /dev/fl0c (floppy) done. Checking /dev/fl0c /sbin/ufs_fsck /dev/rfl0c ** /dev/rfl0c File system unmounted cleanly - no fsck needed Mounting /dev/fl0c on /usr/tmp/cd_mnt8344 Writing Images (dd=/). Image instctrl...done. Image SVGASTATIC100...done. Verifying Images (dd=/). Image instctrl...done. Image SVGASTATIC100...done. Kit MYPRODUCT400 done. Cleaning up working directories. Unmounting /dev/fl0c _4._3._5 _S_o_m_e _e_m_a_c_s _C_o_m_m_a_n_d _L_i_n_e _O_p_t_i_o_n_s _F_a_i_l Digital ships the emacs software as it is received from the source. The following command line options do not work as documented in the emacs reference page: -geometry -iconic -ib -T -iconname -in -mc -i Base System Software Notes 4-9 In some cases a solution is available using an appropriate X resource. _4._3._6 _D_i_r_e_c_t_o_r_y _T_r_e_e /_u_s_r/_o_p_t/_s_t_e_r_l_i_n_g _R_e_n_a_m_e_d The /_u_s_r/_o_p_t/_s_t_e_r_l_i_n_g directory tree has been renamed to /_u_s_r/_o_p_t/_o_b_s_o_l_e_t_e. All the files that were in the /_u_s_r/_o_p_t/_s_t_e_r_l_i_n_g directory have been moved to the /_u_s_r/_o_p_t/_o_b_s_o_l_e_t_e directory tree. The following files have been moved within the /_u_s_r/_o_p_t file system. ___________________________________________________ Old location of commands New location of commands ___________________________________________________ ~sterling/sbin/cpio ~obsolete/sbin/cpio ~sterling/sbin/tar ~obsolete/sbin/tar ~sterling/usr/bin/cpio ~obsolete/usr/bin/cpio ~sterling/usr/bin/tar ~obsolete/usr/bin/tar ___________________________________________________ If you have scripts that rely on the old location, a symbolic link can be placed in /_u_s_r/_o_p_t to point to the new location as follows: # _c_d /_u_s_r/_o_p_t # _l_n -_s _s_t_e_r_l_i_n_g _o_b_s_o_l_e_t_e _4._3._7 _P_O_S_I_X _S_h_e_l_l To run the POSIX shell, the environment variable _B_I_N__S_H, must be set to _x_p_g_4. The POSIX shell is invoked when the user runs the command _s_h. The POSIX shell is located in /_u_s_r/_b_i_n/_p_o_s_i_x/_s_h. If BIN_SH is not set to _x_p_g_4, the Bourne shell is invoked when the user runs the _s_h command. Relative or absolute paths are not determining factors; executing /_u_s_r/_b_i_n/_s_h gives the same result as _s_h. The determining factor is the environment variable BIN_SH. _4._3._8 _S_e_n_d_m_a_i_l _C_o_n_f_i_g_u_r_a_b_l_e _M_a_x_i_m_u_m _H_o_p _C_o_u_n_t In _s_e_n_d_m_a_i_l, the maximum hop count is now configurable. If not specified, the hop count defaults to 17. Each time a message is forwarded 4-10 Base System Software Notes through a host, the hop count is increased. When this count exceeds the maximum hop count value, the message is rejected, because it is automatically assumed that an endless loop has occurred. The default value is acceptable in most installations but you may want to increase the value if too many messages are being lost. _4._3._9 _c_k_s_u_m _R_e_p_o_r_t_s _I_n_c_o_r_r_e_c_t _V_a_l_u_e_s The current values reported by the _c_k_s_u_m command are incorrect according to the IEEE Std 100 3.2-1992. To conform with XPG4 requirements, new calculations have been made for the checksums. For current compatibility, the default action of the _c_k_s_u_m command is to report the present _c_k_s_u_m values. To obtain the new checksums, set the environment variable _C_M_D__E_N_V to the string _x_p_g_4. For example: export CMD_ENV=xpg4 _4._3._1_0 _d_f _a_n_d _X_P_G_4 _C_o_m_p_l_i_a_n_c_e The default behavior for the _d_f command is BSD SVR4 compliant. If XPG4 compliant behavior is desired, set the CMD_ENV environment variable to _x_p_g_4. The XPG4 compliant _d_f command takes the following syntax: df [-eiknPt] [-F fstype] [file | file_system ...] See the _d_f (1) reference page for more information. _4._3._1_1 _U_s_e _o_f _e_c_h_o -_n _i_n _S_c_r_i_p_t_s The default of the /_u_s_r/_b_i_n/_e_c_h_o command is compliant with the XPG4 standard. If the CMD_ENV environment variable is not set or is set to _x_p_g_4, the _e_c_h_o command will treat the option -_n as a string. The _e_c_h_o command supports the -_n option when the environment variable CMD_ENV is set to _b_s_d. _4._3._1_2 _a_w_k _L_i_n_k_e_d _t_o _n_a_w_k In a future version of Digital UNIX, the link between _a_w_k and _n_a_w_k will be removed, leaving an XPG4- compliant version of _a_w_k. You should ensure that your scripts use /_u_s_r/_b_i_n/_a_w_k in place of any other Base System Software Notes 4-11 version of the command currently existing on the system. The _g_a_w_k command invokes GNUawk, the Free Software Foundation version of _a_w_k. This command has been moved out of the base subset to the Free Software Foundation subset. The _o_a_w_k command has been removed. _4._3._1_3 _U_n_s_u_p_p_o_r_t_e_d _v_m_h _C_o_m_m_a_n_d The _v_m_h command in the /_u_s_r/_b_i_n/_m_h suite is not supported in this release. _4._3._1_4 _R_e_s_t_r_i_c_t_i_o_n_s _o_n _t_h_e _o_d _C_o_m_m_a_n_d The /_u_s_r/_b_i_n/_o_d command has the following restrictions: +o You cannot use the _o_d command with disks that have a capacity of more than 4 GB. +o You cannot specify an offset of more than (2**32)-1 as a starting point for the _o_d command. _4._4 _S_y_s_M_a_n _S_y_s_t_e_m _M_a_n_a_g_e_m_e_n_t _G_r_a_p_h_i_c_a_l _U_s_e_r _I_n_t_e_r_f_a_c_e The following notes apply to restrictions on using the SysMan applications. _4._4._1 _R_e_s_t_r_i_c_t_i_o_n_s _o_n _U_s_i_n_g _t_h_e _D_i_s_k _C_o_n_f_i_g_u_r_a_t_i_o_n _M_a_n_a_g_e_r The disk configuration manager is a new application that will allow the inspection and modification of disk attributes, partition information in particular. Type /_u_s_r/_s_b_i_n/_d_i_s_k_c_o_n_f_i_g at the command line to invoke the application and display the top level window. This note describes some restrictions on using the disk configuration manager in Digital UNIX, Version 4.0. The _d_i_s_k_c_o_n_f_i_g utility displays a list of disks attached to the system. This occurs implicitly upon invocation. The selection of a disk from this list presents the attributes of the disk as recorded on the disk label if a label is present and the drive is not defective. If no label is present and the drive is not defective, default information is presented. An error message is presented if the drive is defective. Much of the data displayed in the windows 4-12 Base System Software Notes can be edited by the user to change the characteristics of a disk label. Known problems are as follows: +o The _d_i_s_k_c_o_n_f_i_g utility will ignore an attached disk that has no associated special device files. Such a disk will not appear in the top level list. +o The _d_i_s_k_c_o_n_f_i_g utility will create an AdvFS file system on a specified partition, only in the most primitive way. That is to say that the _d_i_s_k_c_o_n_f_i_g utility does not take advantage of the powerful set of AdvFS file management capabilities. When you choose to create an AdvFS file system, a warning dialog will appear to state same. +o If you are creating AdvFS file systems on multiple partitions, you should commit them one at a time. That is, select AdvFS for the first partition, enter the domain and set names for that partition, and press commit. Then repeat the procedure for subsequent partitions. Failure to do so is not dangerous, but may be confusing as the _d_i_s_k_c_o_n_f_i_g utility will not redisplay the domain and set names once another partition uses these areas of the display. +o The _d_i_s_k_c_o_n_f_i_g utility does not currently support VGA 640x480 graphics. Consequently, the Partition Disks option on the installation GUI cannot be used on a system with VGA 640x480 graphics. The solution is to choose a UNIX shell from the installation GUI and use the shell to accomplish disk partitioning with disklabel. Continue with the installation when the disk is repartitioned. +o Disks moved out of a raid array and still bearing the label written while in the raid array, are not repairable by the _d_i_s_k_c_o_n_f_i_g utility, only by setting the label to default values. Press _d_e_f_a_u_l_t and _c_o_m_m_i_t. Then make your desired changes. Alternatively, you can use the _d_i_s_k_l_a_b_e_l command to change disk labels. +o The _n_o_n_e option when selecting boot blocks means _w_r_i_t_e _n_o _b_o_o_t _b_l_o_c_k_s. Boot blocks will not be removed; rather, they will remain as they were. _4._4._2 _A_c_c_o_u_n_t _M_a_n_a_g_e_r The following notes apply to the account manager, _d_x_a_c_c_o_u_n_t_s. Base System Software Notes 4-13 _4._4._2._1 _U_s_a_g_e _N_o_t_e When copying user accounts via cut and paste or drag and drop, the Allow Duplicate UIDs option in the General Preferences dialog box will be honored. For example, when making a copy of user account that has a UID of 200, if the Allow Duplicate UID's check box is off (the default), the resulting copy will have a unique UID automatically generated. If the Allow Duplicate UID's check box is on, then the copy will have an indentical UID. The same rules apply to copying groups. _4._4._2._2 _A_c_c_o_u_n_t _M_a_n_a_g_e_r _R_e_s_t_r_i_c_t_i_o_n_s The account manager has the following restrictions on both base security and enhanced security (C2) systems: +o Using mouse button 1 (MB1) to drag and drop users, groups, or templates does a copy operation, not a move operation. This is different from the CDE/Motif default where MB1 performs a drag and drop move operation and Shift-MB1 is required to perform a copy operation. For example, using MB1 to drag a user from the Local Users view and dropping it in the NIS Users view will create a copy of that user in NIS. Workaround: Delete the original icon after the copy has been completed. +o The account manager allows you to specifiy the minimum and maximim range for a UID or GID. However you cannot specify the starting value in the range. Workaround: Set a starting value within the range using the _u_s_e_r_m_o_d or _g_r_o_u_p_m_o_d commands: usermod -D -x next_uid=xxx usermod -D -x next_gid=xxx For example, if the Minimum UID is 100 and the Maximum UID is 10000 then: usermod -D -x next_uid=5000 causes account manager to start generating UIDs from 5000. +o If you change the UID of a user, the ownership of user's home directory and files will not be changed. 4-14 Base System Software Notes Workaround: Use the _c_h_o_w_n command to change the directory and files, if applicable. +o You cannot drag and drop items across different instances of account manager. For example, if account manager A on system 1 and account manager B on system 2 are both being displayed on the same workstation, then you cannot drag and drop between account manager A and B Workaround: Use the copy/paste feature to copy users, groups, or templates from account manager A to B. +o Restriction: Two system adminstrators should not run two different concurrent instances of account manager. Workarounds: account manager correctly allows two or more system administrators to work on the same password files simultaneously. The proper file locking will occur and new accounts can be added or modified. However, the local groups file, /_e_t_c/_g_r_o_u_p, and the NIS groups file, /_v_a_r/_y_p/_s_r_c/_g_r_o_u_p, are written out after each group modification. Therefore, the last system administrator to make a change in a groups view window would overwite the any prior changes from a differnt system administrator. For this reason, running multiple, concurrent account manager instances is not recommended. +o When running account manager from a terminal window, occasionally the following message might be written to stdout: Warning: DtComboBoxWidget: Unable to find item to select Workaround: None. These messages can be safely ignored. _4._4._2._3 _A_c_c_o_u_n_t _M_a_n_a_g_e_r _P_r_o_b_l_e_m_s Leading and trailing white space is not stripped from text entry areas. This could lead to confusion, for example, if a field on the Find dialog contains a space character before the desired search string. The search string would not match becuase of the spurious space character. Base System Software Notes 4-15 _4._4._2._4 _E_n_h_a_n_c_e_d _S_e_c_u_r_i_t_y _A_c_c_o_u_n_t _M_a_n_a_g_e_r _P_r_o_b_l_e_m_s The following problems apply to the account manager when running on enhanced security systems. +o The Lock/Unlock Toolbar and Menu Options are inactive for the Template views. Workaround: Change the template lock setting on the Create/Modify Template dialog screen after selecting the template by double clicking on the template icon in the Template view icon box. +o The C1Crypt Encryption Type restricts the password length to between 6 and 8 characters even though the Password Controls' Minimum Length and Maximum Length fields imply otherwise. Workaround: Set passwords through /_u_s_r/_t_c_b/_b_i_n/_d_x_c_h_p_w_d or the /_u_s_r/_b_i_n/_p_a_s_s_w_d command when the C1Crypt Encryption type is chosen. +o Do not set a template Encryption Type to C1Crypt as this will invalidate the template. Workaround: Set the C1Crypt Encryption type for the user from the Create/Modify User dialog. +o Account manager does not enforce the Minimum/Maximum password length limitation when setting passwords. Workaround: Set passwords through /_u_s_r/_t_c_b/_b_i_n/_d_x_c_h_p_w_d or the /_u_s_r/_b_i_n/_p_a_s_s_w_d command if the Minimum/Maximum password length limitation is necessary. +o The Pointer Focus Prompt message in the Status Line of the Icon Box will display Delete instead of Retire when the mouse pointer is in the Retire toolbar icon. +o Error messages generated from the Create/Modify Template dialog box refer to the user name when they should refer to the template name. +o On enhanced security system, you typically retire users instead of deleting them. However, there are times when you might want to delete a user account. account manager supports retiring user accounts but not deleting them. Workaround: To delete a user account you must do the following: 4-16 Base System Software Notes 1. Manually edit the /_e_t_c/_p_a_s_s_w_d and /_e_t_c/_g_r_o_u_p_s files to remove references to the user. 2. Remove the user from the protected password database using the following command: # /_u_s_r/_t_c_b/_b_i_n/_e_d_a_u_t_h -_r <_u_s_e_r _n_a_m_e> +o Renaming a user by changing the Username field of the Create/Modify User dialog box in Modify mode does not clean up the protected password database entry for the old name. Workaround: Use the following command to remove the dangling protected password database entry: # /_u_s_r/_t_c_b/_b_i_n/_e_d_a_u_t_h -_r <_u_s_e_r _n_a_m_e> +o Do not rename a template by changing the Template name field of the Create/Modify Template dialog box in Modify mode. Account manager will actually create a new template without removing the old template. However, the old template's icon will be removed from the icon box. Workaround: Restart the account manager to restore the former template icon. Delete the undesired template using the Delete Toolbar icon or the Edit->Delete... option from the Template view. +o Accounts and templates inherit their settings either from locally defined values in their protected password database entry or from the templates that they may reference. All accounts and templates implicitly reference a default template. The default template is not served by NIS. This creates an inconsistency for the account manager when displaying NIS user accounts and templates on a NIS master. The user and template values displayed may be the default template values of the NIS master. When a NIS user logs into a NIS client, the NIS client's default template might be different from the NIS master's default template. The client's default template will be used to establish the user's account settings. +o Using drag and drop to copy a user copies the user's template references by value when the user is being dropped on a different view. This means that the template itself is no longer referenced by the newly created account. Instead, the Base System Software Notes 4-17 template's values are contained directly in the new user's protected password database entry. For example, assume the local user Joe has a account based on the developers template. If you drag and drop Joe from the to the NIS Users view, the new account will be backed to the default template and the attributes from the developers template will be placed directly in new account's protect password database entry (effectively overriding any corresponding attributes from the default template). Workaround: Modify the copied user and change his template from default to the desired template. Note that the template reference is maintained if the user is dropped within the same view. +o Dropping a template icon on a user changes the user's account to use that template. However, the template's lock attribute is not honored. For example, if the template developer has the lock field enabled, then dropping this template a user should cause the account to be locked but it does not. Workaround: Only the drag and drop method of template assignment has this problem. You can use the Create/Modify dialog box to change a single user's template or use the Modify Selected dialog box to change templates for several selected users. Both methods will correctly propagate the template's lock field. +o Dragging and dropping a template on a user displayes and confirmation message in the view's status line. This message incorrectly displays template %2 instead of the template's name. Workaround: None. +o Deleting a newly created template (the template was created after starting the account manager) will cause the application to crash. Workaround: Please restart account manager and then delete the template. +o After deleting a template, the NIS maps are not remade. Workaround: Manually remake the NIS maps or perform an account manager function (eg. Account Modification) that will trigger the maps to be remade. To manually remake the maps do the 4-18 Base System Software Notes following: # _c_d /_v_a_r/_y_p # _m_a_k_e _a_l_l _4._4._3 _E_n_h_a_n_c_e_d _S_e_c_u_r_i_t_y _a_n_d _A_c_c_o_u_n_t _M_a_n_a_g_e_r +o Only the root user can change a password using the Change Password graphical user interface, /_u_s_r/_t_c_b/_b_i_n/_d_x_c_h_p_w_d. All non-root users must use the Change Password command line interface, /_b_i_n/_p_a_s_s_w_d to change their passwords. +o The Lock/Unlock Toolbar and Menu Options are inactive for the Template views. Workaround: Change the template lock setting on the Create/Modify Template dialog screen after selecting the template by double clicking on the template icon in the Template view icon box. +o The C1Crypt Encryption Type restricts the password length to between 6 and 8 characters even though the Password Controls' Minimum Length and Maximum Length fields imply otherwise. +o Do not set a template Encryption Type to C1Crypt as this will invalidate the template. Workaround: Set the C1Crypt Encryption type for the user from the Create/Modify User dialog. +o The Account Manager does not enforce the Minimum/Maximum password length limitation when setting passwords. Workaround: Set passwords through /_u_s_r/_t_c_b/_b_i_n/_d_x_c_h_p_w_d or the /_u_s_r/_b_i_n/_p_a_s_s_w_d command if the Minimum/Maximum password length limitation is necessary. +o The Pointer Focus Help message in the Status Line of the Icon Box will display Delete instead of Retire when the mouse pointer is in the Retire toolbar icon. +o Error messages generated from the Create/Modify Template dialog reference user name when they should reference template name. +o There is no mechanism to remove a user from the BSD and Protected databases. Base System Software Notes 4-19 Workaround: The user must be removed from the BSD databases by manually editing the /_e_t_c/_p_a_s_s_w_d and /_e_t_c/_g_r_o_u_p files. The user can be removed from the Protected database using the command: # /_u_s_r/_t_c_b/_b_i_n/_e_d_a_u_t_h -_r <_u_s_e_r _n_a_m_e> +o Renaming a user by changing the User name field of the Create/Modify User dialog box in Modify mode does not clean up the Protected Password entry of the old name. Workaround: To remove a dangling protected entry, use the command: # /_u_s_r/_t_c_b/_b_i_n/_e_d_a_u_t_h -_r <_u_s_e_r _n_a_m_e> +o Do not rename a template by changing the Template name field of the Create/Modify Template dialog box in Modify mode. The account manager will actually create a new template without removing the old template. However, the old template's icon will be removed from the icon box. Workaround: Restart the Account Manager to restore the former template icon. Delete the undesired template using the Delete Toolbar icon or the Edit->Delete... option from the Template view. +o Accounts and templates inherit their settings either from locally define values in their private entry or from templates that they may reference. All accounts and templates implicitly reference a default template. The default template is not served by NIS which creates an inconsistency for the Account Manager when displaying NIS user accounts and templates on a NIS master. The user and template values displayed may be the default template values of the NIS master. When a NIS user logs into a NIS client, the NIS client's default template which might be different from the NIS master's default template will be used to establish the user's account settings. +o The Drag/Drop feature to copy a user copies template references by value when the user is being dragged to a different view (eg. Local to NIS). This means that the template is no longer referenced in the newly created account but the template values are contained int the new users profile. The template reference is maintained if the user is dragged within the same view. 4-20 Base System Software Notes +o The Copy/Paste feature to copy a user always copies template references by value. This means that the template is no longer referenced in the newly created user account but the template values are contained in the new users profile. +o Template Assignment through the Drag/Drop feature does not update the user's lock field. Workaround: Manually update the Lock field by selecting the Lock toggle button or assign templates to users through the Template pull down list of the Create/Modify User dialog. +o Template Assignment through the Drag/Drop feature of a newly created template assigns the template by value. This means the user does not reference the template but the template values are contained in the users profile. Workaround: Manually assign the template to the user through the Template pull down list of the Create/Modify User dialog. +o Template Assignment through the Drag/Drop feature of a newly created template displays a confirmation message in the status area which references template %2 instead of the template name. +o Deleting a newly created template (the template was created after starting the Account Manager) will result in a core dump. Workaround: Restart the account manager and then delete the template. +o The NIS Maps are not remade after template deletion. Workaround: Manually remake the NIS maps or perform an Account Manager function (eg. Account Modification) that will trigger the maps to be remade. +o Leading and trailing white space is not stripped from text entry areas. This could lead to confusion when, for example, a field on the Find dialog contains a space before the entered text. The Find dialog includes the white space when attempting to determine the view members that match the given field. Base System Software Notes 4-21 _4._4._4 _S_w_a_p _W_a_r_n_i_n_g _i_n _d_x_s_y_s_i_n_f_o When using System Information, _d_x_s_y_s_i_n_f_o, the swap warning Light will not illuminate if the available swap space falls below 10 percent free, unless the available swap meter is being displayed. Both of these options can be activated by selecting them from the View menu. _4._4._5 _F_i_l_e _S_y_s_t_e_m _P_e_r_c_e_n_t _F_u_l_l _V_a_l_u_e_s _M_a_y _b_e _I_n_c_o_r_r_e_c_t The value of Percent Full in the file system area of _d_x_s_y_s_i_n_f_o may be inaccurate. For the correct value of Percent Full, use the _d_f command and refer to the Capacity value. _4._4._6 _T_h_e _d_x_s_y_s_i_n_f_o _U_t_i_l_i_t_y _M_a_y _D_i_s_p_l_a_y /_d_e_v/_p_r_f _a_s _a _T_a_p_e _D_e_v_i_c_e The _d_x_s_y_s_i_n_f_o application may display /_d_e_v/_p_r_f as a tape device depending on the subsets installed on the particular machine. Also, when Update Devices is selected, another /_d_e_v/_p_r_f icon may be added to the device area. _4._4._7 _d_x_s_h_u_t_d_o_w_n _D_o_e_s _N_o_t _P_r_o_h_i_b_i_t _U_s_e_r _L_o_g_i_n_s The _d_x_s_h_u_t_d_o_w_n application does not create the /_e_t_c/_n_o_l_o_g_i_n files as described in the documentation. This means that users will be able to login to a machine that is being shutdown up until the actual time of the shutdown. Note, this behavior differs from that of the _s_h_u_t_d_o_w_n command which creates the /_e_t_c/_n_o_l_o_g_i_n file at 5 minutes prior to the shutdown. _4._4._8 _P_r_i_n_t _C_o_n_f_i_g_u_r_a_t_i_o_n _M_a_n_g_e_r The Print Configuration Manager may have some problems with /_e_t_c/_p_r_i_n_t_c_a_p files from DEC OSF/1 Version 3.2 or earlier, as follows +o Aliases that conflict with system-assigned names Using /_e_t_c/_p_r_i_n_t_c_a_p files in the current version of Digital UNIX, the system assigns printers names _l_p[_0-_9]*, [_0-_9]*, and for the default printer, lp. For example, the default printer may have a name field such as _l_p_0|_0|_l_p|_d_e_f_a_u_l_t|_d_e_c_l_a_s_e_r_3_5_0_0:.... 4-22 Base System Software Notes Another printer may be named _l_p_7|_7|_s_o_m_e__a_l_i_a_s|_a_n_o_t_h_e_r _a_l_i_a_s:.... Therefore, the system has difficulty with printers that have less than two names or that use these reserved names as aliases. +o Altered attribute validation Some of the attribute value checking is different between earlier versions and the current version. For example, some fields that were not required now are, and some attributes values that were legal no longer are. +o Trailing comments The Print Configuration Manager requires that all comments be associated with a printer. As a result, comments appearing after the last printer are truncated. To avoid these problems, invoke the _p_r_i_n_t_c_o_n_f_i_g utility with the menu interface (_p_r_i_n_t_c_o_n_f_i_g -_u_i _m_e_n_u). This brings up the _l_p_r_s_e_t_u_p utility which is fully compatible with earlier _p_r_i_n_t_c_a_p files. _4._5 _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n The following notes apply to system administration. _4._5._1 _E_n_h_a_n_c_e_d _S_e_c_u_r_i_t_y The following notes apply to the use of enhanced security features. _4._5._1._1 _D_i_s_t_r_i_b_u_t_i_o_n _o_f _E_n_h_a_n_c_e_d _S_e_c_u_r_i_t_y _P_r_o_f_i_l_e_s _v_i_a _N_I_S This note covers problems that may occur when distributing of enhanced security profiles via NIS. +o The NIS master server must always be available, or _l_o_g_i_n attempts will fail after a timeout. +o Logins and failed login attemps for NIS-shared accounts require updating the last unsuccessful and last successful login fields, which requires a response from the master's _r_p_c._y_p_p_a_s_s_w_d_d process. That process will block waiting for any previous updates to complete. Completion of those updates is dependent on the completion of the yppush operation. The _y_p_p_u_s_h completion is dependent on Base System Software Notes 4-23 having the NIS slave servers being reachable and responsive. The more NIS slave servers a given NIS domain has, the slower this update process will be. Also, simultaneous login attempts will be processed sequentially by the NIS master, each waiting on the _y_p_p_u_s_h for the previous to succeed. Thus, with several simultaneous attempts, some may time out and need to be retried by the users. This can be alleviated to some extent by using the -_p option to _y_p_p_u_s_h. One way to do this is to modify the file /_v_a_r/_y_p/_M_a_k_e_f_i_l_e and change the _Y_P_P_U_S_H= line. For example: YPPUSH=$(YPDIR)/yppush -p 6 This example allows up to six simultaneous transfers to NIS slave servers. +o NIS slaves which are listed in the _y_p_s_e_r_v_e_r_s NIS map on the NIS master but which do not already have a copy of the _p_r_p_a_s_s_w_d and _p_r_p_a_s_s_w_d__n_o_n_s_e_c_u_r_e NIS maps will not succeed in transfering those maps during the _y_p_p_u_s_h operation. However, that failure will involve a timeout in the _y_p_p_u_s_h on the master, and will contribute to login failures while waiting since the timeout for the _y_p_p_u_s_h is longer than for _l_o_g_i_n attempts. This can be addressed by ensuring that all the NIS slaves have these maps by a procedure like the following (to be executed on each slave server which does not yet have these maps): # /_v_a_r/_y_p/_y_p_x_f_r -_d <_d_o_m_a_i_n_n_a_m_e> -_h _N_I_S_M_A_S_T_E_R -_c _p_r_p_a_s_s_w_d# /_v_a_r/_y_p/_y_p_x_f_r -_d <_d_o_m_a_i_n_n_a_m_e> -_h _N_I_S_M_A_S_T_E_R -_c _p_r_p_a_s_s_w_d__n_o_n_s_e_c_u_r_e In the above, substitute the name of the local NIS master server for the _N_I_S_M_A_S_T_E_R token. This will transfer initial copies of those maps for those slave servers. +o The time allowed for responses to RPC requests is only 25 seconds. The more profiles which are in the prpasswd map, the more likely that time limit is to expire during a login attempt, causing that attempt to fail. In testing, 4000 accounts seemed to be close to the upper limit. Simultaneous or nearly-simultaneous login attempts will fail if the NIS master server does not respond quickly enough to the waiting login processes. If the 4-24 Base System Software Notes total time taken on the NIS master for the command # _m_a_k_e _p_a_s_s_w_d _p_r_p_a_s_s_w_d exceeds 25 seconds, then only one user will succeed in logging in at a time. Internal testing has demonstrated that 4000 profiles and infrequent logins (3 at a time) can work, but even fewer profiles can be accommodated if bursts of nearly- simultaneous logins are frequent. +o Login updates are checked by the login processes. This requires that the _y_p_p_u_s_h operation for the _p_r_p_a_s_s_w_d map must take place. Therefore that map (at least) must be pushed during the normal operation of the _r_p_c._y_p_p_a_s_s_w_d_d daemon. Setting the /_v_a_r/_y_p/_M_a_k_e_f_i_l_e file variable _N_O_P_U_S_H is not recommended for such configurations. +o Sites which cannot use NIS to share prpasswd information may be able to use NFS to share the files /_t_c_b/_f_i_l_e_s and /_v_a_r/_t_c_b/_f_i_l_e_s directories instead. This will require exporting the directories with root access to the participating nodes (with -_r_o_o_t=_c_l_i_e_n_t_1:_c_l_i_e_n_t_2:_c_l_i_e_n_t_3 or - _r_o_o_t=_0 as appropriate, see the _e_x_p_o_r_t_s(4) reference page). It also requires that NFS locking is enabled to ensure that no database corruption will occur. _4._5._1._2 _E_n_h_a_n_c_e_d _S_e_c_u_r_i_t_y _a_n_d _D_i_s_a_s_t_e_r _R_e_c_o_v_e_r_y Because the user profiles and ttys information are now stored in database files, the previous recovery method of editing the files while in single-user mode is no longer available. However, as long as the /_u_s_r (and, if separate, /_v_a_r) filesystems are mounted, the _e_d_a_u_t_h(8) utility can be used in single-user mode to edit extended profiles and ttys database entries. If the /_e_t_c/_p_a_s_s_w_d file is somehow lost, but the extended profiles are still available, then a command sequence like the following can be used to recover some of the missing data: # bcheckrc # /tcb/bin/convuser -dn | /usr/bin/xargs /tcb/bin/edauth -g | \ sed '/:u_id#/!d;s/.*:u_name=//;s/:u_id#/:*:/;s/:u_.*$/:/' \ >psw.missing This will create a psw.missing file containing Base System Software Notes 4-25 entries like the following: root:*:0: Primary group information, finger information, home directory, and login shell are not recorded in the extended profile. The data for those fields must be recovered by other means. _4._5._1._3 _U_s_e_r_n_a_m_e _L_e_n_g_t_h _R_e_s_t_r_i_c_t_i_o_n Enhanced security will not allow usernames longer than the documented maximum of 8 characters. _4._5._2 _B_o_o_t_a_b_l_e _T_a_p_e For this release, the LSM product and AdvFS _a_d_d_v_o_l utility are not supported. Also, not all platforms and tape drives support bootable tape. Supported processor platforms are: +o DEC 3000-500 +o DEC 3000-400 +o DEC 3000-600 +o DEC 3000-300 +o DEC 3000-300X +o DEC 3000-900 +o DEC 2100 4/275 +o AlphaStation 600 5/266 +o AlphaStation 200 4/100 +o AlphaStation 200 4/166 Supported tape devices are: +o TLZ06, 4mm, 2.0GB/4.0GB +o TLZ07, 4mm, 4-8GB +o TZK10, QIC tape, 320-525 MB +o TZK11, QIC tape, 2.0 GB +o TZ86, 5-1/4-inch cartridge 4-26 Base System Software Notes _4._5._2._1 _D_i_s_k _S_p_a_c_e _I_s_s_u_e_s You should be aware of the following disk space issues before you use the _b_t_c_r_e_a_t_e command: +o If you have installed all the subsets and selected all kernel options, you need 120,000 (512 blocks) in /_u_s_r before you start _b_t_c_r_e_a_t_e. +o If your system has all the subsets with all the kernel options installed then the _b_t_c_r_e_a_t_e utility cannot be run on an RZ26 or lower type of disk with the default partitions. This results in the /_u_s_r file system being full. In that case, you can remove some of the subsets or rebuild the kernel with only the necessary options. In other words, make sure that you have the additional 120,000 (512 blocks) needed in the /_u_s_r file system before you run the _b_t_c_r_e_a_t_e utility. If you want to keep all the subsets along with all the kernel options, do the following to make extra space. Note, the examples in the following procedure are for UFS. For AdvFS, use the _m_k_f_d_m_n and _m_k_f_s_e_t commands to create new partitions and mount them. 1. Run the _n_e_w_f_s command to recreate a new partition; for example: # _n_e_w_f_s /_d_e_v/_r_z_1_d 2. Change the current working directory to the /_u_s_r/_s_y_s directory: # _c_d /_u_s_r/_s_y_s 3. Make a SYSTEM._B_O_O_T_A_B_L_Edirectory under the /_u_s_r/_s_y_s directory, where SYSTEM is the system name; for example: # _m_k_d_i_r _F_L_A_W_L_E_S_S._B_O_O_T_A_B_L_E 4. Mount the new partition on the SYSTEM._B_O_O_T_A_B_L_Edirectory; for example # _m_o_u_n_t /_d_e_v/_r_z_1_d /_u_s_r/_s_y_s/_F_L_A_W_L_E_S_S._B_O_O_T_A_B_L_E Base System Software Notes 4-27 5. Create another new partition; for example: # _n_e_w_f_s /_d_e_v/_r_z_1_b 6. Mount the partition; for example: # _m_o_u_n_t /_d_e_v/_r_z_1_b /_m_n_t 7. Change the current working directory to the /_u_s_r/_s_y_s/_b_i_n directory. 8. Copy the contents of the /_u_s_r/_s_y_s/_b_i_n directory to the /_m_n_t directory: # _c_p * /_m_n_t 9. Unmount the /_m_n_t directory: # _u_m_o_u_n_t /_m_n_t 10.Mount the new partition on the /_u_s_r/_s_y_s/_b_i_n directory; for example: # _m_o_u_n_t /_d_e_v/_r_z_1_b /_u_s_r/_s_y_s/_b_i_n After completing the these steps, start _b_t_c_r_e_a_t_e. If you are using AdvFS, the /_u_s_r/_s_y_s/_b_i_n file system must be dumped during _b_t_c_r_e_a_t_e in order to copy the entire contents of the /_u_s_r file system. _4._5._2._2 _S_e_t_t_i_n_g _S_w_a_p _S_p_a_c_e _o_n _a _R_e_s_t_o_r_e_d _D_i_s_k After restoring your system from bootable tape, you must set the swap space at the bootable tape single- user mode as follows: 1. Mount the root file system: # _m_o_u_n_t -_u / 2. Change the current working directory to the /_e_t_c 4-28 Base System Software Notes directory: # _c_d /_e_t_c 3. Add the swap space to the _f_s_t_a_b file: # _e_c_h_o "/_d_e_v/_r_z_3_b _s_w_a_p_1 _u_f_s _s_w _0 _2" >> _f_s_t_a_b 4. Change the disk label: # _d_i_s_k_l_a_b_e_l -_s _r_z_3_b _s_w_a_p After you complete these steps, shut down and reboot the system from the restored disk. _4._5._2._3 _S_e_t_t_i_n_g _a_n _E_x_i_s_t_i_n_g _F_i_l_e _S_y_s_t_e_m _o_n _a _R_e_s_t_o_r_e_d _D_i_s_k If the restored disk already contains a file system that has not been touched during the _b_t_e_x_t_r_a_c_t process, do the following to see and use that partition: 1. Set the file system type (fstype) on the partition. In the following example, _r_z_1_d is the partition and _4._2_B_S_D is the file system type: # _d_i_s_k_l_a_b_e_l -_s _r_z_1_d _4._2_B_S_D 2. Mount the partition on the file system you want to restore; for example: # _m_o_u_n_t /_d_e_v/_r_z_1_d /_y_o_u_r_f_s _4._5._2._4 _T_a_p_e _D_r_i_v_e _R_e_s_t_r_i_c_t_i_o_n To use a tape drive with any system, make sure that the kernel has been built with the tape drive attached to the system. Otherwise, you get dump errors and the system cannot boot from the tape. _4._5._3 _M_u_l_t_i_m_e_d_i_a _S_e_r_v_i_c_e_s _f_o_r _D_i_g_i_t_a_l _U_N_I_X _V_2._0 _a_n_d _V_2._0_A The initial release of Multimedia Services for Digital UNIX Version 2.0 required several Base System Software Notes 4-29 modifications to fully support Version 4.0 and Version 4.0 components. As a result, Multimedia Services for Digital UNIX Version 2.0A is shipped on the _D_i_g_i_t_a_l _U_N_I_X _A_s_s_o_c_i_a_t_e_d _P_r_o_d_u_c_t_s _V_o_l_u_m_e _1 CD -ROM. The Multimedia Services Version 2.0A runtime should be installed instead of the Version 2.0 runtime. The Multimedia Services Version 2.0 development kit, not distributed with the Digital UNIX Version 4.0 distribution, can be used with the Multimedia Services Version 2.0A runtime kit. See the release notes for Multimedia Services for Digital UNIX Version 2.0A for more details. The release notes can be found on the CD -ROM as DOCUMENTATION/HTML/MME201_RELNOTES* _4._5._4 _s_e_t_t_i_m_e _A_f_t_e_r _a_n _U_p_d_a_t_e _I_n_s_t_a_l_l_a_t_i_o_n. The _s_e_t_t_i_m_e utility is called twice at boot time if an update installation was performed. To prevent this happening on subsequent reboots, remove the link: # _r_m /_s_b_i_n/_r_c_3._d/_S_0_5_s_e_t_t_i_m_e _4._5._5 _S_y_s_t_e_m _C_l_o_c_k _L_o_s_e_s _T_i_m_e When switching between two different boot disks that are running different versions of Digital UNIX, the system clock may lose time. See Section 2.4.5 for a full description of the problem. _4._5._6 _S_y_m_b_o_l_i_c_a_l_l_y _L_i_n_k_e_d _K_e_r_n_e_l_s In this release, _o_s_f__b_o_o_t supports the booting of symbolically linked kernels. For example, assume you have /_t_m_p/_v_m_u_n_i_x symbolically linked to ../_m_d_e_c/_v_m_u_n_i_x as follows: lrwxrwxrwx 1 anyuser system 14 Dec 6 22:41 /tmp/vmunix -> ../mdec/vmunix In this case, _o_s_f__b_o_o_t will detect the link and boot 4-30 Base System Software Notes /_m_d_e_c/_v_m_u_n_i_x as follows: Digital UNIX boot - Wed Dec 6 17:02:04 EST 1995 symbolically linked kernel detected: Loading /mdec/vmunix ... Loading at fffffc0000230000 Current PAL Revision <0x4000000010530> Switching to OSF PALcode Succeeded New PAL Revision <0x4000000020123> _4._5._7 _U_s_a_g_e _N_o_t_e _f_o_r _A_d_d_i_n_g _S_w_a_p _D_e_v_i_c_e_s Do not add swap devices to a heavily loaded symmetric multiprocessing (SMP) machine by using the _s_w_a_p_o_n /_d_e_v/_r_zxx command. Instead, add the device information to the /_e_t_c/_f_s_t_a_b file and reboot the system. _4._5._8 _A_d_d_i_t_i_o_n_a_l _S_C_S_I _D_i_s_k _I_n_f_o_r_m_a_t_i_o_n_a_l _E_n_t_r_i_e_s _i_n _E_r_r_o_r _L_o_g To enhance the ability to detect certain SCSI disk device errors, additional event logging now occurs. However, these events can also occur during normal operation of the system. The events are known as SCSI unit attention events. To distinguish between normal events and abnormal events, the context within the event as well as the surrounding events must be considered. These entries begin as follows: ----- CAM STRING ----- ERROR TYPE Soft Error Detected (recovered) The logging of these events will be associated with the first access after the event has occurred. First examine the ASC and ASQ values of the packet: ----- ENT_SENSE_DATA ----- ERROR CODE x0070 CODE x70 SEGMENT x00 SENSE KEY x0006 UNIT ATTN INFO BYTE 3 x00 INFO BYTE 2 x00 INFO BYTE 1 x00 INFO BYTE 0 x00 ADDITION LEN x0A CMD SPECIFIC 3 x00 CMD SPECIFIC 2 x00 CMD SPECIFIC 1 x00 Base System Software Notes 4-31 CMD SPECIFIC 0 x00 ASC x29 <<<<<<<<<<<<<<<<<< ASQ x02 <<<<<<<<<<<<<<<<<< FRU x00 SENSE SPECIFIC x000000 If the ASC is not x29, this is a device event or error (the SCSI specification contains the details of the meaning of the error). For entries with the ASC of x29, there are several possibilities for newer SCSI devices (older devices do not report these types of events): +o ASQ = x01 - device was powered on (or a firmware rebooted occurred) +o ASQ = x02 - Bus reset occurred +o ASQ = x03 - Device reset occurred Events of ASQ x02 or x03 should also contain other related events in the error log (such as, a bus reset, or a device reset) for the specified bus or device. These types of events are just informational and do not indicate any type of failure on the system. Events of ASQ x01 are normal events when they occur as part of switching on the system. The first access after the system is switched on creates one of these events. If these events occur at times other than the first access after the system is switched on, then it may indicate a problem within the device that is causing it to restart its firmware. Also note that not all SCSI disks are capable of reporting this information. _4._5._9 _M_u_l_t_i_p_l_e _Q_u_e_u_e_s If a printer is connected to multiple queues through a LAT or a local tty port and different jobs are submitted to different queues within a short period, some of the jobs may be lost. If this happens, resubmit the print request. _4._6 _N_e_t_w_o_r_k _a_n_d _C_o_m_m_u_n_i_c_a_t_i_o_n_s The following notes apply to network and communications software. 4-32 Base System Software Notes _4._6._1 _U_s_i_n_g _b_i_n_d _o_n _a_n _U_N_I_X _D_o_m_a_i_n (_A_F__U_N_I_X) _S_o_c_k_e_t When using _b_i_n_d() on a UNIX domain (AF_UNIX) socket, the default modes of the socket have changed in Digital UNIX version 4.0. Previously, the mode of a newly created socket was always 0777, regardless of the value of the creating process's _u_m_a_s_k. In this release, this behavior has changed so the the mode of a newly created socket is as follows: (0777 &~ umask) The previous behavior (0777, regardless of umask) may be restored by setting the kernel configuration flag _i_n_s_e_c_u_r_e__b_i_n_d to a value of 1. This can be done by either or both of the following two methods: 1. inserting the following lines into the /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b file: generic: insecure_bind = 1 Then you must reboot the kernel. 2. using the following command on the running system: # _s_y_s_c_o_n_f_i_g -_r _g_e_n_e_r_i_c _i_n_s_e_c_u_r_e__b_i_n_d=_1 _4._6._2 _C_h_a_n_g_e_s _t_o _A_T_M (_A_s_y_n_c_h_r_o_n_o_u_s _T_r_a_n_s_f_e_r _M_o_d_e) The following changes and restrictions apply to ATM _4._6._2._1 _C_h_a_n_g_e_s _t_o _A_T_M _S_t_a_r_t_u_p _S_c_r_i_p_t_s The command syntax for the _a_t_m_a_r_p command has changed due to Multiple LIS support. The _a_t_m_c_o_n_f_i_g command has added many new options mainly due to CBR (Constant Bit Rate) support. Lastly a new command, _a_t_m_s_i_g, is now required in all ATM startup scripts. Therefore all ATM startup scripts including /_e_t_c/_a_t_m._c_o_n_f will need to be modified. See the reference pages associated with _a_t_m_c_o_n_f_i_g, _a_t_m_a_r_p, and _a_t_m_s_i_g for further details. _4._6._2._2 _D_i_g_i_t_a_l _G_i_g_a_s_w_i_t_c_h _I_n_t_e_r_o_p_e_r_a_b_i_l_i_t_y When the ATM end system is connected to a Digital Gigaswitch, that is running Version 1.3 (or less) of Base System Software Notes 4-33 the Gigaswitch software, the following line specifying the _u_s_e_e_s_i keyword is required: atmconfig up driver=lta0 useesi=1-4 wait _4._6._2._3 _S_u_p_p_o_r_t _o_f _N_F_S _L_o_c_k_i_n_g _o_v_e_r _A_T_M The _l_o_c_k_d daemon will need to be restarted after ATM is brought up. This is because the _l_o_c_k_d daemon takes a one time look at the IP interface list. ATM interfaces such as _L_I_S_0 are dynamically added. _4._6._2._4 _R_e_s_t_r_i_c_t_i_o_n _o_f _U_s_i_n_g _a_t_m_s_i_g _d_o_w_n If UNI signalling is disabled with the _a_t_m_s_i_g _d_o_w_n command, it will not be correctly restarted by an _a_t_m_s_i_g _u_p command. Following a command such as: atmsig down driver=ltaX You must do the following to successfully restart signalling: atmconfig down driver=ltaX atmconfig up driver=ltaX atmsig up driver=ltaX _4._6._3 _L_a_r_g_e _U_s_e_r _S_t_a_c_k _L_i_m_i_t_s _M_a_y _C_a_u_s_e _a _S_y_s_t_e_m _P_a_n_i_c Your system may crash when the user stack limits are increased beyond 2 gigabytes in the /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b file and more than 2 gigabytes are accessed by an application. The crash happens at some time after the location beyond 2G is accessed, typically when the system is paging. The default stack limits are below 2G and therefore this is a problem only if the stack limits have been increased. The solution is to reduce the stack limits in the /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b and reboot. The application will then receive a fatal error when accessing stack above the specified limit. _4._6._4 _S_V_R_4 _S_t_r_e_a_m_s _I_F_N_E_T _p_a_r_a_d_i_g_m. The IFNET paradigm allows the bridging of streams device drivers to sockets. This release supports SVR4 streams, but the IFNET paradigm is not fully 4-34 Base System Software Notes supported. IFNET is only supported over the _l_n ethernet interface and the number of _l_n devices supported is limited to two devices. _4._6._5 _O_r_d_e_r_l_y _R_e_l_e_a_s_e _i_n _X_T_I This release does not support Orderly Release in XPG4 XTI (default XTI interface). It is still available for users of XPG3 XTI. See the _N_e_t_w_o_r_k_i_n_g _P_r_o_g_r_a_m_m_e_r'_s _G_u_i_d_e for information on using XPG3 XTI. _4._6._6 _R_e_s_t_a_r_t_i_n_g _t_h_e _N_e_t_w_o_r_k _W_h_e_n _U_s_i_n_g _I_n_t_e_r_f_a_c_e _A_l_i_a_s_e_s When you restart the network using the following command: # /_u_s_r/_s_b_i_n/_r_c_i_n_e_t _r_e_s_t_a_r_t The _i_f_c_o_n_f_i_g command is run by the /_u_s_r/_s_b_i_n/_r_c_i_n_e_t script. This will clear and reset the primary network interface address. Network interfaces with configured interface aliases use the alias address as a source address for outgoing packets. Resetting the primary network interface address can cause a problem for systems with a firewall or proxy-access configuration based on the primary address. Generally, alias addresses are not in the access control lists in such systems. To avoid this problem, you can use one of the following solutions: +o Add alias addresses in the firewall or proxy- access list in addition to the primary address +o Delete interfaces that are configured with interface aliases before restarting the network. Use the following command so that the restart script will correctly use the primary address in the outgoing packets: # _i_f_c_o_n_f_i_g <_i_f__w__a_l_i_a_s_e_s> _d_o_w_n _d_e_l_e_t_e _4._6._7 _I_n_c_o_r_r_e_c_t _E_r_r_o_r _M_e_s_s_a_g_e _U_s_i_n_g _n_e_t_s_e_t_u_p _a_n_d _r_c_i_n_e_t When restarting the network using _n_e_t_s_e_t_u_p, an error Base System Software Notes 4-35 message similar to the following will be displayed: kill: 204: no such process This problem also exists when running the following commands: # _r_c_i_n_e_t _s_t_o_p # _r_c_i_n_e_t _r_e_s_t_a_r_t The message is incorrect and has no effect on your system. _4._6._8 _C_D_E'_s _S_t_a_t_i_c _D_e_p_e_n_d_e_n_c_y _o_n _t_h_e _N_e_t_w_o_r_k The Common Desktop Environment (CDE) provides facilities and features for applications to communicate in a networked environment. After the network is configured and enabled, these features become available each time a new desktop session is started. After a desktop session has started, the current session has a static dependency on the state of the network configuration. Network and system administrators should be very cautious about dynamic changes to the network configuration while in a network aware desktop session. Prior to making any dynamic network changes, such as changing the state of your network adapter to off or changing your primary network address, add the following entry to the /._d_t_p_r_o_f_i_l_e file: export DTNONETWORK=true The system administrator must then log out and back in as root for the change to take effect. This change removes the dependency on the state of the network. Failure to do this may result in a session hanging after clicking on a CDE icon, such as the screen lock or Exit icons. After all network changes are completed, remove the _e_x_p_o_r_t _D_T_N_O_N_E_T_W_O_R_K=_t_r_u_e entry from the /._d_t_p_r_o_f_i_l_e file. _4._7 _L_o_c_a_l _A_r_e_a _T_r_a_n_s_p_o_r_t The following notes apply to Local Area Transport (LAT). 4-36 Base System Software Notes _4._7._1 _D_u_p_l_i_c_a_t_e _M_i_n_o_r _N_u_m_b_e_r_s _a_n_d _l_a_t_s_e_t_u_p The _l_a_t_s_e_t_u_p utility sometimes creates devices with duplicate minor numbers. If you manually create LAT BSD devices that do not match the valid BSD tty name space convention, _l_a_t_s_e_t_u_p can create devices with duplicate minor numbers. For example, creating device _t_t_y_0 with a minor number 2 instead of 1 can cause this problem. _4._7._2 _C_T_R_L/_A _C_a_u_s_e_s _L_A_T _t_t_y _t_o _C_h_a_n_g_e _t_h_e _C_a_s_e _o_f _C_h_a_r_a_c_t_e_r_s When a CTRL/A character is typed during a LAT tty session, all lowercase characters are converted to uppercase. Another CTRL/A will change the mode back to normal. _4._7._3 _S_i_m_u_l_t_a_n_e_o_u_s _l_l_o_g_i_n _C_o_n_n_e_c_t_i_o_n_s When doing a number of simultaneous _l_l_o_g_i_n connections it is recommended to use _l_l_o_g_i_n with the -_p option. To speed up an _l_l_o_g_i_n connection, it is also recommended to add the target host name as a reserved service. _4._7._4 _L_A_T _K_e_r_n_e_l _M_o_d_u_l_e _I_s _D_y_n_a_m_i_c_a_l_l_y _L_o_a_d_a_b_l_e It is no longer necessary to build LAT into the kernel. LAT is not made a mandatory kernel option upon selecting the LAT subset and will not appear in the kernel configuration file. As LAT requires the Data Link Bridge (DLB), it is still necessary to build DLB into the kernel when using LAT. The default behavior upon booting to multi-user mode is for LAT to be dynamically loaded into the running kernel. If LAT is not started at boot-time via the /_s_b_i_n/_r_c_3._d/_S_5_8_l_a_t script, the recommended method for starting and stopping LAT is to verify that _L_A_T_S_E_T_U_P is enabled in /_e_t_c/_r_c._c_o_n_f_i_g and execute the /_u_s_r/_s_b_i_n/_i_n_i_t._d/_l_a_t program, using the _s_t_a_r_t or _s_t_o_p options. _4._7._5 _G_r_o_u_p _C_o_d_e_s _A_r_e _C_o_m_p_a_t_i_b_l_e _w_i_t_h _V_e_r_s_i_o_n _2._0 _L_A_T _D_r_i_v_e_r. In the slave-only Version 2.0 LAT implementation, service group codes are used in solicitation messages for host-initiated connections, Base System Software Notes 4-37 Many users rely on the ability to control access to server ports by changing the group codes of the locally offered services. Although it is contrary to the recommendations of the LAT protocol, this behavior is once again supported. Outgoing port group codes, normally used for this purpose, continue to be used in all other cases where they are required by the protocol. _4._7._6 _s_h_u_t_d_o_w_n _C_o_m_m_a_n_d _M_a_y _S_t_a_l_l If the _s_h_u_t_d_o_w_n -_r command is executed when there are LAT login sessions with active background processes, the _s_h_u_t_d_o_w_n program appears to stall. The workaround for this problem is to halt LAT (using the _l_a_t_c_p -_h command) either before executing the _s_h_u_t_d_o_w_n command or after it has stalled. _4._8 _F_i_l_e _S_y_s_t_e_m_s The notes in this section apply to file systems. _4._8._1 _U_s_i_n_g _A_C_L_s _o_v_e_r _N_F_S For an NFS client to make direct use of ACLs or extended attributes (property lists) over NFS the _p_r_o_p_l_i_s_t_d daemon must be enabled on an NFS server. The _p_r_o_p_l_i_s_t mount option must be used when mounting on the client. Access checks will be enforced by the server in any case, although NFSv2 client caching could sometimes cause inappropriate read access to be granted. Correctly implemented NFSv3 clients will make the necessary access checks. Start the _p_r_o_p_l_i_s_t_d daemon by selecting the number of _p_r_o_p_l_i_s_t daemons to run when you use the _n_f_s_s_e_t_u_p utility. You can also start the daemon manually with the _p_r_o_p_l_i_s_t_d command. For example: # /_u_s_r/_s_b_i_n/_p_r_o_p_l_i_s_t_d _4 On the client, the filesystem must be mounted with the _p_r_o_p_l_i_s_t option by either of the following methods: +o add _p_r_o_p_l_i_s_t to the options field in the 4-38 Base System Software Notes /_e_t_c/_f_s_t_a_b file: _s_w_a_r_e_1:/_a_d_v_f_s /_n_f_s__a_d_v_f_s _n_f_s _r_w,_p_r_o_p_l_i_s_t _0 _0 +o Alternatively, add the option to the mount command as follows: # _m_o_u_n_t -_o _p_r_o_p_l_i_s_t _s_w_a_r_e_1:/_a_d_v_f_s /_n_f_s__a_d_v_f_s See the _a_c_l(4), _f_s_t_a_b(4), _p_r_o_p_l_i_s_t(4), _m_o_u_n_t(8), _n_f_s_s_e_t_u_p(8), and _p_r_o_p_l_i_s_t_d(8) reference pages for more information. Note that the _p_r_o_p_l_i_s_t option is not documented in _m_o_u_n_t(8). _4._8._2 _A_C_L _S_i_z_e _L_i_m_i_t_a_t_i_o_n_s On AdvFS filesystems there is a hard limit of 1560 bytes for a property list entry. Since Access Control Lists (ACLs) are stored in property list entries, this equates to 62 ACL entries in addition to the 3 required ACL entries. The error _E_I_N_V_A_L will be returned if you attempt to exceed this limit. To facilitate interoperation of the UFS and AdvFS ACLs, a configurable limit has been imposed on UFS ACLs. The default value of the UFS limit is 1548 bytes, equivalent to the 65 entry limit on AdvFS. The UFS configurable limit on ACLs has been added to the _s_e_c subsystem and has been given the attribute name _u_f_s-_s_e_c-_p_r_o_p_l_i_s_t-_m_a_x-_e_n_t_r_y. The attribute can be dynamically configured using the _s_y_s_c_o_n_f_i_g utility or by setting the attribute in the file _s_y_s_c_o_n_f_i_g_t_a_b. A configurable property list element size for UFS has also been added to the _s_e_c subsystem and has been given the attribute name _u_f_s-_p_r_o_p_l_i_s_t-_m_a_x-_e_n_t_r_y. The value of _u_f_s-_p_r_o_p_l_i_s_t-_m_a_x-_e_n_t_r_y must be larger than _u_f_s-_s_e_c-_p_r_o_p_l_i_s_t-_m_a_x-_e_n_t_r_y by enough space to hold a property list element header. Adjustment of _u_f_s- _p_r_o_p_l_i_s_t-_m_a_x-_e_n_t_r_y to achieve this is done automatically by the _s_y_s_c_o_n_f_i_g utility. The default value of _u_f_s-_p_r_o_p_l_i_s_t-_m_a_x-_e_n_t_r_y is 8192 bytes. See the _c_f_g_m_g_r(8), _s_e_c_o_n_f_i_g(8), _s_e_c_o_n_f_i_g_d_b(8), and _s_y_s_c_o_n_f_i_g_t_a_b(4) reference pages for more information. _4._8._3 _P_O_L_Y_C_E_N_T_E_R _A_d_v_a_n_c_e_d _F_i_l_e _S_y_s_t_e_m The following notes discuss features, problems, and restrictions of the POLYCENTER Advanced File System Base System Software Notes 4-39 (AdvFS). _4._8._3._1 _B_a_c_k_w_a_r_d _C_o_m_p_a_t_a_b_i_l_i_t_y _P_r_o_b_l_e_m _w_i_t_h _v_d_u_m_p _a_n_d _v_r_e_s_t_o_r_e _N_o_t_e This is an important note for users of _v_d_u_m_p and _v_r_e_s_t_o_r_e Backups made using _v_d_u_m_p on Digital UNIX Version 4.0 cannot be restored using _v_r_e_s_t_o_r_e on earlier versions of Digital UNIX. Patches will be made available for earlier versions of _v_r_e_s_t_o_r_e to correct this problem. Backups made using _v_d_u_m_p on earlier versions of Digital UNIX can be restored using _v_r_e_s_t_o_r_e under Digital UNIX Version 4.0 without problems. _4._8._3._2 _L_o_g _H_a_l_f _F_u_l_l _E_r_r_o_r Under some circumstances, AdvFS can panic with the following message: log half full This can occur when a big percentage of a very large file is truncated and the fileset containing the file has a clone fileset. Truncation occurs when an existing file is overlaid by another file, and explicitly by the _t_r_u_n_c_a_t_e system call. The same will happen if very large, very fragmented files are migrated. Migration occurs when the _b_a_l_a_n_c_e, _r_m_v_o_l, and _m_i_g_r_a_t_e AdvFS utilities are run. Files with greater than 40000 extents are at risk, unless the transaction logsize is increased as follows: +o 40000 extents use a logsize of 768 +o 60000 extents use a logsize of 1024 +o 80000 extents use a logsize of 1280 The command # _s_h_o_w_f_i_l_e -_x <_f_i_l_e_n_a_m_e> | _g_r_e_p _e_x_t_e_n_t_C_n_t will indicate how many extents a file is using. Backup and restore will help to defragment files as 4-40 Base System Software Notes will copying (not moving with _m_v) a file to another name. However, if the fileset has a clone and if a large file is truncated as a result of the copy, the truncation panic could occur. _4._8._3._3 _A_C_L _S_i_z_e _L_i_m_i_t_a_t_i_o_n_s On AdvFS filesystems there is a hard limit of 1560 bytes for a property list entry. Since Access Control Lists (ACLs) are stored in property list entries, this equates to 62 ACL entries in addition to the 3 required ACL entries. The error _E_I_N_V_A_L will be returned if you attempt to exceed this limit. To facilitate interoperation of the UFS and AdvFS ACLs, a configurable limit has been imposed on UFS ACLs. The default value of the UFS limit is 1548 bytes, equivalent to the 65 entry limit on AdvFS. The UFS configurable limit on ACLs has been added to the _s_e_c subsystem and has been given the attribute name _u_f_s-_s_e_c-_p_r_o_p_l_i_s_t-_m_a_x-_e_n_t_r_y. The attribute can be dynamically configured using the _s_y_s_c_o_n_f_i_g utility or by setting the attribute in the file _s_y_s_c_o_n_f_i_g_t_a_b. A configurable property list element size for UFS has also been added to the _s_e_c subsystem and has been given the attribute name _u_f_s-_p_r_o_p_l_i_s_t-_m_a_x-_e_n_t_r_y. The value of _u_f_s-_p_r_o_p_l_i_s_t-_m_a_x-_e_n_t_r_y must be larger than _u_f_s-_s_e_c-_p_r_o_p_l_i_s_t-_m_a_x-_e_n_t_r_y by enough space to hold a property list element header. Adjustment of _u_f_s- _p_r_o_p_l_i_s_t-_m_a_x-_e_n_t_r_y to achieve this is done automatically by the _s_y_s_c_o_n_f_i_g utility. The default value of _u_f_s-_p_r_o_p_l_i_s_t-_m_a_x-_e_n_t_r_y is 8192 bytes. See the _c_f_g_m_g_r(8), _s_e_c_o_n_f_i_g(8), _s_e_c_o_n_f_i_g_d_b(8), and _s_y_s_c_o_n_f_i_g_t_a_b(4) reference pages for more information. _4._8._3._4 _T_h_e _v_d_u_m_p _a_n_d _v_r_e_s_t_o_r_e _C_o_m_m_a_n_d_s The _v_d_u_m_p and _v_r_e_s_t_o_r_e commands do not have the same functionality as _d_u_m_p and _r_e_s_t_o_r_e commands. When a file is renamed between different level dumps, the file is not backed up on the later dump; the _v_d_u_m_p command assumes it was backed up on the earlier dump. When a file is deleted between different level dumps, the file is restored during the restore process. When a directory entry changes type (for example, a file becomes a directory) between different level Base System Software Notes 4-41 dumps, during the restore of the higher level dump, you get an error message saying it cannot restore the file. The work around on is to remove the file that changed types between the different levels of restore. _4._8._3._5 _T_h_e _v_e_r_i_f_y -_F _C_o_m_m_a_n_d _D_o_e_s _N_o_t _B_y_p_a_s_s _R_e_c_o_v_e_r_y Running the _v_e_r_i_f_y commmand with the -_F flag causes some recovery to be done on the domain before the attempt to mount it. _4._8._3._6 _r_m_f_s_e_t _C_o_m_m_a_n_d _M_a_y _H_a_n_g Avoid using the _r_m_f_s_e_t utility on busy domains. If you attempt to remove a fileset using the _r_m_f_s_e_t command and the target domain is experiencing a lot of I/O, the _r_m_f_s_e_t operation may hang. _4._8._3._7 _A_d_v_F_S _S_p_a_r_s_e _F_i_l_e _S_a_v_e _a_n_d _R_e_s_t_o_r_e The _v_d_u_m_p and _v_r_e_s_t_o_r_e utilities correctly save and restore AdvFS sparse files. In previous versions, the holes in the sparse files were allocated disk space and filled with zeros. Note that sparse files that are striped are still handled as in previous versions. _4._8._3._8 _A_d_v_F_S _V_e_r_i_f_i_e_s _D_o_m_a_i_n _V_o_l_u_m_e _S_i_z_e_s AdvFS will now verify at mount time that all of the data in all of the volumes in a domain can be accessed. It does this by attempting to read the last block in each volume as specified by the disk label that was in use at the time that the volume was added to the domain. If it cannot read that block, it attempts to read the last block that AdvFS has marked as being currently used to hold data. If AdvFS cannot read the last in-use block for any volume in the domain, the mount will fail. If it can read the last in-use block but cannot read the last block as specified by the disk label, the mount will succeed but in read-only mode. One reason that the last block may not be able to be read is that a disk may be mislabeled on a RAID array. The user should check the labels of the flagged volumes in the error message. If the disk label is incorrect, the user can repair the domain in one of the following ways. 4-42 Base System Software Notes Before attempting corrective action, you should back up all filesets in the domain. The corrective action depends on the state of the domain. If the domain consist of multiple volumes and has enough free space to hold two entire volumes, it is possible to remove the offending volumes one at a time, fix the disk label and add them back to the domain. Perform the following operation on each of the failed volumes: 1. Remove volume from domain. 2. Correct the disklabel of the volume. 3. Add the corrected volume back to the domain. 4. Balance the domain. Step 4 is important. If the domain is not balanced after adding the corrected volume, the user runs the risk of filling up one of the incorrectly labeled volumes and inducing an I/O error. If the domain's free space is less than two volumes, you should back up all the filesets in that domain, remove the domain, fix the disk labels of the volumes, and rebuild the domain. Then restore the filesets from the backups. Another example of why a mount might fail in this way would be that an LSM volume upon which an AdvFS domain resides has been shrunk from its original size. _4._8._3._9 _A_d_v_F_S _D_o_m_a_i_n _P_a_n_i_c When log or metadata write errors occur (for example, due to a disk failure or media error) AdvFS initiates a domain panic rather than a system panic on any non root file domains. A domain panic prevents further access to the domain, but allows the filesets in the domain to be unmounted. When a domain panic occurs, a message is displayed in the following format: AdvFS Domain Panic; Domain Id For example: AdvFS Domain Panic; Domain cybase_domain Id 2dad7c28.0000dfbb After a domain panic, use the _m_o_u_n_t command to list Base System Software Notes 4-43 all mounted filesets then use _u_m_o_u_n_t to dismount all filesets in the domain specified in the error message. You can then take the necessary steps to correct the hardware problem. After you have corrected the hardware problem, it is recommended that you run the _v_e_r_i_f_y command (the domain structure checker) on the domain before remounting it. This will determine if the write error compromised the domain. _4._8._3._1_0 _A_d_v_F_S _S_u_p_p_o_r_t_s _U_F_S _Q_u_o_t_a _C_o_m_m_a_n_d_s The UFS and AdvFS user and group quota commands have been consolidated. The standard UFS quota commands can now be used to manage user and group quotas on AdvFS. The following list identifies the old and new AdvFS quota commands: ____________________________________________ Old AdvFS Command New Consolidated Command ____________________________________________ vquotaon quotaon vquotaoff quotaoff vquotacheck quotacheck vquota quota vquot quot vrepquota repquota vedquota edquota vncheck ncheck ____________________________________________ AdvFS quota functions have not changed. Functional differences between UFS and AdvFS quotas exist and are described in the reference pages for the consolidated commands. The /_s_b_i_n/_i_n_i_t._d/_q_u_o_t_a script now checks and enables quotas for both AdvFS and UFS. This script runs during system initialization to stop or start user and group quota enforcement. Support for the existing AdvFS versions of the quota commands will continue for some time. Future versions of AdvFS will drop the unique quota commands. Until then, both versions of the quota commands will work. 4-44 Base System Software Notes _4._8._3._1_1 _A_d_v_F_S _S_u_p_p_o_r_t_s _M_o_r_e _M_o_u_n_t_e_d _F_i_l_e_s_e_t_s While AdvFS supports an unlimited number of filesets per system, the number of filesets that can be mounted at one time is limited to 512 minus the number of active file domains. For example, if a system has three active domains, up to 509 filesets can be mounted at the same time. _4._8._3._1_2 _P_o_s_s_i_b_l_e _C_h_e_c_k _a_n_d _R_e_p_a_i_r _F_a_i_l_u_r_e If a disk has a partition erroneously labeled AdvFS that overlaps a UFS partition, a file system check and repair operation (_f_s_c_k and _u_f_s__f_s_c_k) will fail on a partition that overlaps the AdvFS partition. The solution is to relabel the AdvFS partition on the disk. Conversely, if a disk partition that overlaps AdvFS is erroneously labeled UFS, an AdvFS file system check and repair operation, _v_e_r_i_f_y, will fail on a partition that overlaps the UFS partition. To correct the problem, relabel the UFS partition. _4._8._3._1_3 _A_d_v_F_S _C_o_m_m_a_n_d _a_n_d _Q_u_o_t_a _P_r_o_b_l_e_m_s AdvFS has the following known problems and restrictions: +o The _d_f command does not display accurate information for clone filesets; other fileset information is correct. Use the _d_u command instead of the _d_f command. +o The quota files can become inconsistent if the system fails between the time an application unlinks a file and the time it closes the file. For example, consider a program that creates a file, unlinks the file, and then closes the file. If the system fails between the unlink and close, the quotas for this file will not be updated correctly. The quota files will continue to charge the user or group for this file and its blocks. _4._8._3._1_4 _R_e_u_s_i_n_g _A_d_v_F_S _P_a_r_t_i_t_i_o_n_s You can reuse a partition that was previously part of an AdvFS domain. However, before you reuse the partition, you must remove the domain on the Base System Software Notes 4-45 partition you want to reuse. Remove the entire domain by using the _r_m_f_d_m_n command. After the unused domain is removed, you can create a new domain on the partition. _4._8._3._1_5 _D_a_t_a _E_l_e_m_e_n_t _S_i_z_e _L_i_m_i_t_s _f_o_r _E_x_t_e_n_d_e_d _A_t_t_r_i_b_u_t_e_s Support for extended attributes (vfs+) in AdvFS is limited to data elements of 2KB or less. Application programs attempting to set larger attributes will receive an error return value. _4._8._3._1_6 _I_n_c_r_e_a_s_e _M_e_t_a_d_a_t_a _E_x_t_e_n_t _S_i_z_e _f_o_r _L_a_r_g_e _N_u_m_b_e_r _o_f _F_i_l_e_s On systems with domains that contain very large numbers of files (over 5000), the standard AdvFS metadata extent page allocation may be inadequate. As a result, an incorrect error message is displayed as follows: out of disk space To avoid this problem, AdvFS provides two ways to configure your file domain to handle large numbers of files. You can use the _m_k_f_d_m_n command with the -_x or -_p flags to create a file domain. Then, if the file domain is extended beyond one volume, use the _a_d_d_v_o_l command with the same flags. See the _m_k_f_d_m_n reference page for complete details on using these flags. A table is included in the reference page to indicate the number of extents required for the number of files in the file domain. _4._8._3._1_7 _M_o_u_n_t_i_n_g _U_F_S _F_i_l_e _S_y_s_t_e_m _w_i_t_h _A_d_v_F_S _r_o_o_t If you attempt to mount a UFS file system while in single-user mode on a system that is configured with AdvFS as root, the following error will occur: Error checking for overlapping partitions: Invalid MSFS fileset name (root_device) in mounttab. To manually mount a UFS file system while in single- user mode on a system with an AdvFS root, you must perform a _m_o_u_n_t update on the root file system. Use 4-46 Base System Software Notes the following command: # _m_o_u_n_t -_u / You can then mount any UNIX file systems. _4._8._3._1_8 _D_i_s_k _U_s_a_g_e _I_n_f_o_r_m_a_t_i_o_n Under certain conditions, the disk usage information on an AdvFS file system may become corrupted. To correct this, turn on quotas in the /_e_t_c/_f_s_t_a_b file for the affected file system, and then run the _v_q_u_o_t_a_c_h_e_c_k command on the file system. This should correct the disk usage information. _4._8._3._1_9 _A_d_v_F_S _D_o_e_s _N_o_t _S_u_p_p_o_r_t _t_h_e _H_i_e_r_a_r_c_h_i_c_a_l _S_t_o_r_a_g_e _M_a_n_a_g_e_r Any attempt to enable shelving for an AdvFS fileset using the hierarchical storage manager (HSM) _m_k_e_f_s command results in the following error message: Can't get current fileset shelving info - ENOT_SUPPORTED (-1041) Also, any attempt to mount an existing AdvFS fileset that already has shelving enabled results in the following error message: AdvFS mount - shelving not supported To access an existing AdvFS fileset that already has shelving enabled, restore the data into another fileset that does not have shelving enabled. _4._8._3._2_0 _U_n_i_q_u_e _F_i_l_e _I_d_e_n_t_i_f_i_e_r_s Both the _f_s_t_a_t(2) reference page and the /_u_s_r/_i_n_c_l_u_d_e/_s_y_s/_s_t_a_t._h file inaccurately state that the combination of the _s_t__d_e_v and the _s_t__i_n_o fields of the _s_t_a_t structure create a unique file identifier through time. Because the _s_t__i_n_o value can be reused, the only way to create a unique file identifier is the combination of the _s_t__i_n_o, _s_t__d_e_v, and _s_t__g_e_n fields. While this is true in UFS, it is even more important in AdvFS, which recycles the _s_t__i_n_o values rapidly. Base System Software Notes 4-47 _4._8._3._2_1 _N_F_S _S_e_r_v_e_r _M_a_y _P_r_i_n_t _E_r_r_o_r _M_e_s_s_a_g_e _o_n _N_F_S _C_l_i_e_n_t _R_e_c_o_v_e_r_y If an NFS server is exporting an AdvFS directory and the client to which it is exporting crashes, upon reboot of the client, the following error message may appear on the console of the server: lockd : can't clear lock after crash of client client_name : invalid argument. This message does not disrupt NFS operations. _4._8._3._2_2 _A_d_v_F_S _P_a_n_i_c When a large percentage of a very large file is truncated and the fileset containing the file has a clone fileset, the system will panic with a _l_o_g _h_a_l_f _f_u_l_l error message. Truncation happens when an existing file is overlaid by another file or when the truncate system call is made. The panic also occurs if very large, very fragmented files are migrated. Migration occurs when you run the AdvFS _b_a_l_a_n_c_e, _r_m_v_o_l, and _m_i_g_r_a_t_e utilities. Files with greater than 40,000 extents are at risk. To determine how many extents a file is using, enter the following command: # _s_h_o_w_f_i_l_e -_x filename | _g_r_e_p _e_x_t_e_n_t_C_n_t The _b_a_c_k_u_p, _r_e_s_t_o_r_e, and _c_o_p_y commands tend to defragment files. The _m_v command does not. However, if the fileset has a clone and a large file is truncated as a result of the copy, the _l_o_g _h_a_l_f _f_u_l_l panic again could result. _4._8._4 _L_o_g_i_c_a_l _V_o_l_u_m_e _M_a_n_a_g_e_r Logical Volume Manager (LVM) support is being retired in this release of Digital UNIX and there will be no further support of LVM. All volume management functions are provided by the Logical Storage Manager (LSM). LVM functions are disabled with the exception of the support necessary to encapsulate LVM volumes under LSM. You must encapsulate any LVM volumes under LSM to maintain access to any data in such volumes. In a future release of Digital UNIX, encapsulation support will be dropped and any data still under LVM control will be lost. 4-48 Base System Software Notes LVM volume groups can be encapsulated to the _r_o_o_t_d_g diskgroup. Attempting to encapsulate an LVM volume group to any other LSM disk group fails. You can encapsulate an LVM volume group to a non- rootdg diskgroup by performing the following procedure: 1. Use the _v_o_l_l_v_m_e_n_c_a_p command to encapsulate the LVM group to an existing LSM diskgroup. For example, to encapsulate the _v_g_1 LVM group to the existing _l_v_m_d_g_1 LSM diskgroup, enter the following command: # /_u_s_r/_s_b_i_n/_v_o_l_l_v_m_e_n_c_a_p -_g _l_v_m_d_g_1 /_d_e_v/_v_g_1 The _v_o_l_l_v_m_e_n_c_a_p command creates the LSM scripts in the /_e_t_c/_v_o_l/_r_e_c_o_n_f_i_g._d/_l_v_m._d directory. 2. Change the current working directory to /_e_t_c/_v_o_l/_r_e_c_o_n_f_i_g._d/_l_v_m._d: # _c_d /_e_t_c/_v_o_l/_r_e_c_o_n_f_i_g._d/_l_v_m._d 3. Move the _d_g file in the /_e_t_c/_v_o_l/_r_e_c_o_n_f_i_g._d/_l_v_m._d directory to a sub-directory whose name corresponds to the LVM volume group that is being encapsulated; for example: # _m_v _d_g _v_g_1 Then change the current working directory to root. 4. Execute the /_s_b_i_n/_v_o_l-_l_v_m-_r_e_c_o_n_f_i_g command to execute the LSM scripts created by the _v_o_l_l_v_m_e_n_c_a_p command. When you execute the /_s_b_i_n/_v_o_l-_l_v_m-_r_e_c_o_n_f_i_g command, an error message is displayed; ignore this message. For more information, see the _L_o_g_i_c_a_l _S_t_o_r_a_g_e _M_a_n_a_g_e_r manual. _4._8._5 _L_o_g_i_c_a_l _S_t_o_r_a_g_e _M_a_n_a_g_e_r The following notes describe problems and restrictions of the Logical Storage Manager (LSM). Base System Software Notes 4-49 _4._8._5._1 _P_o_s_s_i_b_l_e _P_r_o_b_l_e_m_s _A_c_c_e_s_s_i_n_g _P_h_y_s_i_c_a_l _B_l_o_c_k _0 _w_i_t_h _L_S_M Physical block 0 on Digital disks is typically write-protected by default. If a disk is added to LSM by using the _v_o_l_d_i_s_k_a_d_d utility, physical block 0 is skipped. However, if a partition that includes physical block 0 is encapsulated into LSM by using the _v_o_l_e_n_c_a_p, _v_o_l_l_v_m_e_n_c_a_p, or _v_o_l_a_d_v_d_o_m_e_n_c_a_p utility, physical block 0 is not skipped. This is not a problem because the file system already skips block 0 and does not write to it. A problem can occur when an LSM volume that contains a write-protected block 0 is dissolved and its disk space is reused for a new purpose. Neither the new application nor LSM know about the write-protected physical disk block 0 and a write failure can occur. To fix this problem, use the following steps to remove the write-protected physical disk block 0 from the LSM disk before it can be assigned to the new volume: 1. Use the _v_o_l_d_g command to remove the LSM disk. 2. Use the _v_o_l_d_i_s_k_a_d_d command to add either a specific partition of the disk or the entire disk to LSM. _4._8._5._2 _U_s_i_n_g _L_S_M _w_i_t_h _S_W_X_C_R-_P(_A/_B) _a_n_d _S_W_X_C_R-_E(_A/_B) _R_A_I_D _C_o_n_t_r_o_l_l_e_r_s When an LSM mirror is created using a disk that is configured as Just-a-Bunch-of-Disks (JBOD) off of either the SWXCR-P or SWXCR-E RAID controllers, a disk failure requires that you reconfigure the disk on the controller. The disk is in an unusable state once it is set to off line by the controller and cannot be used by LSM until it is reconfigured. Refer to the _S_t_o_r_a_g_e_W_o_r_k_s _R_A_I_D _A_r_r_a_y _2_0_0 _S_u_b_y_s_t_e_m _F_a_m_i_l_y _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _C_o_n_f_i_g_u_r_a_t_i_o_n _G_u_i_d_e. _4._8._5._3 _E_n_a_b_l_i_n_g _L_S_M _A_f_t_e_r _I_n_s_t_a_l_l_a_t_i_o_n _R_e_q_u_i_r_e_s _R_e_b_u_i_l_d_i_n_g _t_h_e _K_e_r_n_e_l If you install LSM by using the _s_e_t_l_d utility after you originally install Digital UNIX, you must rebuild the system kernel to enable LSM. To rebuild the kernel, run the _d_o_c_o_n_f_i_g utility with 4-50 Base System Software Notes no command flags. Note that the _d_o_c_o_n_f_i_g menu display does not include LSM. However, the _d_o_c_o_n_f_i_g utility will build a kernel that includes LSM. Refer to the LSM Installation documentation for more information. _4._8._5._4 _T_h_e _v_o_l_r_o_o_t_m_i_r _S_c_r_i_p_t _S_u_p_p_o_r_t_s _O_n_l_y _L_U_N _0 _o_n _H_S_Z Only _L_U_N _0 is supported as a boot device by the console. Hence, the LSM _r_o_o_t_v_o_l and _s_w_a_p_v_o_l volumes can be mirrored only to _L_U_N _0 in an _H_S_Z. Therefore, when you use the _v_o_l_r_o_o_t_m_i_r script to mirror _r_o_o_t_v_o_l and _s_w_a_p_v_o_l, use only an _L_U_N _0 on an _H_S_Z as an argument to the _v_o_l_r_o_o_t_m_i_r script. _4._8._5._5 _B_o_o_t _F_a_i_l_u_r_e_s _M_a_y _O_c_c_u_r _W_h_e_n _U_s_i_n_g _L_S_M _V_o_l_u_m_e _r_o_o_t_v_o_l _f_o_r _t_h_e _r_o_o_t _F_i_l_e _S_y_s_t_e_m If you use the LSM _r_o_o_t_v_o_l volume for the root file system and the _s_w_a_p_v_o_l volume is in use as a primary swap volume, LSM adds the following entries to the /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b file to enable rootability: lsm: lsm_rootvol_is_dev=1 lsm_swapvol_is_dev=1 If these entries are deleted or if the /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b file is deleted, the system will not boot. If this happens, you can boot the system interactively as follows: >>> _b_o_o_t -_f_l _i Enter kernel_name option_1 ... option_n: _v_m_u_n_i_x _l_s_m__r_o_o_t_d_e_v__i_s__v_o_l_u_m_e=_1 After the system boots, edit the /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b file and add the LSM entries as shown above. Reboot the system for the changes to take effect. _4._8._5._6 _B_l_o_c_k _C_h_a_n_g_e _L_o_g_g_i_n_g _S_u_b_d_i_s_k _S_i_z_e _R_e_c_o_m_m_e_n_d_a_t_i_o_n LSM Volumes enabled with Block Change Logging (BCL) requires two or more log subdisks that are at a minimum one sector long. If you intend to use BCL on any volumes that do not already have logging subdisks, Digital recommends that you allocate at least two sectors to each log subdisk. Any volumes that currently use single sector logging Base System Software Notes 4-51 subdisks will continue to work correctly. However, Digital recommends that you reconfigure as soon as convenient to avoid being forced to do so at a later date. Implementing these recommendations now will make the transition to new requirements in future releases easier. 4-52 Base System Software Notes Development Environment Notes 5 This chapter contains notes about issues and known problems with the development environment software and, whenever possible, provides solutions or workarounds to those problems. _5._1 _S_o_m_e _C _L_i_b_r_a_r_y _F_u_n_c_t_i_o_n_s _H_a_v_e _T_w_o _V_e_r_s_i_o_n_s In this release of Digital UNIX, the following C library functions exist in two versions due to conflicts between previous versions of Digital UNIX (to maintain binary compatibility these interfaces remain the default in this version of Digital UNIX as well) and the recent X/Open Single UNIX Specification. The Single UNIX Specification interfaces will be used when the _c_8_9 command is used or when the C preprocessor symbol __X_O_P_E_N__S_O_U_R_C_E__E_X_T_E_N_D_E_D is defined. a64l dbm_forder getsockname readv sigaction accept dbm_nextkey l64a recvfrom signal basename dbm_store nftw recvmsg sigpause dbm_delete dirname pipe sendmsg sigset dbm_fetch ftw putmsg setpgrp ttyslot dbm_firstkey getpeername putpmsg setrlimit The Single UNIX Specification interfaces are recommended for new designs and implementations. They will ensure portability of code on all UNIX platforms. In most cases the changes in the function will not require changes to the application source code using the function, just a recompilation. _5._2 _M_i_s_s_i_n_g _D_e_b_u_g_g_e_r _I_n_f_o_r_m_a_t_i_o_n When using the -_g flag with the C compiler, debug information is not produced for small integer types (8-bit and 16-bit) in old-style function definitions. Correct code is generated, it is only the debugger information that is incomplete. The following example illustrates the types of definitions that will result in the missing information: "int sub1(a, b, c)" "int a;" "short b;" "char c;" "{ ... }" In this example, both _b and _c are small integer types, and _s_u_b_1 has an old-style definition. The following example uses the new prototype-style definition, so there is no missing information: "int sub1(int a, short b, char c)" "{ ... }" You will notice the missing information when using the _w_h_e_r_e command in dbx as follows: % cc -g dbx.c % dbx a.out (dbx) where > 0 sub1(a = 1) ["dbx.c":1, 0x1200011c4] 1 main() ["dbx.c":11, 0x120001220] The missing information can also cause a problem if using the dbx _c_a_l_l command, as the debugger interprets _s_u_b_1 as only having a single parameter: (dbx) call sub1(5, 6, 7) too many parameters in call to sub1 It is possible to work around this problem by converting to the ANSI C prototype style function definitions or by avoiding the small integer types as parameters in old-style function definitions. Alternatively, use the -_o_l_d_c option when compiling. _5._3 _D_E_C _A_d_a _I_s _N_o_t _S_u_p_p_o_r_t_e_d DEC Ada is not supported in Digital UNIX Version 4.0. _5._4 _I_n_i_t _E_x_e_c_u_t_i_o_n _O_r_d_e_r _M_o_d_i_f_i_e_d The execution order for init routines in static executables has been modified to more closely match the execution order for init routines in dynamic executables. See Section 1.8.6 in Chapter 1 for more information. 5-2 Development Environment Notes _5._5 _U_s_i_n_g _p_i_x_i_e _o_n _A_p_p_l_i_c_a_t_i_o_n_s _B_u_i_l_t _w_i_t_h -_o_m If your application was built with the -_o_m switch, you must use the previous version of _p_i_x_i_e for performance analysis work on the application. This version is located in /_u_s_r/_o_p_t/_o_b_s_o_l_e_t_e/_u_s_r/_b_i_n/_p_i_x_i_e. The Atom-based tools, including a new version of _p_i_x_i_e, cannot currently process executables produced with the -_o_m switch. This is a limitation with the _o_m utility which will be corrected in a future release. _5._6 _p_i_x_i_e _C_o_m_m_a_n_d _C_a_n _F_a_i_l _t_o _L_o_c_a_t_e _a_t_o_m _C_o_m_m_a_n_d The /_u_s_r/_b_i_n/_p_i_x_i_e command fails to invoke the _a_t_o_m command it needs, if the atom command's file is in the last directory in the process environment variable _P_A_T_H. The _a_t_o_m command is usually found in the /_u_s_r/_b_i_n and /_b_i_n directories, so when you use the _p_i_x_i_e command, make sure that one of these is included in the value of your process's _P_A_T_H and that it is not the last one. The default ._l_o_g_i_n and ._p_r_o_f_i_l_e files in /_u_s_r/_s_k_e_l (used to create new user accounts by _a_d_d_u_s_e_r) define values for _P_A_T_H that allow use of the _p_i_x_i_e command in various shells. The following code is included in the default ._l_o_g_i_n file: set path=($HOME/bin /usr/bin .) The following code is included in the default ._p_r_o_f_i_l_e file: PATH=$HOME/bin:${PATH:-/usr/bin:.} _5._7 _c_8_9 _C_o_m_m_a_n_d _C_o_n_f_o_r_m_s _t_o _S_p_e_c_1_1_7_0 The _c_8_9 command now conforms to the Spec1170 requirements for command option spelling. The old command syntax is also supported. See the updated _c_8_9 reference page for details. Development Environment Notes 5-3 _5._8 _A_l_t_e_r_n_a_t_e _C_o_m_p_i_l_e_r _S_u_i_t_e The _C_M_P_D_E_V_A_L_T_4_0_0 subset contains an alternate application compiler suite. The README file contained in the subset explains its use. _5._9 _D_E_C _C The default C compiler on Digital UNIX has changed to Digital's DEC C compiler. The previous default C compiler, is still a supported viable option and can be accessed by specifying -_o_l_d_c on the _c_c command line. Much work has been done to minimize the differences between DEC C and the previous compiler. Both compilers have full binary compatibility with each other. This release note provides a list of differences that may be helpful for you to know as you begin to use DEC C in Digital UNIX version 4.0. +o DEC C offers many features that were not available with the previous compiler. See the _c_c(1) and _c_8_9(1) reference pages and the _P_r_o_g_r_a_m_m_e_r'_s _G_u_i_d_e for details. +o Latent errors in your source code may be exposed with this new compiler. Several types of these that we have observed include: - When accessing unaligned short data types through pointers, you will get an unaligned access fault with DEC C and not with the previous compiler. - The stack frames generated by DEC C are packed much tighter than those of the previous compiler. Consequently, any code that overwrites stack data is much more likely to corrupt the next stack variable with DEC C than with the previous compiler. - The use of uninitialized variables that worked with the previous compiler are not guaranteed to work with DEC C. - If data structures are not properly aligned on their natural boundaries, runtime unaligned access faults will more likely result when compiled with DEC C. - Compiling undefined C programming constructs may produce different behaviour with DEC C. In 5-4 Development Environment Notes C, some constructs are undefined by ANSI standards and their behaviour may differ when complied on DEC C instead of ACC. +o Parameter cleaning, which the previous compiler did by default in all modes, is not done by default in -_s_t_d_1 mode with DEC C. For more information, see -_a_n_s_i__a_r_g_s in the _c_c(1) reference page. +o DEC C assumes the ANSI C aliasing rules are adhered to in the -_s_t_d and -_s_t_d_1 modes, and as a result, allows the optimizer to perform more optimizations. The previous compiler did not perform these optimizations. If your program does access the same data through pointers of a different type (for example, by a pointer to int and a pointer to float), then you must not allow the compiler to assume ANSI C aliasing rules. Otherwise, incorrect code might be generated. See the _c_c(1) reference page for details. +o DEC C does not support the -_j command line switch. Equivalent functions are provided by either the - _i_f_o or the -_O<_n> switches, where is a number. +o By default, when no optimization level is specified, DEC C does perform a few more optimizations than the previous compiler did. See the _c_c(1) reference page for details. +o If your link line did not require linking with _l_i_b_c in the past, it may be required now as DEC C utilizes __O_t_s support routines found in _l_i_b_c. Prior to this release, these support routines were in _l_i_b_o_t_s. +o DEC C defines the ___D_E_C_C macro whenever it is used to compile C programs. +o The maximum length for external names allowed by DEC C is 1024 characters. The previous compiler allowed longer external names. _5._9._1 _R_e_m_o_v_e _t_h_e _D_E_C _C -_m_i_g_r_a_t_e _S_w_i_t_c_h If you are currently using DEC C with the -_m_i_g_r_a_t_e switch, Digital encourages you to remove this option and use the default _c_c. Development Environment Notes 5-5 Removal is recommended because: +o The optimization switches have different mappings. See the _c_c(1) reference page for more information. +o You no longer need to explicitly link with the _l_i_b_o_t_s library. The _l_i_b_o_t_s routines used by DEC C now reside in _l_i_b_c. If you call _l_d directly in the command string, replace the switch -_l_o_t_s with -_l_c. _5._9._2 _O_b_j_e_c_t _F_i_l_e _A_d_d_r_e_s_s _R_e_f_e_r_e_n_c_e _L_i_m_i_t There is a restriction with the DEC C compiler in that a single object file cannot contain more than 4093 external address references. The compiler will issue the following error message when compiling a module that exceeds this limit: GP-relative section overflows limit of 32752 bytes To workaround this problem break your module into smaller compilation units or use the -_o_l_d_c compiler option. _5._1_0 _D_E_C _C -_i_f_o _S_w_i_t_c_h When using the -_i_f_o switch in DEC C, symbol information for external variables may be incorrect. For example: % cat simple.c int global_array[100][4]; main() { int local_array[100][4]; } % cc -O1 -g2 -ifo simple.c % dbx a.out (dbx) whatis global_array int global_array; (dbx) whatis local_array local_array[100][4] of int ; Note that the global array is reported as _i_n_t and the local array is a two dimensional array of ints. Both should report the same thing. 5-6 Development Environment Notes If this program is executed without -_i_f_o, the results are as expected. The problem is in the generation of the symbol table, not the debugger. _5._1_1 _X_T_I _a_n_d _T_L_I _L_i_b_r_a_r_i_e_s _A_r_e _T_h_r_e_a_d-_S_a_f_e The libraries _l_i_b_x_t_i._a, _l_i_b_t_l_i._a, _l_i_b_x_t_i._s_o, and _l_i_b_t_l_i._s_o now support multithreaded applications. New _x_t_i._h (for XTI) and _t_i_u_s_e_r._h (for TLI) are available to be included by applications. Binary backwards compatibility has been preserved and unithreaded applications built with previous include files will still run. _5._1_2 _D_E_C_l_a_d_e_b_u_g _P_r_o_d_u_c_t _N_a_m_e _C_h_a_n_g_e (_L_a_d_e_b_u_g) Note that the product name DECladebug has changed to Ladebug. The release notes for Ladebug are in the subset _O_S_F_L_D_B_D_O_C_4_0_0 in the _D_i_g_i_t_a_l _U_N_I_X _V_4._0 _O_p_e_r_a_t_i_n_g _S_y_s_t_e_m _V_o_l_u_m_e _1 CD-ROM and can only be accessed when Ladebug is installed. After installation the release notes can be found in: _u_s_r/_d_o_c/_l_a_d_e_b_u_g/_l_a_d_e_b_u_g-_r_e_l_n_o_t_e_s._t_x_t _5._1_3 _A_n_a_l_y_s_i_s _T_o_o_l _w_i_t_h _O_b_j_e_c_t _M_o_d_i_f_i_c_a_t_i_o_n (_A_T_O_M) The following notes apply to the Analysis Tool with Object Modification utility _a_t_o_m. _5._1_3._1 _P_r_o_f_i_l_i_n_g _S_i_g_n_a_l _H_a_n_d_l_e_r_s _a_n_d _f_o_r_k _w_i_t_h _M_u_l_t_i_t_h_r_e_a_d_e_d _h_i_p_r_o_f A multithreaded program instrumented with the default _h_i_p_r_o_f command, _a_t_o_m appl_prog-_t_o_o_l _h_i_p_r_o_f -_e_n_v _t_h_r_e_a_d_s will sometimes deadlock (enter an infinite polling and sleeping loop). This can happen if the program calls the _s_i_g_n_a_l, _s_i_g_a_c_t_i_o_n or _f_o_r_k function or if it was compiled with a _c_c -_s_p_e_c_u_l_a_t_e ... command (which introduces signal handlers). You can avoid this problem by adding the -_t_o_o_l_a_r_g_s=- _c_a_l_l_t_i_m_e or the -_t_o_o_l_a_r_g_s='-_c_a_l_l_t_i_m_e -_t_h_r_e_a_d_s' option to the command line. For programs that call _f_o_r_k function, instrumenting _l_i_b_c._s_o is always recommended. You should also add the -_a_l_l or -_i_n_c_o_b_j _l_i_b_c._s_o option. Instrumenting _l_i_b_c._s_o also minimizes the risk of deadlock with the Development Environment Notes 5-7 default command, _h_i_p_r_o_f. If the default _h_i_p_r_o_f command must be used for a multithreaded program that calls the _s_i_g_n_a_l or _s_i_g_a_c_t_i_o_n and if _l_i_b_c._s_o must be profiled, add -_e_x_c ___s_i_g_t_r_a_m_p -_e_x_c ___E_s_i_g_t_r_a_m_p to the -_t_o_o_l_a_r_g_s option used to exclude the signal handling procedures and any other procedures they call. Alternatively, or when the program is compiled with a _c_c -_s_p_e_c_u_l_a_t_e ... command, do not instrument _l_i_b_c._s_o by omitting -_a_l_l or adding -_e_x_c_o_b_j _l_i_b_c._s_o. Similarly, if the application's signal handlers call many other procedures directly or indirectly (for example, in _l_i_b_c._s_o), the whole library can be excluded instead of excluding a long list of individual procedures. _5._1_3._2 _T_h_i_r_d _D_e_g_r_e_e _a_n_d _h_i_p_r_o_f _E_r_r_o_r_s _w_i_t_h _M_u_l_t_i-_t_h_r_e_a_d_e_d _A_p_p_l_i_c_a_t_i_o_n_s The Atom _h_i_p_r_o_f tool may not work correctly with threaded applications. The problem may cause threaded applications instrumented with the _h_i_p_r_o_f tool to get a segmentation fault and dump core. You can avoid this problem by passing the -_e_x_c ___s_i_g_e_m_p_t_y_s_e_t switch with the _a_t_o_m _h_i_p_r_o_f command; for example: % _a_t_o_m -_t_o_o_l _h_i_p_r_o_f -_e_n_v _t_h_r_e_a_d_s -_t_o_o_l_a_r_g_s="-_e_x_c ___s_i_g_e_m_p_t_y_s_e_t" _m_y_a_p_p This switch causes the _s_i_g_e_m_p_t_y_s_e_t routine to be excluded from the profile, but avoids the segmentation fault. The Atom _t_h_i_r_d tool (Third Degree) also may not work correctly with threaded applications. The problem may cause threaded applications instrumented with Third Degree to get a segmentation fault and dump core. You can avoid this problem by including the _i_g_n_o_r_e ___s_i_g_e_m_p_t_y_s_e_t entry in your ._t_h_i_r_d file. This entry causes the _s_i_g_e_m_p_t_y_s_e_t routine to be excluded from Third Degree's error checking, but avoids the segmentation fault. 5-8 Development Environment Notes _5._1_3._3 _A_t_o_m _t_h_i_r_d _T_o_o_l (_T_h_i_r_d _D_e_g_r_e_e) _M_a_y _N_o_t _W_o_r_k _C_o_r_r_e_c_t_l_y _w_i_t_h _C++ The Atom _t_h_i_r_d tool may not work correctly with C++ applications that use the tasking library (_l_i_b_t_a_s_k._s_o or _l_i_b_t_a_s_k._a). The problem causes Atom to issue a number of the following warnings: atom: Warning: Object 't' has invalid instruction at 0xhexaddress, treating as data. These are followed by the following Third Degree assertion failure: Assertion failed: pc==InstPC(inst) You avoid the problem by linking your application with the -_c_a_l_l__s_h_a_r_e_d switch and passing the -_e_x_c_o_b_j _l_i_b_t_a_s_k._s_o switch to Atom. For example: % _a_t_o_m -_t_o_o_l _t_h_i_r_d -_e_x_c_o_b_j _l_i_b_t_a_s_k._s_o _m_y_a_p_p This switch excludes the tasking library from Third Degree's error checking, but avoids the assertion failure. _5._1_3._4 _A_t_o_m _E_r_r_o_r _w_i_t_h _D_y_n_a_m_i_c_a_l_l_y _L_i_n_k_e_d _F_o_r_t_r_a_n _A_p_p_l_i_c_a_t_i_o_n_s If a dynamically linked Fortran application is instrumented with -_a_l_l or -_i_n_c_o_b_j _l_i_b_c._s_o, you may get a loader error similar to the following when running the instrumented application: pid:myapp.pixie: /sbin/loader: Fatal Error: Multiple instances of shared object libc.so loaded as both /usr/shlib/libc_r.so and You can avoid this problem by doing one of the following: +o If you have the ability to rebuild your application, you can relink it using the - _n_o_n__s_h_a_r_e_d switch. This produces an application that does not use shared libraries, thereby avoiding the problem. +o If you must use shared libraries but do not need to instrument _l_i_b_c._s_o, you can avoid the problem by passing the -_e_x_c_o_b_j _l_i_b_c._s_o -_e_x_c_o_b_j _l_i_b_c__r._s_o Development Environment Notes 5-9 switches to Atom. For example: % _a_t_o_m -_t_o_o_l _p_i_x_i_e -_a_l_l -_e_x_c_o_b_j _l_i_b_c._s_o -_e_x_c_o_b_j _l_i_b_c__r._s_o _m_y_a_p_p Note, this workaround does not work if you use the Third Degree tool, because Third Degree needs to instrument _l_i_b_c._s_o. +o If you need to instrument _l_i_b_c._s_o (or if you are using the Third Degree tool), you can avoid the problem by passing the -_i_n_c_o_b_j _l_i_b_c__r._s_o switch to Atom to ensure that both _l_i_b_c._s_o and _l_i_b_c__r._s_o are instrumented. After running Atom, remove the instrumented version of _l_i_b_c__r._s_o. Then, replace the instrumented _l_i_b_c__r._s_o library with a hard link to the instrumented version of _l_i_b_c._s_o. Then run the instrumented application. The following example demonstrates the workaround using the _p_i_x_i_e tool. % _a_t_o_m -_t_o_o_l _p_i_x_i_e -_i_n_c_o_b_j _l_i_b_c._s_o -_i_n_c_o_b_j _l_i_b_c__r._s_o _m_y_a_p_p % _r_m _l_i_b_c__r._s_o._m_y_a_p_p._p_i_x_i_e % _l_n _l_i_b_c._s_o._m_y_a_p_p._p_i_x_i_e _l_i_b_c__r._s_o._m_y_a_p_p._p_i_x_i_e % _s_e_t_e_n_v _L_D__L_I_B_R_A_R_Y__P_A_T_H . % ./_m_y_a_p_p._p_i_x_i_e _5._1_4 _C_h_a_n_g_e _t_o _S_t_a_t_i_c _L_i_b_r_a_r_i_e_s _a_n_d _K_e_r_n_e_l _O_b_j_e_c_t_s To save disk space, all the static system libraries and kernel objects are shipped as archive files that contain compressed object files. System tools that manipulate objects and archives understand the new format. Therefore, in most cases, you do not have to make any changes. Any non-Digital tools that rely on the ability to read those objects without going through the supported _a_r interface will fail. You can use the _a_r -_R command to decompress the objects contained in an archive. _5._1_5 _D_E_C _C++ _C_l_a_s_s _L_i_b_r_a_r_y _F_i_x_e_s The following notes apply to DEC C++. 5-10 Development Environment Notes _5._1_5._1 _F_i_l_e _P_o_s_i_t_i_o_n_i_n_g _f_o_r _B_i_d_i_r_e_c_t_i_o_n_a_l _f_s_t_r_e_a_m_s _H_a_s _B_e_e_n _C_o_r_r_e_c_t_e_d A file positioning problem for bidirectional _f_s_t_r_e_a_m_s has been corrected. Previously, if your application switched from reading an _f_s_t_r_e_a_m to writing an _f_s_t_r_e_a_m (with or without an intervening seek operation) the necessary synchronization of the external file position with the _g_e_t pointer was often skipped. This resulted in the written data being placed incorrectly within the file. _5._1_5._2 _r_e_a_l _F_u_n_c_t_i_o_n _H_a_s _B_e_e_n _C_o_r_r_e_c_t_e_d The _r_e_a_l function within the _s_t_o_p_w_a_t_c_h class was incorrectly returning the CPU time. Now it returns the clock time as documented. _5._1_5._3 _f_l_u_s_h _F_u_n_c_t_i_o_n _H_a_s _B_e_e_n _C_o_r_r_e_c_t_e_d The _f_l_u_s_h function within the _o_s_t_r_e_a_m class was incorrectly calling the _o_v_e_r_f_l_o_w function. Now the _f_l_u_s_h function calls the _s_y_n_c function as documented. _5._1_5._4 _L_A_N_G _E_n_v_i_r_o_n_m_e_n_t _V_a_r_i_a_b_l_e _N_o _L_o_n_g_e_r _C_l_e_a_r_e_d During the destruction of a Message object, the value of the _L_A_N_G environment variable is no longer cleared. _5._1_5._5 _E_x_t_r_a_c_t_i_o_n _O_p_e_r_a_t_o_r _C_o_n_v_e_r_t_i_n_g _H_e_x_a_d_e_c_i_m_a_l _V_a_l_u_e_s _H_a_s _B_e_e_n _C_o_r_r_e_c_t_e_d The _e_x_t_r_a_c_t_i_o_n (>>) function within the _i_s_t_r_s_t_r_e_a_m class now works correctly when the conversion base format is _h_e_x and when hexadecimal values, which begin with 0 (zero) but not prefixed with 0x, are read. _5._1_5._6 _S_e_g_m_e_n_t_a_t_i_o_n _F_a_u_l_t _a_t _I_m_a_g_e _E_x_i_t _H_a_s _B_e_e_n _C_o_r_r_e_c_t_e_d A segmentation fault no longer occurs during image exit for applications that call the _s_y_n_c__w_i_t_h__s_t_d_i_o function. Previously, a call to the _s_y_n_c__w_i_t_h__s_t_d_i_o function would free memory that was again freed at image exit. This problem sometimes generated a segmentation fault. Development Environment Notes 5-11 _5._1_6 _G_e_n_e_r_a_l _P_r_o_g_r_a_m_m_i_n_g The following notes apply to general programming. _5._1_6._1 _N_e_w _I_n_t_e_r_f_a_c_e_s _t_o _t_h_e _C _R_u_n_t_i_m_e _L_i_b_r_a_r_y Certain C runtime library functions have new interfaces when compiled with __P_O_S_I_X__C__S_O_U_R_C_E set to a value greater than or equal to _1_9_9_5_0_6_L. This is the default setting in the relevant include files if you do not set __P_O_S_I_X__C__S_O_U_R_C_E to any other value. The relevant library functions are: asctime_r() getpwuid_r() ctime_r() gmtime_r() getgrgid_r() localtime_r() getgrnam_r() rand_r() getlogin_r() readdir_r() getpwnam_r() ttyname_r() To access the old version, define the preprocessor symbol __P_O_S_I_X__C__S_O_U_R_C_E to the appropriate value. See Section 5.16.3.1. Existing binary code will continue to reference the old, binary compatible interfaces. _5._1_6._2 _p_r_o_f _C_o_m_m_a_n_d _I_n_f_o_r_m_a_t_i_o_n _M_e_s_s_a_g_e_s The _p_r_o_f command suppresses informational heading messages in cases where a full profiling report will not be generated. For example, when the -_m_e_r_g_e switch is used to consolidate profiling data files, no report will be generated. The informational messages from _p_r_o_f will be suppressed. These informational messages give a time and date stamp, and display the _p_r_o_f command line. _5._1_6._3 _R_e_a_l_t_i_m_e The following notes apply to realtime programming. _5._1_6._3._1 _S_A__S_I_G_I_N_F_O _N_o_t _V_i_s_i_b_l_e _U_n_d_e_r _C_e_r_t_a_i_n _N_a_m_e_s_p_a_c_e _C_o_n_d_i_t_i_o_n_s The symbol _S_A__S_I_G_I_N_F_O, defined in _s_y_s/_s_i_g_n_a_l._h, is not visible under certain namespace conditions when __P_O_S_I_X__C__S_O_U_R_C_E is explicitly defined in the 5-12 Development Environment Notes application or on the compile line. The _S_A__S_I_G_I_N_F_O symbol will be visible if you do not explicitly define __P_O_S_I_X__C__S_O_U_R_C_E. For most applications, _u_n_i_s_t_d._h provides the standards definitions needed, including __P_O_S_I_X__C__S_O_U_R_C_E. As a general rule, avoid explicitly defining standards macros in your application or on the compile line. If you do explicitly define __P_O_S_I_X__C__S_O_U_R_C_E then be_S_A__S_I_G_I_N_F_Owill visible if you also explicitly define __O_S_F__S_O_U_R_C_E _5._1_6._3._2 _P_O_S_I_X _1_0_0_3._1_b _S_y_n_c_h_r_o_n_i_z_e_d _I/_O _a_n_d _F_i_l_e _T_r_u_n_c_a_t_i_o_n POSIX 1003.1b synchronized I/O using file status flags does not apply to file truncation. When file status flags are used to control I/O synchronization, no synchronization occurs for file truncation operations. The _f_s_y_n_c() or _f_d_a_t_a_s_y_n_c() function can be used to explicitly synchronize truncation operations. _5._1_6._3._3 _f_c_n_t_l() _a_n_d _F__G_E_T_F_L _w_i_t_h _O__D_S_Y_N_C _F_i_l_e _S_t_a_t_u_s. A problem occurs when _f_c_n_t_l() is called with the _F__G_E_T_F_L request, and the file operated on has the _O__D_S_Y_N_C file status flag set. The return mask incorrectly indicates _O__S_Y_N_C instead of _O__D_S_Y_N_C. _5._1_6._3._4 _R_e_a_l_t_i_m_e _P_r_o_b_l_e_m_s _w_i_t_h _A_s_y_n_c_h_r_o_n_o_u_s _I/_O _a_n_d _S_t_r_e_a_m_i_n_g _D_e_v_i_c_e_s When using asynchronous I/O (AIO) with streaming devices, such as tape drives, make sure that you post AIO requests in small numbers; otherwise, the devices will be unable to detect errors, particularly end- of-media errors, in time to prevent further AIO requests to the device. In the case of end-of-media errors, excessive AIO requests can result in the tape running off of its reel. Having two AIO requests outstanding on the device should provide an adequate balance between efficiency and responsiveness to critical device errors. _5._1_6._4 _D_E_C_t_h_r_e_a_d_s (_p_t_h_r_e_a_d_s) The following notes apply to DECthreads. Development Environment Notes 5-13 _5._1_6._4._1 _T_h_e _c_c _C_o_m_m_a_n_d _S_u_p_p_o_r_t_s _t_h_e -_p_t_h_r_e_a_d _O_p_t_i_o_n The -_p_t_h_r_e_a_d option has been added to the _c_c command. This option will provide the IEEE Std 1003.1C-1995, POSIX System Application Program Interface environment for developers of multithreaded and threadsafe code. For compatibility the -_t_h_r_e_a_d_s option remains and provides a P1003.4a Draft 4 environment (P1003.1C was previously named P1003.4a). The -_t_h_r_e_a_d_s option should not be used in applications utilizing the 1003.1c-1995 environment. _5._1_6._4._2 _L_i_b_r_a_r_i_e_s _l_i_b_c _a_n_d _l_i_b_c__r _a_r_e _M_e_r_g_e_d The threadsafe functions in _l_i_b_c__r._s_o and _l_i_b_c__r._a have been merged into _l_i_b_c._s_o and _l_i_b_c._a. It is no longer necessary to link with _l_i_b_c__r, and this library has now been replaced with a link to _l_i_b_c for binary and makefile compatibility. See Section 5.16.4.1 for information on how to compile and link multithreaded and threadsafe code. To determine the thread safety of individual _l_i_b_c functions, consult the appropriate reference page. The number of thread safe functions has been considerably increased in Version 4.0. In many cases the original API of functions for which there is a *__r variant are now also threadsafe. In these cases the *__r API is also retained for compatibility, and documented as obsolete. _5._1_6._4._3 _D_E_C_t_h_r_e_a_d_s _E_x_c_e_p_t_i_o_n _H_a_n_d_l_i_n_g DECthreads Exception Handling now relies on the DEC C exception handling capabilities. Threaded applications must now link with _l_i_b_e_x_c. Note that if you are compiling your threaded application as Digital recommends (using the -_t_h_r_e_a_d or -_p_t_h_r_e_a_d_s switch) this change will not affect the building of your application. If you are using the DECthreads Exception Package with POSIX 1003.1c threads interface, you must include _p_t_h_r_e_a_d__e_x_c_e_p_t_i_o_n._h in your source file. This does not apply to applications which use the CMA or draft 4 POSIX threads interfaces. 5-14 Development Environment Notes _5._1_6._4._4 _D_E_C_T_h_r_e_a_d_s _S_i_g_n_a_l _M_o_d_e_l _I_n_c_o_m_p_a_t_i_b_i_l_i_t_i_e_s _i_n _T_h_r_e_a_d_e_d _A_p_p_l_i_c_a_t_i_o_n_s Full support of the POSIX 1003.1c signal model may cause a binary compatability problem for applications using threads. This is not an API change but a change in runtime behavior. A thread that was never interrupted before may now be interrupted. _5._1_6._4._5 _d_b_x _a_n_d _D_E_C_t_h_r_e_a_d_s You cannot use _d_b_x to debug threads (pthreads) in this release. Use the Ladebug debugger to debug threaded applications. _5._1_6._4._6 _T_h_r_e_a_d_e_d _A_p_p_l_i_c_a_t_i_o_n _C_o_d_i_n_g _E_r_r_o_r_s This release contains substantial changes to threads that will likely expose programming errors in existing applications that use DECthreads. Such errors include, but are not limited to, the following: +o Attempting to unlock a mutex that is not locked +o Use of uninitialized variables +o Improper use of data structures (for example, using a _p_t_h_r_e_a_d__a_t_t_r__t instead of a _p_t_h_r_e_a_d__m_u_t_e_x_a_t_t_r__t in a call to _p_t_h_r_e_a_d__m_u_t_e_x_a_t_t_r__c_r_e_a_t_e) +o Improper data access synchronization +o Use of an undocumented or unsupported routine _5._1_6._4._7 _M_i_s_s_i_n_g _T_h_r_e_a_d _R_o_u_t_i_n_e_s The following routines: +o _p_t_h_r_e_a_d__b_i_n_d__t_o__c_p_u__n_p +o _c_m_a__t_h_r_e_a_d__b_i_n_d__t_o__c_p_u are not provided in this release. If you use an application that requires one of these routines, it is recommended that you not migrate to Digital UNIX V4.0. Note that applications using _p_t_h_r_e_a_d__b_i_n_d__t_o__c_p_u__n_p Development Environment Notes 5-15 are using the draft 4 POSIX interface which is scheduled for retirement. These applications should be migrated as soon as possible to the POSIX 1003.1c compliant interface. (See the retirement notice in this volume for _p_t_h_r_e_a_d_s draft 4). _5._1_6._4._8 _D_E_C_t_h_r_e_a_d_s _S_t_a_t_i_c _L_i_b_r_a_r_i_e_s The following static libraries for DECthreads have not been provided in this release: +o libpthread.a +o libpthreads.a The libraries will be provided in a future release. _5._1_6._4._9 _D_E_C_t_h_r_e_a_d_s _S_y_s_t_e_m _C_a_n_c_e_l_l_a_t_i_o_n _P_o_i_n_t_s Threaded applications that require system cancellation points must use the POSIX 1003.1c DECthreads interface. Cancellation points are not supported for the CMA or draft POSIX DECthreads interfaces. See the _G_u_i_d_e _t_o _D_E_C_t_h_r_e_a_d_s Appendix A for the list of supported cancellation points. _5._1_6._4._1_0 _D_E_C_t_h_r_e_a_d_s _a_n_d _F_o_r_k_i_n_g In this release, the metering capabilities of DECthreads may not be reliable in a process which forks. _5._1_6._4._1_1 _D_E_C_t_h_r_e_a_d_s _a_n_d _R_e_a_l_t_i_m_e In previous releases of Digital UNIX, thread scheduling attributes were system wide. In this release, all thread policies and priorities are now local to the process. Thread priorities between processes cannot be controlled. No artificial limit now exists on thread priorities: the full priority range is now accessible by every thread. See the IEEE POSIX 1003.1c standard or Appendix A of the _G_u_i_d_e _t_o _D_E_C_t_h_r_e_a_d_s for further discussion of contention scopes. _5._1_6._4._1_2 _D_E_C_t_h_r_e_a_d_s _a_n_d _A_l_p_h_a _F_i_r_m_w_a_r_e _R_e_v_i_s_i_o_n_s Use the current minimum firmware revisions for Digital UNIX 4.0 to get the best DECthreads 5-16 Development Environment Notes performance. The correct firmware revisions for your processor are identified in the Digital UNIX _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e. _5._1_6._4._1_3 _D_E_C_t_h_r_e_a_d_s _a_n_d _S_i_g_n_a_l _H_a_n_d_l_i_n_g Signal handling in the POSIX 1003.1c (pthread) interface of DECthreads is substantially different than signal handling is for the draft 4 POSIX and the CMA interfaces of DECthreads. When migrating your application from the draft 4 POSIX or CMA interfaces to the POSIX 1003.1c interface, please see the IEEE POSIX 1003.1c standard or Appendix A in the _G_u_i_d_e _t_o _D_E_C_t_h_r_e_a_d_s for a discussion of signal handling in threaded applications. _5._1_6._5 _C_h_a_n_g_e_s _i_n _K_e_r_n_e_l _D_e_b_u_g_g_i_n_g _U_s_i_n_g _d_b_x To reduce the size of the operating system, some kernel symbol table information useful for debugging with the _d_b_x debugger has been removed. This information is mostly the type information for variables inside the kernel. (This feature was implemented in DEC OSF/1 Version 3.0.) For example, assume you have the following variable declaration: struct vnodeops procfs_vnodeops; The _d_b_x debugger might not know that the _p_r_o_c_f_s__v_n_o_d_e_o_p_s variable is of the _s_t_r_u_c_t _v_n_o_d_e_o_p_s type. Instead, the _d_b_x debugger will regard it as an _i_n_t, as follows: (dbx) print procfs_vnodeops 0x12345678 (dbx) whatis procfs_vnodeops int procfs_vnodeops; To resolve this problem, explicitly cast the variable to the correct type. Using the previous variable declaration, issue either of the following _d_b_x commands: (dbx) print *(struct vnodeops *)&procfs_vnodeops (dbx) px &procfs_vnodeops 0xfffffc0000660540 (dbx) print (struct vnodeops)0xfffffc0000660540 Development Environment Notes 5-17 If the variable is a pointer to a type, cast the pointer and dereference it without the & operator. For example: (dbx) print *(struct vnodeops *)procfs_vnodeops Type information can usually be obtained from files in the /_u_s_r/_i_n_c_l_u_d_e/_s_y_s directory. To avoid repetitive casting, use _d_b_x aliases interactively or store them in a ._d_b_x_i_n_i_t file. For example, the following alias yields the results shown: (dbx) alias procfs_vnodeops "print *(struct vnodeops *)&procfs_vnodeops" (dbx) procfs_vnodeops struct { vn_lookup = 0xfffffc000027f0c0 vn_create = 0xfffffc000027f0a0 vn_mknod = 0xfffffc000027f0a0 You might find the following two aliases helpful: alias pst(x,y) "print *(struct x *)y" alias pvst(x,y) "print *(struct x *)&y" The first alias prints the structure of an address or pointer; the second alias prints a variable of a specified structure. For example: (dbx) pst(thread,0xfffffc00002cacb8) struct { links = struct { next = 0xd3431d90a21e0018 prev = 0x23de0040a75e0000 . . . (dbx) pvst(vnodeops,procfs_vnodeops) struct { vn_lookup = 0xfffffc000027f0c0 vn_create = 0xfffffc000027f0a0 vn_mknod = 0xfffffc000027f0a0 . . . _5._1_6._6 _W_a_r_n_i_n_g_s _f_r_o_m _s_y_s_c_o_n_f_i_g _A_b_o_u_t _L_o_a_d_a_b_l_e _S_u_b_s_y_s_t_e_m _A_t_t_r_i_b_u_t_e _T_a_b_l_e_s When a loadable subsystem is loaded and there are no 5-18 Development Environment Notes _s_y_s_c_o_n_f_i_g_t_a_b entries in the loadable subsystem's attribute table, the _s_y_s_c_o_n_f_i_g utility might issue warnings in the _x_c_o_n_s_o_l_e window. To work around this problem, make sure that the loadable subsystem's _s_y_s_c_o_n_f_i_g_t_a_b table contains the same number of attributes as the loadable subsystem's attribute table. Then, if an attribute appears in the _x_c_o_n_s_o_l_e it will correctly indicate that an entry could not be properly loaded or parsed. _5._1_6._7 _D_e_v_i_c_e _D_r_i_v_e_r _E_x_a_m_p_l_e _F_i_l_e_s Previously, Digital has supplied the _n_o_n_e._c example driver in the /_u_s_r/_e_x_a_m_p_l_e_s/_d_e_v_d_r_i_v_e_r area. In this release, the _n_o_n_e._c and _n_o_n_e_1_0_0 kit examples have been replaced by the _e_d_1_0_0 driver example now in /_u_s_r/_e_x_a_m_p_l_e_s/_d_e_v_d_r_i_v_e_r. The file _e_d_1_0_0 is a directory that contains the driver source and the associated files required to configure the driver in Digital UNIX Version 4.0. Please refer to the _G_u_i_d_e _t_o _W_r_i_t_i_n_g _D_e_v_i_c_e _D_r_i_v_e_r_s: _A_d_v_a_n_c_e_d _T_u_t_o_r_i_a_l for more information about writing device drivers. _5._1_7 _F_u_n_c_t_i_o_n_s _a_n_d _S_y_s_t_e_m _C_a_l_l_s The following notes apply to functions and system calls. _5._1_7._1 _C_h_a_n_g_e_s _i_n _p_i_p_e _S_y_s_t_e_m _C_a_l_l _B_e_h_a_v_i_o_r In DEC OSF/1 Version 3.0, the behavior for interrupted read and write calls on a pipe was changed to be POSIX compliant. When a read or write on a pipe is interrupted by a signal and no bytes have been transferred, the _r_e_a_d system call and _w_r_i_t_e system call returns -1 with _e_r_r_n_o set to [EINTR]. In previous releases, the _r_e_a_d system call either restarted or returned [EINTR], depending on the setting of the SA_RESTART flag for the interrupting signal. Applications must be prepared to handle the [EINTR] return value or block any expected signals for the duration of the read or write operation. See _p_i_p_e(2), _r_e_a_d(2), and _w_r_i_t_e(2) for more information. _5._1_7._2 _s_h_m_a_t() _F_a_i_l_s _W_i_t_h _I_n_v_a_l_i_d _A_r_g_u_m_e_n_t (_E_I_N_V_A_L) Existing applications that use large shared memory segments (>= 8MB) may fail during a _s_h_m_a_t system call. This is because, by default, the system allocates shared page tables when a segment size >= Development Environment Notes 5-19 8MB is specified in _s_h_m_g_e_t and therefore requires that attach addresses are aligned at 8MB. If an application uses an unaligned address to attach to such a segment and does not specify _S_H_M__R_N_D, the attach operation will fail and _E_I_N_V_A_L is returned. This behaviour can be modified using the _s_y_s_c_o_n_f_i_g utility on a running system as follows: # _s_y_s_c_o_n_f_i_g -_q _i_p_c _s_s_m-_t_h_r_e_s_h_o_l_d ipc: ssm-threshold = 8388608 # _s_y_s_c_o_n_f_i_g -_r _i_p_c _s_s_m-_t_h_r_e_s_h_o_l_d=_0 ssm-threshold: reconfigured_s_y_s_c_o_n_f_i_g -_q _i_p_c _s_s_m- _t_h_r_e_s_h_o_l_d ipc: ssm-threshold = 0 If this behaviour is to be preserved across a reboot then edit the /_e_t_c/_s_y_s_c_o_n_f_i_t_a_b file to add the following: ipc: ssm-threshold = 0 To make use of shared page tables the application must be modified to use 8MB aligned attach addresses. Applications that use a large shared region (such as databases) are likely to use more than one segment to form a contiguous shared region. This could be due to either of the following conditions: +o the configured segment size is small +o the configured segment size is at the largest SystemV shared segment of 2GB (Gigabytes). For this to work correctly the segments must be attached to contiguous virtual addresses. Typically this is done by attaching the next segment at the address formed by adding the size of the segment to the start address. If a segment size is not a multiple of 8MB then, the attach address will be unaligned and it will fail if SSM is enabled. Application vendors typically use the _s_h_m-_m_a_x value to determine the size of a segment and configure an aligned size for _s_h_m-_m_a_x. This is all that needs to be done to continue using SSM. The recommended optimum size is 2GB - 8MB = 2139095040 (0x7f800000). To reconfigure _s_h_m-_m_a_x, edit the /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b 5-20 Development Environment Notes file, and add the following ipc: shm-max=0x7f800000 Then reboot your system. Development Environment Notes 5-21 Window System Software Notes 6 This chapter contains notes about issues and known problems with the windowing software and, whenever possible, provides solutions or workarounds to those problems. The following topics are discussed in this chapter: +o Hardware notes and restrictions +o X servers +o X clients +o CDE clients +o Windows programming +o Internationalization _6._1 _H_a_r_d_w_a_r_e _N_o_t_e_s _a_n_d _R_e_s_t_r_i_c_t_i_o_n_s The following notes apply to graphics hardware restrictions. _6._1._1 _C_a_l_c_o_m_p _T_a_b_l_e_t This section provides information about how configure a CalComp DrawingBoard III tablet, an input device supported by the Xinput extension to the Xserver. Once the software for the tablet is installed on your system, you can configure it to emulate a system mouse. _6._1._1._1 _C_o_n_f_i_g_u_r_i_n_g _t_h_e _C_a_l_C_o_m_p _D_r_a_w_i_n_g_B_o_a_r_d _I_I_I _T_a_b_l_e_t If you intend to use the CalComp DrawingBoard III tablet software, you must edit /_u_s_r/_v_a_r/_X_1_1/_X_s_e_r_v_e_r._c_o_n_f to turn on support for the X Input extension. To do this, remove the comment characters surrounding the following lines. The backslash in this example indicates line continuation and is not in the actual display: input < < _dec_xi_db3 lib_dec_xi_db3.so XiDb3Init /dev/tty00:1:12:12:16:\ 1:8:1000:1:1 > > You should also review these lines to ensure that the options specified for the tablet are correct, especially the _t_t_y that is specified as the serial port where the tablet is connected to your system. The last line of this file has the following syntax. The backslash in this example indicates line continuation and is not in the actual display: device:mode:tabletWidth:tabletHeight:numbtns:corePointer:mouseScale:\ resolution:Xincrement:Yincrement Table 6-1 can help you determine how to set up the entries for the tablet in the /_u_s_r/_v_a_r/_X_1_1/_X_s_e_r_v_e_r._c_o_n_f file. Table 6-1: _C_a_l_C_o_m_p _D_r_a_w_i_n_g_B_o_a_r_d _I_I_I _T_a_b_l_e_t _C_o_n_f_i_g_u_r_a_t_i_o_n _O_p_t_i_o_n_s _a_n_d _V_a_l_u_e_s __________________________________________________ Option Description __________________________________________________ device The port (tty) to which the device is connected. The default is tty00. mode This should be set to 1 for absolute motion. tabletWidth Width of the active tablet area in inches, not the physical size. The default is 12. tabletHeight Height of the active tablet area in inches, not the physical size. The default is 12. numbtns Number of buttons on the puck or pen. The maximum number is 16 and the default is 16. 6-2 Window System Software Notes Table 6-1: (continued) __________________________________________________ Option Description __________________________________________________ corePointer 0 indicates a native tablet mode (no system mouse). 1 indicates emulate core pointer (the mouse and tablet are both core pointer devices. The default is 1 (emulate core pointer). mouseScale 1 to 50 scaling factor in relative mode. Determines the speed of the cursor; the higher the number, the slower the cursor moves. The default is 8. resolution 1 to 2540 lines per inch (lpi). The default is 1000. Xincrement How much the X axis must be incremented to cause the tablet to send new coordinates to the Xserver. The range is 0 to 65536. The default is 1. Yincrement How much the Y axis must be incremented to cause the tablet to send new coordinates to the Xserver. The range is 0 to 65536. The default is 1. __________________________________________________ The device option is required and specifies which _t_t_y device should be associated with the tablet. By default, the installation software assigns the CalComp DrawingBoard III tablet to tty00, which you may want to change if that _t_t_y is already allocated. For information on how to determine which serial port your tablet is connected to, see the hardware documentation that was shipped with your processor. Note that when the stylus or puck is moved as far as the minimum Xincrement or Yincrement value, the value of the corresponding axis is updated. For example, if the Xincrement value is set to 10 and the tablet is moved 10 units along the X axis, the value of the Y axis will also be updated simultaneously with the X Window System Software Notes 6-3 axis, even if the Yincrement value has not been reached. Keep this in mind when setting the Xincrement and Yincrement options. After you have configured the /_u_s_r/_v_a_r/_X_1_1/_X_s_e_r_v_e_r._c_o_n_f file, you must follow these steps to turn on support for the tablet in the Xserver: 1. Plug the tablet into your system and turn it on. 2. Enter the following command to restart the Xserver so that the Xinput extension can recognize the tablet (the backslash in this example indicates line continuation and is not in the actual display): # /_u_s_r/_s_b_i_n/_s_h_u_t_d_o_w_n -_r +_5 "_T_u_r_n_i_n_g _o_n _s_u_p_p_o_r_t _f_o_r _t_h_e _C_a_l_c_o_m_p \ _D_r_a_w_i_n_g_b_o_a_r_d _I_I_I _t_a_b_l_e_t" When the system comes back up, the tablet will be configured into the Xserver and ready to use. When the Xserver first accesses the tablet, it performs some hardware-specific initialization that can be saved in the on-board memory of the tablet. To save these settings, follow these steps: 1. Press the EXIT CONFIG button on the tablet's menu. 2. Under the SAVE button, press the DEFAULT button. 3. Press the EXIT CONFIG button to save the settings. _6._1._1._2 _N_o_t_e_s _a_n_d _R_e_s_t_r_i_c_t_i_o_n_s The following notes and restrictions apply to the CalComp DrawingBoard III tablet. +o If the puck or stylus is not used within a 5 minute period, the tablet will automatically shut off. To reactivate it, press any button on the puck or stylus while they are in close proximity to the tablet. +o If you configure the tablet as the system's core pointer, moving the puck and the system mouse simultaneously will cause the cursor to move in an unpredictable fashion. +o Use only one puck or stylus at a time. If you try 6-4 Window System Software Notes to use both input devices simultaneously, you will encounter unpredictable behavior. +o Digital UNIX does not support manual configuration of the tablet via the tablet buttons. If you try to use these buttons to configure the tablet, the Xserver will malfunction and may even crash. If you need to reconfigure the tablet, edit the /_u_s_r/_v_a_r/_X_1_1/_X_s_e_r_v_e_r._c_o_n_f file and then reboot the Xserver. +o You can modify some parts of the tablet setup by programming the Xinput extension. For more information on how to do this, see the XInput specification provided by the X Consortium. _6._1._2 _Q_v_i_s_i_o_n _G_r_a_p_h_i_c_s _D_i_s_p_l_a_y _E_r_r_o_r Different versions of Qvision demonstrate _f_i_l_l_s_o_l_i_d drawing problems, leaving a line at the bottom of the screen, which is evident when running CDE blank lock screen. The line varies in color and intensity depending on the version of the Qvision board. _6._2 _X _S_e_r_v_e_r_s The following notes apply to X servers. _6._2._1 _W_i_n_d_o_w _S_y_s_t_e_m _R_e_s_p_o_n_s_e _a_n_d _P_a_g_i_n_g _L_o_a_d The windowing system on AlphaStation 600 systems may experience poor response times in a heavy paging environment. This problem occurs on all platforms, but is most pronounced on AlphaStation 600 series processors. Mouse movement is unaffected, but windowing operations such as exposing a window may be degraded. When this condition occurs you may not be able to use _t_e_l_n_e_t or _r_l_o_g_i_n. The poor response period may be greater than 2 minutes or it may stop after a few seconds. The cause is usually a memory intensive application that depletes the number of available pages on the free list to an absolute minimum. When this occurs, only privileged tasks are able to access any free pages. All other tasks are blocked, most notably the window manager. To verify if your system is experiencing this problem, open a terminal with _x_t_e_r_m while your memory-intensive application is running and enter the following Window System Software Notes 6-5 command: # _v_m_s_t_a_t _2 The output from this command will show the number of free pages available under the heading _f_r_e_e. If this number falls below the reserved amount _v_m-_p_a_g_e-_f_r_e_e- _r_e_s_e_r_v_e_d, your system is exhibiting the memory problem. The following is sample output on a machine experiencing this condition: Virtual Memory Statistics: (pagesize = 8192) procs memory pages intr cpu r w u act free wire fault cow zero react pin pout in sy cs us sy id 2 37 15 5832 4021 1108 20K 5975 4575 285 4761 0 62 196 266 1 1 98 2 37 15 5851 4002 1108 99 13 50 0 8 0 4 13 239 0 1 99 3 37 15 7039 2788 1134 26 0 26 0 0 0 17 51 255 1 9 90 3 37 15 9791 10 1140 7291 17 7258 0 13 48 288 12 422 1 68 31 3 37 15 9790 9 1149 1049 0 1048 39 1 146 472 15 527 0 32 68 3 36 15 9784 9 1116 743 0 741 0 2 106 446 12 466 0 22 78 3 36 15 9811 9 1096 460 0 459 0 1 107 434 12 459 0 20 79 In this example, _v_m-_p_a_g_e-_f_r_e_e-_r_e_s_e_r_v_e_d is set to its default value of ten pages and the VM subsystem has been overwhelmed. The system will demonstrate degraded window performance and other performance degradations. If the output from _v_m_s_t_a_t on your machine does not exhibit similar results, do not tune your system as Digital recommends in this note. An interim solution to this problem is to: +o Raise the priority of the _m_w_m or _d_t_w_m window manager. +o Change some _v_m (virtual memory) tuning parameters. Make the changes to three tuning parameters in the /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b file as described in the next paragraph. Digital recommends that you systematically double the parameter values until you reach an acceptable balance between user interactivity and application performance. The following parameter values provide reasonable interactivity with moderate performance degradation on a Alphatop Station 6000 with 128M of physical memory These changes are intended to keep a larger than normal number of pages on the free list as a buffer: +o _v_m-_p_a_g_e-_f_r_e_e-_m_i_n=_2_0_4_8 This value enables the system to start paging earlier than usual. 6-6 Window System Software Notes +o _v_m-_p_a_g_e-_f_r_e_e-_t_a_r_g_e_t=_4_0_9_6 This value enables the system to stop paging later than usual. +o _v_m-_p_a_g_e-_f_r_e_e-_o_p_t_i_m_a_l=_4_0_9_6 This value enhances the swapping of tasks to force the memory intensive application to be swapped out occasionally. You must reboot your system after making these changes. You may find that your system performs acceptably with some manipulation of these parameters. However, these suggested tuning parameters were devised to provide some level of user interactivity in a heavy paging/swapping environment. They may not be the best solution for your particular needs, but may provide a reasonable starting place. If your system does not have 128MB of memory, reduce the suggested numbers. The units for these values are pages (which are 8KB) resulting in a substantial 32MB of memory use. If you are uncertain, try doubling the default parameter values until you reach acceptable perfromance. You can check the default values using dbx on a running system as follows: # dbx -k /vmunix (dbx) p vm_page_free_target 2048 (dbx) p vm_page_free_optimal 1029 (dbx) p vm_page_free_min 20 (dbx) p vm_page_free_reserved 10 Refer to the _S_y_s_t_e_m _T_u_n_i_n_g _a_n_d _P_e_r_f_o_r_m_a_n_c_e _M_a_n_a_g_e_m_e_n_t manual for information on these parameters and system tuning in general. To raise the priority of the window manager, open a terminal window and find the process ID of the window manager found using the _p_s command. Stop the window manager process with the _k_i_l_l command. Restart the window manager using _n_i_c_e as follows: # _n_i_c_e -_2 _d_t_w_m & IN this example, replace _d_t_w_m with _m_w_m or _t_w_m if you are using a different window manager. If your Window System Software Notes 6-7 system is tuned correctly, there should be is a small latency when the memory intensive application starts, which will balance as the memory subsystem recovers. You should be able to expose windows and drag them around with a reasonable response time. If you expose a window that has not been used for some time, expect some latency. This is because you are now working in a heavy paging/swapping environment and those pages are not yet available. To avoid system panics after modifying the _s_y_s_c_o_n_f_i_g_t_a_b file, you must use this release of Digital UNIX. Keep in mind, you will need to kill and restart the window manager each time you terminate your xsession. Note that to use _n_i_c_e, you need to be a privileged (root) user. _6._2._2 _L_i_m_i_t_e_d _M_u_l_t_i_s_c_r_e_e_n _D_i_s_p_l_a_y _S_u_p_p_o_r_t _W_i_t_h _C_D_E CDE provides limited support for X servers with more than one screen. While a multiscreen environment is possible, a number of inconsistencies are noticeable. For example, colors in secondary screens may not be correct, icons may not display properly, and applications may not appear on the screen where they are invoked. Digital is currently working with OSF to resolve issues related to multiscreen environments for future releases of CDE. _6._2._3 _K_e_y_m_a_p _I_n_t_e_r_o_p_e_r_a_b_i_l_i_t_y _P_r_o_b_l_e_m If you use the Keyboard Options desktop application /_u_s_r/_d_t/_b_i_n/_d_x_k_e_y_b_o_a_r_d, to change the keymap, X11R5 clients will not be notified of the change. For example, a _d_x_t_e_r_m running on DEC OSF/1 Version 3.2 displaying to a Digital UNIX Version 4.0 system will not be notified that the keyboard mapping changed. To avoid this problem, enter the following command after using _d_x_k_e_y_b_o_a_r_d to change the keyboard mapping: xmodmap -e "keycode 248 = NoSymbol" _6._2._4 _D_o _N_o_t _M_o_d_i_f_y _t_h_e _k_e_y_m_a_p_s._d_i_r _F_i_l_e The final revision of the X Keyboard Extension, XKB Version 1.0, will be different from XKB Version 0.65, shipping with this release. The format of /_u_s_r/_l_i_b/_X_1_1/_x_k_b/_k_e_y_m_a_p_s._d_i_r will change. Do not 6-8 Window System Software Notes modify this file as it will not be preserved with future updates of the operating system. To force the server to use a specific XKB keymap, add the -_x_k_b_m_a_p option to the server options line in /_u_s_r/_l_i_b/_X_1_1/_X_s_e_r_v_e_r._c_o_n_f. Refer to the reference page on _X_d_e_c for more information. _6._2._5 _I_n_t_e_r_l_e_a_f _D_i_s_p_l_a_y _P_r_o_b_l_e_m Some versions of Interleaf running under Digital UNIX exhibit display anomalies when manipulating Interleaf PullDown or PopUp menus. This will appear as a section of the screen that is not correctly repainted when the menu is removed. This is due to a problem with Interleaf in relying on the contents of a Save-Unders region without responding to expose events. The problem may be fixed in a later version of Interleaf but can also be eliminated by disabling Save-Unders on the X Server command line. Do this by editing the /_v_a_r/_X_1_1/_X_s_e_r_v_e_r._c_o_n_f file to add the -_s_u argument to the _a_r_g_s statement. Refer to the _X_d_e_c(1X) reference page for the exact syntax. _6._3 _X _C_l_i_e_n_t_s The following notes apply to X clients. _6._3._1 _X _W_i_n_d_o_w _C_o_l_o_r_m_a_p _R_e_s_o_u_r_c_e_s Color rich applications, such as Netscape, exhaust a large number of colormap resources. This results in problems with other graphical applications. For example, you may notice that icons normally displayed by the CDE Application Manager are not displayed when a color rich application is currently running on the system. Graphics displayed by applications and online help volumes may also be affected. The icon editor, _d_t_i_c_o_n, may not be able to open a pixmap that contains a large number of colors. In most cases this is a visual problem, and it may not be necessary to take any corrective actions. The CDE icon labels can be used in the same way as the icon for user actions such as drag-and-drop, single and double click. The simplest solution is to exit the color rich application. There are several alternate actions: Window System Software Notes 6-9 +o use the CDE Style Manager's Color application to select the number of colors used by the desktop or an application. Alternatively, if supported: - set an application resource to limit color usage - start the application with a flag that controls color map installation. (Refer to the application documentation for further details.) +o In the case of Netscape, two workarounds are available, the first is preferred: - Use Netscape's _m_a_x_I_m_a_g_e_C_o_l_o_r_s resource to limit the number of colors that Netscape uses. A suggested limit is 96. You can do this by placing the following line in the $_H_O_M_E/._X_d_e_f_a_u_l_t_s file: Netscape*maxImageColors: 96 - Start Netscape with the -_i_n_s_t_a_l_l flag, which specifies that Netscape should install its own colormap. Although this is supported, there are side affects such as: +o Noticeable application and background color changes when focus is moved in and out of the Netscape window. +o Inability to clearly view the contents of the Netscape window when focus is moved out of the Netscape window. _6._3._2 _M_a_n_u_a_l _M_e_r_g_e _o_f _D_X_n_o_t_e_p_a_d _R_e_s_o_u_r_c_e _D_e_f_i_n_i_t_i_o_n _F_i_l_e A new resource definition (*_D_X_m_f_i_t_T_o_S_c_r_e_e_n_P_o_l_i_c_y: _A_S__N_E_E_D_E_D) has been added to the /_u_s_r/_l_i_b/_X_1_1/_a_p_p- _d_e_f_a_u_l_t_s/_D_X_n_o_t_e_p_a_d resource file for the C locale. If you are doing an update installation, this new resource is not automatically merged into your existing /_u_s_r/_l_i_b/_X_1_1/_a_p_p-_d_e_f_a_u_l_t_s/_D_X_n_o_t_e_p_a_d file. Therefore, you must manually manually append the following text to your C-locale _D_X_n_o_t_e_p_a_d resource 6-10 Window System Software Notes file: *DXmfitToScreenPolicy: AS_NEEDED This definition tells the toolkit to add scroll bars to a dialog box if the dialog box does not fit on the screen. It is required to support new workstations with smaller monitor resolutions. _6._3._3 _D_e_f_a_u_l_t_s _f_o_r _L_o_c_k_i_n_g _M_a_i_l_b_o_x_e_s MH and _d_x_m_a_i_l default to using _l_o_c_k_f for locking mailboxes. This differs from the default used by both _b_i_n_m_a_i_l and _m_a_i_l_x. This is not a problem unless NFS is used to share mailbox directories (for example, /_v_a_r/_s_p_o_o_l/_m_a_i_l and $_H_O_M_E/_M_a_i_l). If NFS is used, then the lock style should be explicitly set. See the _m_a_i_l__m_a_n_u_a_l__s_e_t_u_p(7) reference page for more information. _6._3._4 _S_w_i_t_c_h_i_n_g _L_o_c_a_l_e_s _i_n _d_x_m_a_i_l When _d_x_m_a_i_l is run using a new locale setting, mail subjects in the mail folders are still encoded in the codeset used by the previous locale. Non-ASCII characters in these subjects will be displayed incorrectly. To correct this, use the rescan mail folder function to convert all existing subjects lines to the codeset used by the new locale. _6._3._5 _C_l_i_p_b_o_a_r_d _I_n_t_e_r_o_p_e_r_a_b_i_l_i_t_y _P_r_o_b_l_e_m MH and A Motif clipboard interoperability problem prevents applications from exchanging clipboard data with applications from releases prior to DEC OSF/1 Version 3.0. This break in compatibility was necessary to restore clipboard interoperability between Digital UNIX and 32-bit architectures. To work around this problem, use the quick copy function to transfer data. Quick copy is normally performed by selecting the text to be transferred and then clicking MB2 in the paste location. _d_x_m_a_i_l default to using _l_o_c_k_f for locking mailboxes. This differs from the default used by both _b_i_n_m_a_i_l and _m_a_i_l_x. This is not a problem unless NFS is used to share mailbox directories (for example, /_v_a_r/_s_p_o_o_l/_m_a_i_l and $_H_O_M_E/_M_a_i_l). If NFS is used, then the lock style should be explicitly set. See Window System Software Notes 6-11 the _m_a_i_l__m_a_n_u_a_l__s_e_t_u_p(7) reference page for more information. _6._3._6 _H_i_l_i_t_e _M_o_u_s_e _T_r_a_c_k_i_n_g _D_i_s_a_b_l_e_d _b_y _D_e_f_a_u_l_t _i_n _x_t_e_r_m Hilite Mouse Tracking is disabled by default. See the _x_t_e_r_m(1X) reference page for information on how to reenable this feature. _6._3._7 _M_o_t_i_f _V_e_r_s_i_o_n _1._1._3 _C_l_i_e_n_t_s Motif applications built on a release of Digital UNIX prior to v2.0 rely on the Motif 1.1.3 libraries. These retired runtime libraries are no long installed by default. These libraries are to be found in subset _O_S_F_M_O_T_I_F_1_1_4_0_0. If an application that relies on these retired libraries is executed, it will fail with an error message. For example: # _x_m_o_s_a_i_c This command produces an error message similar to the following: 1166:/usr/local/bin/xmosaic: /sbin/loader: Fatal Error: object libXm.so from liblist in /usr/local/bin/xmosaic has version "", which does not match the found object: /usr/shlib/libXm.so (with version "motif1.2") _6._3._8 _O_l_d _X _E_n_v_i_r_o_n_m_e_n_t If /_u_s_r/_s_b_i_n/_x_s_e_t_u_p is used to switch login environments from the CDE to XDM, it may need to install the subset _O_S_F_O_L_D_X_1_1_4_0_0 to regain the expected user environment. If this subset is missing, the default X session will consist of a single _x_t_e_r_m and the _t_w_m window manager instead of the more familiar Digital session manager. _6._4 _C_D_E _C_l_i_e_n_t_s The following notes apply to CDE clients. 6-12 Window System Software Notes _6._4._1 _R_e_m_o_t_e _I_n_v_o_c_a_t_i_o_n _o_f _C_D_E _F_i_l_e _M_a_n_a_g_e_r _d_t_f_i_l_e File Manager, Application Manager and Trash Manager are different views supported by the _d_t_f_i_l_e application. Avoid invoking _d_t_f_i_l_e from a remote system with the environement variable _D_I_S_P_L_A_Y set appropriately. This is because of the client-server model used by the _d_t_f_i_l_e application and its close interaction with the tooltalk messaging system. In the event of an unexpected behaviour from any of these utilities, please close down all windows associated with the File Manager, Application Manager and Trash Manager. Then kill all processes associated with _d_t_f_i_l_e. You can get the pid for each process using the following command line: # _p_s -_a_e_f | _g_r_e_p _d_t_f_i_l_e _6._4._2 _A_u_t_o_p_a_u_s_e _a_n_d _E_n_h_a_n_c_e_d _S_e_c_u_r_i_t_y When using enhanced security, Autopause does not allow you to resume a suspended CDE session. If you are not logged in as root, the _d_t_s_e_s_s_i_o_n Autopause and Locking features will not unlock. The session must be unlocked either by typing the root password or remotely killing the _d_t_s_e_s_s_i_o_n process, terminating and restarting the session. The _d_x_p_a_u_s_e program exhibits the same behavior and there is no workaround for this problem. To avoid the problem, turn off the Screen Lock toggle on the Style Manager menu, Screen option. _6._4._3 _d_t_m_a_i_l _a_n_d _t_h_e _E_n_v_i_r_o_n_m_e_n_t _V_a_r_i_a_b_l_e _M_A_I_L_L_O_C_K_I_N_G the _d_t_m_a_i_l utility does not honor the user configurable mail locking environment variable _M_A_I_L_L_O_C_K_I_N_G. If you are using NFS, you must have _n_f_s locking enabled on both client and server systems. _6._4._4 _d_t_m_a_i_l _D_i_s_a_b_l_e_s _T_o_o_l_t_a_l_k _L_o_c_k_i_n_g _B_y _D_e_f_a_u_l_t DtMail will disable tooltalk locking by default. To enable it, select the following option from the Mail Window System Software Notes 6-13 Options->Advance dialog box: Use network aware mail file locking Alternatively, set the following option in your $_H_O_M_E/._m_a_i_l_r_c file: cdenotooltalklock='f' If tooltalk locking is enabled, and the _r_p_c._t_t_d_b_s_e_r_v_e_r_d daemon is not running, you will get the following message: Mailer is unable to obtain exclusive access to this mailbox because the system is not responding. For this time only, you can choose to open this mailbox read-only, or to open it read-write without exclusive access (use only if no one else is using this mailbox). You can either quit and start the _r_p_c._t_t_d_b_s_e_r_v_e_r_d daemon, or click on read-write allowing you to continue without tooltalk lock. _6._4._5 _d_t_m_a_i_l _R_o_w _a_n_d _C_o_l_u_m_n _D_i_s_p_l_a_y Changing the values for rows and columns in the Mail Options->Message View will not take effect immediately when you click on OK or APPLY. Exit _d_t_m_a_i_l and restart it again from the control panel, command line, or file manager. _6._4._6 _d_t_m_a_i_l _A_t_t_a_c_h_m_e_n_t_s _a_r_e _N_o_t _I_n_c_l_u_d_e_d If you compose a mail message by selecting one of the following from the _d_t_m_a_i_l main window, attachments will not be included: +o Compose->New, Include All +o Compose->Reply to Sender, Include +o Compose->Reply to All, Include Include the attachments manually using the drag and drop feature. _6._4._7 _d_t_m_a_i_l _S_t_a_r_t-_u_p Incorrect default permissions on /_d_e_v/_z_e_r_o prevent 6-14 Window System Software Notes _d_t_m_a_i_l from starting. You may see the following message when starting _d_t_m_a_i_l: "No memory available for operation" If you see this message, set the permission mode on /_d_e_v/_z_e_r_o to 666 as follows: # _c_h_m_o_d _6_6_6 /_d_e_v/_z_e_r_o _6._4._8 _C_D_E'_s _S_t_a_t_i_c _D_e_p_e_n_d_e_n_c_y _o_n _t_h_e _N_e_t_w_o_r_k The Common Desktop Environment (CDE) has a static dependency on the state of the network configuration. For more information, see Section 4.6.8. _6._4._9 _x_n_l_L_a_n_g_u_a_g_e _R_e_s_o_u_r_c_e _C_a_n _C_a_u_s_e _P_r_o_b_l_e_m_s _w_i_t_h _C_D_E CDE users should remove any _x_n_l_L_a_n_g_u_a_g_e resource settings from their ._X_d_e_f_a_u_l_t_s files. Those settings are typically left over from one of the user's earlier DECwindows sessions, where the user selected a language from the session manager's language menu and then saved that setting. The _x_n_l_L_a_n_g_u_a_g_e settings should be removed because they override whatever language you select from the language menu in the CDE login window. _6._4._1_0 _P_o_s_s_i_b_l_e _F_a_i_l_u_r_e _i_n _t_h_e _X_O_p_e_n_D_i_s_p_l_a_y _C_a_l_l When logging in to the CDE desktop, it is possible that not all desired applications will be restarted. The X server process may not be able to handle all of the requests for new open connections causing some to fail in the _X_O_p_e_n_D_i_s_p_l_a_y call. Some applications, like _x_t_e_r_m, will log startup errors, such as: xterm error: can't open display :0 in the dxconsole window. To avoid this problem, add the following resource to Window System Software Notes 6-15 your $_H_O_M_E/._X_d_e_f_a_u_l_t_s file: Dtsession*contManagement: 2 This resource enables a handshake protocol between the CDE session manager and window manager during the login phase to control the appearance of new windows. While it may marginally increase the time before the login completes, it better assures that all applications will be restarted. For a multiuser system, this resource can be added to the /_u_s_r/_d_t/_a_p_p-_d_e_f_a_u_l_t_s/_C/_D_t_s_e_s_s_i_o_n file to make the change for all users automatically. _6._5 _W_i_n_d_o_w_s _P_r_o_g_r_a_m_m_i_n_g The following note applies to windows programming. _6._5._1 _X_1_1 _F_o_n_t _P_r_o_b_l_e_m In the fonts _L_u_c_i_d_a-_T_y_p_e_w_r_i_t_e_r-_m_e_d_i_u_m-_R-_n_o_r_m_a_l, the glyphs for multiply (_X) and divide (-:-) are reversed. The multiply is where the divide should be, and vice versa. If the representation of these glyphs are important to your application, use a different font. _6._6 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_z_a_t_i_o_n The following notes apply to restrictions on use of internationalization features in the windowing environments. _6._6._1 _U_s_i_n_g _T_a_i_w_a_n_e_s_e _E_U_C _C_o_d_e_s_e_t _w_i_t_h _C_h_i_n_e_s_e _D_E_C_t_e_r_m _S_o_f_t_w_a_r_e Chinese DECterm software supports the use of DEC Hanyu, Big5 and DEC Hanzi as its terminal code. To process Taiwanese EUC codeset, users should do the following: 1. Start the Chinese DECterm software using the zh_TW.dechanyu locale, % /_u_s_r/_b_i_n/_X_1_1/_d_x_t_e_r_m -_x_n_l _z_h__T_W._d_e_c_h_a_n_y_u 2. In the DECterm just started, issue the following 6-16 Window System Software Notes command: % _s_e_t_e_n_v _L_A_N_G _z_h__T_W._e_u_c_T_W % /_u_s_r/_i_1_8_n/_b_i_n/_s_t_t_y _a_d_e_c _a_c_o_d_e _e_u_c_T_W _t_c_o_d_e _d_e_c_h_a_n_y_u After that, users can use terminal applications to process Taiwanese EUC files. _6._6._2 _B_a_c_k_s_p_a_c_e _K_e_y _N_o_t _S_u_p_p_o_r_t_e_d _i_n _A_s_i_a_n _I_n_p_u_t On PC-style keyboards, the Hanyu, Hanzi, Hangul and Kanji input servers use the Delete key instead of the Backspace key to erase information. _6._6._3 _T_r_a_n_s_p_o_r_t _L_a_y_e_r _I_n _I_n_p_u_t _S_e_r_v_e_r_s The Digital UNIX input servers for Hanyu, Hanzi, and Kanji support only X and local transports. Transports over DECnet and TCP/IP are not supported. DECnet and TCP/IP transports are available only for IM servers that have a single input-server atom name. _6._6._4 _A_s_i_a_n _M_u_l_t_i_s_c_r_e_e_n _S_u_p_p_o_r_t X11R6 input servers can connect to R4, R5 and R6 clients under the same locale. However, if the system is using multiscreen support, only R6 clients can be connected. _6._6._5 _H_a_n_y_u _I_M _S_e_r_v_e_r _S_u_p_p_o_r_t _o_f _E_D_P_C _U_n_d_e_r _z_h__T_W._b_i_g_5 _L_o_c_a_l_e When the Language setting is _z_h__T_W._b_i_g_5, EDPC support must be turned off. Otherwise, random characters will appear in the candidate list for unsupported 4-byte encodings. Select the Input Method Customization... option from the Options button of the input server window in the lower left corner of your screen. Then in the customization dialog box, click the EDPC support button to off. _6._6._6 _S_t_r_i_n_g _C_o_n_v_e_r_s_i_o_n _a_n_d _t_h_e _j_a__J_P._S_J_I_S _L_o_c_a_l_e String conversion using _X_S_t_r_i_n_g_S_t_y_l_e() is not supported for interclient communication under the _j_a__J_P._S_J_I_S locale. This is because the X library assumes that the 7-bit string data has _I_S_O_8_8_5_9-_1:_G_L Window System Software Notes 6-17 encoding, whereas the _j_a__J_P._S_J_I_S locale assumes the data has _J_I_S_X_0_2_0_1._1_9_7_9-_0:_G_L encoding. _6._6._7 _U_s_i_n_g _B_o_o_k_r_e_a_d_e_r _t_o _P_r_i_n_t _C_h_i_n_e_s_e _a_n_d _K_o_r_e_a_n _C_h_a_r_a_c_t_e_r_s The new _m_d_x_b_o_o_k command in the _I_O_S_W_W_O_L_D_B_K_R_4_0_0 subset is a variant of _d_x_b_o_o_k Version 3.0. Unlike _d_x_b_o_o_k, the _m_d_x_b_o_o_k command supports printing files with Chinese and Korean characters. The display quality of _m_d_x_b_o_o_k is not as good as _d_x_b_o_o_k. Therefore, install _m_d_x_b_o_o_k only if you need to print Chinese and Korean characters. _6._6._8 _H_e_b_r_e_w _E_d_i_t_i_n_g _S_t_y_l_e The following notes apply to Hebrew support. +o Hebrew Input Method (HIM) supports the _X_I_M_P_r_e_e_d_i_t_N_o_n_e editing style only (no preedit area is needed). HIM currently supports the following status styles - _X_I_M_S_t_a_t_u_s_N_o_t_h_i_n_g (a common status area for all clients) - _X_I_M_S_t_a_t_u_s_N_o_n_e (no status display) - _X_I_M_S_t_a_t_u_s_A_r_e_a (currently w/o dynamic area change and negotiation). +o To have the _X_I_M_S_t_a_t_u_s_N_o_n_e status, you should also define the environment variable (the value does not matter): HIM_ ALLOW_STATUSNONE If _X_I_M_S_t_a_t_u_s_N_o_n_e is required but the variable is not defined, _X_I_M_S_t_a_t_u_s_N_o_t_h_i_n_g will be used. +o In a Motif 1.2 application, Motif uses _X_I_M_S_t_a_t_u_s_N_o_n_e for Hebrew, but _X_I_M_S_t_a_t_u_s_N_o_t_h_i_n_g will be applied unless the _X_I_M_S_t_a_t_u_s_N_o_n_e environment variable is defined. +o If _X_I_M_S_t_a_t_u_s_N_o_n_e is being used and the Keyboard Manager (KM) is running, keyboard status will be reported by HIM, as it is done for _X_I_M_S_t_a_t_u_s_N_o_t_h_i_n_g. 6-18 Window System Software Notes _6._6._8._1 _C_u_t _a_n_d _P_a_s_t_e _O_p_e_r_a_t_i_o_n The environment variable _A_D_E_C_W__M_O_T_I_F_1_2 is needed for the cut and paste operation of the _D_X_m_C_S_T_e_x_t to work properly in the Hebrew environment. If you encounter problems with the cut and paste operation of a mixed English/Hebrew/Numeric strings, use this workaround and define the variable in your working environment (the value is arbitrary). _6._6._9 _H_e_b_r_e_w _C_D_E _U_s_e_r_s _S_h_o_u_l_d _A_v_o_i_d _U_s_i_n_g _C_e_r_t_a_i_n _A_p_p_l_i_c_a_t_i_o_n_s Hebrew CDE users should avoid using the following CDE applications: +o Text Editor - _d_t_p_a_d +o Terminal - _d_t_t_e_r_m +o File and Application Manager - _d_t_f_i_l_e These applications can hang in the Hebrew locale because of problems in the Hebrew input method. _6._6._1_0 _N_o_t_e_p_a_d _W_i_n_d_o_w _D_i_s_p_l_a_y _a_n_d _I_n_p_u_t _S_t_y_l_e When the notepad application is started with off- the-spot input style, the input area attached at the bottom of the application disappears during split view and delete view. _6._6._1_1 _D_e_f_a_u_l_t _K_e_y_b_o_a_r_d _M_a_p_p_i_n_g The X server will automatically choose a keymap based upon the language and keyboard settings of the system console. If your locale is not available on the system console, or you wish for the server to load a different keymap, you must set the system default keyboard map. The default keyboard map is specified by adding the -_x_k_b_m_a_p option to the args list in the /_u_s_r/_v_a_r/_X_1_1/_X_s_e_r_v_e_r._c_o_n_f file. Add the -_x_k_b_m_a_p option using the following syntax: ! you specify command line arguments here args < -pn -xkbmap _ > Window System Software Notes 6-19 For example: -pn -xkbmap digital_japanese_lk411aj The available keymap files are located in /_u_s_r/_l_i_b/_X_1_1/_x_k_b/_k_e_y_m_a_p, where there is one file for each locale. The individual keymaps for the locale are in the keymap file, and are specified by the keyword _x_k_b__k_e_y_m_a_p. For example, the keymap file /_u_s_r/_l_i_b/_X_1_1/_x_k_b/_k_e_y_m_a_p/_d_i_g_i_t_a_l__j_a_p_a_n_e_s_e, contains an entry for the _l_k_4_1_1_a_j keymap. In addition, keymaps can be changed after logging in by running the Keyboard Options desktop application /_u_s_r/_d_t/_b_i_n/_d_x_k_e_y_b_o_a_r_d if you are using CDE. Use the keyboard setting option of the session manager if you are using _x_d_m. _6._6._1_2 _L_i_t_h_u_a_n_i_a_n _a_n_d _S_l_o_v_e_n_e _L_a_n_g_u_a_g_e _S_u_p_p_o_r_t The following instructions are for modifying some system files to allow for some support of Lithuanian and Slovene. _6._6._1_2._1 _M_n_e_m_o_n_i_c_s _i_n _L_i_t_h_u_a_n_i_a_n _a_n_d _S_l_o_v_e_n_e _D_X _A_p_p_l_i_c_a_t_i_o_n_s DX applications V4.0 do not support the use of mnemonics in Lithuanian and Slovene language variants. _6._6._1_2._2 _D_X _A_p_p_l_i_c_a_t_i_o_n_s _I_n_t_e_g_r_a_t_e_d _t_o _C_D_E _D_e_s_k_t_o_p (_A_p_p_l_i_c_a_t_i_o_n _M_a_n_a_g_e_r) For the Visual Differences application, /_u_s_r/_b_i_n/_X_1_1/_d_x_d_i_f_f, to display differences between two text files written in Lithuanian or Slovene language you must do the following. Edit the resource file _D_x_D_i_f_f located on /_u_s_r/_l_i_b/_X_1_1/_a_p_p- _d_e_f_a_u_l_t_s directory and change the following line: *dxdiff*textdisplay*fontList: fixed to: *dxdiff*textdisplay*fontList: -*-terminal-medium-r-narrow--18-*-*-*-c-*-*-* You need superuser (root) privileges to make this change. 6-20 Window System Software Notes _6._6._1_2._3 _D_X _a_p_p_l_i_c_a_t_i_o_n_s _n_o_t _i_n_t_e_g_r_a_t_e_d _i_n_t_o _t_h_e _C_D_E _d_e_s_k_t_o_p (_A_p_p_l_i_c_a_t_i_o_n _M_a_n_a_g_e_r) Some DX applications that are not integrated as part of the CDE desktop, but can be invoked using the File Manager or command line, do not set all display fonts according to the locale in use. If users want these applications to provide full Lithuanian and/or Slovene language support, they must perform the following corrective actions on the system with Lithuanian and/or Slovene language variant installed. Note that all these actions must be performed by superuser. +o Mail -/usr/bin/X11/dxmail To use Lithuanian and/or Slovene national characters in _d_x_m_a_i_l, edit the resource file /_u_s_r/_l_i_b/_X_1_1/_a_p_p-_d_e_f_a_u_l_t_s/_D_X_M_a_i_l and change the following lines: *outlineList*DXmfontListDefault: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 *outlineList*DXmfontListLevel0: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 *outlineList*DXmfontListLevel1: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 *tocList*DXmfontListDefault: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 *tocList*DXmfontListLevel0: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 *Item.fontList: *-*-Helvetica-Bold-R-Normal--*-100-*-*-*-*-ISO8859-1 *XmText.FontList: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 *Text.FontList: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 to: *outlineList*DXmfontListDefault: *-*-*-Medium-R-Normal--*-120-*-*-M-*-*-* *outlineList*DXmfontListLevel0: *-*-*-Medium-R-Normal--*-120-*-*-M-*-*-* *outlineList*DXmfontListLevel1: *-*-*-Medium-R-Normal--*-120-*-*-M-*-*-* *tocList*DXmfontListDefault: *-*-*-*-R-Normal--*-120-*-*-*-*-*-* *tocList*DXmfontListLevel0: *-*-*-*-R-Normal--*-120-*-*-*-*-*-* *Item.fontList: *-*-*-*-R-Normal--*-120-*-*-*-*-*-* *XmText.FontList: *-*-*-Medium-R-Normal--*-120-*-*-*-*-*-* *Text.FontList: *-*-*-Medium-R-Normal--*-120-*-*-*-*-*-* +o Notepad - /_u_s_r/_b_i_n/_X_1_1/_d_x_n_o_t_e_p_a_d To use Lithuanian and/or Slovene national characters in _d_x_n_o_t_e_p_a_d, edit the resource file /_u_s_r/_l_i_b/_X_1_1/_a_p_p-_d_e_f_a_u_l_t_s/_D_X_n_o_t_e_p_a_d and change the following line: *textwindow.fontList: -*-Terminal-Medium-R-Narrow--*-140-*-*-C-*-ISO8859-1 Window System Software Notes 6-21 to: *textwindow.fontList: -*-Terminal-Medium-R-Narrow--*-140-*-*-C-*-*-* +o Bookreader - /_u_s_r/_b_i_n/_X_1_1/_d_x_b_o_o_k In order to use Lithuanian and/or Slovene national characters in Bookreader bookshelf and book names, edit the resource file /_u_s_r/_l_i_b/_X_1_1/_a_p_p- _d_e_f_a_u_l_t_s/_D_X_B_o_o_k_r_e_a_d_e_r and change all occurences of string: -*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1 to: -*-*-*-R-Normal--*-120-*-*-P-*-*-* +o Paint - /_u_s_r/_b_i_n/_X_1_1/_d_x_p_a_i_n_t The _d_x_p_a_i_n_t Lithuanian and Slovene language variants do not support the insertion of Lithuanian and Slovene national specific characters. +o Clock - /_u_s_r/_b_i_n/_X_1_1/_d_x_c_l_o_c_k The _d_x_c_l_o_c_k application displays date and time using english day/month abbreviations and format. +o Calendar - /_u_s_r/_b_i_n/_X_1_1/_d_x_c_a_l_e_n_d_a_r The _d_x_c_a_l_e_n_d_a_r application displays date and time using english day/month abbreviations and format. To create calendar entries using Lithuanian and/or Slovene national specific characters, edit the resource file /_u_s_r/_l_i_b/_X_1_1/_a_p_p-_d_e_f_a_u_l_t_s/_D_X_c_a_l_e_n_d_a_r and change the following two lines: *font_small_tb.fontList: \ -*-Menu-Medium-R-Normal--*-100-*-*-P-*-ISO8859-1 *font_medium_tb.fontList: \ -*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1 to: *font_small_tb.fontList: -*-*-*-R-Normal--*-100-*-*-P-*-*-* *font_medium_tb.fontList: -*-*-*-R-Normal--*-120-*-*-P-*-*-* 6-22 Window System Software Notes _6._6._1_2._4 _D_X _A_p_p_l_i_c_a_t_i_o_n_s _I_n_v_o_k_e_d _f_r_o_m _D_X_s_e_s_s_i_o_n In addition to the new default Common Desktop Environment (CDE), Digital UNIX V4.0 still supports DECwindows interface as an optional user interface. However, if you want to use the old DECwindows user interface you need to log in after selecting Dxsession session from Options --> Session menu of Digital UNIX login screen. _6._6._1_2._5 _L_i_t_h_u_a_n_i_a_n _L_a_n_g_u_a_g_e _V_a_r_i_a_n_t Lithuanian language variant users that wish to operate in Dxsession environment must specify the default user interface font by editing the file ._X_d_e_f_a_u_l_t_s located on their home directory and adding the following line and log in again: *FontList: -*-*-*-r-Normal--*-120-*-*-*-*-*-* If users operate in a multilingual user interface environment, this above corrective action will cause other language variants to display using the default font which is slightly different than to the font family used before this action was performed. Users that wish to have the default user interface font to be used with the Motif window manager need to edit the resource file /_u_s_r/_l_i_b/_X_1_1/_a_p_p-_d_e_f_a_u_l_t_s/_M_w_m and change the following line: Mwm*fontList: -*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1 to: Mwm*fontList: -*-*-*-R-Normal--*-120-*-*-P-*-*-* Note that this change must be performed by a superuser (root). Window System Software Notes 6-23 Documentation Notes 7 This chapter discusses notes that apply to Digital UNIX Version 4.0 documentation. _7._1 _R_e_l_e_a_s_e _N_o_t_e_s The on-line HTML and PostScript versions of the release notes are not complete due to last minute changes. Use only the printed version supplied with the software media. _7._2 _M_e_d_i_a _C_D-_R_O_M_s The Digital UNIX distribution media is comprised of three CD-ROM discs. +o Digital UNIX V4.0 Operating System Volume 1 Contains the following: - Digital UNIX operating system - The _R_e_l_e_a_s_e _N_o_t_e_s and _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e PostScript versions are located in the mnt_point/_D_O_C_U_M_E_N_T_A_T_I_O_N/_P_O_S_T_S_C_R_I_P_T directory. Text versions are located in the mnt_point/_D_O_C_U_M_E_N_T_A_T_I_O_N/_T_E_X_T directory. +o Digital UNIX V4.0 Associated Products Volume 1 Associated software. See the _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for a description. +o Digital UNIX V4.0 Documentation Volume 1 Disc 3 Contains the Digital UNIX Bookreader and HTML files for the Digital UNIX documentation set. It also contains files for worldwide support documents and some documentation for Digital UNIX associated products such as DECevent. HTML files can be viewed with Netscape; see the _D_i_g_i_t_a_l _U_N_I_X _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for more information. _7._3 _G_e_n_e_r_a_l _I_n_f_o_r_m_a_t_i_o_n _A_b_o_u_t _t_h_e _D_o_c_u_m_e_n_t_a_t_i_o_n This section provides general information about changes to the Digital UNIX documentation set. _7._3._1 _N_e_w _M_a_n_u_a_l_s A number of manuals have been added to the documentation set. Refer to the _D_o_c_u_m_e_n_t_a_t_i_o_n _O_v_e_r_v_i_e_w, _G_l_o_s_s_a_r_y _a_n_d _M_a_s_t_e_r _I_n_d_e_x for more information. _7._3._2 _R_e_v_i_s_e_d _D_o_c_u_m_e_n_t_s The title page of each document has an updated operating system revision number if the book has been revised since Version 3.0 All other documents labeled for Version 3.0 or later of the DEC OSF/1 or Digital UNIX operating system are applicable to this release. _7._3._3 _L_i_s_t _o_f _A_v_a_i_l_a_b_l_e _P_a_t_c_h_e_s Lists of patches for known problems are provided on the Digital UNIX Operating System Volume 1 CD-ROM, in the <_m_o_u_n_tpoint>/DOCUMENTATION/TEXT directory. The files are named _D_i_g_i_t_a_l__U_N_I_X__V_3._2_C__C_L_D__F_i_x_e_s._t_x_t, _D_i_g_i_t_a_l__U_N_I_X__V_3._2_D-_1__C_L_D__F_i_x_e_s._t_x_t, and _D_i_g_i_t_a_l__U_N_I_X__V_4._0__C_L_D__F_i_x_e_s._t_x_t. _7._3._4 _C_o_m_p_r_e_s_s_e_d _P_o_s_t_S_c_r_i_p_t _F_i_l_e_s Some PostScript format files on the CD-ROM may be stored in compressed PostScript. This compressed format saves disk storage space and it requires less time to copy the files to other media. To decompress the files, use the _u_n_c_o_m_p_r_e_s_s(1) or _z_c_a_t(1) commands. There is an instruction file on the CD-ROM named as follows: /DOCUMENTATION/POSTSCRIPT/00-READ-ME-FIRST _7._4 _R_e_f_e_r_e_n_c_e _P_a_g_e_s This section provides information about the Digital 7-2 Documentation Notes UNIX Version 4.0 reference pages. _7._4._1 [_X_P_G_4__U_N_I_X] _U_s_e_d _I_n_c_o_r_r_e_c_t_l_y _i_n _S_e_c_t_i_o_n _1 _R_e_f_e_r_e_n_c_e _P_a_g_e_s In this release, reference pages for interfaces and commands that are included in the Single UNIX Specification include tags to differentiate standard and proprietary information. The _s_t_a_n_d_a_r_d_s(5) reference page explains how standard-conformant and proprietary information should be differentiated in reference pages. The [_X_P_G_4__U_N_I_X] tag should appear at the beginning of text paragraphs when the paragraph discusses a UNIX extension added by Issue 4, Version 2 of X/Open CAE specifications. Text should not be flagged when discussing features of a command or function that were included in Issue 4, Version 1 of X/Open CAE specifications. However, in many reference pages for user commands, the [_X_P_G_4__U_N_I_X] tag appears before all descriptions of standard-conformant features rather than only before descriptions of the UNIX extensions. _7._4._2 _w_e_b_m_a_n _U_t_i_l_i_t_y _f_o_r _N_e_t_s_c_a_p_e The Digital UNIX system's documentation CD-ROM includes a tool called _w_e_b_m_a_n, which allows you to view the reference pages with the Netscape Navigator World Wide Web browser. However, because of security restrictions imposed by the browser, it is not possible to view the files by opening them locally on the user's own system. Making the reference pages viewable requires that you set up your system (or one of the systems on your network) as a World Wide Web server by installing and running a server daemon. With a server running, all of the systems on your network can view the reference pages. Server software is available from third-party vendors such as Netscape Communications Corporation. When the documentation CD-ROM is mounted as instructed in the _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e, instructions for installing _w_e_b_m_a_n are in the following file: /usr/share/doclib/online/DOCUMENTATION/HTML/webman/Installing_webman.txt Documentation Notes 7-3 _7._4._3 _M_o_d_e_s _o_f _U_N_I_X _d_o_m_a_i_n _i_n _t_h_e _T_h_e _b_i_n_d() _R_e_f_e_r_e_n_c_e _P_a_g_e The bind() manpage does not discuss the modes of UNIX domain sockets. In previous releases, the mode was always 777. In this release, Digital has introduced a tuneable kernel parameter _i_n_s_e_c_u_r_e__b_i_n_d, which can be set either in the _g_e_n_e_r_i_c stanza of /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b, or can be set using the /_s_b_i_n/_s_y_s_c_o_n_f_i_g utility. The new behavior for _b_i_n_d() is that if _i_n_s_e_c_u_r_e__b_i_n_d has a value of 0 as follows: insecure_bind=0 Then new _A_F__U_N_I_X sockets have the mode set as follows: 0777 &~ umask If _i_n_s_e_c_u_r_e__b_i_n_d is not set to =_0, new _A_F__U_N_I_X sockets have mode _0_7_7_7 The default setting is _i_n_s_e_c_u_r_e__b_i_n_d=_0. _7._4._4 _N_o_n_e_x_i_s_t_a_n_t _A_C_L _I_n_t_e_r_f_a_c_e_s _i_n _t_h_e _a_c_l(_4) _R_e_f_e_r_e_n_c_e _P_a_g_e The following ACL interfaces are mentioned in the acl(4) reference page, but do not exist. Where possible, alternatives are specified: +o _a_c_l__s_e_t__i_d - use _a_c_l__s_e_t__q_u_a_l_i_f_i_e_r +o _a_c_l__s_e_t__n_a_m_e - use _a_c_l__s_e_t__q_u_a_l_i_f_i_e_r +o _a_c_l__s_e_t__p_e_r_m - use _a_c_l__s_e_t__p_e_r_m_s_e_t +o _a_c_l__c_o_n_v_e_r_t__p_o_s_i_x - unsupported, there is no substitute +o _a_c_l__s_e_t__a_c_l__f_d - use _a_c_l__s_e_t__f_d +o _a_c_l__s_e_t__a_c_l__f_i_l_e -use _a_c_l__s_e_t__f_i_l_e +o _a_c_l__v_a_l_i_d_a_t_e__a_n_d__s_o_r_t - sorting is unsupported. For validation use _a_c_l__v_a_l_i_d +o _a_c_l__m_a_k_e__d_e_c - unsupported, there is no substitute See the _a_c_l(4), _a_c_l__s_e_t__q_u_a_l_i_f_i_e_r(3), _a_c_l__s_e_t__p_e_r_m_s_e_t(3), _a_c_l__s_e_t__f_d(3), _a_c_l__s_e_t__f_i_l_e(3), and _a_c_l__v_a_l_i_d(3) reference pages. 7-4 Documentation Notes _7._4._5 _P_r_o_p_e_r_t_y _L_i_s_t _R_e_f_e_r_e_n_c_e _P_a_g_e_s The _s_e_t_p_r_o_p_l_i_s_t(3), _g_e_t_p_r_o_p_l_i_s_t(3), and _d_e_l_p_r_o_p_l_i_s_t(3) reference pages should be corrected as follows. In the EXAMPLES section of the _s_e_t_p_r_o_p_l_i_s_t(3) reference page, the definition for _s_t_r_u_c_t _p_r_o_p_l_i_s_t_n_a_m_e__a_r_g_s is both incorrect (no variable) and unnecessary (only _g_e_t_p_r_o_p_l_i_s_t() and _d_e_l_p_r_o_p_l_i_s_t() use this structure.) In the SYNOPSIS section of the _g_e_t_p_r_o_p_l_i_s_t(3) reference page, the _i_n_t *_b_u_f argument to _g_e_t_p_r_o_p_l_i_s_t() should be _i_n_t *_m_i_n__b_u_f__s_i_z_e. In the EXAMPLES section, the _s_t_r_u_c_t _p_r_o_p_l_i_s_t_n_a_m_e__a_r_g_s; definition should be _s_t_r_u_c_t _p_r_o_p_l_i_s_t_n_a_m_e__a_r_g_s _g_e_t_a_r_g_s. In the EXAMPLES section of the _d_e_l_p_r_o_p_l_i_s_t(3) reference page, the _s_t_r_u_c_t _p_r_o_p_l_i_s_t_n_a_m_e__a_r_g_s definition should be _s_t_r_u_c_t _p_r_o_p_l_i_s_t_n_a_m_e__a_r_g_s _e_n_t_r_y__n_a_m_e_s;. _7._4._6 _m_a_i_l__m_a_n_u_a_l__s_e_t_u_p _R_e_f_e_r_e_n_c_e _P_a_g_e In step 7 of the instructions for setting up _P_O_P, use the command _c_r_e_a_t_e=_2_0 to create a file called /_u_s_r/_s_p_o_o_l/_p_o_p/_P_O_P instead of a directory. _7._4._7 _q_u_o_t_a _a_n_d _v_q_u_o_t_a _S_h_o_w _W_r_o_n_g _U_s_a_g_e _o_f _O_p_t_i_o_n_s The _q_u_o_t_a and _v_q_u_o_t_a reference pages show the wrong usage of options. The correct usage for the _q_u_o_t_a reference page is as follows: _q_u_o_t_a[-_q_v] -_u username ... _q_u_o_t_a[-_q_v] -_g groupname ... The correct usage for the _v_q_u_o_t_a reference page is as follows: _v_q_u_o_t_a[-_g_u_q_v] _v_q_u_o_t_a[-_q_v] -_u username ... _v_q_u_o_t_a[-_q_v-_g groupname ... Documentation Notes 7-5 _7._5 _D_e_v_i_c_e _D_r_i_v_e_r _D_o_c_u_m_e_n_t_a_t_i_o_n The following notes apply to device driver documentation. _7._5._1 _W_r_i_t_i_n_g _V_M_E_b_u_s _D_e_v_i_c_e _D_r_i_v_e_r_s The following notes apply to writing VMEbus Device Drivers. +o Updating Digital UNIX Device Drivers to the Current Version of the Digital UNIX Operating System Although existing VMEbus device drivers are compatible with the current version of Digital UNIX, you should plan on migrating your device drivers to take advantage of the single binary module technology. Refer to Writing Device Drivers: Tutorial for more information on the single binary module technology, and for previous device driver mechanisms that are not being supported in this release, such as the _c_o_n_f_i_g._f_i_l_e, _s_t_a_n_z_a._s_t_a_t_i_c, and _s_t_a_n_z_a._l_o_a_d_a_b_l_e files. The syntax in the _f_i_l_e_s file fragment also has changed to accommodate the single binary module in this release of Digital UNIX. +o Device Driver Configuration VMEbus device drivers written according to guidelines for Digital UNIX V4.0 single binary module technology are supported by the Static configuration method only. The Dynamic configuration method will be supported in a future release of Digital UNIX. +o Defining Bus-Specific Name Constants Device drivers written according to Digital UNIX V4.0 single binary module technology must specify _v_b_a as the bus name when creating a controller structure. Device drivers cannot specify * for a VMEbus device driver. +o VMEbus Configuration Information In previous versions of Digital UNIX, VMEbus configuration information was passed to device drivers through the config.file file fragment. VMEbus csr, csr2, vector, and interrupt request priority level were specified using the configuration keywords - _c_s_r 7-6 Documentation Notes - _c_s_r_2 - _v_e_c_t_o_r - _p_r_i_o_r_i_t_y respectively. This mechanism has changed for Digital UNIX V4.0. As you read the Digital UNIX V4.0 Writing VMEbus Device Drivers book, you should refer to the following description of VBA_Option when the book discusses the configuration keywords _c_s_r, _c_s_r_2, _v_e_c_t_o_r, and _p_r_i_o_r_i_t_y. The book will be updated in a future release of Digital UNIX to reflect these changes. New and existing device drivers need to supply VMEbus configuration information by specifying a _V_B_A__O_p_t_i_o_n entry in /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b. _V_B_A__O_p_t_i_o_n fields have the following definitions and restrictions: _____________________________________________________ Field Definition and Restriction _____________________________________________________ Manufact_Name Specify up to a 31-character manufacturer name for this field. Enclose the name in single quotes ('). Product_Name Specify up to a 31-character product name describing the product that the device driver is supporting. Enclose the name in single quotes ('). Bus_Instance Specify the _v_b_a bus number that this device driver is being installed on. In most cases the _B_u_s__I_n_s_t_a_n_c_e will be specified as zero. If the system consists of multiple VME buses, specify the appropriate bus instance, i.e. 0, 1, 2, etc. The bus numbers are associated with the physical order in which _v_b_a buses are detected. Driver_Name Documentation Notes 7-7 _____________________________________________________ Field Definition and Restriction _____________________________________________________ Specify up to a 15-character device driver name. Enclose the name in single quotes ('). The Driver_Name must match the subsystem name used in the V4.0 single binary module interface _c_r_e_a_t_e__c_o_n_t_r_o_l_l_e_r__s_t_r_u_c_t or the driver name specified in the configuration file fragment in previous versions of Digital UNIX. Driver_Instance Specify the instance of the hardware device for which this device driver is being installed. If this is the first instance specify 0. This value is used to match against the controller number assigned in the V4.0 single binary module when a controller structure is created, or the controller number specified in the configuration file in previous versions of Digital UNIX. The same device driver can be installed multiple times to control different VMEbus device options of the same type. Typically. the only differences are the VMEbus device register addresses, interrupt vector and possibly the interrupt request level. Csr1 Specify a VMEbus device register or memory address to map into CPU I/O space. A nonzero value in this field and the device driver's driver structure elements _a_d_d_r_1__s_i_z_e and _a_d_d_r_1__a_t_y_p_e will cause the autoconfiguration software to map the specified VMEbus address space into system I/O space. The controller structure element _a_d_d_r will receive the resultant _i_o__h_a_n_d_l_e__t address. This value will be passed to the device driver's probe interface. Csr2 7-8 Documentation Notes _____________________________________________________ Field Definition and Restriction _____________________________________________________ Specify an optional VMEbus device register or memory address to map into CPU I/O space. A nonzero value in this field and the device driver's driver structure elements _a_d_d_r_2__s_i_z_e and _a_d_d_r_2__a_t_y_p_e will cause the autoconfiguration software to map the specified VMEbus address space into system I/O space. The controller structure element _a_d_d_r_2 will receive the resultant _i_o__h_a_n_d_l_e__t address. This value is not passed to the device driver's probe interface, but is available in the controller structure. Vector Specify a VMEbus interrupt vector at which interrupts from the device interrupt the processor. This value is passed to the device driver in the _i_v_n_u_m element of the controller structure. The device driver's probe interface uses this value plus the VMEbus interrupt request level obtained in the next entry to add and enable VMEbus interrupt handlers via _h_a_n_d_l_e_r__a_d_d and _h_a_n_d_l_e_r__e_n_a_b_l_e interfaces. Bus_Priority Specify a VMEbus interrupt request level at which the device will present its hardware interrupt request. This value is passed to the device driver in the _b_u_s__p_r_i_o_r_i_t_y element of the controller structure. This interrupt request level and vector specified above is used by device driver's probe interface to add and enable VMEbus interrupt handlers via _h_a_n_d_l_e_r__a_d_d and _h_a_n_d_l_e_r__e_n_a_b_l_e interfaces. Type Specify the character _C for this entry. This indicates the entry is for a controller. Adpt_Config Documentation Notes 7-9 _____________________________________________________ Field Definition and Restriction _____________________________________________________ Specify the character _N. This entry will be used in a subsequent __________________r_e_l_e_a_s_e__o_f__D_i_g_i_t_a_l__U_N_I_X_.____________ The VBA_Option entry below is included in /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b to provide VMEbus configuration information for the _v_b device driver. The _v_b device driver is the Digital UNIX supported VMEbus Backplane Network Driver. VBA_Option = Manufact_Name - 'Digital', Product_Name - 'VME Backplane Network Driver', Bus_Instance - 0, Driver_Name - vb, Driver_Instance - 0, Csr1 - 0, Csr2 - 0, Vector - 0x1150, Bus_Priority - 7, Type - C, Adpt_Config - N VBA_Option information is supplied on a contiguous line with no "newline" characters inserted. The data following the dash (-) is the data for the specified field. The comma (,) separates the fields within _V_B_A__O_p_t_i_o_n. ASCII data fields are enclosed in single quotes ('). The above entry indicates that the manufacturer is Digital and that the product is the VME Backplane Network Driver. The driver name is _v_b and installed on the first instance of _v_b_a as _v_b_a_0. The controller is for the first instance of _v_b as _v_b_0. The device driver requires no device register or memory mapping by the autoconfiguration software. This is indicated by zero being specified for _C_s_r_1 and _C_s_r_2. The interrupt information to the driver indicates that the driver needs to add and enable an interrupt handler to vector 0x1150 with a VMEbus interrupt request level of 7. +o VMEbus Backplane Network Driver, _v_b. The Digital UNIX book Writing VMEbus Device Drivers indicates that the _v_b driver interrupt vector may need to be changed. This depends upon the module switch interrupt being selected. This was done in previous releases of Digital UNIX by specifying the information on the controller line in the system configuration file. This is no longer valid. In order to change the interrupt vector now, the /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b file must be edited and the _V_e_c_t_o_r field of the _V_B_A__O_p_t_i_o_n entry for the _v_b driver must be changed to the 7-10 Documentation Notes appropriate vector. The configuration line in section D.5.5 of Writing VMEbus Device Drivers was previously specified as follows: controller vb0 at vba0 vector vbintr 0x1150 priority 7 The configuration line must now be specified as follows: controller vb0 at vba0 +o Fictitious VMEbus /_d_e_v/_d_m_a_e_x device driver The /_d_e_v/_d_m_a_e_x device driver included in Appendix B of the Digital UNIX V4.0 book Writing VMEbus Device Drivers has not been updated to support the Digital UNIX V4.0 single binary module for Static configuration. The following sections provide an updated version of the /_d_e_v/_d_m_a_e_x device driver that supports the Digital UNIX V4.0 single binary module for Static configuration. The following sections also provides an example files file and _s_y_s_c_o_n_f_i_g_t_a_b fragment for the /_d_e_v/_d_m_a_e_x device driver. Refer to the Digital UNIX V4.0 book Writing Device Drivers: Tutorial for examples, discussions, and interfaces that support the single binary module and differences between Static and Dynamic device driver configurations. - VMEbus /_d_e_v/_d_m_a_e_x _f_i_l_e_s file fragment The following _f_i_l_e_s file fragment assumes the /_d_e_v/_d_m_a_e_x 3rd party device driver kit has been installed at /_u_s_r/_o_p_t/_D_M_1_0_0. MODULE/STATIC/dmaex standard Binary /usr/opt/DM100/dmaex.c module dmaex - VMEbus /_d_e_v/_d_m_a_e_x _s_y_s_c_o_n_f_i_g_t_a_b files file fragment dmaex: Subsystem_Description = DMAEX device driver Module_Config_Name = dmaex Method_Type = Static Module_Type = Static Device_Char_Major = Any Device_Char_Minor = 0 Device_Char_Files = dmaex Device_Major_Req = Same Documentation Notes 7-11 VBA_Option = Manufact_Name - 'Digital', Product_Name - 'DMAEX Driver', Bus_Instance - 0, Driver_Name - dmaex, Driver_Instance - 0, Csr1 - 0x00100000, Csr2 - 0x0, Vector - 0x24, Bus_Priority - 1, Type - C, Adpt_Config - N VBA_Option information is supplied on a contiguous line with no newline characters inserted. Line break characters have been added to the above text for clarity. The data following the dash (-) is the data for the specified field. The comma (,) separates the fields within _V_B_A__O_p_t_i_o_n. ASCII data fields are enclosed in single quotes ('). The above entry indicates that the manufacturer is Digital and that the product is the DMAEX Driver. The driver name is _d_m_a_e_x and installed on the first instance of _v_b_a as _v_b_a_0. The controller is for the first instance of _d_m_a_e_x as _d_m_a_e_x_0. The device driver requires the autoconfiguration software to map eight (8) bytes of VMEbus address at address 0x00100000 in A24 User Data Mode address space into CPU I/O space. This is done by specifying a value in _C_s_r_1 above and specifying values for _a_d_d_r_1__s_i_z_e and _a_d_d_r_1__a_t_y_p_e in the /_d_e_v/_d_m_a_e_x driver structure. The mapped I/O space address, _i_o__h_a_n_d_l_e__t, is passed to _d_m_a_e_x_p_r_o_b_e and stored in the controller structure's _a_d_d_r element. The /_d_e_v/_d_m_a_e_x device driver uses this I/O mapped address to access its device control and status registers. A value of zero (0) was specified for _C_s_r_2 above. Therefore, no VMEbus to CPU I/O space mapping will be performed by the autoconfiguration software for _C_s_r_2. The interrupt information to the driver indicates that the driver needs to add and enable interrupt handlers to vector 0x24 with a VMEbus interrupt request level of 1. The /_d_e_v/_d_m_a_e_x device driver installs two interrupt handlers at 0x24 and 0x25. The vector and bus_priority is passed to the device driver in the controller structure elements _i_v_n_u_m and _b_u_s__p_r_i_o_r_i_t_y. +o VMEbus /_d_e_v/_d_m_a_e_x _d_m_a_e_x_r_e_g._h header file See ~_D_O_C_U_M_E_N_T_A_T_I_O_N/_T_E_X_T/_d_m_a_e_x__s_a_m_p_l_e._t_x_t on the _D_i_g_i_t_a_l _U_N_I_X _V_4._0 _D_o_c_u_m_e_n_t_a_t_i_o_n _V_o_l_u_m_e _1 CD-ROM for an example of a driver. 7-12 Documentation Notes _7._5._2 _D_e_v_i_c_e _D_r_i_v_e_r _T_u_t_o_r_i_a_l Section 14.1.1 of the tutorial states that you should create a directory to contain your driver source in the form of: # _m_k_d_i_r /_u_s_r/_s_y_s/_i_o/_E_S_A_1_0_0 When you create a new directory to replace ESA100 you must place it in the path /_u_s_r/_s_y_s/_i_o/ using your directory selection to replace ESA100. _7._6 _N_e_t_w_o_r_k _A_d_m_i_n_i_s_t_r_a_t_i_o_n _M_a_n_u_a_l The following notes describe changes to the _N_e_t_w_o_r_k _A_d_m_i_n_i_s_t_r_a_t_i_o_n manual. _7._6._1 _C_h_a_n_g_e_s _t_o _S_e_c_t_i_o_n _4._2._2._2, "_V_e_r_i_f_y_i_n_g _P_P_P _S_u_p_p_o_r_t _i_n _t_h_e _K_e_r_n_e_l" To verify that PPP is supported in the kernel, enter the following command: # _s_y_s_c_o_n_f_i_g -_s | _g_r_e_p _p_p_p If it is not loaded and configured, do the following: 1. Log in as root. 2. Save the /_v_m_u_n_i_x file. 3. Rebuild the kernel by running the _d_o_c_o_n_f_i_g program and selecting the Point-to-Point (PPP) option. 4. Copy the new _v_m_u_n_i_x file to /_v_m_u_n_i_x. 5. Edit the /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b file and add the following lines: ppp: nppp=2 This provides for 2 PPP connections. If your system requires a greater number of PPP connections, increase the number. 6. Reboot the system. Documentation Notes 7-13 _7._6._2 _S_e_c_t_i_o_n_s _4._2._3._1, _4._2._3._2, _a_n_d _4._2._3._3 _a_r_e _o_b_s_o_l_e_t_e Use the instructions n the following sections instead. _7._6._2._1 _E_s_t_a_b_l_i_s_h_i_n_g _a _P_P_P _D_i_a_l-_O_u_t _C_o_n_n_e_c_t_i_o_n After you have connected your modem to a serial port on your system, do the following: 1. Verify that you can communicate with the modem. Do the following: a. Edit the /_e_t_c/_r_e_m_o_t_e file and copy the _k_d_e_b_u_g entry. b. Modify the new entry, providing a system name for the entry, the correct Digital UNIX device (_t_t_y_0_0 or _t_t_y_0_1 depending on your system), the correct baud rate, and correct parity. See _r_e_m_o_t_e(4) for more information. c. Use the _t_i_p command to access the modem as follows: % _t_i_p _s_y_s_t_e_m__n_a_m_e system_name is the system name from the /_e_t_c/_r_e_m_o_t_e file. d. If your modem is using the AT command language, enter the following command: AT If the modem is not in quiet mode, it responds with an _O_K message. 2. Contact the remote system administrator or your Internet Service Provider (ISP) and obtain the following information: - Your remote IP address and netmask, unless the remote system assigns the IP address dynamically - Characters that might need to be escaped - Instructions on how to log in and use the remote service This information is used to create a chat script, which automates the dial-out process. 7-14 Documentation Notes 3. Create a file for commands that the _c_h_a_t program uses to direct the modem what number to dial and what to send the remote system in order to start _p_p_p_d. This file is called a cccchhhhaaaatttt ssssccccrrrriiiipppptttt. Each entry in a chat script has the following format: string_chat_expects string_chat_sends For example, the following file named /_e_t_c/_p_p_p/_c_h_a_t-_s_c_r_i_p_t contains the following information: "" atdt2135476 [1] CONNECT "" [2] login: myname [3] Password: "\qmypassword" [4] "$ " "\qpppd" [5] [1]_c_h_a_t expects nothing and sends a dial command to the modem. [2]_c_h_a_t expects a _C_O_N_N_E_C_T message and sends a carriage return (implied). [3]_c_h_a_t expects the _l_o_g_i_n: string and sends the _m_y_n_a_m_e string. [4]_c_h_a_t expects the _P_a_s_s_w_o_r_d: string and sends the _m_y_p_a_s_s_w_o_r_d string. The _e_q prevents _c_h_a_t from logging it when you use the -_v option. [5]_c_h_a_t expects the $ (the shell prompt) and sends _p_p_p_d to start the _p_p_p_d daemon on the remote machine. The _e_q cancels the effect of the previous _e_q. See _c_h_a_t(8) for more information on _c_h_a_t and chat scripts. _N_o_t_e You might want to use the _t_i_p command to dial out and log in to the remote system and to write down the exact prompt, login sequence, and _p_p_p_d start-up sequence. 4. Edit the /_e_t_c/_p_p_p/_o_p_t_i_o_n_s file and include the following _p_p_p_d options as required by the remote Documentation Notes 7-15 system or ISP: defaultroute [1] asyncmap 0 [2] mru 296 [3] netmask dd.dd.dd.dd [4] lcp-echo-interval 60 [5] lcp-echo-failure 5 [6] noipdefault [7] crtscts [8] debug [9] [1]If you system is standalone and you are connecting to the Internet through the remote system, add a default route via the remote host by specifying this option. [2]If the serial line is not completely 8-bit transparent, specify this option; _a_s_y_n_c_m_a_p _2_0_0_a_0_0_0_0 is appropriate if the serial link includes a _t_e_l_n_e_t link. [3]Reduces the MRU (maximum receive unit) on the local and remote systems to improve performance for multiple IP connection. [4]Sets the interface netmask to the specified value. Your ISP should provide this information. [5]Sends an Link Control Protocol (LCP) echo request frame to the remote system every 60 seconds. This determines whether the link to the remote system is still active. [6]If the local system does not receive a response from the remote system after 5 LCP echo request frames, _p_p_p_d considers the link dead and tears down the connection. [7]Specifies that the remote system (ISP) is to provide the local system an IP address, unless an IP address is specified explicitly on the command line or in an options file. [8]Enables hardware flow control on the serial device. If the modem does not support hardware flow control, do not add this entry. See your modem documentation to verify this information. [9]Enables debugging. All log messages are sent to the file specified in the /_e_t_c/_s_y_s_l_o_g._c_o_n_f file. After your connection is working 7-16 Documentation Notes correctly, remove this entry from the PPP options file. See _p_p_p_d(8) for a complete list of _p_p_p_d options. 5. Edit the /_e_t_c/_s_y_s_l_o_g._c_o_n_f file and do the following: a. Add the _l_o_c_a_l_2 facility (used by _p_p_p_d and _c_h_a_t) to the line that specifies /_d_e_v/_c_o_n_s_o_l_e as the message destination as follows: kern.debug;local2.notice /dev/console In this example, the _n_o_t_i_c_e level is specified. b. Add the following entry to the file to create a _p_p_p-_l_o_g file: local2.debug /etc/ppp/ppp-log c. Save the edits and close the file. 6. Stop and restart _s_y_s_l_o_g_d by entering the following commands: # /_s_b_i_n/_i_n_i_t._d/_s_y_s_l_o_g _s_t_o_p # /_s_b_i_n/_i_n_i_t._d/_s_y_s_l_o_g _s_t_a_r_t 7. Invoke _p_p_p_d on the local system to connect to the remote system. For example, the following command starts a link on _t_t_y_0_1 and specifies the _c_o_n_n_e_c_t option to run the _c_h_a_t program using the specified chat script file. % _p_p_p_d /_d_e_v/_t_t_y_0_1 _3_8_4_0_0 _c_o_n_n_e_c_t '_c_h_a_t -_v -_f /_e_t_c/_p_p_p/_c_h_a_t-_s_c_r_i_p_t' 8. Issue the following command to monitor the _p_p_p-_l_o_g file and to determine whether the PPP connection is active: % _t_a_i_l -_f /_e_t_c/_p_p_p/_p_p_p-_l_o_g If any problems occur while using PPP, see Chapter 13 in _N_e_t_w_o_r_k _A_d_m_i_n_i_s_t_r_a_t_i_o_n. Documentation Notes 7-17 _7._6._2._2 _E_s_t_a_b_l_i_s_h_i_n_g _a _P_P_P _D_i_a_l-_I_n _C_o_n_n_e_c_t_i_o_n After you have connected your modem to a serial port on your system, to configure a dial-in system, complete the following steps: 1. Set up your modem for dial-in access. See Section 4.3.2 in _N_e_t_w_o_r_k _A_d_m_i_n_i_s_t_r_a_t_i_o_n for more information. 2. Edit the /_e_t_c/_p_a_s_s_w_d file and create a dedicated entry for a PPP user. For the login shell field, specify /_u_s_r/_s_b_i_n/_s_t_a_r_t_p_p_p; for example: ppp1:password:_1_0:_2_0:_R_e_m_o_t_e _P_P_P _U_s_e_r:/_u_s_r/_u_s_e_r_s/_g_u_e_s_t:/_u_s_r/_s_b_i_n/_s_t_a_r_t_p_p_p 3. Edit the /_e_t_c/_i_n_i_t_t_a_b file and create an entry for each terminal device that is to run PPP. For example: modem:3:respawn:/usr/sbin/getty /dev/tty00 M38400 vt100 See _i_n_i_t_t_a_b(4) for more information. 4. Issue the _i_n_i_t _q command to start the _g_e_t_t_y process immediately. 5. If the dial-in system is going to be a gateway for the dial-out system to reach other systems on the LAN, the dial-in system must be configured as IP router and must also run _g_a_t_e_d. Edit the /_e_t_c/_g_a_t_e_d._c_o_n_f file and delete the _n_o_b_r_o_a_d_c_a_s_t option (if specified) in the _r_i_p statement. See Chapter 2 of _N_e_t_w_o_r_k _A_d_m_i_n_i_s_t_r_a_t_i_o_n for basic network setup information and _g_a_t_e_d._c_o_n_f(4) for _g_a_t_e_d options. 6. Edit the /_e_t_c/_p_p_p/_o_p_t_i_o_n_s file and include the following _p_p_p_d options required to support dial-in access for all remote users: netmask dd.dd.dd.dd [_1] _p_r_o_x_y_a_r_p [_2] _c_r_t_s_c_t_s [_3] _a_s_y_n_c_m_a_p _0 [_4] :_r_e_m_o_t_e__i_p__a_d_d_r_e_s_s [5] debug [6] [1]Sets the interface netmask to the specified value. 7-18 Documentation Notes [2]Adds an entry to the local system's Address Resolution Protocol (ARP) table containing the IP address of the remote system and the Ethernet address of the local system. This is not necessary if _g_a_t_e_d is running. [3]Enables hardware flow control for the serial port. [4]If the serial line is not completely 8-bit transparent, specify this option; _a_s_y_n_c_m_a_p _2_0_0_a_0_0_0_0 is appropriate if the serial link includes a _t_e_l_n_e_t link. [5]Specifies an IP address for the remote system. If you want to specify options for each individual serial port, create a /_e_t_c/_p_p_p/_o_p_t_i_o_n_s._t_t_yxx file and include the remote IP address and any other options that apply to that specific serial port. See _p_p_p_d(8) for a complete list of _p_p_p_d options. 7. After an incoming call is received and a connection established, _s_t_a_r_t_p_p_p runs in the background. The process ID is logged in the /_e_t_c/_p_p_p/_p_p_pxx._p_i_d file. 8. Enables debugging. All log messages are sent to the file specified in the /_e_t_c/_s_y_s_l_o_g._c_o_n_f file. After your connection is working correctly, remove this entry from the PPP options file. If any problems occur while using PPP, see Chapter 13 in _N_e_t_w_o_r_k _A_d_m_i_n_i_s_t_r_a_t_i_o_n. _7._7 _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n _M_a_n_u_a_l _I_n_s_t_r_u_c_t_i_o_n_s _f_o_r _S_y_s_M_a_n _A_p_p_l_i_c_a_t_i_o_n_s The _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n omits the following information on starting SysMan applications. _7._7._1 _A_c_c_e_s_s_i_n_g _t_h_e _S_y_s_M_a_n _T_o_o_l_s In this release of Digital UNIX, the Common Desktop Environment (CDE) is the default desktop. The SysMan suite of graphical system management applications is the preferred interface for system administration. The SysMan applications are also available in the DECwindows and base X Windows graphical environments. In CDE, the SysMan applications are available in the Application Manager. You can access the Application Documentation Notes 7-19 Manager from the CDE Front Panel by clicking on its icon. The SysMan applications are organized into five groups within the System_Admin group. You can double click on the System_Admin group to access the SysMan Configuration Checklist, the Welcome to SysMan online help volume, and the five application groups. You can access online help for the SysMan applications without running the applications. Click on the Help Manager icon on the CDE Front Panel to display the online help browser. The browser includes help families for CDE, the CDE Desktop, and Digital System Management. In DECwindows, the SysMan applications are listed in the Session Manager's Options menu. You can use the Applications Definitions menu item to add SysMan applications that are used frequently to the Applications menu. In other X Windows environments, the SysMan applications can be invoked from the command line. See the _s_y_s_m_a_n__i_n_t_r_o(8X) reference page for a list of the SysMan applications. This reference page also describes how to display the online help browser in graphical environments other than CDE. To support nongraphical environments, some of the SysMan applications offer command line and question and answer interfaces. The following applications have a command line interface. A single command starts the application, which then performs the actions specified by the command line arguments. +o Network Configuration +o BIND Configuration +o NFS Configuration +o Mail Configuration +o Account Manager The following applications have a question and answer interface invoked using the following command-line argument: -_u_i _m_e_n_u. The application prompts the user interactively. +o Network Configuration +o BIND Configuration 7-20 Documentation Notes +o NFS Configuration +o Printer Configuration The menu interface for Mail Configuration is called _m_a_i_l_s_e_t_u_p. Finally, there are a variety of scripts invoked by commands such as SysMan Configuration Checklist and /_u_s_r/_s_b_i_n/_s_e_t_u_p. They are documented in other sections of the System Administration guide. _7._8 _T_e_c_h_n_i_c_a_l _O_v_e_r_v_i_e_w Note that the information on Maximum System Limits has moved from the _T_e_c_h_n_i_c_a_l _O_v_e_r_v_i_e_w to the _R_e_l_e_a_s_e _N_o_t_e_s. _7._9 _A_s_s_e_m_b_l_y _L_a_n_g_u_a_g_e _P_r_o_g_r_a_m_m_e_r'_s _G_u_i_d_e The Assembly Language Programmer's Guide (Chapter 5) should include a description of the ._r_c_o_n_s_t directive. This derective instructs the assembler to add subsequent data into the ._r_c_o_n_s_t section. This behavior is similar to the ._r_d_a_t_a directive, except that the entries cannot be relocatable. _7._1_0 _D_E_C _C _L_a_n_g_u_a_g_e _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l In the _D_E_C _C _L_a_n_g_u_a_g_e _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l, the conventions table states that the DEC C extensions to the ANSI C standard are shown in teal in the printed manual, and are shaded in the online manual. This is incorrect. _7._1_1 _G_u_i_d_e _t_o _P_r_e_p_a_r_i_n_g _P_r_o_d_u_c_t _K_i_t_s The following notes apply to the _G_u_i_d_e _t_o _P_r_e_p_a_r_i_n_g _P_r_o_d_u_c_t _K_i_t_s. manual. _7._1_1._1 _G_u_i_d_e _t_o _P_r_e_p_a_r_i_n_g _P_r_o_d_u_c_t _K_i_t_s _i_s _n_o_w _a_v_a_i_l_a_b_l_e _o_n _C_D-_R_O_M The _G_u_i_d_e _t_o _P_r_e_p_a_r_i_n_g _P_r_o_d_u_c_t _K_i_t_s is a new manual that describes the procedures for creating, managing, and installing layered product kits. You can view this guide on line with the Netscape browser. The book is part of the Supplementary Documentation bookshelf. Documentation Notes 7-21 A compressed PostScript version of the book is also available for printing. You can find it on the documentation CD-ROM in the following location: /usr/share/doclib/online/DOCUMENTATION/POSTSCRIPT/AA-QTLVA-TE.ps.Z If you cannot find the file at this location, contact your system administrator. The file named _0_0-_R_E_A_D-_M_E-_F_I_R_S_T in the _P_O_S_T_S_C_R_I_P_T directory describes how to view and print compressed files. It also lists the other PostScript files in the directory. _7._1_1._2 _D_e_s_c_r_i_p_t_i_o_n _o_f _s_e_t_l_d The following information used to be in _P_r_o_g_r_a_m_m_i_n_g _S_u_p_p_o_r_t _T_o_o_l_s, and was left out of the _G_u_i_d_e _t_o _P_r_e_p_a_r_i_n_g _P_r_o_d_u_c_t _K_i_t_s. _7._1_1._2._1 _s_e_t_l_d _F_u_n_c_t_i_o_n_s This release note describes the steps the _s_e_t_l_d utility performs when executed with each of its options. _N_o_t_e The _s_e_t_l_d command's action is divided into phases. Some phases have _P_R_E_phase and _P_O_S_T_phase subphases. If a given subset's _P_R_E_phase subphase fails during any applicable operation, _s_e_t_l_d displays a message indicating that the subset control program has declined the operation and does not proceed further with that subset. No attempt is made to run the phase or _P_O_S_T_phase code. _7._1_1._2._2 _L_o_a_d_i_n_g _S_o_f_t_w_a_r_e When you load software by using the -_l option to _s_e_t_l_d, the utility performs the following steps: 1. Verifies access to location. 2. Copies product installation information from location into a temporary area. The information copied is in the _I_N_S_T_C_T_R_L file for each product kit to be installed. If the _s_e_t_l_d command line 7-22 Documentation Notes included specific subset identifiers, only those subsets are considered; otherwise, all subsets in location are considered. 3. Determines which subsets to load by calling each subset's subset control program with the _A_C_T environment variable set to _M. Subsets whose subset control programs determine that their respective subsets are candidates for installation are divided into mandatory and optional groups according to the subset control flags contained in the subset-id._c_t_r_l files. 4. Displays a list of the candidate subsets, listing the mandatory subsets (if any) and offering the optional subsets in a menu for selection by the user. If there are no optional subsets, no menu is displayed; instead, the mandatory subsets are listed and the user is asked for permission to proceed. 5. Performs the following operations for each subset to be installed: a. Verifies that the subset will fit on the system. b. Invokes the subset's subset control program to perform product-specific tasks that must be done before the subset is loaded (_A_C_T set to _P_R_E__L). A nonzero return status from the subset control program causes _s_e_t_l_d to abort the load operation. c. Creates a subset corrupt lock file. d. Loads the subset, using the subset's control and inventory files; then verifies the subset and upgrades the lock file to indicate that the subset is correctly installed. 6. Performs the following steps for each subset after loading all of the selected subsets: a. Invokes the subset's subset control program to perform product-specific tasks that must be done after the subset is loaded (_A_C_T set to _P_O_S_T__L). The subset control program's actions at this time usually include dependency locking. b. Invokes the subset control program to perform product-specific tasks that must be done after the subset is installed (_A_C_T set to _C and $_1 Documentation Notes 7-23 set to _I_N_S_T_A_L_L). This step is bypassed if the -_D command option was invoked. The installation control files (subset-id._c_t_r_l, subset-id._i_n_v, subset-id._s_c_p, and subset-id._l_k or subset-id._d_w) are stored in the &./_u_s_r/._s_m_d_b. directory. The kit's subset archives are not stored because their contents have been placed in the appropriate locations. If you specified an alternative root path, this directory path is created under the directory you specify. _7._1_1._2._3 _C_o_n_f_i_g_u_r_i_n_g _a _S_u_b_s_e_t When you load a product, the next-to-last stage of the _s_e_t_l_d process is to invoke the subset's subset control program with the _A_C_T environment variable set to _C and the command argument ($1) _s_e_t _t_o _I_N_S_T_A_L_L. When you issue a command to reconfigure a subset (the -_c option), _s_e_t_l_d first verifies that the specified subset exists. If it does, _s_e_t_l_d sets the _A_C_T environment variable to _C and calls the subset's subset control program with message as a command argument ($1). Usually, the only valid messages are _I_N_S_T_A_L_L and _D_E_L_E_T_E. These two messages are reserved in their meaning. For special needs, a particular subset control program could be designed to accept other messages. The _s_e_t_l_d utility cannot pass other messages except in response to its -_c option. _7._1_1._2._4 _V_e_r_i_f_y_i_n_g _a _S_u_b_s_e_t When you load a product, the final stage of the _s_e_t_l_d process is to invoke the subset's subset control program with the _A_C_T environment variable set to _V. This action instructs the subset control program to run its verification test. When you issue a command to verify a subset (the -_v option), _s_e_t_l_d first verifies that the specified subset exists. If it does, _s_e_t_l_d runs the subset's Installation Verification Procedure (IVP), if there is one. _7._1_1._2._5 _R_e_m_o_v_i_n_g _S_o_f_t_w_a_r_e When you issue a _s_e_t_l_d -_d command, the _s_e_t_l_d utility performs the following steps for each subset to be deleted: 7-24 Documentation Notes 1. Verifies that the subset is installed. 2. Verifies that the subset's sticky bit, originally specified in the product's key file, is not set. If the sticky bit is set, _s_e_t_l_d declines to remove the subset. 3. Checks dependencies. If the subset's lock file (subset-id._l_k) names any subsets that depend on the one to be removed, _s_e_t_l_d displays their names and requests confirmation that the subset should be deleted. 4. Invokes the subset's subset control program to perform product-specific tasks that must be done before any deletions are made. (_A_C_T set to _C and $_1 set to _D_E_L_E_T_E.) 5. Invokes the subset's subset control program to perform product-specific tasks that must be done before the subset is deleted. (_A_C_T set to _P_R_E__D.) If the subset control program returns nonzero status, _s_e_t_l_d aborts the deletion operation. 6. Deletes all files contained in the subset. 7. Invokes the subset's subset control program to perform product-specific tasks that must be done after the subset is deleted. (_A_C_T set to _P_O_S_T__D.) 8. Marks the subset as being uninstalled by deleting its lock file. _7._1_2 _O_n_l_i_n_e _H_e_l_p _V_o_l_u_m_e_s. The notes in this section refer to problems with the online help volumes. The Help viewer has the following known problem: +o In some cases, the help viewer is not correctly initialized. As a result, it will sometimes exhibit the expected behavior the second time an action is taken, but not the first time. For example, the first time a quick help dialog box displays a reference page, the Backtrack button may be enabled even though there is no place to which to backtrack. If the dialog box is closed and then opened again, the Backtrack button is dimmed. Documentation Notes 7-25 +o Similarly, if a request for on-item help displays the correct help, but one line has scrolled off the top, the online help will typically be displayed in exactly the right position when the on-item help request is repeated. For each of the SysMan applications online help is available from the Help menu or from the Help button in the main window. The online help contains: +o An overview of the capabilities of the application +o A set of tasks illustrating typical uses of the application +o A reference section documenting every window and dialog box in the application. The Using Help item on the Help menu displays a help volume supplied by CDE that explains how to use the online help. _7._1_2._1 _G_e_n_e_r_a_l _P_r_o_b_l_e_m_s The following known problems occur in the online help: +o The Appearance menu is not consistently documented. In the Archiver, License Manager, and System Information applications, there is an Appearance item on one of the menus. The item should offer three options: Text Only, Large Icon, and Small Icon. In some help volumes, not all of these are documented. +o Some links from one help volume to another are displayed in a new view. There are a few links from one help volume to another that display in a new help viewer window. In some situations, a distracting proliferation of help viewer windows can result. You can get a new view when you want one using the New Window item on the File menu in the help viewer. 7-26 Documentation Notes _7._1_2._2 _I_n_t_e_g_r_a_t_i_o_n The SyMman configuration applications on-item help does not work on the items in the menu bar. In all the SysMan applications, the keyboard method of getting on-item help does not work on the Help menu. _7._1_2._3 _H_e_l_p _V_o_l_u_m_e_s _b_y _A_p_p_l_i_c_a_t_i_o_n The following problems apply only to help in specific applications: +o Kernel Tuner The Kernel Tuner application records its changes immediately, so if a system failure occurs while the Kernel Tuner is running, any boot time changes will take effect the next time the system boots. If the file /_e_t_c/_s_y_s_c_o_n_f_i_g_t_a_b contains invalid values, you can enter the following command at the boot prompt to boot using default values: boot -fl c +o Display Window The help volume for Display Window has opening instructions that show how to access the application from the CDE Application Manager. These should show that the Display Window icon appears in two groups. +o Network Configuration The names of the _g_a_t_e_d, _j_o_i_n_d, _r_o_u_t_e_d, and _r_w_h_o_d daemons are misspelled in the online help volume. In the Configuring Interfaces dialog box, the fields under To Obtain IP Address are relevant for all interfaces. +o Printer Configuration In the Local Printer Settings dialog box and the Remote Printer Settings dialog box, the aliases in the Printer Aliases field must be separated by vertical bars because spaces are allowed in an alias. +o Shutdown The /_u_s_r/_s_b_i_n/_s_h_u_t_d_o_w_n command now sends the Shutdown Message each time a reminder is sent of Documentation Notes 7-27 the time remaining before the system is shut down. The /_e_t_c/_n_o_l_o_g_i_n file is not created until immediately before the shutdown occurs. System shutdown messages are sent to all users that are locally or remotely logged-into the system being shutdown. Additionally, if the Broadcast to NFS Clients" option is selected, shutdown messages are broadcast to all hosts that are NFS clients of the system being shutdown. +o Disk Configuration The following corrected definitions replace the definitions in the glossary for Disk Configuration. - Skew A deviation from a reference direction, either by design or in response to lateral forces. - Track skew On a disk, the sector skew per track. The skew is the angle that sector 0 of the track changes from an imaginary radius line, due to a nonuniform number of sectors per track. +o BIND Configuration The following corrected definitions replace the definitions in the glossary for BIND Configuration: - BIND client A system that queries a BIND server for host name and address information, interprets the responses, and passes the information to requesting applications. - BIND server An authoritative source for information about one or more zones. It either maintains the master copy of the hosts database for the zone or obtains the information required to serve the hosts database from another server. - DCE Distributed Computing Environment. The capabilities of DCE are defined by the Open Software Foundation (OSF). - DCE cell 7-28 Documentation Notes A logical group of systems that share services offered by DCE. - DCE server The server in a DCE cell. - service type In BIND Configuration, the available service types are BIND client and BIND server. The service type determines whether a system is configured to be a BIND client or a BIND server. _7._1_3 _O_n_l_i_n_e _P_o_s_t_S_c_r_i_p_t _F_o_r_m_a_t _D_o_c_u_m_e_n_t_a_t_i_o_n The Digital UNIX documentation set includes documents that are available only in PostScript format. The following list describes these documents and their locations: +o Digital UNIX Software Product Description The Software Product Description (SPD) is a legal description of the Digital UNIX product. It describes the software and gives information about its capabilities and about the hardware it supports. This information is intended for anyone who needs a legal description of the Digital UNIX product. The SPD is provided on the operating system distribution media in both PostScript and text versions. To obtain a copy of the PostScript version, mount the Digital UNIX V4.0 Operating System, Volume 1 CD-ROM. Then change to the mnt_point/_D_O_C_U_M_E_N_T_A_T_I_O_N/_P_O_S_T_S_C_R_I_P_T directory and print the following files: Digital_UNIX_Developers_Toolkit_SPD.ps Digital_UNIX_Logical_Storage_Manager_SPD.ps Digital_UNIX_Operating_System_SPD.ps Digital_UNIX_Server_Extensions_SPD.ps Prestoserve_for_Digital_UNIX_SPD.ps To obtain a copy of the text version, change to the mnt_point/_D_O_C_U_M_E_N_T_A_T_I_O_N/_T_E_X_T directory and print the following files: Digital_UNIX_C_Developers_Extensions_SPD.txt Digital_UNIX_Logical_Storage_Manager_SPD.txt Digital_UNIX_Operating_System_SPD.txt Digital_UNIX_Server_Extensions_SPD.txt Documentation Notes 7-29 Prestoserve_for_Digital_UNIX_SPD.txt +o _G_N_U _E_m_a_c_s _M_a_n_u_a_l This manual (developed by the Free Software Foundation) provides information about how to use and customize the Emacs text editor. It is primarily a reference manual, but can also be used as a tutorial. This manual is intended for general users and anyone who uses Emacs. You can obtain a copy of this manual by printing the following file: /_u_s_r/_l_i_b/_e_m_a_c_s/_d_o_c/_e_m_a_c_s._p_s This file is available only if the _F_S_F_E_M_A_C_S_S_R_C_3_0_0 subset is installed on your system. (To use Emacs, install the _O_S_F_E_M_A_C_S_3_0_0 subset.) +o _G_N_U _E_m_a_c_s _L_i_s_p _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l This manual (developed by the Free Software Foundation) describes Emacs Lisp and presumes considerable familiarity with how to use the Emacs text editor. The earlier chapters describe Emacs features that have counterparts in many other programming languages. The later chapters describe features that are peculiar to Emacs Lisp or relate specifically to editing. This manual is for programmers. You can obtain a copy of this manual by printing the following file: /_u_s_r/_l_i_b/_e_m_a_c_s/_d_o_c/_e_l_i_s_p._p_s This file is available only if the _F_S_F_E_M_A_C_S_S_R_C_3_0_0 subset is installed on your system. (To use Emacs Lisp, install the _O_S_F_E_M_A_C_S_3_0_0 subset.) +o Display PostScript Documentation Supplements The Display PostScript system is described in the manual _P_o_s_t_S_c_r_i_p_t _L_a_n_g_u_a_g_e _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l which is available in printed format from Digital. To update the Display PostScript documentation, Adobe System, Inc. provides a number of supplements describing new and changed features of the Display PostScript system. The Display PostScript documentation supplements are provided in compressed format in the following directory: /_u_s_r/_s_h_a_r_e/_d_o_c_l_i_b/_d_p_s Before you can print a copy of one of the supplements, you must uncompress that supplement. 7-30 Documentation Notes For example, to uncompress the _L_e_v_e_l _2 _C_h_a_n_g_e_s _f_o_r _X, issue the following command: % _u_n_c_o_m_p_r_e_s_s /_u_s_r/_s_h_a_r_e/_d_o_c_l_i_b/_d_p_s/\ _D_e_v_e_l_o_p_e_r-_T_e_c_h_N_o_t_e._1-_0_0_1._p_s._Z You can then print the resulting, uncompressed file: /_u_s_r/_s_h_a_r_e/_d_o_c_l_i_b/_d_p_s/\ _D_e_v_e_l_o_p_e_r-_T_e_c_h_N_o_t_e._1-_0_0_1._p_s You might want to remove the PostScript file once you have printed it to save space on your system. The following list describes the Display PostScript documentation supplements: - _L_e_v_e_l _2 _C_h_a_n_g_e_s _f_o_r _X This supplement describes the changes made to the X implementations of the Display PostScript system for PostScript Level 2. This supplement is provided in the following file: _D_e_v_e_l_o_p_e_r-_T_e_c_h_N_o_t_e._1-_0_0_1._p_s._Z - _T_y_p_e _2 _I_m_a_g_e _D_i_c_t_i_o_n_a_r_y This supplement describes the Type 2 image dictionary, an operand for the _i_m_a_g_e operator in the Display PostScript system. The Type 2 image dictionary is an extension to the Type 1 dictionary. It allows the _i_m_a_g_e operator to use pixel data from a pixmap, the current window, or another window as source when copying into the current window. This supplement is provided in the following file: _D_e_v_e_l_o_p_e_r-_T_e_c_h_N_o_t_e._1-_0_0_2._p_s._Z - _M_u_l_t_i_p_l_e _M_a_s_t_e_r _F_o_n_t_s _i_n _t_h_e _D_P_S _T_o_o_l_k_i_t _F_o_n_t _P_a_n_e_l This supplement describes new support for multiple master fonts in the Display PostScript Toolkit for X font panel. The supplement also describes how the font panel supports nontypographic sorting and a value-changed callback. This supplement is provided in the following file: _D_e_v_e_l_o_p_e_r-_T_e_c_h_N_o_t_e._1-_0_0_3._p_s. - _W_r_i_t_i_n_g _A_p_p_l_i_c_a_t_i_o_n_s _T_h_a_t _U_s_e _t_h_e _R_e_s_o_u_r_c_e _L_o_c_a_t_i_o_n _L_i_b_r_a_r_y This supplement describes how applications can use resource paths to become easier to use and Documentation Notes 7-31 customize. Resource paths are included in calls to the resource location library, which applications can use to find resources such as fonts. This supplement is provided in the following file: _D_e_v_e_l_o_p_e_r-_T_e_c_h_N_o_t_e._1-_0_0_4._p_s. - _P_o_s_t_S_c_r_i_p_t(_t_m) _L_a_n_g_u_a_g_e _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l _S_u_p_p_l_e_m_e_n_t The version 2015 supplement to the _P_o_s_t_S_c_r_i_p_t(_t_m) _L_a_n_g_u_a_g_e _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l which contains all updates that manual (232pp). _2_0_1_5_s_u_p_p_l_e_m_e_n_t._p_s._Z. - _A_d_o_b_e _S_h_o_w_P_S _Q_u_i_c_k _R_e_f_e_r_e_n_c_e (_C_a_r_d) This Quick Reference card describes the command syntax and lists the available X resources, command options and keyboard commands. _S_h_o_w_P_S_R_e_f_e_r_e_n_c_e_C_a_r_d._p_s - _A_d_o_b_e _S_h_o_w_P_S _U_s_e_r _G_u_i_d_e General instructions for installing, starting and using the Adobe ShowPS PostScript previewer. Contains tutorial material and a troubleshooting guide (72pp). _S_h_o_w_P_S_U_s_e_r_G_u_i_d_e._p_s._Z. - _A_d_o_b_e _S_h_o_w_P_S _B_r_o_c_h_u_r_e A sample brochure in overhead format that gives an overview of the Adobe ShowPS PostScript previewer (5pp). _S_h_o_w_P_S__B_r_o_c_h_u_r_e._p_s._Z. +o X Image Exension documentation The X Image Extension (XIE) code (developed by the X Consortium) provides a powerful mechanism for the transfer and display of virtually any image on X-capable hardware. Documentation for XIE is provided in compressed format in the following directory: /_u_s_r/_s_h_a_r_e/_d_o_c_l_i_b/_x_i_e Before you can print a copy of one of the XIE manuals, you must uncompress that manual. For example, to uncompress the _X _I_m_a_g_e _E_x_t_e_n_s_i_o_n 7-32 Documentation Notes _O_v_e_r_v_i_e_w, issue the following command: % _g_z_i_p -_d /_u_s_r/_s_h_a_r_e/_d_o_c_l_i_b/_x_i_e/_x_i_e__o_v_e_r_v_i_e_w._p_s._Z You can then print the resulting, uncompressed file: /_u_s_r/_s_h_a_r_e/_d_o_c_l_i_b/_x_i_e/_x_i_e__o_v_e_r_v_i_e_w._p_s. You might want to remove the PostScript file once you have printed it to save space on your system. The following list describes the manuals that describe the XIE code. A README file is also available in /_u_s_r/_s_h_a_r_e/_d_o_c_l_i_b/_x_i_e. - _X _I_m_a_g_e _E_x_t_e_n_s_i_o_n _O_v_e_r_v_i_e_w This manual provides general information about the X Image Extension (XIE) code. Topics covered include: XIE design goals, XIE historical summary, XIE architecture, element definitions, and subsetting. This manual is provided in the following file: /_u_s_r/_s_h_a_r_e/_d_o_c_l_i_b/_x_i_e/_o_v_e_r_v_i_e_w._p_s._g_z - _X_I_E_l_i_b _S_p_e_c_i_f_i_c_a_t_i_o_n This manual contains reference information about the XIElib functions, XIElib events, and XIElib errors. The Functions section covers the following types of functions: startup, LUT, photomap, ROI, photoflo, client data, abort and await, photoflo element, technique, and free. This manual is provided in the following file: /_u_s_r/_s_h_a_r_e/_d_o_c_l_i_b/_x_i_e/_x_i_e_l_i_b._p_s._g_z - _X_I_E _S_a_m_p_l_e _I_m_p_l_e_m_e_n_t_a_t_i_o_n _A_r_c_h_i_t_e_c_t_u_r_e This manual provides an architecture overview of XIE, including chapters on the following topics: extension initialization, memory management, request dispatching, data representation, data structures, protocol requests, DIXIE photoflo management, DDXIE photoflo management, and photo elements. This manual is provided in the following file: /_u_s_r/_s_h_a_r_e/_d_o_c_l_i_b/_x_i_e/_x_i_e_S_I_a_r_c_h._p_s._g_z - _X _I_m_a_g_e _E_x_t_e_n_s_i_o_n _P_r_o_t_o_c_o_l _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l, _V_e_r_s_i_o_n _5._0 This manual specifies the X wire protocol for XIE. It defines the syntax, structure, and Documentation Notes 7-33 semantics of the XIE protocol elements. Topics covered include syntax specification, parameter types, resources, pipelined processing, import elements, process elements, export elements, events and errors, techniques, service class, and protocol encodings. This manual is provided in the following file: /_u_s_r/_s_h_a_r_e/_d_o_c_l_i_b/_x_i_e/_X_I_E_P_r_o_t_o._p_s._g_z +o OSF/Motif Release Documentation OSF/Motif release notes and problems have been provided by the Open Software Foundation (OSF). These notes are contained in the following PostScript files: - /_u_s_r/_d_o_c/_m_o_t_i_f/_M_o_t_i_f__r_e_l__n_o_t_e_s._p_s - A list of known problems in Release 1.2.3: /_u_s_r/_d_o_c/_m_o_t_i_f/_O_P_E_N_B_U_G_S These files are available only if you have installed the OSFXDEV200 subset on your system. +o _S_T_R_E_A_M_S _D_L_P_I _P_a_p_e_r This paper provides the specification for a STREAMS Data Link Provider Interface (DLPI) It complies with DIS 8886 and Logical Link Control (LLC) DIS 8802/2 This paper is provided uncompressed in the following file: /_u_s_r/_s_h_a_r_e/_d_o_c_l_i_b/_d_l_p_i/_d_l_p_i._p_s. Depending on the optional software subsets or environments installed on your system, a number of other documents may also be available in the /_u_s_r/_d_o_c _7._1_3._1 _P_o_s_t_S_c_r_i_p_t _M_a_n_u_a_l_s _R_e_p_l_a_c_i_n_g _O_n_l_i_n_e _o_r _P_r_i_n_t_e_d _V_o_l_u_m_e_s In this release, several X Window and DECwindows manuals are shipped in PostScript format only. To access these documents, mount the DigitalUNIX V4.0 Documentation Volume 1CD-ROM and read the following file: /DOCUMENTATION/POSTSCRIPT/00-READ-ME-FIRST This file provides a list of documents and instructions for decompressing the files. Depending on the installation at your site, the files may 7-34 Documentation Notes already be mounted at the following location: /usr/share/doclib/online/DOCUMENTATION/POSTSCRIPT . Documentation Notes 7-35 Features and Interfaces Scheduled for Retirement 8 This chapter lists features of Digital UNIX Version 4.0 scheduled to be removed from, or changed in, future major functional releases of Digital UNIX. Users and developers should plan to migrate away from these features in the near future. This chapter is also part of the Bookreader book _N_e_w _a_n_d _C_h_a_n_g_e_d _F_e_a_t_u_r_e_s, which is available on the distribution CD-ROM. _8._1 _R_e_t_i_r_e_d _i_n _T_h_i_s _R_e_l_e_a_s_e This section lists features of Digital UNIX that have been retired in this release. These changes were announced in previous releases of DEC OSF/1. +o Support for ULTRIX RIS to Digital UNIX client functionality +o The _o_a_w_k version of the _a_w_k command +o Duplicate _l_i_b_c and _l_i_b_m routines +o The -_n option from /_u_s_r/_b_i_n/_e_c_h_o and /_b_i_n/_e_c_h_o +o Ethernet trailer encapsulation +o Linkworks run-time library +o Logical Volume Manager +o Obsolete POSIX real-time interfaces +o XIE V3.0 interface, server support Runtime support will still be provided transparently through the client +o The POLYCENTER Common Agent (extensions to the SNMP V1.0 agent). _8._2 _N_o_n_c_o_n_f_o_r_m_i_n_g _C_u_r_s_e_s _L_i_b_r_a_r_y Digital UNIX 4.0 is now shipping a new X/Open- Compliant Internationalized Curses library. This is not binary compatible with previous versions of the Digital UNIX Curses library, so compatible binaries (named _l_i_b_c_u_r_s_e_s._a and _l_i_b_c_u_r_s_e_s._s_o) are also shipped in separate directories. These compatible binaries will be retired on this schedule: +o In the next major release (5.0) they will be moved to an obsolete subset. +o In the following major release (6.0) they will be removed. _8._3 _A_C_C The C compiler for Digital UNIX will be officially replaced by DEC C for Digital UNIX in a future release of Digital UNIX. Both compilers were available in Digital UNIX Version 3.2 and both continue to be available in Digital UNIX Version 4.0. The licensing terms and conditions remain the same as they were in Digital UNIX Version 3.2 and earlier products. In Digital UNIX Version 4.0, the newer DEC C is the default compiler invoked using the _c_c command. In releases prior to Digital UNIX (Version 3.2) it was invoked using the following option: # _c_c -_m_i_g_r_a_t_e DEC C offers additional language and compiler features while also offering better, smaller, and faster executable files. The older C compiler had been the default compiler for Digital UNIX Version 3.2 and earlier. It remains available in Digital UNIX Version 4.0 and is invoked using the following option: # _c_c -_o_l_d_c Refer to the _c_c(1) reference page or the _D_e_v_e_l_o_p_e_r_s' _T_o_o_l_k_i_t _f_o_r _D_i_g_i_t_a_l _U_N_I_X, _V_e_r_s_i_o_n _4._0 _S_o_f_t_w_a_r_e _P_r_o_d_u_c_t _D_e_s_c_r_i_p_t_i_o_n _4_4._3_6._1_1 for additional information. 8-2 Features and Interfaces Scheduled for Retirement _8._4 _K_e_r_n_e_l _B_u_i_l_d _P_r_o_c_e_d_u_r_e_s Several parts of the kernel interface and kernel build procedures will be retired in a future release of Digital UNIX. These interfaces and procedures are not compatible with new features being implemented in the Digital Unix Kernel. Each item being retired has a new interface that can be migrated to. Consult the _W_r_i_t_i_n_g _D_e_v_i_c_e _D_r_i_v_e_r_s _T_u_t_o_r_i_a_l manual for specific information. The following items are scheduled for future retirement: +o The _i_f__d_y_n_a_m_i_c keyword in _c_o_n_f/_f_i_l_e_s and _c_o_n_f/_a_l_p_h_a/_f_i_l_e_s is being replaced with the new _M_O_D_U_L_E syntax. +o The use of _N_o_t_B_i_n_a_r_y files. As part of the single-binary module format and dynamic load/topology requirements, _N_o_t_B_i_n_a_r_y files are no longer recommended for use. +o The following kernel interfaces: bdevsw_add, bdevsw_del, cdevsw_add, cdevsw_del, dualdevsw_add, dualdevsw_del, disable_option, enable_option, kalloc, kfree, kget, zinit, zalloc, zchange, zfree, zget ldbl_ctlr_configure, ldbl_ctlr_unconfigure, ldbl_stanza_resolver, +o The kernel data structures _b_d_e_v_s_w, _c_d_e_v_s_w, and _z_o_n_e. +o The following stanza fields: Subsystem_Description, Module_Type, Module_Path, Module_Config, Device_Block_Open, Device_Block_Close, Device_Block_Strategy, Device_Block_Dump, Device_Block_Psize, Device_Block_Flags, Device_Block_Ioctl, Device_Block_Funnel, Device_Char_Flags Device_Char_Open, Device_Char_Close, Device_Char_Read, Device_Char_Write, Device_Char_Ioctl, Device_Char_Stop, Device_Char_Reset, Device_Char_Ttys, Device_Char_Select, Device_Char_Mmap, Device_Char_Funnel, Device_Char_Segmap, _8._5 _T_U_R_B_O_c_h_a_n_n_e_l _D_e_n_a_l_i _G_r_a_p_h_i_c_s The TURBOchannel Denali graphics subsystem (formerly Features and Interfaces Scheduled for Retirement 8-3 marketed by Kubota Graphics Corporation and by Digital Equipment Corporation) is not supported by Digital UNIX Version 4.0. The KWS_TD device driver support, which was present in the Version 3.0 and later releases of DEC OSF/1 and Digital UNIX, is removed. The TURBOchannel Denali graphics subsystem is supported using the generic character-cell style support, but will not operate with the X Window System software. No device dependent X (DDX) support compatible with the X11R6 based X Window System software is available from Kubota Graphics Corporation or its business successors. Due to the limited performance of the generic character-cell style support provided, customers installing Digital UNIX Version 4.0 on a DEC 3000 family system with a TURBOchannel Denali graphics subsystem should consider installing a supported graphics subsystem (such as the Digital ZLX 2D or 3D options), or using a character cell terminal on systems that support operation in server mode. Refer to your system's hardware documentation for information on using a character cell terminal as the system console. _8._6 _d_b_x _D_e_b_u_g_g_e_r The _d_b_x symbolic debugger will be retired in a future release of Digital UNIX. The _d_b_x debugger will be replaced by the Digital _l_a_d_e_b_u_g debugger, which is a superset of the _d_b_x functionality. The Digital _l_a_d_e_b_u_g debugger is command line compatible with _d_b_x and also supports a graphical user interface. Digital recommends that you begin using the Digital _l_a_d_e_b_u_g debugger now and report any problems. This will enable Digital to provide a higher quality replacement when _d_b_x is finally retired. _8._7 _N_e_m_a_c_s Nemacs V3.3.2, a public domain Japanese implementation of _e_m_a_c_s, will be retired in a future release of Digital UNIX. Mule, a public domain multilingual implementation of emacs is shipping in Digital UNIX Version 4.0 and will be carried forward as the replacement functionality for Nemacs. The Nemacs subsets _I_O_S_J_P_N_E_M_A_C_S_4_0_0 and _I_O_S_J_P_N_E_M_A_C_S_S_R_C_4_0_0 will be removed from the system. For more information on Mule, refer to the _m_u_l_e(1) reference 8-4 Features and Interfaces Scheduled for Retirement page. _8._8 _S_e_c_u_r_i_t_y _I_n_t_e_r_f_a_c_e_s Several interfaces in _l_i_b_s_e_c_u_r_i_t_y will be retired in a future release of Digital UNIX. These interfaces are not capable of supporting new functionality offered in Digital UNIX 4.0. Binary Compatibility will be preserved until the interfaces are retired which will be no sooner than 12 months after the current release is shipped. The complete list of documented interfaces follows. There may be some undocumented interfaces that will be retired at the same time. getprtcent(), getprtcnam(), putprtcnam(), getprdfent(), getprdfnam(), putprdfnam(), getprfient(), getprfinam(), putprfinam(), getprlpent(), getprlpnam(), putprlpnam(), getdvagent(), putprfinam(), getprlpent(), getprlpnam(), putprlpnam(), getdvagent(), getfvagnam(), putdvagnam(), getprpwent(), getprpwuid(), getprpwnam(), putprpwnam(), getprlpent(), getprlpnam(), putprlpnam() read_pw_fields(), store_pw_fields(), read_tc_fields(), store_tc_fields(), time_lock(), get_seed(), auth_for_terminal(), locked_out(). The following list of associated data structures will be retired at the same time as the interfaces: struct pr_field, struct pr_flag, struct t_field, struct t_flag, struct l_field, struct l_flag, struct dev_field, struct dev_flag, struct pr_passwd, struct pr_term, struct pr_file, struct pr_lp, struct pr_default, struct dev_asg, struct system_default_fields, struct system_default_flags. _8._9 _S_e_c_u_r_i_t_y _W_i_n_d_o_w_s-_B_a_s_e_d _A_d_m_i_n_i_s_t_r_a_t_i_o_n _U_t_i_l_i_t_i_e_s The functions previously performed with the _X_I_s_s_o and _X_S_y_s_A_d_m_i_n programs have been moved to other graphical user interfaces (_d_x_a_c_c_o_u_n_t_s, _d_x_a_u_d_i_t, and _d_x_d_e_v_i_c_e_s) The _X_I_s_s_o and _X_S_y_s_A_d_m_i_n programs in this release are only interfaces to the other GUIs and support for _X_I_s_s_o and _X_S_y_s_A_d_m_i_n will be discontinued in a future release. Features and Interfaces Scheduled for Retirement 8-5 _8._1_0 _S_y_s_t_e_m _M_a_n_a_g_e_m_e_n_t _U_t_i_l_i_t_i_e_s The following system management utilities will be retired in a future release of Digital UNIX. These applications are being replaced by new more robust implementations under the new system management framework. ____________________________________________________ Old Application Replacement Application ____________________________________________________ lprsetup Printer Configuration netsetup Network Configuration nfssetup NFS Configuration mailsetup Mail Configuration bindsetup Bind Configuration adduser User and Group Account Manager removeuser User and Group Account Manager XISSO, Xsysadmin dxaccounts, dxaudit and dxdevices ____________________________________________________ _8._1_1 _B_S_D _T_T_Y-_N_A_M_E The intent to retire the BSD _T_T_Y-_N_A_M_E namespace was announced in DEC OSF/1 Version 3.0. The retirement will not be implemented in Digital UNIX Version 4.0 but will be deferred to a later release. _8._1_2 _N_C _a_n_d _N_L _I_n_t_e_r_f_a_c_e_s _i_n _t_h_e _S_t_a_n_d_a_r_d _C _L_i_b_r_a_r_y A list of undocumented _l_i_b_c _N_C and _N_L header files and interfaces was announced as obsolete in DEC OSF/1 Version 2.0, superseded by X/OPEN functionality added in the same release. The following interfaces will be removed in a future version of Digital UNIX: NCchrlen NCcollate NCcoluniq NCdec NCdechr NCdecode NCdecstr NCenc NCencode NCencstr NCflatchr NLchrlen 8-6 Features and Interfaces Scheduled for Retirement NLctime NLflatstr NLflattab NLfprintf NLgetamsg NLisNLcp NLxcol _8._1_3 _D_e_s_k_t_o_p _A_p_p_l_i_c_a_t_i_o_n_s The introduction of the Common Desktop Environment (CDE) in Digital UNIX 4.0 includes new graphical desktop tools for: +o Session management +o Calculator +o Calender +o Text editing The Motif X applications corresponding to the new CDE applications are dxsession and _d_x_p_a_u_s_e, _d_x_c_a_l_c, _d_x_c_a_l_e_n_d_e_r, and _d_x_n_o_t_e_p_a_d. These existing applications will be retired in a future release of Digital UNIX. _8._1_4 _S_C_S_I _D_e_v_i_c_e _N_a_m_e_s Support for _r_z SCSI device names will be retired in a future release of Digital UNIX. Retirement is not expected to be implemented for at least two major releases. Any code that derives knowledge about a device from the ASCII name or minor number may be impacted. All code that uses the current namespace will be compatible in Digital UNIX Version 4.0 because a mechanism that ensures binary compatability is provided. Existing interfaces such as names and minor numbers are fully supported. No code changes are required in this release, unless programmers want to take advantage of the new extended address capability. Conversion to the new interfaces is strongly recommended. Features and Interfaces Scheduled for Retirement 8-7 _8._1_5 _P_O_S_I_X _1_0_0_3._4_a (_d_r_a_f_t _4) _p_t_h_r_e_a_d _R_o_u_t_i_n_e_s _i_n _D_E_C_t_h_r_e_a_d_s The POSIX 1003.4a, Draft 4 interface of DECthreads is being retired and will not work in a future release. Applications that were written using the POSIX 1003.4a, Draft 4 API should be migrated to the new IEEE Std 1003.1c-1995, POSIX System Application Program Interface provided by DECthreads. The POSIX 1003.1c standard interface is the most portable, efficient, and powerful programming interface offered by DECthreads. A compatibility mode for the draft 4 POSIX 1003.4a API has been provided in this release to help ease migration. This compatibility mode will be removed in a future release. _8._1_6 _D_E_C_t_h_r_e_a_d_s _C_M_A _I_n_t_e_r_f_a_c_e The CMA interface of DECthreads will be made obsolete in a future release. Obsolescence means that this API will always exist in Digital UNIX and will be supported, but will no longer be documented or enhanced. It is recommended that you port your CMA based application to the IEEE Std 1003-1c-1995, POSIX System Application Program Interface provided by DECthreads. _8._1_7 _F_u_n_c_t_i_o_n_s _R_e_t_i_r_e_d _f_r_o_m _l_i_b_c The following functions existed in both the _l_i_b_m and _l_i_b_c libraries until version Digital UNIX Version 3.2: ceil() modf() frexp() rint() ldexp() trunc() floor() fabs() The _l_i_b_c versions of these functions have been retired. In this version, and in future versions of Digital UNIX the functions will only be available in _l_i_b_m. _8._1_8 _A_d_v_F_S _Q_u_o_t_a _C_o_m_m_a_n_d_s The UFS and AdvFS user and group quota commands have been consolidated for Digital UNIX Version 4.0. The standard UFS quota commands can now be used to manage user and group quotas on AdvFS. AdvFS quota functions have not changed; AdvFS-specific options are now 8-8 Features and Interfaces Scheduled for Retirement incorporated into the UFS commands. Support for existing AdvFS versions of the quota commands will continue until a future release. Until then, both the UFS and AdvFS versions of the quota commands will be supported. _8._1_9 _L_V_M-_t_o-_L_S_M _M_i_g_r_a_t_i_o_n _T_o_o_l_s With the retirement of LVM in this release, the LVM- to-LSM migration tools will become redundant in later releases of Digital UNIX. These migration tools were provided to enable migration from the retired LVM interfaces to Digital UNIX Logical Storage Manager volumes. The LVM-to-LSM Migration Tool will be retired in a future release of the operating system. The UFS and AdvFS Migration Tools are not planned to be retired. In a future release of Digital UNIX, the device driver for the base audio on the Digital AlphaStation 200 and Digital AlphaStation 400 systems will not be part of the base operating system. The following files will be removed from the base operating system: +o ./_u_s_r/_s_y_s/_B_I_N_A_R_Y/_m_s_b._o +o ./_u_s_r/_s_y_s/_i_n_c_l_u_d_e/_i_o/_d_e_c/_e_i_s_a/_m_s_b._h You can get support for this device from the Multimedia Services for DEC OSF/1 kit that is located on the layered products CD-ROM. Support is also factory-installed on all Digital AlphaStation Digital UNIX packaged systems. The license for this product is bundled with the Digital AlphaStations so you can use it at no additional cost. _8._2_0 _O_S_F/_M_o_t_i_f _V_e_r_s_i_o_n _1._1._3 The Motif Version 1.1.3 libraries have been provided as run-time services for compatibility with applications that had not yet converted to Motif 1.2. Development support was retired in DEC OSF/1 Version 2.0. In Digital UNIX Version 4.0 the Motif 1.1.3 libraries have been moved to an optional subset. Applications requiring the libraries will see an error from the loader and you must install the optional subset. This optional subset will be removed from the product Features and Interfaces Scheduled for Retirement 8-9 in a future release. _8._2_1 _X_I_E _V_e_r_s_i_o_n _3._0 _X _C_l_i_e_n_t _E_x_t_e_n_s_i_o_n Digital UNIX Version 4.0 supports XIE Version 5.0. Support for XIE v3.0 Server extensions has been removed in Digital UNIX Version 4.0, but Client support will not be removed until a later release of Digital UNIX. Digital UNIX Version 4.0 supports the POSIX 1003.1b realtime functions, and provides compatibility with older P1003.4 draft functions by allowing you to define the _P_O_S_I_X__4_D_1_1 feature test macro before compiling your applications. In a future release, support for the obsolete P1003.4 draft functions will be removed from the system. Developers should take steps to convert their applications to use the POSIX 1003.1b realtime functions. _8._2_2 _U_L_T_R_I_X _R_e_m_o_t_e _I_n_s_t_a_l_l_a_t_i_o_n (_R_I_S) _S_u_p_p_o_r_t Support for ULTRIX Remote Installation Services (RIS) to Digital UNIX client functionality has been retired in Digital UNIX Version 4.0. The ability to remotely install ULTRIX clients from an ULTRIX server, as well as the ability to remotely install Digital UNIX clients from a Digital UNIX server, will continue to be supported. _8._2_3 _D_i_s_k _S_p_a_c_e _R_e_q_u_i_r_e_m_e_n_t _f_o_r _I_n_s_t_a_l_l_a_t_i_o_n Due to additional functionality being planned, the disk space requirement for a custom installation will be increased in a future functional release of Digital UNIX. A 680 MB disk will not offer sufficient default capacity to contain this type of installation. _8._2_4 _M_S_B _D_r_i_v_e_r In Digital UNIX V4.0, the device driver for the base audio on the Digital AlphaStations and Digital AlphaServers will not be part of the base operating system. This device driver supports the Microsoft Sound Board, the AlphaStation Sound Card, and the built-in audio hardware shipped with certain AlphaStation systems. Instead, the driver binaries will be available as 8-10 Features and Interfaces Scheduled for Retirement part of the Multimedia Services for Digital UNIX kit available on the System Integrated Product CD-ROM in the _M_M_E_D_R_V_M_S_B_2_0_1 subset. The following files will be removed from the base operating system: +o /_u_s_r/_s_y_s/_B_I_N_A_R_Y/_m_s_b._o +o /_u_s_r/_s_y_s/_i_n_c_l_u_d_e/_i_o/_d_e_c/_e_i_s_a/_m_s_b._h +o /_u_s_r/_s_y_s/_i_n_c_l_u_d_e/_i_o/_d_e_c/_e_i_s_a/_m_s_b__r_e_g._h You can also get support for this device from the Multimedia Services for Digital UNIX kit that is located on the Software Products Library CD-ROM. Support is also factory-installed on all Digital AlphaStation Digital UNIX packaged systems. The license for this product is bundled with the Digital AlphaStations so you can use it at no additional cost. _8._2_5 _C _L_i_b_r_a_r_y _F_u_n_c_t_i_o_n_s _a_n_d _P_O_S_I_X _P_1_0_0_3._1_C As of Digital UNIX V4.0 the following C library functions exist in two versions due to conflicts between previous versions of Digital UNIX and the recent IEEE POSIX P1003.1C standard (these new interfaces are in affect by default). The old interfaces are currently accessible by defining the C preprocessor symbol __P_O_S_I_X__C__S_O_U_R_C_E to _1_9_9_3_0_9_L. asctime_r getgrnam_r getpwuid_r localtime_r readdir_r ctime_r getlogin_r gmtime_r rand_r ttyname_r getgrgid_r getpwnam_r Binary compatibility is maintained in Digital UNIX V4.0, however these routines will be retired in a future release of Digital UNIX, no sooner than April 1997. The obsolete versions should not be used in new designs. These routines formerly resided in libc_r.a and libc_r.so, but were merged into the standard C runtime library (see the Development Chapter of this document for additional information). Features and Interfaces Scheduled for Retirement 8-11 Maximum System Limits A _A._1 _M_a_x_i_m_u_m _S_y_s_t_e_m _L_i_m_i_t_s This section lists the maximum system limits for the major components of this release. For hardware information specific to your individual processor, see the _S_o_f_t_w_a_r_e _P_r_o_d_u_c_t _D_e_s_c_r_i_p_t_i_o_n (SPD) and the _S_y_s_t_e_m_s _a_n_d _O_p_t_i_o_n_s _C_a_t_a_l_o_g. For information on how to tune system parameters, see the _S_y_s_t_e_m _T_u_n_i_n_g _a_n_d _P_e_r_f_o_r_m_a_n_c_e _M_a_n_a_g_e_m_e_n_t guide and the _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n guide. +o Backup Utility Limits - _c_p_i_o Files per archive: No limit Files per file system: No limit File size: 4 GB File name size: 256 bytes - _d_d Files per archive: Not used Files per file system: Not used File size: 4 GB File name size: Not used - _d_u_m_p Files per archive: 4 GF Files per file system: 4 GF File size: 4 GB File name size: No limit (part of the inode data) - _t_a_r Files per archive: No limit Files per file system: No limit File size: 4 GB File name size: 256 bytes (with prefix) +o Device Addressing Limits - Device Access In this release there are two types of disk device access: raw or character and block or buffered. For raw or character access, the structure field _u_i_o._u_i_o__o_f_f_s_e_t describes the byte offset within the disk partition. In this release the _u_i_o__o_f_f_s_e_t is an unsigned 64-bit value, allowing an offset up to 264 or 18 Exabytes. This value is converted to a physical block/sector number that is the data transfer start position. The physical block/sector number is limited by the structure field _b_u_f._b__b_l_k_n_o. For block or buffered access, the structure field _b_u_f._b__b_l_k_n_o describes the block/sector offset within the disk partition and is a signed 32-bit value. Since this release supports a fixed 512-byte block/sector size defined by _D_E_V__B_S_I_Z_E, the offset is limited to 1 TB. A-2 Maximum System Limits (Digital UNIX Version 4.0) - Major-Minor Numbers (_d_e_v__t) Devices are described by a major-minor pair of numbers, where the major number describes the device driver and the minor number describes the device. In this release these pairings are represented by a 32-bit value described by the type _d_e_v__t. The major number portion of _d_e_v__t consists of bits 20 to 31 (12 bits). Since each device driver requires 12 bits for its major number, 4096 device drivers may be configured into the system. The minor number portion of _d_e_v__t consists of bits 0 to 19 (20 bits). The content of these bits is left up to the device driver. A device driver utilizing all 20 bits for device addressing could address up to 1048576 devices per major number. For device drivers supporting disk devices, some number of bits in the minor device number will be reserved for the partition number. This release requires disk drivers to reserve the lower 6 bits for device attributes and partition numbers. However, This release restricts support to 8 partitions. - SCSI/CAM Addressing Common Access Method (CAM) is an ANSI-proposed standard for a common software interface to Small Computer Systems Interface (SCSI). There are no restrictions or limitations within CAM for disk block addressing; the address is an incoming value. For SCSI-2, the Command Descriptor Block (CDB) defines the starting disk block number for the transfer. In this release the 10-byte CDB has 4 bytes reserved for the disk block address. This is an unsigned 32-bit value allowing 232-1 or 4 Gigasectors of addressing, which corresponds to 2 TB given the 512-byte block/sector size. In this release the SCSI/CAM driver can address a maximum of 64 buses, with up to 7 device targets per bus, and a maximum of 8 LUNs per device target. As a result, in this release, SCSI/CAM can address a maximum of 3584 devices. - Redundant Array of Independent Disks This release supports three Redundant Array of Independent Disks (RAID) controllers: two for the SCSI bus (HSZ10 and HSZ40) and one for the EISA or PCI bus (SWXCR). Each RAID device is seen by the operating system as a single target Maximum System Limits (Digital UNIX Version 4.0) A-3 device (that is, as a single disk) with up to 8 Logical Unit Numbers (LUNs) on the SCSI controllers and 8 Logical Units (LUs) on the EISA or PCI controller, regardless of the number of disks on each RAID device. The HSZ10 SCSI RAID controller supports a maximum of 35 back-end disks; the HSZ40 SCSI RAID controller, a maximum of 42 back-end disks. As a result of hardware constraints, the maximum number of HSZ10 disks that can be concatenated into a logical volume is 5; the maximum number of HSZ40 disks that can be concatenated into a RAID 0 set for a logical volume is 14 with a total size limit of 32 GB. The EISA and PCI RAID controllers supports a maximum of 8 Logical units with a maximum of 8 drive groups. A Logical Unit refers to an amount of storage space presented to the host operating system as a single storage device. A drive group consists of one to eight physical drives that operate (defined and addressed) as a single unit. Logical volume sizes are not fixed sizes as compared to other disk devices. The size of a logical volume is configurable based on needs with a total size limit of 32 GB. In addition, the SWXCR controller may have either a one or a three channel SCSI adapter which supports 7 or 21 back-end SCSI disks, respectively. In addition, the SWXCR controller may have either one or three SCSI channels which support 7 or 21 back-end SCSI disks, respectively. Although RAID theoretically increases the number of addressable disks significantly, Digital recommends that the maximum number of devices for each system - even with RAID configured - should not exceed the numbers listed in the following section on device limits per processor. - Disklabel The disklabel defines the partitions of a disk and their starting block/sector number. The starting block/sector number of a partition is defined by the structure field _p_a_r_t_i_t_i_o_n._p__o_f_f_s_e_t, which is an unsigned 32-bit value allowing 2 TB of addressing with a 512- byte block/sector size. A-4 Maximum System Limits (Digital UNIX Version 4.0) +o Device Limits Per Processor - SCSI Bus +o Buses/Adapter - 1 or 2 +o RZ/TZ Devices/Bus - 7 - Digital Storage Architecture (DSA) +o CIXCD Controller - 1 to 4 HSCs +o HSC - Up to the limit supported by each HSC, with a combined maximum of 96 RA/TA devices +o KDM Controller - 8 RA/TA devices up to 6 controllers +o CI Star - A maximum of 16 nodes Note that DSA supports a maximum of 96 RA/TA devices. - Processors * Alpha Station 200 series - 21 RZ/TZ Devices (1 Baseboard PCI) + (2 PCI SCSI Adapters) = 3 SCSI Buses * 7 devices/bus * Alpha Station/Server 400 series - 28 RZ/TZ Devices (1 Baseboard PCI) + (3 PCI SCSI Adapters) = 4 SCSI Buses * 7 devices/bus * Alpha Station 600 series - 35 RZ/TZ Devices (1 Baseboard PCI) + (4 PCI SCSI Adapters) = 5 SCSI Buses * 7 devices/bus * Alpha Server 1000 series - 28 RZ/TZ Devices (1 Baseboard PCI) + (3 PCI SCSI Adapters) = 4 SCSI Buses * 7 devices/bus * AlphaServer 8200/8400 - 32 SCSI Buses * 7 devices/bus * DEC 2000 series + Model 300 - 28 RZ/TZ Devices (4 Single SCSI Adapters) = 4 SCSI buses * 7 devices/bus + Model 500 - 28 RZ/TZ Devices Maximum System Limits (Digital UNIX Version 4.0) A-5 (4 Single SCSI Adapters) = 4 SCSI buses * 7 devices/bus * DEC 2100 series - 35 RZ/TZ (SCSI) Devices -42 RE (RAID) Devices (1 PCI Baseboard Single SCSI) + (3 Single SCSI PCI Adapters) + (1 EISA Baseboard Single SCSI) + (2 Tri-SCSI Adapters) = 6 SCSI buses * 7 devices/bus * DEC 2100 4/233, 4/275, 5/250, 5/300 (8 PCI slots, each supporting 1 SCSI adapter) + (3 EISA slots, 1 SCSI internal) * DEC 3000 series + Model 800/800S - 98 RZ/TZ Devices (1 Baseboard Dual SCSI) + (6 Dual SCSI TURBOchannel Adapters) = 14 SCSI buses * 7 devices/bus + Model 600S - 56 RZ/TZ Devices (1 Baseboard Dual SCSI) + (3 Dual SCSI TURBOchannel Adapters) = 8 SCSI buses * 7 devices/bus + Model 600 - 42 RZ/TZ Devices (1 Baseboard Dual SCSI) + (2 Dual SCSI TURBOchannel Adapters) = 6 SCSI buses * 7 devices/bus + Model 500 - 98 RZ/TZ Devices (1 Baseboard Dual SCSI) + (6 Dual SCSI TURBOchannel Adapters) = 14 SCSI buses * 7 devices/bus + Model 500X - 84 RZ/TZ Devices (1 Baseboard Dual SCSI) + (5 Dual SCSI TURBOchannel Adapters) = 12 SCSI buses * 7 devices/bus + Model 400S - 56 RZ/TZ Devices (1 Baseboard Dual SCSI) + (3 Dual SCSI TURBOchannel Adapters) = 8 SCSI buses * 7 devices/bus + Model 400 - 42 RZ/TZ Devices (1 Baseboard Dual SCSI) + (2 Dual SCSI TURBOchannel Adapters) = 6 SCSI buses * 7 devices/bus A-6 Maximum System Limits (Digital UNIX Version 4.0) + Model 300/300X - 35 RZ/TZ Devices (1 Baseboard Single SCSI) + (2 Dual SCSI TURBOchannel Adapters) = 5 SCSI buses * 7 devices/bus + Model 300L/300LX - 7 RZ/TZ Devices (1 Baseboard Single SCSI) = 1 SCSI bus * 7 devices/bus * DEC 4000 series 28 RZ/TZ Devices (4 Baseboard Single SCSI) = 4 SCSI buses * 7 devices/bus * DEC 7000/10000 series 96 RA/TA Devices (DSA) 112 RZ/TZ Devices (SCSI) (8 Dual SCSI XMI Adapters) = 32 SCSI buses * 7 devices/bus +o CPU Limits Per Processor AlphaStation 200 series: 1 AlphaStation/Server 400 series: 1 AlphaStation/Server 600 series: 1 AlphaServer 1000 series: 1 AlphaServer 2000: 2 AlphaServer 2100: 4 AlphaServer 2100A: 4 AlphaServer 8200: 6 AlphaServer 8400: 12 DEC 2000 series: 1 DEC 2100 series: 4 DEC 3000 series: 1 DEC 4000 series: 2 DEC 7000/10000 series: 6 +o File System Limits - Maximum Size Maximum System Limits (Digital UNIX Version 4.0) A-7 * Logical Storage Manager In this release the Logical Storage Manager (LSM) supports a maximum of 768 disk groups and 256 disks either in a disk group or across the system. In LSM, the term vvvvoooolllluuuummmmeeee describes a virtual disk representing an addressable range of disk blocks used by applications such as file systems or databases. This release supports a maximum of 512 GB of disk space in a disk group or on a system, with a maximum supported volume of 512 GB. The maximum number of supported LSM volumes is 4093 for all disk groups in a 4093 for all disk groups in a system: 4091 non-system volumes and 2 system (root/swap) volumes. In LSM, the term pppplllleeeexxxx describes the physical disk or disks that contain a complete copy of a volume's data. So, for example, a mirrored volume would be made up of at least two plexes. In this release the maximum number of supported plexes per volume is 8 and the maximum number of supported plexes per system is 4093 (or 4091 if root and swap volumes are not used). In LSM, the term ssssuuuubbbbddddiiiisssskkkk describes a contiguous portion of a physical disk which can be striped or concatenated together to form a plex. A maximum of 4096 subdisks can be associated with one plex, and Digital supports 4096 subdisks per disk group or per system. LSM object names (such as volumes, plexes, subdisks, disk groups), volume attribute names (such as user and group), and _d_x_l_s_m _v_i_e_w names are limited to 14 characters. * Advanced File System In the Advanced File System (AdvFS), a vvvvoooolllluuuummmmeeee is any single logical device which can be a partition on a physical disk or a logical volume. A ddddoooommmmaaaaiiiinnnn is a named set of bound volumes on which filesets are placed. A ffffiiiilllleeeesssseeeetttt is a named collection of files that is bound to a single domain. An aaaaccccttttiiiivvvveeee ffffiiiilllleeeesssseeeetttt is a fileset that has been mounted, like a mounted UFS file system, for example. Although the architectural maximum limit of domains is 2048, in this release the AdvFS supports a maximum fileset and file size of A-8 Maximum System Limits (Digital UNIX Version 4.0) 512 GB, up to 100 active file domains per system, and a maximum of 256 volumes per domain. Since a single disk failure in a domain can make the entire domain inaccessible, Digital also recommends that you create no more than 8 volumes per domain. Note that while Digital UNIX supports an unlimited number of filesets per system, only 512 filesets can be mounted at one time. 32 The number of files per fileset is 2 , limited by the tag used to uniquely identify a file in a fileset. Note that over time the actual limit of files per fileset decreases, since a tag can only be used 4096 times due to a sequence number limit. Although AdvFS can support page sizes larger than 13 bits, the theoretical maximum AdvFS fil1e3 and fi3l1eset size is 16 TB (2 ^*^ 2 ) with a 13-bit page size and 31-bit page number. * UNIX File System In this release, the UNIX File System (UFS) file size is limited by the amount of space that the kernel _b_u_f structure can address. The structure field _b_u_f._b__b_l_k_n_o, defined as _d_a_d_d_r__t, is the block/sector offset within a disk partition and is a 32-bit signed value. The block or sector size, _D_E_V__B_S_I_Z_E, is 512 bytes. As a result, the theoretical maximum file system size that this release supports is 1 TB (231 ^*^ 29). Note that Digital only supports 128 GB. The UFS file system and file size is limited by the maximum logical volume size supported by the Logical Volume Manager. (the maximum logical volume size supported by the Logical Storage Manager). * CD-ROM File System The size of the CD-ROM File System (CDFS) files and file systems is limited by the compact read-only optical disk (CD-ROM) media where they reside. Currently, the CD-ROM media supports approximately 0.60 GB. However, Digital UNIX is able to support larger CD-ROMs should they become available. Maximum System Limits (Digital UNIX Version 4.0) A-9 * Sparse Files Digital UNIX supports ssssppppaaaarrrrsssseeee ffffiiiilllleeeessss on AdvFS and UFS, which means that the size of a file may exceed the size of the file system where it resides. Digital UNIX supports the following maximum sizes for sparse files: 43 AdvFS 2 +2 UFS 244-8K * Network File System In this release, the theoretical maximum size of a file that is accessible through the Network File System (NFS) is as follows: + NFS Version 2.0 - (2 GB - 1 byte) 64 + NFS Version 3.0 - 16 Exabytes (2 -1) Digital supports the following maximum file sizes: + NFS Version 2.0 - 2 GB + NFS Version 3.0 - 512 GB Note that an NFS server is always limited by the size of the underlying local file system. - Memory Mapped File Limit The supported maximum size of a file that can be mapped into memory without segmenting the file is 1 GB. - Mounts * Advanced File System The Advanced File System (AdvFS) supports a maximum of 512 mounted filesets. However, each active domain has an invisible mounted fileset associated with it which must be factored into the total number of mounted filesets. So, for example, if you have an active domain with two mounted filesets, the invisible fileset associated with the domain itself brings the total number of mounted filesets to three. A-10 Maximum System Limits (Digital UNIX Version 4.0) * UNIX File System The UNIX File System (UFS) supports a total of 512 mounts, which are now allocated dynamically by the system rather than being dependent on statically configured mount tables as they were in previous releases of the operating system. * CD-ROM File System this release supports a maximum of 512 CD- ROM File System (CDFS) mounts. * Network File System A Network File System (NFS) Version 2.0 or Version 3.0 client can mount a maximum of 2048 files or directories. The _v_n_o_d_e_s necessary to support the NFS-mounts are now allocated dynamically rather than being dependent on a statically configured _v_n_o_d_e table as they were in previous releases of - Open files The maximum number of files a process can open is set to 4096 by default in the _O_P_E_N__M_A_X__S_Y_S_T_E_M variable in the file /_u_s_r/_s_y_s/_i_n_c_l_u_d_e/_s_y_s/_p_a_r_a_m._h. This number can be adjusted between 64 and 4096, either in individual programs by using the _s_e_t_r_l_i_m_i_t(2) system call or on a system-wide basis by editing the file /_u_s_r/_s_y_s/_c_o_n_f/_p_a_r_a_m._c, changing the _o_p_e_n__m_a_x__s_o_f_t and _o_p_e_n__m_a_x__h_a_r_d variables, and then relinking or rebuilding the kernel. Note that file descriptor entries in the per process file table are dynamically allocated after the initial 64 entries in the _u_t_a_s_k structure are used. - File Locking Limits The Digital UNIX file record locking service allows applications to lock any n6u3mber of bytes in a file in the range of 0 to 2 -1 inclusive. File locking is supported by UFS, AdvFS, and both NFS Version 2 and Version 3. Note that since the NFS Version 2 protocol suite only allows ranges to be specified with 32-bit numbe3r1s, it supports a file locking range of 0 to 2 -1 inclusive. - Pathname Limits AdvFS, UFS, CDFS, and NFS support a maximum pathname component of 255 bytes and a maximum Maximum System Limits (Digital UNIX Version 4.0) A-11 file pathname of 1023 bytes. +o Installation Limits This section lists the disk space required for _r_o_o_t, /_u_s_r, and /_v_a_r when performing a default or a custom installation of this release. These are approximate numbers, as the values will depend on the system configuration and are based on the UFS files system. - Default Installation (mandatory subsets) _r_o_o_t: 39.7 MB /_u_s_r: 168.4 MB - Custom Installation (mandatory and all optional subsets) _r_o_o_t: 49.1 MB /_u_s_r: 333.7 MB /_v_a_r: 6.1 MB +o Memory Limits - Physical Memory The maximum supported memory is different for each individual processor, although the DEC 7000/10000/8200/8400 series a total of 14 GB of physical memory. The operating system, however, supports a total of approximately 4 GB of physical memory. For more information on supported memory, see the _S_y_s_t_e_m_s _a_n_d _O_p_t_i_o_n_s _C_a_t_a_l_o_g. and the SPD. A-12 Maximum System Limits (Digital UNIX Version 4.0) - Virtual Memory * Per process The default virtual memory per process is 2 GB, although available swap space may in many cases be exhausted before this limit is reached. This value can be increased to a maximum of 8 TB by defining the _M_A_X_V_A_S variable in the system configuration file and relinking or rebuilding the kernel. * Page size The default page size is 8 KB and is not configurable. The page size is hardware dependent and is set up by the console at boot time. +o Networking Limits - Pseudoterminals (_p_t_y_s) The maximum number of supported _p_t_y_s is 8192. - LAT Connections +o The maximum number of incoming LAT connections is 4800 +o The maximum number of outgoing LAT connections is 4000 - IP Alias Addresses Digital UNIX allows the use of up to 5,000 IP alias addresses before system performance begins to degrade. - Packetfilter limits The packetfilter pseudo-driver can support up to 255 simultaneous open filters (each filter is usually mapped to one instance of an application program). The packetfilter can support a maximum of 255 devices, where each device can be displayed using _i_f_c_o_n_f_i_g -_a. - Network Transfer Rates For information on network transfer rates, see the _T_e_c_h_n_i_c_a_l _O_v_e_r_v_i_e_w. +o Process Limits Maximum System Limits (Digital UNIX Version 4.0) A-13 - Per system The number of processes per system depends on the value of _M_A_X_U_S_E_R_S, which is configurable and set in the configuration file to 32 by default. With _M_A_X_U_S_E_R_S at its default value, the number of processes per system is set to 276 in the _N_P_R_O_C variable in /_u_s_r/_s_y_s/_c_o_n_f/_p_a_r_a_m._c. You can increase this value by either changing the value of _M_A_X_U_S_E_R_S in the system configuration file or by adding the _m_a_x_p_r_o_c variable to the system configuration file and relinking or rebuilding the kernel. You might increase the value of _M_A_X_U_S_E_R_S to allow more users to log in to your system or to allow applications that run as _r_o_o_t to fork more processes than _N_P_R_O_C allows by default. However, increasing the number of processes per system reserves more system memory, so the upper limit of _N_P_R_O_C is dependent upon the system's total memory, the number of actual users on the system, and the requirements of your applications. - Per user The number of processes that each user can fork is set to 64 by default through the _C_H_I_L_D_M_A_X variable in the file /_u_s_r/_s_y_s/_i_n_c_l_u_d_e/_s_y_s/_s_y_s_l_i_m_i_t_s._h. The number of processes per user can be varied by adding the _m_a_x_u_p_r_c variable to the system configuration file, setting its value to some number of processes, and then relinking or rebuilding the kernel. You might increase this value if you had an application that needed more processes than _C_H_I_L_D_M_A_X is set to by default. However, increasing the value of _m_a_x_u_p_r_c reserves more system memory, so the upper limit of _m_a_x_u_p_r_c is dependent upon the system's total memory, the number of actual users on the system, and the requirements of your applications. A-14 Maximum System Limits (Digital UNIX Version 4.0) Additional Notes B This appendix contains any release notes that were not included in the Bookreader version of the release notes or the PostScript and text versions shipped on the distribution media. _B._1 _D_e_m_o_n_s_t_r_a_t_i_o_n _P_r_o_g_r_a_m _d_x_m_a_n_d_e_l The source code as provided in /_u_s_r/_e_x_a_m_p_l_e_s/_m_o_t_i_f/_d_x_m_a_n_d_e_l does not produce a working version of the demonstration. This can be corrected if you change the first function call of _X_t_T_o_o_l_k_i_t_T_h_r_e_a_d_I_n_i_t_i_a_l_i_z_e() to read _X_I_n_i_t_T_h_r_e_a_d_s(). Then remove the second call to _X_t_T_o_o_l_k_i_t_T_h_r_e_a_d_I_n_i_t_i_a_l_i_z_e(). _B._2 _A_d_d_i_t_i_o_n_a_l _B_o_o_t_a_b_l_e _T_a_p_e _R_e_s_t_r_i_c_t_i_o_n_s Additional restrictions apply to the use of bootable tape, described in Section 4.5.2 has changed. The first paragraph should read as follows: For this release, the following features are not supported: +o The LSM product. +o The AdvFS _a_d_d_v_o_l utility +o 32MB systems using AdvFS file systems In the section titled Disk Space Issues, there are two references to 120,000 (512 blocks) of disk space required in /_u_s_r. The number of blocks should be 156,000 (512-blocks). Step 4 of the instructions in this section refers to mounting device /_d_e_v/_r_z_i_d. This step should mention that device _r_z_1_d should have 75,000 (512-blocks) available. Step 10 of the instructions refers to mounting device /_d_e_v/_r_z_i_b. This step should mention that device _r_z_1_b should have 156,000 (512-blocks) available. The rest of Section 4.5.2 still applies. _B._3 _M_a_x_i_m_u_m _S_y_s_t_e_m _L_i_m_i_t_s The release notes appendix on Maximum System Limits has been updated. please refer only to the information in this printed version of the release notes, or in the versions supplied on the Digital UNIX Version 4.0 Operating System Volume 1 CD-ROM. These files are located in the /_D_O_C_U_M_E_N_T_A_T_I_O_N/_P_O_S_T_S_C_R_I_P_T and /_D_O_C_U_M_E_N_T_A_T_I_O_N/_T_E_X_T directories. _B._4 _R_e_m_o_t_e _I_n_s_t_a_l_l_a_t_i_o_n _S_e_r_v_i_c_e_s (_R_I_S) _V_e_r_s_i_o_n _R_e_q_u_i_r_e_m_e_n_t There are incompatibilities between utilities used by Digital UNIX Version 4.0 (formerly DEC OSF/1) and DEC OSF/1 V2.0. Therefore, it is not possible for a OSF/1 V2.0 server to serve Digital UNIX V4.0 clients. You must upgrade the server operating system software to a minimum revision of DEC OSF/1 V3.0 to be able to serve Digital UNIX V4.0 clients. _B._5 _U_p_s_o_l_e_t_e _F_i_l_e_s _A_f_t_e_r _a_n _U_p_d_a_t_e _I_n_s_t_a_l_l_a_t_i_o_n If the following obsolete files exist on your system after a V4.0 update installation, they can be removed. These files will not appear in the /_v_a_r/_a_d_m/_s_m_l_o_g_s/_u_p_d__o_b_s_o_l_e_t_e__f_i_l_e_s log file and must be removed manually. +o /_i_s_l/_s_a_s/._p_r_o_f_i_l_e +o /_i_s_l/_s_i_f_s_y_n_c B-2 Additional Notes (Digital UNIX Version 4.0) Index _A _A_d_v_F_S (cont.) _A_C_C, 1-26, 8-2 vrestore, 4-42 _a_c_c_o_u_n_t _m_a_n_a_g_e_r, 4-13 _A_d_v_F_S _d_o_m_a_i_n _v_e_r_i_f_i_c_a_t_i_o_n, _A_C_L, 1-35, 4-38, 4-39, 4-41, 4-42 4-5, 4-6, 4-7, 7-4 _A_l_p_h_a_S_e_r_v_e_r _1_0_0_0 _A_C_L_s _o_v_e_r _N_F_S, 4-38 ECU, 3-3 _a_d_d_v_o_l, 1-8 _A_l_p_h_a_S_e_r_v_e_r _8_2_0_0 _5/_3_0_0 _a_n_d _A_d_v_a_n_c_e_d _F_i_l_e _S_y_s_t_e_m _A_l_p_h_a_S_e_r_v_e_r _8_4_0_0 _5/_3_0_0 _S_e_e AdvFS resetting the cursor after _A_d_v_F_S, 4-41 running the ECU, 3-4 ACL, 4-39, 4-41 _A_l_p_h_a_S_t_a_t_i_o_n _6_0_0, 6-5 and extended attributes, _a_l_t_e_r_n_a_t_e _c_o_m_p_i_l_e_r, 5-4 4-46 _a_r_c_h_i_v_i_n_g _a_n_d _s_e_c_u_r_i_t_y, 4-6 directory truncation, 1-35 _A_s_i_a_n _k_e_y_b_o_a_r_d, 6-17 disk usage information, _A_s_i_a_n _l_a_n_g_u_a_g_e _p_r_i_n_t_i_n_g, 4-1 4-47 _A_s_i_a_n _m_u_l_t_i_s_c_r_e_e_n _s_u_p_p_o_r_t, domain panic, 4-43 6-17 du command, 4-47 _a_s_s_e_m_b_l_e_r ._r_c_o_n_s_t, 7-21 filesets, 4-45 _a_s_y_n_c_h_r_o_n_o_u_s _I/_O _r_e_q_u_e_s_t_s, fsck, 4-45 5-13 group quota commands, 4-44 _A_T_I _g_r_a_p_h_i_c_s _c_o_n_t_r_o_l_l_e_r, 2-4 HSM, 4-47 _A_T_I _M_a_c_h_6_4, 3-1 incorrect disk space _A_T_M, 4-33 messages, 4-46 _a_t_o_m, 5-3 increase metadata size, _A_t_o_m, 5-3 4-46 _a_t_o_m log half full, 4-48 fork, 5-7 migration to, 8-9 Fortran, 5-9 NFS, 4-48 hiprof, 5-8, 5-9 panic, 4-40 multi-threaded hiprof, 5-7 problems, 4-45 signal handlers, 5-7 quota commands, 8-8 third degree, 5-8, 5-9 reusing partitions, 4-45 _a_u_t_o_p_a_u_s_e, 6-13 sparse file systems, 4-42 _a_w_k, 4-11 tuning, 1-34 UFS file system, 4-46 ufs_fsck, 4-45 unique file identifiers, 4-47 vdump, 4-42 _B _c_k_s_u_m, 4-11 _C_L_D_s, 7-2 _b_a_c_k_u_p _u_t_i_l_i_t_y _l_i_m_i_t_s, A-1 _c_l_i_p_b_o_a_r_d _i_n_t_e_r_o_p_e_r_a_b_i_l_i_t_y, _B_C_L, 4-51 6-11 _b_i_d_i_r_e_c_t_i_o_n_a_l _f_s_t_r_e_a_m_s, 5-11 _c_l_o_c_k, 4-30 _b_i_n_d, 4-33, 7-4 _C_M_A, 8-8 _b_l_o_c_k _c_h_a_n_g_e _l_o_g_g_i_n_g _c_o_l_o_r_m_a_p, 6-9 _S_e_e BCL _c_o_m_m_a_n_d_s _b_o_o_t_a_b_l_e _t_a_p_e, 1-7, 4-26 tip, 7-14 disk space, 4-27 _c_o_m_p_i_l_e_r, 5-4, 8-2 setting an existing file pthreads, 5-14 on, 4-29 _c_o_m_p_r_e_s_s_e_d _P_o_s_t_S_c_r_i_p_t, 7-2 setting swap space on, _c_o_n_v_a_u_t_h, 2-9 4-28 _c_p_i_o, 4-6 TZK11 restriction, 4-29 _c_u_r_s_e_s, 1-2, 4-2, 8-2 _b_o_o_t_s_t_r_a_p _l_i_n_k_i_n_g, 1-38 _c_u_r_s_o_r _B_S_D _n_a_m_e_s_p_a_c_e _r_e_t_i_r_e_m_e_n_t, resetting after running 8-6 the ECU, 3-4 _c_u_t _a_n_d _p_a_s_t_e _i_n _M_o_t_i_f _a_p_p_l_i_c_a_t_i_o_n_s, 6-11 _C _c _c_o_m_p_i_l_e_r debugging information, 5-1 _D integer types, 5-1 _C _l_i_b_r_a_r_y _f_u_n_c_t_i_o_n_s, 5-1 _d_a_t_e _a_n_d _t_i_m_e, 2-10 _C _r_u_n_t_i_m_e _l_i_b_r_a_r_y, 5-12 _d_b_x, 8-4 _c_8_9, 5-3 pthreads, 5-15 _C_a_l_C_o_m_p _D_r_a_w_i_n_g_B_o_a_r_d _d_e_b_u_g_g_e_r, 5-1 _s_u_p_p_o_r_t, 6-1 _S_e_e _a_l_s_o dbx _c_a_l_c_u_l_a_t_o_r, 1-1 dbx, 5-17 _c_a_l_e_n_d_a_r, 1-1 ladebug, 5-7 _c_a_p_t_o_i_n_f_o, 1-5 _D_E_C _A_d_a _R_T_L, 5-2 _c_a_t_a_l_a_n, 1-43 _D_E_C _C, 1-26, 5-4 _c_b_r_e_a_k(), 4-4 -ifo, 5-6 _c_c, 1-23, 1-27 _D_E_C _C _m_a_n_u_a_l, 7-21 pthread option, 5-14 _D_E_C _C++ _C_D_E, 1-1, 6-8 class library, 5-11 dtmail, 6-14 clog(), 1-25 network dependency, 4-36, divide-by-zero, 1-24 6-15 exception handling, 1-25 screen savers, 1-2 ios::ate mode, 1-25 xnlLanguage resource, 6-15 iostream assignment ops, XOpenDisplay call, 6-15 1-24 _c_h_a_n_g_e_d _f_e_a_t_u_r_e_s string extraction, 1-24 Standards, 1-23 structured exceptions, _c_h_e_c_k_i_n_g _d_i_s_k _p_a_r_t_i_t_i_o_n_s, 1-25 1-38 thread safe, 1-24 _c_h_i_n_e_s_e _d_e_c_t_e_r_m, 6-16 underflow errors, 1-24, _C_h_i_n_e_s_e _s_u_b_s_e_t_s 1-25 RIS, 2-12 _D_E_C _F_U_S_E, 2-5 _c_i_t_h_u_a_n_i_a_n, 1-43 _D_E_C_l_a_d_e_b_u_g _S_e_e ladebug Index-2 _D_E_C_n_e_t/_O_S_I, 2-5 _d_i_s_k _u_s_a_g_e _i_n_f_o_r_m_a_t_i_o_n _D_E_C_t_h_r_e_a_d_s, 5-13, 5-16 AdvFS, 4-47 _S_e_e pthreads _d_i_s_k_c_o_n_f_i_g, 4-12 _D_E_C_w_i_n_d_o_w_s _b_o_o_k_s, 7-34 _d_i_s_k_e_t_t_e, 4-7 _d_e_f_a_u_l_t _l_o_c_k_i_n_g _o_f _m_a_i_l, _d_m_u, 1-7 6-11 _d_o_c_o_n_f_i_g, 1-38 _d_e_n_a_l_i _g_r_a_p_h_i_c_s, 8-3 _d_o_c_u_m_e_n_t_a_t_i_o_n _d_e_p_o_r_d, 2-3 CDROM, 7-1 _d_e_s_k_t_o_p _a_p_p_l_i_c_a_t_i_o_n_s new, 7-2 _r_e_t_i_r_i_n_g, 8-7 release notes, 7-1 _d_e_s_k_t_o_p _e_n_v_i_r_o_n_m_e_n_t _d_o_m_a_i_n _S_e_e CDE _S_e_e AdvFS _d_e_v_e_l_o_p_m_e_n_t _e_n_v_i_r_o_n_m_e_n_t, _d_r_i_v_e_r, 8-10 1-26 _d_t_f_i_l_e, 6-19 _d_e_v_e_l_o_p_m_e_n_t _e_n_v_i_r_o_n_m_e_n_t _d_t_m_a_i_l, 6-13, 6-14 _e_n_h_a_n_c_e_m_e_n_t_s, 1-23 _d_t_p_a_d, 6-19 _d_e_v_i_c_e _a_d_d_r_e_s_s_i_n_g _l_i_m_i_t_s, _d_t_t_e_r_m, 6-19 A-2 _d_u _c_o_m_m_a_n_d _d_e_v_i_c_e _d_r_i_v_e_r, 7-13 AdvFS, 4-47 _d_e_v_i_c_e _d_r_i_v_e_r _e_x_a_m_p_l_e_s, 5-19 _d_u_p_l_i_c_a_t_e _m_i_n_o_r _n_u_m_b_e_r_s, _d_e_v_i_c_e _d_r_i_v_e_r_s, 7-6 4-37 _d_e_v_i_c_e _l_i_m_i_t_s, A-5 _d_x_a_c_c_o_u_n_t_s _p_r_o_g_r_a_m, 8-5 _d_f, 1-5 _d_x_a_u_d_i_t _p_r_o_g_r_a_m, 8-5 XPG4 compliance, 4-11 _d_x_d_e_v_i_c_e_s _p_r_o_g_r_a_m, 8-5 _D_H_C_P, 1-31 _D_X_I_m_a_g_e_v_i_e_w, 1-4 _D_i_g_i_t_a_l _A_X_P_p_c_i _3_3 _d_x_m_a_i_l, 6-11 IRQs for PCI options, 3-6 default locking, 6-11 _D_i_g_i_t_a_l _A_X_P_v_m_e _1_0_0, 3-5 _d_x_m_a_n_d_e_l, B-1 hardware restriction, 3-5 _d_x_n_o_t_e_p_a_d, 6-19 _D_i_g_i_t_a_l _A_X_P_v_m_e _1_6_0, 3-5 resource definition file, hardware restriction, 3-5 6-10 master block, 3-6 _d_x_s_h_u_t_d_o_w_n, 4-22 _D_i_g_i_t_a_l _A_X_P_v_m_e _1_6_6, 3-5 _d_x_s_y_s_i_n_f_o, 4-22 hardware restriction, 3-5 /dev/prf, 4-22 _D_i_g_i_t_a_l _A_X_P_v_m_e _2_3_0, 3-5 _d_x_t_e_r_m, 1-6 hardware restriction, 3-5 _D_i_g_i_t_a_l _A_X_P_v_m_e _6_4, 3-5 hardware restriction, 3-5 _E master block, 3-6 _D_i_g_i_t_a_l _P_o_r_t_i_n_g _A_s_s_i_s_t_a_n_t, _e_c_h_o, 4-11 1-30 _e_d_i_t_i_n_g, 1-1 _D_i_g_i_t_a_l _V_M_E _2_1_0_0 _e_m_a_c_s, 1-6, 4-7, 4-9 master block transfers, _e_n_c_a_p_s_u_l_a_t_i_o_n, 1-36 3-4 _e_n_h_a_n_c_e_d _s_e_c_u_r_i_t_y, 1-34, _d_i_r_e_c_t_o_r_i_e_s _r_e_n_a_m_e_d, 4-10 2-9, 4-19, 4-23, 4-25, _d_i_s_a_s_t_e_r _r_e_c_o_v_e_r_y, 4-25 4-26, 6-13 _d_i_s_k _c_o_n_f_i_g_u_r_a_t_i_o_n, 4-12 _e_r_r_o_r _r_e_p_o_r_t_i_n_g _d_i_s_k _c_o_n_t_r_o_l_l_e_r, 3-4 system administration, _d_i_s_k _d_e_t_e_c_t_i_o_n, 2-2 4-31 _d_i_s_k _s_p_a_c_e, 8-10 /_e_t_c/_f_d_m_n_s, 2-6 _d_i_s_k _s_p_a_c_e _r_e_q_u_i_r_e_m_e_n_t_s, 2-8 _e_x_a_m_p_l_e _c_o_d_e, 5-19 Index-3 _E_x_s_t_e_n_s_i_b_l_e _S_N_M_P, 1-32 _g_r_a_n_u_l_a_r_i_t_y _h_i_n_t_s, 2-8 _e_x_t_e_n_d_e_d _a_t_t_r_i_b_u_t_e_s _g_r_a_p_h_i_c_a_l _i_n_s_t_a_l_l_a_t_i_o_n, 2-3 and AdvFS limits, 4-46 _g_r_a_p_h_i_c_s, 8-3 _e_x_t_r_a_c_t_i_o_n _o_p_e_r_a_t_o_r _g_r_a_p_h_i_c_s _c_o_n_t_r_o_l_l_e_r, 2-2, converting hexadecimal 2-7, 3-1 values, 5-11 _g_r_o_u_p _q_u_o_t_a_s, 4-44 _G_u_i_d_e _t_o _P_r_e_p_a_r_i_n_g _P_r_o_d_u_c_t _K_i_t_s, 7-21, 7-22 _F _F__G_E_T_F_L, 5-13 _H _f_c_n_t_l(), 5-13 _f_i_l_e, 1-1 _H_a_n_g_u_l, 6-17 _f_i_l_e _m_a_n_a_g_e_r, 6-13 _H_a_n_y_u, 6-17 _f_i_l_e _s_y_s_t_e_m _i_n_f_o_r_m_a_t_i_o_n, _H_a_n_z_i, 6-17 4-22 _H_e_b_r_e_w, 6-18, 6-19 _f_i_l_e _s_y_s_t_e_m _l_i_m_i_t_s, A-7 _h_e_l_p maximum size, A-7 glossaries, 7-25 mounts, A-10 integration restrictions, open files, A-11 7-25 _f_i_l_e _s_y_s_t_e_m_s _h_i_l_i_t_e _m_o_u_s_e _t_r_a_c_k_i_n_g, 6-12 unique file identifiers, _h_i_p_r_o_f, 5-8, 5-9 4-47 _H_S_M _f_i_r_m_w_a_r_e AdvFS, 4-47 pthreads, 5-16 _f_l_o_p_p_y _d_i_s_k_s, 4-7 _f_l_u_s_h _f_u_n_c_t_i_o_n, 5-11 _I _f_o_r_k _I_1_8_N atom, 5-7 _S_e_e internationalization _f_o_r_k_s _I/_O pthreads, 5-16 asynchronous, 5-13 _F_o_r_t_r_a_n, 5-9 _i_c_o_n_v, 1-43 _f_s_c_k _I_C_R_N_L, 4-4 AdvFS, 4-45 _I_E_E_E _P_O_S_I_X _s_t_a_n_d_a_r_d_s, 8-8 _f_s_t_r_e_a_m_s _I_F_N_E_T, 4-34 bidirectional, 5-11 _I_f_r_e_e _f_i_e_l_d, 1-5 _f_t_r_u_n_c_a_t_e(), 5-13 _i_n_i_t _r_o_u_t_i_n_e_s _f_u_l_l _i_n_s_t_a_l_l_a_t_i_o_n dynamic executables, 5-2 LSM execution order, 5-2 /etc/vol/volboot, 2-6 static executables, 5-2 Prestoserve _i_n_o_d_e_s, 1-5 /etc/prestotab, 2-7 _i_n_s_t_a_l_l_a_t_i_o_n broken pipe messages, 2-4 DECnet/OSI, 2-5 _G guide, 7-1 _g_a_t_e_d, 1-31 layered products, 2-6 _g_a_t_e_w_a_y OSFBASE400.lk file, 2-6 and PPP, 7-18 _i_n_s_t_a_l_l_a_t_i_o_n _d_i_s_k, 2-2 _g_a_w_k, 4-11 _i_n_s_t_a_l_l_a_t_i_o_n _l_i_m_i_t_s, A-12 _g_e_n_d_i_s_k, 4-7 _i_n_s_t_a_l_l_u_p_d_a_t_e _c_o_m_m_a_n_d, 2-11 _G_N_U _e_m_a_c_s, 1-6 _i_n_t_e_r_l_e_a_f _d_i_s_p_l_a_y _p_r_o_b_l_e_m, 6-9 Index-4 _i_n_t_e_r_n_a_t_i_o_n_a_l_i_z_a_t_i_o_n, 4-2 _l_i_b_c._s_o CDE configuration, 1-41 pthreads, 5-14 configuration, 1-41 _l_i_b_o_t_s, 5-4 _I_S_O _C _9_4, 1-23 _l_i_b_p_t_h_r_e_a_d _I_S_O_9_9_9_6, 1-3 pthreads, 1-23 _i_s_w_a_l_n_u_m, 4-1 _l_i_b_t_l_i._a, 5-7 _i_s_w_d_i_g_i_t, 4-1 _l_i_b_t_l_i._s_o, 5-7 _I_u_s_e_d _f_i_e_l_d, 1-5 _l_i_b_x_t_i._a, 5-7 _l_i_b_x_t_i._s_o, 5-7 _l_i_g_h_t _w_e_i_g_h_t _w_i_r_i_n_g, 2-8 _K _l_i_n_k_e_r execution order, 5-2 _K_a_n_j_i, 6-17 new option, 5-2 _K_D_M_7_0 _d_i_s_k _c_o_n_t_r_o_l_l_e_r, 3-4 _l_i_n_k_i_n_g, 1-38 _k_e_r_n_e_l, 1-38 _l_i_t_h_u_a_n_i_a_n, 6-20 _k_e_r_n_e_l _b_u_i_l_d, 8-3 _l_l_o_g_i_n, 4-37 _k_e_r_n_e_l _d_e_b_u_g_g_i_n_g, 5-17 _l_o_a_d_a_b_l_e _s_u_b_s_y_s_t_e_m_s _k_e_r_n_e_l _o_b_j_e_c_t _f_i_l_e_s, 2-1, and sysconfig warning, 2-11 5-18 _k_e_y_b_o_a_r_d _l_o_c_a_l_e _s_w_i_t_c_h_i_n_g Japanese, 6-19 dxmail, 6-11 _k_e_y_m_a_p_s, 6-8 _l_o_g _h_a_l_f _f_u_l_l, 4-40 _k_i_t_t_i_n_g _g_u_i_d_e, 7-21 _l_o_g_i_c_a_l _s_t_o_r_a_g_e _m_a_n_a_g_e_r _S_e_e LSM _L_o_g_i_c_a_l _V_o_l_u_m_e _M_a_n_a_g_e_r _L _S_e_e LVM _l_a_d_e_b_u_g, 5-7 _L_S_M, 2-2, 8-9 _L_A_N_G _e_n_v_i_r_o_n_m_e_n_t _v_a_r_i_a_b_l_e, block change logging 5-11 (BCL), 4-51 _L_A_T boot failure, 4-51 dynamically loadable, 4-37 encapsulation, 1-36 kernel option, 4-37 full installation protocol, 4-37 /etc/vol/volboot, 2-6 service group codes, 4-37 kernel rebuild required, services, 4-37 4-50 shutdown command, 4-38 mirroring, 1-36 subset, 4-37 rootvol, 4-51 _L_A_T _t_t_y, 4-37 using with SWXCR-E(A/B), _l_a_t_s_e_t_u_p, 4-37 4-50 _l_a_y_e_r_e_d _p_r_o_d_u_c_t_s, 2-4 using with SWXCR-P(A/B), installation, 2-6 4-50 OSFBASE400.lk file, 2-6 volencap, 1-36 _l_i_b_c, 5-4 volrootmir, 1-36, 4-51 pthreads, 1-28 volunroot, 1-36 _l_i_b_c _l_i_b_r_a_r_y, 8-8 writing to block 0, 4-50 _l_i_b_c._a _L_u_c_i_d_a-_T_y_p_e_w_r_i_t_e_r-_m_e_d_i_u_m-_R- pthreads, 5-14 _n_o_r_m_a_l _f_o_n_t _l_i_b_c__r._a X11, 6-16 pthreads, 5-14 _L_V_M, 8-9 _l_i_b_c__r._s_o _S_e_e _a_l_s_o LSM pthreads, 5-14 _S_e_e _a_l_s_o volume encapsulation under LSM Index-5 _L_V_M (cont.) _m_u_l_t_i_l_i_n_g_u_a_l _e_m_a_c_s, 1-42 and update installation, _m_u_l_t_i_m_e_d_i_a _s_e_r_v_i_c_e_s, 4-29 2-6 _m_u_l_t_i_s_c_r_e_e_n _e_n_v_i_r_o_n_m_e_n_t, 6-8 retirement, 4-48 _m_u_l_t_i_t_h_r_e_a_d_e_d, 5-7 _L_V_M-_t_o-_L_S_M _M_i_g_r_a_t_i_o_n, 8-9 _m_u_l_t_i_t_h_r_e_a_d_e_d _c_o_d_e, 5-14 _M _N _m_a_i_l, 1-1, 4-12 _n_a_w_k, 4-11 address fuzzy matching, _n_e_m_a_c_s, 8-4 1-5 _n_e_t_s_c_a_p_e, 7-3 command behavior, 4-7 _N_e_t_s_c_a_p_e _N_a_v_i_g_a_t_o_r, 1-6 default locking, 6-11 _n_e_t_s_e_t_u_p, 4-35 maximum hop count, 4-10 _n_e_t_w_o_r_k, 4-35 _M_A_I_L_L_O_C_K_I_N_G, 6-13 CDE, 4-36 _m_a_i_l_x, 4-7 _n_e_t_w_o_r_k _a_d_m_i_n_i_s_t_r_a_t_i_o_n _m_a_n, 1-43 _m_a_n_u_a_l, 7-13 _m_a_n_d_e_l_b_r_o_t _d_e_m_o, B-1 _n_e_t_w_o_r_k _i_n_t_e_r_f_a_c_e_s, 4-35 _m_a_n_p_a_g_e _c_o_d_e_s_e_t _c_o_n_v_e_r_s_i_o_n, _n_e_t_w_o_r_k_i_n_g _l_i_m_i_t_s, A-13 1-43 _n_e_w _f_e_a_t_u_r_e_s _m_d_x_b_o_o_k, 6-18 CDE, 1-1 _m_e_d_i_a, 7-1 Exstensible SNMP, 1-32 _m_e_m_o_r_y _l_i_m_i_t_s, A-12 system management, 1-9 physical memory, A-12 _N_F_S virtual memory, A-13 AdvFS, 4-48 _m_e_t_e_r_i_n_g _c_a_p_a_b_i_l_i_t_i_e_s NFSv2, 4-38 pthreads, 5-16 _n_o_t_e_p_a_d, 6-19 _M_H resource definition file, default locking, 6-11 6-10 _M_I_B _N_T_P, 1-33 _S_e_e Host Resources MIB _n_t_p_d_a_t_e, 1-33 _m_i_r_r_o_r_i_n_g, 1-36 _n_t_p_s_e_t_u_p, 1-33 _m_k_f_d_m_n, 1-8 _M_M_E _S_e_e multimedia services _O _m_o_n_i_t_o_r, 1-27 _O__D_S_Y_N_C, 5-13 _m_o_n_i_t_o_r _p_o_w_e_r, 3-3 _O__T_R_U_N_C, 5-13 _M_o_t_i_f _o_a_w_k, 4-11 clipboard _o_b_j_e_c_t _f_i_l_e _a_d_d_r_e_s_s_e_s, 5-6 interoperability, 6-11 _o_d _c_o_m_m_a_n_d, 4-12 cut and paste, 6-11 _o_n_l_i_n_e _d_o_c_u_m_e_n_t_a_t_i_o_n, 1-6 Version 1.1.3, 8-9 _O_p_e_n _3_D, 2-10 _m_o_u_n_t, 1-8, 4-38 _O_S_F_B_A_S_E_4_0_0._l_k _f_i_l_e, 2-6 _m_r_o_u_t_e_d, 1-33 _O_S_I, 2-5 _M_S_B _d_r_i_v_e_r, 8-10, 8-9 _M_t_o_o_l_s, 1-4 _m_u_l_e _P _S_e_e multilingual emacs _m_u_l_t_i-_t_h_r_e_a_d_e_d _h_i_p_r_o_f _p_a_g_i_n_g _l_o_a_d, 6-5 atom, 5-7 _p_a_n_i_c, 2-8 AdvFS, 4-43 Index-6 _p_a_r_t_i_t_i_o_n _o_v_e_r_l_a_p _c_h_e_c_k_s, _p_p_p _d_o_c_u_m_e_n_t_a_t_i_o_n, 7-13 1-38, 1-8 _p_r_e_s_t_o_s_e_r_v_e addvol, 1-8 full installation mkfdmn, 1-8 /etc/prestotab, 2-7 mount, 1-8 _P_r_i_n_t _M_a_n_a_g_e_r, 4-22 newfs, 1-8 _p_r_i_n_t _q_u_e_u_e_s rmvol, 1-8 system administration, swapon, 1-8 4-32 voldisk, 1-8 _p_r_i_n_t_i_n_g, 1-1 voldisksetup, 1-8 Asian languages, 4-1 _p_a_r_t_i_t_i_o_n_s _p_r_o_c_e_s_s _l_i_m_i_t_s, A-13 reusing AdvFS, 4-45 _p_r_o_f, 1-27, 5-12 _p_a_s_s_w_o_r_d, 2-3 _p_r_o_p_e_r_t_y _l_i_s_t, 7-5 _p_a_s_t_i_n_g _i_n _M_o_t_i_f _p_r_o_p_l_i_s_t, 4-38 _a_p_p_l_i_c_a_t_i_o_n_s, 6-11 _p_r_o_p_l_i_s_t_d _d_a_e_m_o_n, 4-38 _p_a_t_c_h_e_s, 7-2 _p_t_h_r_e_a_d _p_a_x, 4-6 coding errors, 5-15 _P_C_I, 3-1 _p_t_h_r_e_a_d__e_x_c_e_p_t_i_o_n._h, 5-14 _P_C_M_C_I_A, 1-43 _p_t_h_r_e_a_d_s, 5-13, 5-14, 5-15, _P_e_r_f_o_r_m_a_n_c_e _M_a_n_a_g_e_r, 1-7 8-8 _p_i_p_e _s_y_s_t_e_m _c_a_l_l, 5-19 CMA, 8-8 _p_i_x_i_e, 1-25, 5-3 compilers, 5-14 -om, 5-3 dbx, 5-15 _p_o_i_n_t-_t_o-_p_o_i_n_t _p_r_o_t_o_c_o_l, exception package, 5-14 1-32 firmware, 5-16 _P_O_L_Y_C_E_N_T_E_R _A_d_v_a_n_c_e_d _F_i_l_e forks, 5-16 _S_y_s_t_e_m libc, 1-28 _S_e_e AdvFS libc.a, 5-14 _p_o_r_t_i_n_g _a_s_s_i_s_t_a_n_t, 1-30 libc_r.a, 5-14 _p_o_r_t_i_n_g _s_o_f_t_w_a_r_e, 1-30 libc_r.so, 5-14 _P_O_S_I_X libc.so, 5-14 obsolete functions, 8-10 libpthread, 1-23 sh, 4-10 missing thread routines, shell, 4-10 5-15 _P_O_S_I_X _1_0_0_3._4_a, 8-8 option to cc, 5-14 _P_O_S_I_X _1_0_0_3._1_b, 1-29, 1-30, realtime, 5-16 5-13 signal handling, 5-17 _P_O_S_I_X _1_0_0_3._1_c, 1-23, 8-8 static libraries, 5-16 _P_O_S_I_X _P_1_0_0_3._1_C, 5-14, 8-11 system cancellation __P_O_S_I_X__4_S_O_U_R_C_E, 1-30 points, 5-16 __P_O_S_I_X__C__S_O_U_R_C_E, 1-30, 5-12, thread independent 8-11 services, 1-28 _p_o_s_t_s_c_r_i_p_t Asian languages, 4-1 _p_o_s_t_s_c_r_i_p_t _b_o_o_k_s, 7-34 _Q _p_o_s_t_s_c_r_i_p_t _b_o_o_k_s _o_n_l_i_n_e, 7-29 _Q_L_O_G_I_C _I_S_P_1_0_2_0, 2-4 _p_o_w_e_r _m_a_n_a_g_e_m_e_n_t, 3-3 _q_u_o_t_a _c_o_m_m_a_n_d _r_e_t_i_r_e_m_e_n_t, _p_p_p, 1-32 8-8 _P_P_P _q_u_o_t_a _c_o_m_m_a_n_d_s and gateways, 7-18 _S_e_e AdvFS Index-7 _q_u_o_t_a _r_e_f_e_r_e_n_c_e _p_a_g_e, 7-5 _s_e_t_l_d, 1-7, 2-3, 7-22 _Q_v_i_s_i_o_n, 6-5 _s_e_t_t_i_m_e, 4-30 _s_h_m_a_t(), 5-19 _s_i_g_n_a_l _h_a_n_d_l_e_r_s _R atom, 5-7 _s_i_g_n_a_l _h_a_n_d_l_i_n_g _r_c_i_n_e_t, 4-35 pthreads, 5-17 _r_e_a_d _s_y_s_t_e_m _c_a_l_l, 5-19 _s_l_o_v_e_n_e, 1-43, 6-20 _r_e_a_l _f_u_n_c_t_i_o_n, 5-11 _S_N_M_P _r_e_a_l_t_i_m_e, 1-23, 1-29, 1-30, MIB, 1-33 5-12, 5-13 _s_n_m_p_d, 1-32 high-resolution clock, _s_o_u_n_d, 8-10 1-29 _S_p_e_c_1_1_7_0, 5-3 obsolete functions, 8-10 _s_t_a_c_k _l_i_m_i_t_s, 4-34 pthreads, 5-16 _s_t_a_n_d_a_r_d_s, 5-3 synchronized I/O, 1-29 _s_t_a_r_t_p_p_p _c_o_m_m_a_n_d _r_e_a_l_t_i_m_e _s_i_g_n_a_l_s, 1-29 use for dial-in _r_e_f_e_r_e_n_c_e _p_a_g_e_s, 7-1, 7-5 connections, 7-18 compressed, 1-5 _s_t_a_t_i_c _e_x_e_c_u_t_a_b_l_e_s, 5-2 mail_manual_setup, 7-5 _s_t_a_t_i_c _l_i_b_r_a_r_i_e_s, 5-10 _R_e_l_e_a_s_e _N_o_t_e_s, 7-1 pthreads, 5-16 _r_e_l_e_a_s_e _n_o_t_e_s, 7-1 _s_t_r_e_a_m_s, 4-34 _r_e_m_o_t_e _i_n_s_t_a_l_l_a_t_i_o_n _S_V_R_4, 4-34 _S_e_e RIS _s_w_a_p _s_p_a_c_e, 4-31 _r_i_s, 1-7 _s_w_a_p _w_a_r_n_i_n_g, 4-22 _R_I_S, 8-10 _s_w_a_p_o_n, 1-8 Chinese subsets, 2-12 _S_W_X_C_R _R_A_I_D, 3-4 server version, B-2 _s_y_m_b_o_l_i_c_a_l_l_y _l_i_n_k_e_d _k_e_r_n_e_l_s, _R_M_F_S_E_T, 4-42 4-30 _r_m_v_o_l, 1-8 _S_y_n_c_h_r_o_n_i_z_e_d _I/_O, 5-13 _r_o_o_t _d_i_s_k, 2-2 _s_y_s_c_o_n_f_i_g _m_e_s_s_a_g_e_s _r_o_o_t_v_o_l, 4-51 and loadable subsystems, 5-18 _S_y_s_M_a_n, 1-9, 4-22 _S _S_y_s_t_e_m _A_d_m_i_n _g_u_i_d_e, 7-19 _S_A__S_I_G_I_N_F_O, 5-12 _s_y_s_t_e_m _a_d_m_i_n_i_s_t_r_a_t_i_o_n _s_a_m_p_l_e _p_r_o_g_r_a_m_s, B-1 error reporting, 4-31 _S_B_C, 3-5 print queues, 4-32 hardware restriction, 3-5 _s_y_s_t_e_m _c_a_n_c_e_l_l_a_t_i_o_n _p_o_i_n_t_s _s_c_r_i_p_t_s, 4-10, 4-11 pthreads, 5-16 _S_C_S_I _d_e_v_i_c_e _n_a_m_i_n_g, 8-7 _s_y_s_t_e_m _c_l_o_c_k, 2-10 _S_C_S_I/_C_A_M _I/_O, 1-51 _s_y_s_t_e_m _m_a_n_a_g_e_m_e_n_t _G_U_I, 1-9 _s_c_s_i_m_g_r, 1-9 _s_y_s_t_e_m _m_o_n_i_t_o_r_i_n_g, 1-7 _s_e_c_u_r_i_t_y, 1-35, 2-9, 4-6, _s_y_s_t_e_m _p_a_n_i_c, 4-34 8-5 _s_y_s_t_e_m _p_e_r_f_o_r_m_a_n_c_e, 1-7 _s_e_c_u_r_i_t_y _i_n_t_e_r_f_a_c_e_s _r_e_t_i_r_i_n_g, 8-5 _s_e_g_m_e_n_t_a_t_i_o_n _f_a_u_l_t, 5-11 _T _s_e_n_d_m_a_i_l, 1-5, 4-10 _s_e_r_v_e_r, B-2 _t_c_l/_t_k, 1-23 _s_e_s_s_i_o_n, 1-1 _T_C_P, 1-32 Index-8 _T_e_c_h_n_i_c_a_l _O_v_e_r_v_i_e_w, 7-21 _V_M_E_b_u_s _d_e_v_i_c_e _d_r_i_v_e_r_s, 7-6 _t_e_l_n_e_t, 1-33 _v_m_h, 4-12 _t_e_r_m_i_n_a_l _e_m_u_l_a_t_o_r, 1-1 _v_o_l_d_i_s_k, 1-8 _t_e_r_m_i_n_f_o, 1-5 _v_o_l_d_i_s_k_s_e_t_u_p, 1-8 _T_h_a_i _v_o_l_e_n_c_a_p, 1-36 vi, 4-2 _v_o_l_r_o_o_t_m_i_r, 1-36, 4-51 _t_h_i_r_d _d_e_g_r_e_e, 5-8, 5-9 _v_o_l_u_n_r_o_o_t, 1-36 _t_h_r_e_a_d _i_n_d_e_p_e_n_d_e_n_t _s_e_r_v_i_c_e_s _v_q_u_o_t_a _r_e_f_e_r_e_n_c_e _p_a_g_e, 7-5 pthreads, 1-28 _v_r_e_s_t_o_r_e, 4-41 _t_h_r_e_a_d_s, 5-14, 5-15 _v_r_e_s_t_o_r_e _c_o_m_p_a_t_a_b_i_l_i_t_y, _S_e_e pthreads 4-40, 4-5 _t_i_c, 1-5 _t_i_p _c_o_m_m_a_n_d, 7-14 _T_L_I, 5-7 _W _T_O_Y _c_l_o_c_k, 2-10 _t_p_u_t, 1-5 _w_e_b_m_a_n, 7-3 _T_U_R_B_O_c_h_a_n_n_e_l, 8-3 _w_i_n_d_o_w _s_y_s_t_e_m _r_e_s_p_o_n_s_e, 6-5 _w_i_n_d_o_w_i_n_g _e_n_v_r_o_n_m_e_n_t _S_e_e CDE _U _w_o_r_l_d_w_i_d_e _m_a_i_l _h_a_n_d_l_e_r, 1-42 _w_r_i_t_e _s_y_s_t_e_m _c_a_l_l, 5-19 _U_F_S, 4-39, 4-41 _w_r_i_t_i_n_g _V_M_E_b_u_s _d_e_v_i_c_e _U_F_S _f_i_l_e _s_y_s_t_e_m _d_r_i_v_e_r_s, 7-6 AdvFS, 4-46 _u_f_s__f_s_c_k AdvFS, 4-45 _X _U_n_i_c_o_d_e, 1-42 _X _k_e_y_b_o_a_r_d _e_x_t_e_n_s_i_o_n _u_n_i_q_u_e _f_i_l_e _i_d_e_n_t_i_f_i_e_r_s, _S_e_e XKB 4-47 _X _s_e_r_v_e_r AdvFS, 4-47 interleaf display problem, _u_p_d_a_t_e _i_n_s_t_a_l_l, 2-11 6-9 _u_p_d_a_t_e _i_n_s_t_a_l_l_a_t_i_o_n, 2-9 _X _w_i_n_d_o_w _b_o_o_k_s, 7-34 LVM, 2-6 _X_1_1 obsolete files, B-2 Lucida-Typewriter-medium- space requirements, 2-8 R-normal font, 6-16 _u_p_d_a_t_e_i_n_s_t_a_l_l _X_1_1_R_6, 1-1 kernel object files, 2-11 _X_I_E _u_s_e_r _q_u_o_t_a_s, 4-44 Version 3.0, 8-10 _u_s_e_r_n_a_m_e _l_e_n_g_t_h, 4-26 _X_I_s_s_o _p_r_o_g_r_a_m, 8-5 /_u_s_r/_o_p_t/_s_t_e_r_l_i_n_g, 4-10 _X_K_B, 1-3 _u_t_i_l_u_p_d_a_t_e, 1-7 ISO9996, 1-3 _X_k_e_y_m_a_p_s, 6-19 _x_n_l_L_a_n_g_u_a_g_e _r_e_s_o_u_r_c_e _V CDE, 6-15 _v_d_u_m_p, 4-41 _x_n_t_p, 1-33 _v_d_u_m_p _c_o_m_p_a_t_a_b_i_l_i_t_y, 4-40, _x_n_t_p_d, 1-33 4-5 _X_P_G_4__U_N_I_X _t_a_g, 7-3 _v_e_r_i_f_y, 4-42 _X_S_y_s_A_d_m_i_n _p_r_o_g_r_a_m, 8-5 _v_i _x_t_e_r_m line wrapping, 4-2 hilite mouse tracking, Thai, 4-2 6-12 Index-9 _X_T_I, 4-35, 5-7 Index-10