FLOSS on NonStop User Manual

Document Organization
This document is organized as follows:
ContentsSection
This chapter provides an overview of FLOSS package.“Introduction to FLOSS” (page 8)
This chapter provides the installation procedure for
installing FLOSS package on NonStop systems.
“Installing the FLOSS Package” (page 9)
This chapter provides a brief information on how to port
a package to NonStop systems.
“Porting a Software Package Using FLOSS” (page 11)
Appendices
This appendix provides the information on FLOSS
commands and APIs.
“FLOSS Commands and APIs” (page 12)
Notation Conventions
General Syntax Notation
This list summarizes the notation conventions for syntax presentation in this manual.
UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words. Type these
items exactly as shown. Items not enclosed in brackets are required.
For example:
MAXATTACH
Italic Letters Italic letters, regardless of font, indicate variable items that you supply.
Items not enclosed in brackets are required. For example:
file-name
Computer Type Computer type letters indicate:
• C and Open System Services (OSS) keywords, commands, and
reserved words. Type these items exactly as shown. Items not
enclosed in brackets are required. For example:
Use the cextdecs.h header file.
• Text displayed by the computer. For example:
Last Logon: 14 May 2006, 08:02:23
• A listing of computer code. For example
if (listen(sock, 1) < 0)
{
perror("Listen Error");
exit(-1);
}
Bold Text Bold text in an example indicates user input typed at the terminal. For
example:
ENTER RUN CODE
?123
CODE RECEIVED: 123.00
The user must press the Return key after typing the input.
[ ] Brackets Brackets enclose optional syntax items. For example:
Document Organization 5