![[Return to Library]](BOOKSHELF.GIF)
![[Contents]](TOC.GIF)
![[Previous Chapter]](REW.GIF)
![[Next Section]](NEXT.GIF)
![[Next Chapter]](FF.GIF)
![[Index]](INDEX.GIF)
![[Help]](HELP.GIF)
This chapter discusses notes that apply to Digital UNIX Version 4.0 documentation.
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.
![[Previous Section]](PREV.GIF)
The Digital UNIX distribution media is comprised of three CD-ROM discs.
Contains the following:
PostScript versions are located in the mnt_point/DOCUMENTATION/POSTSCRIPT directory. Text versions are located in the mnt_point/DOCUMENTATION/TEXT directory.
Associated software. See the Installation Guide for a description.
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 Digital UNIX Installation Guide for more information.
This section provides general information about changes to the Digital UNIX documentation set.
A number of manuals have been added to the documentation set. Refer to the Documentation Overview, Glossary and Master Index for more information.
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.
Lists of patches for known problems are provided
on the Digital UNIX Operating System Volume 1 CD-ROM,
in the directory:
<mountpoint>/DOCUMENTATION/TEXT
The files are named Digital_UNIX_V3.2C_CLD_Fixes.txt, Digital_UNIX_V3.2D-1_CLD_Fixes.txt, and Digital_UNIX_V4.0_CLD_Fixes.txt.
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 uncompress(1) or zcat(1) commands.
There is an instruction file on the CD-ROM named as follows:
/DOCUMENTATION/POSTSCRIPT/00-READ-ME-FIRST
This section provides information about the Digital UNIX Version 4.0 reference pages.
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 standards(5) reference page explains how standard-conformant and proprietary information should be differentiated in reference pages.
The [XPG4_UNIX] 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 [XPG4_UNIX] tag appears before all descriptions of standard-conformant features rather than only before descriptions of the UNIX extensions.
The Digital UNIX system's documentation CD-ROM includes a tool called webman, 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 Installation Guide, instructions for installing webman are in the following file:
/usr/share/doclib/online/DOCUMENTATION/HTML/webman/Installing_webman.txt
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 insecure_bind, which can be set either in the generic stanza of /etc/sysconfigtab, or can be set using the /sbin/sysconfig utility. The new behavior for bind() is that if insecure_bind has a value of 0 as follows:
insecure_bind=0
Then new AF_UNIX sockets have the mode set as follows:
0777 &~ umask
If insecure_bind is not set to =0, new AF_UNIX sockets have mode 0777 The default setting is insecure_bind=0.
The following ACL interfaces are mentioned in the acl(4) reference page, but do not exist. Where possible, alternatives are specified:
See the acl(4), acl_set_qualifier(3), acl_set_permset(3), acl_set_fd(3), acl_set_file(3), and acl_valid(3) reference pages.
The setproplist(3), getproplist(3), and delproplist(3) reference pages should be corrected as follows.
In the EXAMPLES section of the setproplist(3) reference page, the definition for struct proplistname_args is both incorrect (no variable) and unnecessary (only getproplist() and delproplist() use this structure.)
In the SYNOPSIS section of the getproplist(3) reference page, the int *buf argument to getproplist() should be int *min_buf_size. In the EXAMPLES section, the struct proplistname_args; definition should be struct proplistname_args getargs.
In the EXAMPLES section of the delproplist(3) reference page, the struct proplistname_args definition should be struct proplistname_args entry_names;.
In step 7 of the instructions for setting up POP, use the command create=20 to create a file called /usr/spool/pop/POP instead of a directory.
The quota and vquota reference pages show the wrong usage of options.
The correct usage for the quota reference page is as follows:
quota [ -qv ] -u username ...
quota [ -qv ] -g groupname ...
The correct usage for the vquota reference page is as follows:
vquota [ -guqv ]
vquota [ -qv ] -u username ...
vquota [ -qv -g groupname ...
The following notes apply to device driver documentation.
The following notes apply to writing VMEbus Device Drivers.
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 config.file, stanza.static, and stanza.loadable files. The syntax in the files file fragment also has changed to accommodate the single binary module in this release of Digital UNIX.
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.
Device drivers written according to Digital UNIX V4.0 single binary module technology must specify vba as the bus name when creating a controller structure. Device drivers cannot specify * for a VMEbus device driver.
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
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 csr, csr2, vector, and priority. 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 VBA_Option entry in /etc/sysconfigtab.
VBA_Option 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 vba bus number that this device driver is being installed on. In most cases the Bus_Instance 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 vba buses are detected. | |
| Driver_Name | |
| 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 create_controller_struct 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 addr1_size and addr1_atype will cause the autoconfiguration software to map the specified VMEbus address space into system I/O space. The controller structure element addr will receive the resultant io_handle_t address. This value will be passed to the device driver's probe interface. | |
| Csr2 | |
| 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 addr2_size and addr2_atype will cause the autoconfiguration software to map the specified VMEbus address space into system I/O space. The controller structure element addr2 will receive the resultant io_handle_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 ivnum 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 handler_add and handler_enable 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 bus_priority 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 handler_add and handler_enable interfaces. | |
| Type | |
| Specify the character C for this entry. This indicates the entry is for a controller. | |
| Adpt_Config | |
| Specify the character N. This entry will be used in a subsequent release of Digital UNIX. |
The VBA_Option entry below is included in /etc/sysconfigtab to provide VMEbus configuration information for the vb device driver. The vb 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 VBA_Option. 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 vb and installed on the first instance of vba as vba0. The controller is for the first instance of vb as vb0. The device driver requires no device register or memory mapping by the autoconfiguration software. This is indicated by zero being specified for Csr1 and Csr2. 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.
The Digital UNIX book Writing VMEbus Device Drivers indicates that the vb 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 /etc/sysconfigtab file must be edited and the Vector field of the VBA_Option entry for the vb driver must be changed to the 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
The /dev/dmaex 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 /dev/dmaex 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 sysconfigtab fragment for the /dev/dmaex 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.
The following files file fragment assumes the /dev/dmaex 3rd party device driver kit has been installed at /usr/opt/DM100.
MODULE/STATIC/dmaex standard Binary /usr/opt/DM100/dmaex.c module dmaex
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 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 VBA_Option. 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 dmaex and installed on the first instance of vba as vba0. The controller is for the first instance of dmaex as dmaex0.
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 Csr1 above and specifying values for addr1_size and addr1_atype in the /dev/dmaex driver structure. The mapped I/O space address, io_handle_t, is passed to dmaexprobe and stored in the controller structure's addr element. The /dev/dmaex device driver uses this I/O mapped address to access its device control and status registers. A value of zero (0) was specified for Csr2 above. Therefore, no VMEbus to CPU I/O space mapping will be performed by the autoconfiguration software for Csr2.
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 /dev/dmaex 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 ivnum and bus_priority.
See ~DOCUMENTATION/TEXT/dmaex_sample.txt on the Digital UNIX V4.0 Documentation Volume 1 CD-ROM for an example of a driver.
Section 14.1.1 of the tutorial states that you should create a directory to contain your driver source in the form of:
#
mkdir /usr/sys/io/ESA100
When you create a new directory to replace ESA100 you must place it in the path /usr/sys/io/ using your directory selection to replace ESA100.
The following notes describe changes to the Network Administration manual.
To verify that PPP is supported in the kernel, enter the following command:
#
sysconfig -s | grep ppp
If it is not loaded and configured, do the following:
ppp: nppp=2
This provides for 2 PPP connections. If your system requires a greater number of PPP connections, increase the number.
Use the instructions n the following sections instead.
After you have connected your modem to a serial port on your system, do the following:
%
tip system_name
system_name is the system name from the /etc/remote file.
AT[Return]
If the modem is not in quiet mode, it responds with an OK message.
This information is used to create a chat script, which automates the dial-out process.
string_chat_expects string_chat_sends
For example, the following file named /etc/ppp/chat-script contains the following information:
atdt2135476 [1] CONNECT [2] login: myname [3] Password: "\qmypassword" [4] "$ " "\qpppd" [5]
See chat(8) for more information on chat and chat scripts.
Note
You might want to use the tip command to dial out and log in to the remote system and to write down the exact prompt, login sequence, and pppd start-up sequence.
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]
See pppd(8) for a complete list of pppd options.
kern.debug;local2.notice /dev/console
In this example, the notice level is specified.
local2.debug /etc/ppp/ppp-log
#
/sbin/init.d/syslog stop
#
/sbin/init.d/syslog start
%
pppd /dev/tty01 38400 connect 'chat -v -f /etc/ppp/chat-script'
%
tail -f /etc/ppp/ppp-log
If any problems occur while using PPP, see Chapter 13 in Network Administration.
After you have connected your modem to a serial port on your system, to configure a dial-in system, complete the following steps:
ppp1:password:10:20:Remote PPP User:/usr/users/guest:/usr/sbin/startppp
modem:3:respawn:/usr/sbin/getty /dev/tty00 M38400 vt100
See inittab(4) for more information.
netmask dd.dd.dd.dd [1] proxyarp [2] crtscts [3] asyncmap 0 [4] :remote_ip_address [5] debug [6]
If you want to specify options for each individual serial port, create a /etc/ppp/options.ttyxx file and include the remote IP address and any other options that apply to that specific serial port. See pppd(8) for a complete list of pppd options.
If any problems occur while using PPP, see Chapter 13 in Network Administration.
The System Administration omits the following information on starting SysMan applications.
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 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 sysman_intro(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.
The following applications have a question and answer interface invoked using the following command-line argument: -ui menu. The application prompts the user interactively.
The menu interface for Mail Configuration is called mailsetup.
Finally, there are a variety of scripts invoked by commands such as SysMan Configuration Checklist and /usr/sbin/setup. They are documented in other sections of the System Administration guide.
Note that the information on Maximum System Limits has moved from the Technical Overview to the Release Notes.
The Assembly Language Programmer's Guide (Chapter 5) should include a description of the .rconst directive. This derective instructs the assembler to add subsequent data into the .rconst section. This behavior is similar to the .rdata directive, except that the entries cannot be relocatable.
In the DEC C Language Reference Manual, 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.
The following notes apply to the Guide to Preparing Product Kits. manual.
The Guide to Preparing Product Kits 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.
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 00-READ-ME-FIRST in the POSTSCRIPT directory describes how to view and print compressed files. It also lists the other PostScript files in the directory.
The following information used to be in Programming Support Tools, and was left out of the Guide to Preparing Product Kits.
This release note describes the steps the setld utility performs when executed with each of its options.
Note
The setld command's action is divided into phases. Some phases have PRE_phase and POST_phase subphases. If a given subset's PRE_phase subphase fails during any applicable operation, setld 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 POST_phase code.
When you load software by using the -l option to setld, the utility performs the following steps:
The installation control files (subset-id.ctrl, subset-id.inv, subset-id.scp, and subset-id.lk or subset-id.dw) are stored in the &./usr/.smdb. 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.
When you load a product, the next-to-last stage of the setld process is to invoke the subset's subset control program with the ACT environment variable set to C and the command argument ($1) set to INSTALL.
When you issue a command to reconfigure a subset (the -c option), setld first verifies that the specified subset exists. If it does, setld sets the ACT 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 INSTALL and DELETE. These two messages are reserved in their meaning. For special needs, a particular subset control program could be designed to accept other messages. The setld utility cannot pass other messages except in response to its -c option.
When you load a product, the final stage of the setld process is to invoke the subset's subset control program with the ACT 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), setld first verifies that the specified subset exists. If it does, setld runs the subset's Installation Verification Procedure (IVP), if there is one.
When you issue a setld -d command, the setld utility performs the following steps for each subset to be deleted:
The notes in this section refer to problems with the online help volumes.
The Help viewer has the following known problem:
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.
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:
The Using Help item on the Help menu displays a help volume supplied by CDE that explains how to use the online help.
The following known problems occur in the online help:
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.
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.
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.
The following problems apply only to help in specific applications:
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 /etc/sysconfigtab contains invalid values, you can enter the following command at the boot prompt to boot using default values:
boot -fl c
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.
The names of the gated, joind, routed, and rwhod 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.
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.
The /usr/sbin/shutdown command now sends the Shutdown Message each time a reminder is sent of the time remaining before the system is shut down.
The /etc/nologin 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.
The following corrected definitions replace the definitions in the glossary for Disk Configuration.
A deviation from a reference direction, either by design or in response to lateral forces.
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.
The following corrected definitions replace the definitions in the glossary for BIND Configuration:
A system that queries a BIND server for host name and address information, interprets the responses, and passes the information to requesting applications.
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.
Distributed Computing Environment. The capabilities of DCE are defined by the Open Software Foundation (OSF).
A logical group of systems that share services offered by DCE.
The server in a DCE cell.
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.
The Digital UNIX documentation set includes documents that are available only in PostScript format. The following list describes these documents and their locations:
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/DOCUMENTATION/POSTSCRIPT 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/DOCUMENTATION/TEXT 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 Prestoserve_for_Digital_UNIX_SPD.txt
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:
/usr/lib/emacs/doc/emacs.ps
This file is available only if the FSFEMACSSRC300 subset is installed on your system. (To use Emacs, install the OSFEMACS300 subset.)
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:
/usr/lib/emacs/doc/elisp.ps
This file is available only if the FSFEMACSSRC300 subset is installed on your system. (To use Emacs Lisp, install the OSFEMACS300 subset.)
The Display PostScript system is described in the manual PostScript Language Reference Manual 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:
/usr/share/doclib/dps
Before you can print a copy of one of the supplements, you must uncompress that supplement. For example, to uncompress the Level 2 Changes for X, issue the following command:
%
uncompress /usr/share/doclib/dps/\
Developer-TechNote.1-001.ps.Z
You can then print the resulting, uncompressed file:
/usr/share/doclib/dps/\
Developer-TechNote.1-001.ps
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:
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:
Developer-TechNote.1-001.ps.Z
This supplement describes the Type 2 image dictionary, an operand for the image operator in the Display PostScript system. The Type 2 image dictionary is an extension to the Type 1 dictionary. It allows the image 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:
Developer-TechNote.1-002.ps.Z
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:
Developer-TechNote.1-003.ps.
This supplement describes how applications can use resource paths to become easier to use and 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:
Developer-TechNote.1-004.ps.
The version 2015 supplement to the PostScript(tm) Language Reference Manual which contains all updates that manual (232pp).
2015supplement.ps.Z.
This Quick Reference card describes the command syntax and lists the available X resources, command options and keyboard commands.
ShowPSReferenceCard.ps
General instructions for installing, starting and using the Adobe ShowPS PostScript previewer. Contains tutorial material and a troubleshooting guide (72pp).
ShowPSUserGuide.ps.Z.
A sample brochure in overhead format that gives an overview of the Adobe ShowPS PostScript previewer (5pp).
ShowPS_Brochure.ps.Z.
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:
/usr/share/doclib/xie
Before you can print a copy of one of the XIE manuals, you must uncompress that manual. For example, to uncompress the X Image Extension Overview, issue the following command:
%
gzip -d /usr/share/doclib/xie/xie_overview.ps.Z
You can then print the resulting, uncompressed file:
/usr/share/doclib/xie/xie_overview.ps.
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 /usr/share/doclib/xie.
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:
/usr/share/doclib/xie/overview.ps.gz
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:
/usr/share/doclib/xie/xielib.ps.gz
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:
/usr/share/doclib/xie/xieSIarch.ps.gz
This manual specifies the X wire protocol for XIE. It defines the syntax, structure, and 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:
/usr/share/doclib/xie/XIEProto.ps.gz
OSF/Motif release notes and problems have been provided by the Open Software Foundation (OSF). These notes are contained in the following PostScript files:
These files are available only if you have installed the OSFXDEV200 subset on your system.
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:
/usr/share/doclib/dlpi/dlpi.ps.
Depending on the optional software subsets or environments installed on your system, a number of other documents may also be available in the /usr/doc
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:
<mount point>/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 already be mounted at the following location:
/usr/share/doclib/online/DOCUMENTATION/POSTSCRIPT .