 |
» |
|
|
|
Most HP systems
are delivered with the operating system already installed on the
root disk; this is called instant ignition.
See “Starting A Preloaded
System”. If you ordered your system without instant ignition, you will
have to install HP-UX from a CD-ROM or DDS tape. Read the HP-UX installation
guide for your version of HP-UX to guide you through the installation
process. Once the new system is up and running, you will need to do
the tasks described under Chapter 3 “Configuring a System”. You will also need to configure the system into the local
network, and into the workgroup. The following subsections provide
help with these tasks. Configure
New Systems into the Network | |
You can use any text
editor to edit the /etc/hosts file. If you are not running BIND or NIS, you can use
SAM. If no /etc/hosts file exists on your system, copy /usr/newconfig/etc/hosts to /etc/hosts, or use ftp to copy another system’s/etc/hosts file to your system. See the ftp(1) manpage for more information. Make sure the /etc/hosts file contains the following line: 127.0.0.1 localhost loopback |
Add your own host’s IP address, name, and aliases
to the /etc/hosts file, as in the following example: 15.nn.xx.103 wszx6 patrick |
The first field is the IP address, the second is the official
host name (as returned by the hostname command), and any remaining fields are aliases. See the hosts(4) manpage. If the system has more than one network card, add a
line to /etc/hosts for each IP address. The entries for the additional cards
should have the same official host name but different aliases and
different IP addresses. Add the names of any other hosts that you need to reach.
If you will be using a BIND or NIS server on a different host, add
the name of that host. If your site uses DNS (Domain Name Service) or NIS (Network Information
Service), /etc/hosts acts as a backup resource in case the name server goes
down; so it is a good idea to add the names of systems the local
system frequently needs to reach.
Setting
Network InformationIf
you do install HP-UX onto the system yourself, or do not provide networking
information during the installation, you can add this information
later by running /sbin/set_parms initial. The program prompts you for the following information: host name and Internet protocol (IP) address. optional parameters: IP address of a Domain Name Server Network Information Service (NIS) domain name
whether to make the system a font client or font
server
You can reset networking parameters at any time by running /sbin/set_parms again and rebooting the system. See “Manually Setting Initial Information ” for a list and description of the set_parms options. If a system is having trouble communicating with other systems,
check that /etc/rc.config.d/netconf, /var/adm/inetd.sec, and /etc/hosts files all contain the correct official host name. Allowing
Access to Remote SystemsTo allow a user access
to a remote system using rcp or remsh or rlogin without supplying a password, set up an /etc/hosts.equiv or $HOME/.rhosts file on the remote system. See the hosts.equiv(4) manpage for more information. The /etc/hosts.equiv file can contain NFS netgroups. See Installing and
Administering NFS Services for more information. Users
listed in $HOME/.rhosts are allowed access to the local system, from the remote
systems and accounts named in the file, without supplying a password.
This file should be owned by the local user. In the following example, /users/spence/.rhosts resides on system wsj6700.
Users tom and patrick can log in to spence’s account on wsj6700, from ws732 and wsb2600 respectively,
without supplying a password. ws732 tom To allow an X client to
send output to an X server using the display option,
use the xhost command. For example, to allow system ws732 to
send a window to system wszx6, enter: xhosts +ws732 on system wszx6. Configure
New Systems into a Workgroup | |
To configure
a new system into a workgroup, do the following tasks: |
Printable version
