 |
» |
|
|
|
This section describes post-installation tasks. For information
on installing HP-UX, refer to Installing HP-UX 10.01
and Updating HP-UX 10.0 to 10.01. Setting Up Networking | |
You need to establish the connection if your system will be
part of a network (that is, connected to other computers via Local
Area Network (LAN), Wide Area Network (WAN), or other kind of link).
A network link consists of both hardware (for example, a LAN card)
and software (for example, the LAN/9000 and Internet Services packages). Setting up the network depends on the type of network you
are using and whether you are connecting to an existing network
or setting up a new one. The Hewlett-Packard manuals you may need to refer to are listed
in the Networking Overview. Setting Up the Online Manpages | |
Depending on the desired response time to the man
command (fast, medium, or slow) and your available disk space, you
have three choices for setting up the online manpages: Fastest response to the man
command (but heaviest disk usage): Create a formatted version of all the
manpages. This is a good method if you have enough disk space to
hold the nroff
originals and the formatted pages for the time it takes to finish
formatting. To start the formatting process, enter: Formatting all the manpages can take some time, so you might
want to run the process at a lower priority. Medium response time to the
man command
(with medium disk usage): Format only heavily used sections of the manpages. To format
selected sections, enter: where sections is one or more logical
sections from the HP-UX Reference, such as
123. Slowest response to the man
command (but lightest disk usage): Do not format any manpages. HP-UX will format each manpage
the first time a user specifies the man
command to call up a page. The formatted version is used in subsequent
accesses (only if it is newer than the unformatted source file). To improve response time, you can make directories to hold
the formatted manpages. To determine the directory names you need,
check the $MANPATH
variable. For example, to create directories for the default /usr/share/man
directory, execute the following script: mkdir cat1.Z cat1m.Z cat2.Z cat3.Z cat4.Z cat5.Z cat7.Z cat8.Z cat9.Z |
You only need to create the cat8.Z
directory if /usr/share/man/man8.Z
exists. To save disk space, make sure you use the cat*.Z
directories (not cat*)
because if both cat*.Z
and cat* exist,
both directories are updated by man.
To save disk space, you can NFS mount the manpages on a remote
system. See Chapter 4, "Working with HP-UX File Systems" in this
manual for details. Regardless of how you set up the manpages, you can recover
disk space by removing the nroff
source files. (Caution: Before removing any files, make a backup
of the man directories
you created in case you need to restore any files.) For example,
to remove files for section 1 in /usr/share/man,
enter: This concept for recovering disk space applies to localized
manpages as well. For further details, see man(1)
and catman(1M). Setting Up Electronic Mail | |
Electronic mail ("email") can be run by any of these three
utilities: mailx,
elm, or mail.
See mailx(1), elm(1),
or mail(1) for details. If your users will not send mail to users on other systems
in a network, you do not need to do any setup. The mailer will do
the needed initialization when each user initially invokes the mailer. If your users will be sending and receiving mail over a network,
you need to set up routing through either UUCP or Internet Services: To configure UUCP, refer to the commercial
manuals Managing UUCP and Usenet or Using
UUCP and Usenet. See manuals(5)
for ordering instructions. To configure Internet Services, follow the directions
in Installing & Administering Internet Services.
You will also need to install the Internet Services sendmail
utility, which is described in Installing & Administering
Internet Services.
You may want to supply each mailx
and elm user
with a customization file that sets up useful defaults. Use the
following customization files: - For mailx:
(In addition, mailx
uses a system-wide defaults file /usr/lib/mailx/mailx.rc.) - For elm:
Listing Available HP-UX Documentation | |
For a listing of current HP-UX manuals (in English), see manuals(5). Setting Up Non-HP Terminals | |
For detailed information on setting up non-HP terminals, see
Configuring HP-UX for Peripherals. To set up a user with a non-HP terminal, do the following: Make sure the fileset NONHPTERM
is on the system by using either of these methods: Enter swlist -l fileset NonHP-Terminfo |
If the fileset exists, the entry for NonHP-Terminfo.NONHPTERM
will be displayed. Or, enter: ll /var/adm/sw/products/NonHP-Terminfo |
If the fileset exists, the directory /var/adm/sw/products/NonHP-Terminfo/NONHPTERM
will exist. If the fileset is not on the system, you will need to load
it from your latest HP-UX media. See Managing HP-UX Software
with SD-UX for details. Look in the directory /usr/share/lib/terminfo
for a file that corresponds to the terminal you want to set up.
For example, suppose you want to set up a user with a Wyse™
100 terminal. All supported terminals whose names begin with w
are contained in the /usr/share/lib/terminfo/w
directory. Because this directory contains an entry wy100,
you have probably found the correct file. To be sure, examine the
contents of the file with more.
You will see a screenful of special characters, but near the beginning
you will see wy100|100|wyse 100.
This verifies the correct file and shows that you can refer to the
Wyse 100 by any of the names wy100,
100, or wyse 100. If there is a terminfo
file for the terminal you want to add, skip the next step and go
to Step 4. If there is no terminfo
file for the terminal you want to add, you will need to create one.
See the next step for details. To create a terminfo
file, follow the directions in terminfo(4). To adapt an existing terminfo
file, follow these steps: Log in as superuser. Make an ASCII copy of an existing terminfo
file. For example, make a copy of the file /usr/share/lib/terminfo/w/wy100
by entering: untic /usr/share/lib/terminfo/w/wy100 > new_file |
Edit the new file to reflect the capabilities of
the new terminal. Make sure you change the name(s) of the terminal
in the first line. Compile the new terminfo
file: For more further information, see tic(1M)
and untic(1M).
Set the user's TERM
variable in the appropriate login script (either .profile
for Korn and POSIX shell users or .login
for C shell users) in their home directory to any of the names you
uncovered in Step 2. For example: export TERM=wy100 (Korn or POSIX shell) |
setenv TERM wy100 (C shell) |
The default versions of these scripts prompt the user for
the terminal type upon log in, so rather than editing the script,
you could simply tell the user to respond with the terminal name.
For example:
You can also set the TERM
variable with the /sbin/ttytype
command. See ttytype(1) for details. Setting Up news | |
/usr/bin/news
is a utility that allows you to post messages for users to read.
To use news,
do the following: Create a news
item file with your text editor and place it in the directory /var/news. Allow for users to be informed about news
items by checking the contents of the file listed below and adding
the statements if they are not there. For Korn and POSIX shell users, make sure that the
file /etc/profile
includes the following: then news -n # notify if new news. |
For C shell users, make sure that the file /etc/csh.login
includes the following: if ( -f /usr/bin/news ) then |
news -n # notify if new news. |
When users log in and there are news items they have not read,
they will see a message similar to this: where news_filename is the name
you gave the file in /var/news. Users can enter the command and the item or items will print on the screen. For more information,
see news(1). |
Printable version
