Skip Navigation Links | |
Exit Print View | |
System Administration Guide: Printing Oracle Solaris 10 8/11 Information Library |
1. Introduction to Printing in the Oracle Solaris Operating System
2. Planning for Printing (Tasks)
3. Setting Up Network Printing Services (Tasks)
4. Setting Up and Administering Printers by Using Oracle Solaris Print Manager (Tasks)
5. Setting Up Printers by Using LP Print Commands (Tasks)
6. Administering Printers by Using LP Print Commands (Tasks)
7. Customizing LP Printing Services and Printers (Tasks)
8. Administering the LP Print Scheduler and Managing Print Requests (Tasks)
9. Administering Printers on a Network (Tasks)
10. Administering Character Sets, Filters, Forms, and Fonts (Tasks)
11. Administering Printers by Using the PPD File Management Utility (Tasks)
12. Printing in the Oracle Solaris Operating System (Reference)
13. Troubleshooting Printing Problems in the Oracle Solaris OS (Tasks)
System Administration Guide: Printing is part of a documentation set that covers a significant part of the Oracle Solaris system administration information. This book includes information for both SPARC and x86 based systems.
This book assumes that you have installed the Oracle Solaris operating system (OS). It also assumes that you have set up any networking software that you plan to use.
For the Oracle Solaris release, new features that are interesting to system administrators are covered in sections called What's New in ... ? in the appropriate chapters.
Note - This Oracle Solaris release supports systems that use the SPARC and x86 families of processor architectures. The supported systems appear in the Oracle Solaris OS: Hardware Compatibility Lists. This document cites any implementation differences between the platform types.
In this document, these x86 related terms mean the following:
x86 refers to the larger family of 64-bit and 32-bit x86 compatible products.
x64 relates specifically to 64-bit x86 compatible CPUs.
"32-bit x86" points out specific 32-bit information about x86 based systems.
For supported systems, see the Oracle Solaris OS: Hardware Compatibility Lists.
This book is intended for anyone responsible for administering one or more systems that are running the Oracle Solaris release. To use this book, you should have 1-2 years of UNIX system administration experience. Attending UNIX system administration training courses might be helpful.
Here is a list of the topics that are covered by the System Administration Guides.
|
Note - Oracle is not responsible for the availability of third-party web sites mentioned in this document. Oracle does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Oracle will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
The following table describes the typographic conventions that are used in this book.
Table P-1 Typographic Conventions
|
The following table shows the default UNIX system prompt and superuser prompt for shells that are included in the Oracle Solaris OS. Note that the default system prompt that is displayed in command examples varies, depending on the Oracle Solaris release.
Table P-2 Shell Prompts
|
Be aware of the following conventions that are used in this book.
When following steps or using examples, be sure to type double-quotes ("), left single-quotes (`), and right single-quotes (') exactly as shown.
The key referred to as Return is labeled Enter on some keyboards.
It is assumed that the root path includes the /sbin, /usr/sbin, /usr/bin, and /etc directories, so the steps in this book show the commands in these directories without absolute path names. Steps that use commands in other, less common, directories show the absolute path in the example.