Disclaimer ---------- The following document has been passed to us by Hewlett Packard for information only, to assist Apollo/Domain and Series 700/HP-UX users who require to operate both workstation families side by side or who are planning to migrate from one to the other. The provision of this information should not be taken as a commitment by HP to provide services based on its contents. Users with particular questions Arising from this information are invited to send them to Alan Silverman ====================================================================== ====================================================================== === === === Domain/HP-UX Migration and Interoperability Lab Notes === === === === === === Last update: 2/17/92 === === === ====================================================================== ====================================================================== Contents: Boot Up and Shutdown Overview Booting & Installing from Cartridge Tape - Domain Booting & Installing from CDROM - HP-UX Instant Ignition - HP-UX Software Installation Overview Diskless Systems Overview File System Characteristics Overview System Configuration Overview Adding a SCSI DAT Drive to a Series 400 - Domain Adding a SCSI DAT Drive to a Series 700 - HP-UX (No overview section written yet for the following:) Setting up TCP/IP - Domain Setting up TCP/IP - HP-UX User Account Management - Domain User Account Management - HP-UX Host Name to Address Mapping - Domain Host Name to Address Mapping - HP-UX Setting up NFS 2.3 - Domain Setting up NFS - HP-UX Setting up BSD Print Services - Domain SR10.4 Setting up Print Services - HP-UX Sections to be added: Setting up NIS (Network Information Services) Setting up the Automounter Installing an ATR card in a Series 720 Backups Window systems, X11, HP VUE User environment files ... ====================================================================== ====================================================================== == Boot Up and Shutdown Overview == == Last update: 2/17/92 == ====================================================================== ====================================================================== This section gives an overview of system boot up and shutdown procedures on Domain/OS and HP-UX. Detailed information for Domain systems can be found in the following manuals: "Operating the Domain Personal Workstations and Servers" "Using Your Aegis/BSD/SysV Environment" "Installing Software with Apollo's Release and Installation Tools" Detailed information for HP-UX systems can be found in the following manuals: "How HP-UX Works: Concepts for the System Administrator" "Installing and Updating HP-UX 8.07" ======================================== Boot Up and Shutdown Overview Last update: 2/17/92 ======================================== Domain/OS HP-UX ----------------------------------- ----------------------------------- Boot sequence: Boot sequence: o Mnemonic Debugger (MD) loaded o Boot program loaded from boot ROM, from boot prom. initializes and tests hardware. o MD transfers control to sysboot o Boot program runs secondary loader. program which loads OS. o Secondary loader loads OS. o OS loads global libraries. o OS locates root file system. o OS starts init process as PID 1 o OS starts init process as PID 1 o init reads /etc/inittab o /etc/bcheckrc is run o /etc/brc is run o /etc/rc is run which starts o /etc/rc is run which starts daemons daemons (per contents of /etc/daemons directory), runs /etc/rc.local, runs /etc/rc.user o run /etc/ttys which loads o run /etc/getty which invokes login Display Manager (DM) and runs DM startup script ----------------------------------- ----------------------------------- System "states": System "states" (run-levels): o Lowest state - Mnemonic Debugger o Run-level "s" - single-user mode. (MD). From the MD, you can do Used for system administration things like set system clock and tasks when you don't want anyone system configuration table. else on the system. The OS is not loaded when you are o Run-level 2 - multi-user mode. in the MD. This is the normal operating mode. o Next state - Phase II boot shell. o Run-level 0 - reserved for system You get here if you boot up in installation. service mode, or if you use the o Run-levels 0, 2, and "s" are Display Manager "ex" command pre-defined. User-defined run-levels to exit the DM. This state is can be added by changing pretty much single-user mode. /etc/inittab. The OS is loaded and you have a o Use "who -r" to determine your limited set of shell commands. current run-level. This also will o When you are in the MD, the tell you what the previous run-level prompt will be an ">". was. When you are in the Phase II Example: boot shell, the prompt will > who -r be a ")". . run-level 3 3 0 2 ----------------------------------- ----------------------------------- Booting diskless: Booting diskless: See section "Diskless Systems See section "Diskless Systems Overview" Overview" ----------------------------------- ----------------------------------- Booting over the network is pretty Booting over the network can only be much the same thing as booting done as a diskless node or for a cold diskless. network install. ----------------------------------- ----------------------------------- Rebooting a node can be done in Rebooting a node can only be done several ways. Any user can by root or by users who are specified shutdown from the DM command prompt in /etc/shutdown.allow. and then load the OS. Command: shut > /etc/reboot or BEGINNING SHUTDOWN SEQUENCE... > /etc/shutdown -r SHUTDOWN SUCCESSFUL Shutdown at 12:38 (in 0 minutes) > > RE *** FINAL System shutdown message > from root@ *** (you should here a beep) System going down IMMEDIATELY MD7R REV 4.00, 1989/08/16.16:23:08 System shutdown time has arrived > EX DOMAIN_OS sync'ing disks (nn buffers to flush) 0 buffers not flushed Rebooting from a shell must be done 0 buffers still dirty by root. (You'll then see boot messages) > /etc/reboot (You'll see self test messages and then the normal boot messages) To shutdown and power off a node, To shutdown and power off a node, use "shut" at the DM command prompt use "shutdown -h" as root. You'll or "shutdown -i0" from a shell see the shutdown messages and then prompt as root. This gets you to a mesage like: the MD prompt, and then you can Halted, you may now cycle power. power off. *** WARNING *** *** WARNING *** Exit all processes and windows Exit all processes and windows before before doing a "shut" to avoid doing a reboot or shutdown to avoid losing data. You could also losing data. You could also execute execute the "sync" command the "sync" command just before the just before doing "shut" to reboot or shutdown if you really want flush system buffers to disk. to be sure that system buffers are The /etc/shutdown command flushed. does a sync (i.e., flushes system buffers to disk) for you. ================================================= Booting & Installing from Cartridge Tape - Domain Last update: 2/14/92 ================================================= Use this procedure to boot up from cartridge tape, and then install Domain/OS from cartridge tape to a clean disk. This assumes that the node you are on has a cartridge tape attached or built-in. (1) If node is up, shut it down and put it in service mode using toggle switch on back of the box. (2) Insert boot tape into cartridge tape drive and reset the node. Detailed procedure: - At the Mnemonic Debugger prompt: > RE > (you should here a beep) MD7R REV 4.00, 1989/08/16.16:23:08 > (3) Select the cartridge tape drive. If this is a new system, or you are going to initialize the disk, run the calendar utility to set the system clock so that the disk initialization creates valid UIDs. If you aren't going to initialize the disk, just select the cartridge tape drive and go to step (5) Detailed procedure: > DI C (select cartridge tape) > EX CALENDAR (interactive program, follow prompts) > RE > MD7R REV 4.00, 1989/08/16.16:23:08 (4) Initialize the disk with the invol utility. This will take maybe 30 minutes or more, depending on the size of the root disk. When invol is done, run the calendar utility to set the system clock on disk. Detailed procedure: > DI C (select cartridge tape) > EX INVOL (interactive program, follow prompts to initialize virgin volume) > RE > MD7R REV 4.00, 1989/08/16.16:23:08 > DI C (select cartridge tape) > EX CALENDAR (interactive program, follow prompts) (5) Load the minimum bootable software, then follow the prompts to install the OS. The install will prompt you to change tapes, and this process will take 2-3 hours. Detailed procedure: > EX DOMAIN_OS ) GO (prompt changes when you are at Phase II boot shell) - Login as "user" with password "-apollo-". THe system will automatically invoke an installation program which leads you through the remainder of the process. Check the transcript pad for errors when finished. (6) Log out, shutdown, switch to normal mode, then boot up. ======================================== Booting & Installing from CDROM - HP-UX Last update: 2/14/92 ======================================== Use this procedure to boot up from a CDROM, and then install HP-UX from CDROM on a Series 700. You may want to do this to create a new root disk, for example. (1) With system powered off, connect external CDROM drive (if you don't have a built-in CDROM). (2) Power on external CDROM drive, then power up system, and boot up in attended mode to select CDROM drive as boot device. Follow menus to complete the procedure. A typical install takes 2-3 hours. Root will not have a password. Login and check /tmp/update.log for any errors. Detailed procedure: - When you see start seeing boot messages, press and hold the ESCAPE key until you see "Selection Process Stopped". You'll then see a menu from which to select boot devices. - Select CDROM as boot device. NOTE: At this point, you could do a cold install over the network if you know the boot server's link level address. You'd specify that address as the boot device. - Follow the remaining menus to install the OS. *** WARNING *** You will be asked whether your root file system should use long file names (up to 255 char) or short file names (up to 14 char). If you choose short file names, you can later convert to long file names. However, you can't easily convert from long to short. Unless there is a requirement (from applications, for example), long file names is usually a good choice, especially if you will be sharing files with Domain systems. ======================================== Instant Ignition - HP-UX Last update: 2/17/92 ======================================== (1) Assemble system and power up according to installation instructions. (2) Answer questions to set timezone, host name, and Internet address. If you don't have a host name, Internet address, or time zone ready, just use the defaults and later you can enter this information by executing "/etc/set_parms " as root. The transcript below shows an example of what happens when you first bring up a Series 700 system with Instant Ignition. (3) You can login as root at this point. Root will have no password, so you may want to set one now. ------------------------------------------------------------------------------ Welcome to HP-UX! Before using your system, you will need to answer a few questions. The first question is whether you plan to use this system on a network. Answer if: * You are ready to connect the system to the network right now. Answer if: * You plan to set up this system as a standalone (no networking). * You want to use the system now as a standalone and connect to a network later. Do you want to connect this system to a network? Please type or , then press y Before you begin using this system, you need to obtain the following information from your local network administrator: * Your system name (host name). * Your internet protocol (IP) address. * Your time zone. If you do not have this information, you may stop now and restart your system once you have it. Do you wish to continue? Type for yes or for no, then type y ###################################################################### For the system to operate correctly , you must assign it a unique system name. The system name, or host name, must: * Contain no more than 8 characters. * Contain only letters, numbers, underscore (_), or dash (-). * Start with a letter. NOTE: Uppercase letters are not recommended. If you do not yet have a system name, you may select the default name of 'unknown' by pressing . Enter the system name, then press hpdemo You have chosen hpdemo as the name for this system. Is this correct? Type for yes or for no, then type y ##################################################################### If you wish networking to operate correctly, you must also assign the system a unique Internet Protocol (IP) address. The IP address must: * Contain 4 numeric components. * Have a period (.) separating each numeric component. * Contain numbers between 0 and 255. For example: 255.32.3.10 If you have not yet obtained an IP address from your local system administrator, you may use the default address of 127.0.0.1 by pressing . Enter your Internet Protocol address, then press 15.1.22.33 You have chosen 15.1.22.33 as the IP address for this system. Is this correct? Type for yes or for no, then type y ############################################################################ The following procedure will allow you to set the time zone. Select your location from the following list: 1. North America or Hawaii 2. Central America 3. South America 4. Europe 5. Africa 6. Asia 7. Australia, New Zealand Enter the number corresponding to your location (1-7), then press 1 ############################################################################ Select your time zone from the following list: 1. Newfoundland Standard/Daylight | 7. Mountain Standard Only (Arizona) | 2. Atlantic Standard/Daylight | 8. Pacific Standard/Daylight | 3. Eastern Standard/Daylight | 9. Yukon Standard/Daylight | 4. Eastern Standard (US:Indiana only) | 10. Aleutian Standard/Daylight Central Daylight | | 5. Central Standard/Daylight | 11. Hawaii Standard | 6. Mountain Standard/Daylight | 12. Unlisted time zone | | 13. Previous menu Enter the number corresponding to your time zone (1-13), then press 6 The time zone entered is Mountain Standard/Daylight. Is this correct? Type for yes or for no, then type y The current system time is Thu Feb 6 20:09:12 MST 1992 Is this correct? Type for yes or for no, then type y Congratulations! Your system is now configured for networking, with system name hpfcmmh, and IP address 15.2.72.34! To fully utilize all the networking capabilities of your system, you may have to perform some additional networking configuration. Consult your network administrator or the "HP-UX System Administration Tasks" manual for more information. The system will now complete its boot process, and allow you to login as 'root'. Press to continue. . . . GenericSysName [Release] (see /etc/issue) Console Login: ====================================================================== ====================================================================== == Software Installation Overview == == Last update: 2/17/92 == ====================================================================== ====================================================================== This section gives an overview of OS and layered software installation procedures as implemented under Domain/OS and HP-UX. Detailed information for Domain systems can be found in the following manuals: "Installing Software with Apollo's Release and Installation Tools" Detailed information for HP-UX systems can be found in the following manuals: "Installing and Updating HP-UX 8.07" ======================================== Software Installation Overview Last update: 2/17/92 ======================================== Domain/OS HP-UX ----------------------------------- ----------------------------------- Source area for software: Source area for software: o Software products are transferred o Software products come in units from media to an Authorized Area called filesets. Software can be (AA). Software is then installed installed from removable media or a from an AA to a target node. Any netdist server. Netdist servers node with enough disk space can can contain architecture-specific have an AA. AA's contain software. Any node running at least architecture-specific software. HP-UX 8.05 (for S700) and with enough disk space can be a netdist server. o The AA is usually the root dir of o Filesets contain the software to a node. The AA contains install be installed, customization scripts, tools, release documentation, and fileset dependency information. software to be installed, and Example netdist structure: configuration files. /netdist/MAIN.pkg - file listing Example AA: available filesets //node_aa = AA for a site /netdist/700/NFS-RUN/netdist.index - /install/doc/apollo - dir NFS-RUN fileset index for release notes /netdist/700/NFS-RUN/netdist.info - /install/tools - dir for NFS-RUN fileset info install tools /netdist/700/NFS-RUN/netdist.pkg - /ri.apollo.os.v.10.3 - dir NFS-RUN fileset installation containing software for script Domain/OS SR10.3 /netdist/700/NFS-RUN/product - dir containing software for NFS runtime o Release notes o Release notes (e.g., 807RelNotes) are (e.g., os.v.10.3__notes) are found found in /etc/newconfig after in /install/doc/apollo where installation is done. is the pathname to your Authorized Area. ----------------------------------- ----------------------------------- Creating source area (AA): Creating source area (netdist server): o Usually you load software from o Usually you load software from media into an AA and that's it. media into /netdist. Server must have anonymous ftp already set up (can use SAM to do this). Example, AA=//node_aa: Example: Insert tape. Insert media (tape or CDROM) Set working dir to AA Create /netdist directory > cd //node_aa > mkdir /netdist Load install tools, release index If /etc/services doesn't have an > rbak -dev c -f 1 -ms -sacl -pdt entry for netdist, add the line -l -force "netdist 2106/tcp #netdist" Determine what selection file to Run /etc/updist to load filesets. use to load the software that you You must run it once for each want, or just load all software architecture (i.e., S300, S700) > distaa -c -v //node_aa if appropriate. or When updist finishes, start > distaa -a -c -v //node_aa netdist server process. > /etc/netdist -l You'll be prompted to switch tapes. Make service available to clients You will end up with files in > cd /netdist/700/TOOL/product //node_aa/install > tar -cvf /tmp/TOOL.700 etc system > mkdir /users/ftp/dist > mv /tmp/TOOL.700 /users/ftp/dist/TOOL.700 > chmod 444 /users/ftp/dist/TOOL.700 Allow clients permission via entry in /usr/adm/inetd.sec "netdist allow " ----------------------------------- ----------------------------------- Installing software: Installing software: o Can do multiple node installs by o Software is usually installed one either pushing software to nodes node at a time, but you could from a work node, or pulling do multiple nodes remotely. software on remote nodes. o Can install interactive with o Can install interactive or install++ or non-interactive non-interactive with update. with config and install. o Installed software can be copied o Installed software is always to target node or can link from AA copied to target node. to target node (usually done for installing to the node that has the AA already on it) Example: Example install from netdist svr: > cd //my_node Get TOOL fileset from netdist svr > //node_aa/install/tools/install++ using ftp and tar. -pvx -s //node_aa > /etc/update (follow menus) -c my_config //my_node Follow the menus to select filesets. Answer the questions to select, configure, and install a product. Select products to install, Select and load filesets. configure product by choosing Check /tmp/update.log for errors. pieces to install, exit config to start install. Check transcript pad for errors. ====================================================================== ====================================================================== == Diskless Systems Overvew == == Last update: 2/17/92 == ====================================================================== ====================================================================== This section gives an overview of diskless systems as implemented under Domain/OS and HP-UX. Detailed information for Domain systems can be found in the following manuals: "Unpacking and Installing Your Domain Personal Workstations and Servers" Detailed information for HP-UX systems can be found in the following manuals: "Managing Clusters of HP 9000 Computers Sharing the HP-UX File System" ======================================== Diskless Systems Overview Last update: 2/17/92 ======================================== Domain/OS HP-UX ----------------------------------- ----------------------------------- Partner node: Cluster server: o Must be on same principal network o Must be on same subnet as cnodes that diskless nodes are on. If being served. partner node has more than one network controller, one must be chosen for principal network. o Must run appropriate OS release o Must run appropriate OS release for for diskless nodes. cnodes. o Must have appropriate /sau dir o Must have appropriate architecture for diskless ndoes (/sau specific software if serving a directories contain architecture mixed cluster. specific files.) sau2 - DN3xx sau3 - DSP90 sau4 - DN460, DN660, DSP160 sau5 - DN5xx sau6 - DN5xxT sau7 - DN3500/DN4500 sau8 - DN4000 sau9 - DN2500 sau10 - DN10000 sau11 - 425T/S, 425E 68040 sau12 - 400 68030 sau14 - DN5500 68040 o Must be running /sys/net/netman o Use SAM to configure cluster server. which are started at boot up It sets up /etc/rc to start cluster from /etc/rc.user. server processes (/etc/csp). o Optional file o SAM also configures /etc/clusterconf /sys/net/diskless_list contains which contains cnode information. node id's of diskless nodes which partner can volunteer to boot. o Diskless node specific files are o Cnode-specific files are in context- in /sys/node_data.xxxxx where dependent files (CDF's). CDFs are xxxxx is diskless node's node id. actually directories that look files. For example, /etc/inittab+ is a CDF and /etc/inittab+/my_node is the actual inittab file for cnode my_node. ----------------------------------- ----------------------------------- Diskless node: Cnode: o Must be on same principal network o Must be on same subnet as cluster that partner is on. Can choose server. Server must be configured any partner which has the right properly as a cluster server and OS software for the diskless node. must have appropriate OS for cnodes. o Can be disked (and already have o Can be disked (and already have an an OS) or diskless. OS) or diskless. o When powered up and at Mnemonic o Boot up cnode in attended mode (hold Debugger (MD) prompt, reset, a key for a few seconds as soon as specify partner's node id, then boot up messages are displayed). boot Domain/OS. You should see messages on the right, one of which tells you that > RE there is a server available. > (you should here a beep) LAN, 21, 1H SYSHPUX MD7R REV 4.00, 1989/08/16.16:23:08 1D SYSDEBUG 1B SYSBCKUP If on ATR, > DI N Choose SYSHPUX (enter 1H). or if on Ethernet > DI E Cnode should boot and you should MY NETWORK NODE ID: 0271A0 get a login prompt. NETWORK PARTNER ID: 020482 > EX DOMAIN_OS ............. xxxxx BYTES LOADED. ............. xxxxx BYTES LOADED. ... ====================================================================== ====================================================================== == File System Characteristics Overview == == Last update: 2/17/92 == ====================================================================== ====================================================================== This section gives an overview of file system characteristics as for Domain/OS and HP-UX. Detailed information for Domain systems can be found in the following manuals: "Domain/OS Design Principles" "Using your Aegis Environment" "Using your BSDEnvironment" "Using your SysV Environment" Detailed information for HP-UX systems can be found in the following manuals: "System Administration Tasks" ======================================== File System Characteristics Overview Last update: 2/17/92 ======================================== Domain/OS HP-UX ----------------------------------- ----------------------------------- Distributed file system, "Traditional" UNIX file system, NFS and CDROM file system NFS and CDROM file system also also available. available. ----------------------------------- ----------------------------------- /etc/fstab is file system table /etc/checklist is file system for /etc/mount. table for /etc/mount. Example fstab entry: Example checklist entry: /dev/dsk/W0d0s1 /mnt 4.3 rw 0 0 0 /dev/dsk/6s0 / hfs defaults 0 1 where where /dev/dsk/W0d0s1 = block special /dev/dsk/6s0 = block special file device name name /mnt = file system path for mount / = file system path for mount 4.3 = file system type hfs = file system type (4.3 for BSD4.3) (hfs for local HFS file system) rw = mount option read/write defaults = mount options 0 0 0 = ignored - included for 0 = (for future use) compatibility with /etc/mtab 1 = pass number used by fsck and for future use. ----------------------------------- ----------------------------------- Some file system utilities: Some file system utilities: invol - initialize disk volumes mediainit - initialize disk or salvol - verify and correct cartridge tape media, partition allocation of disk blocks DDS tape lvolfs - list free space on newfs - construct a new file system logical volumes fsck - file system consistency mtvol - mount logical volume check and interactive repair dmtvol - dismount logical volume df - report no. of free disk blocks df - report no. of free disk bdf - report no. of free disk blocks blocks and i-nodes (Berkeley version) mount - mount file systems mount - mount file systems umount - unmount file systems umount - unmount file systems ----------------------------------- ----------------------------------- File name lengths: File name lengths: Long file names are default. Short file names (up to 14 char) Up to 255 char per leaf name, are default. Can convert to long max of 1024 char per path name. file names (up to 255 char) from short. Can't convert from long to short without backing up files, creating a new file system with short names, then restoring files. ----------------------------------- ----------------------------------- Optional disk quota feature Optional disk quota feature available. available in SR10.4. ----------------------------------- ----------------------------------- Demand paging allows paging Configure device swap space when locally and across the network. creating a file system on a disk. No swap space is configured on File system swap space can later disk. be added but cannot be recovered until system is rebooted. ----------------------------------- ----------------------------------- Some significant UID's & GID's: Some significant UID's & GID's: name UID name UID ------------- ------------- root 0 root 0 daemon 1 daemon 1 bin 3 bin 2 uucp 4 adm 4 none 12 uucp 5 sys_person 13 lp 9 user 14 hpdb 27 (ALLBASE) admin 15 lp 16 name GID name GID ------------ ------------- wheel 0 root 0 daemon 1 other 1 bin 3 bin 2 mail 6 sys 3 staff 10 adm 4 none 12 daemon 5 sys_proj 13 mail 6 locksmith 14 lp 7 login 15 users 20 backup 16 sys_admin 17 server 18 sys 19 ----------------------------------- ----------------------------------- Files have types and are managed Files are treated as sequences by type managers. Some types are: of bytes (unstruct in the coff, cmpexe, unstruct, passwd, Domain/OS sense). obj, nil. Type managers can support extended naming to allow a type manager to interpret pathnames in a specific manner. DSEE and Domain NFS use extended naming. ----------------------------------- ----------------------------------- Links can be hard, symbolic, or Links are hard or symbolic. variant. A variant link allows an environment variable to be used as part of the link text. This is used mainly for supporting the duplicate name space of the BSD and SysV environments. For example, /bin could be a symbolic link to $(SYSTYPE)/bin. ----------------------------------- ----------------------------------- File permissions based on Access File permissions based on owner Control Lists (ACLs). ACLs are group, and other. Access rights composed of a subject identifier are read, write, execute for files. and access rights. Execute rights on directories determines who can access files in Subject identifier (SID): that directory. person.group.organization bob.rnd.eng Umask is used to determine default norm.beer.cheers permissions when files are created. joe.%.eng (% is wildcard) Required ACL entries for a file specify rights for owner, group, organization, and world. Extended ACL entries specify rights to other users, groups, and organizations. Access rights for files and directories: p (protect) - change object's ACLs k (keep) - prevent deletion or changing of name r (read) - list dir entries; read file contents w (write) - add, change, or delete dir entries; write file x (execute/search) - allow dir to be searched; execute file Initial file and directory ACLs determince ACLs of new files. If you are just using UNIX permissions, you can use umask. Example: require ACLs access rights ------------ ------------- bob.%.% (owner) prwxk %.rnd.% (group) -r-x- %.%.none (org) [ignored] %.%.% (world) ----- extended ACLs access rights ------------- ------------- bill.%.% prwxk %.backup.% -r--- Bob has all rights, rnd group has read/execute rights, none organization rights ignored, Bill has all rights, backup group has read rights. ====================================================================== ====================================================================== == System Configuration Overview == == Last update: 2/17/92 == ====================================================================== ====================================================================== This section gives an overview of some system configuration tasks for Domain/OS and HP-UX. Detailed information for Domain systems can be found in the following manuals: "Unpacking and Installing Your Domain Personal Workstations and Servers" Detailed information for HP-UX systems can be found in the following manuals: "How HP-UX Works: Concepts for the System Administrator" "Installing Peripherals" ======================================== System Configuration Overview Last update: 2/17/92 ======================================== Domain/OS HP-UX ----------------------------------- ----------------------------------- Board installation (e.g. adding Board installation (e.g., adding memory, coprocessors, etc.): memory, graphics cards, etc.): o Install board o Install board o Must run "config" utility to o ???May have to regen kernel??? update configuration table so that system knows what components to look for during power-on and diagnostic tests. ----------------------------------- ----------------------------------- Adding SCSI devices: Adding SCSI devices: *** WARNING *** Do not connect or disconnect any SCSI device while the system is running, or turn power on or off to any SCSI device while connected to a powered-up system. This could result in invalid data on the SCSI bus. ----------------------------------- ----------------------------------- Setting system clock: Setting system clock: o Can use calendar utility from o As root, use date command. Mnemonic Debugger - can be done by any user this way. *** WARNING *** o As root, use date command from "make" is sensitive to a file's a shell. date and time and to current clock. Incremental backups depend on date so *** WARNING *** they could be disrupted. Cron jobs The OS uses date & time to compute could be disrupted. unique identifiers (UID's) for OS objects. If date & time is set BACKWARDS, this could risk using a previously used date & time for a new UID resulting in undesirable (to put it mildly) system behavior. If you have to set date & time backwards, don't reboot until the previous date and time have passed. ================================================= Adding a SCSI DAT Drive to a Series 400 - Domain Last update: 2/17/92 ================================================= Use this procedure to add a SCSI DAT drive to a Domain Series 400 node. (1) Decide on and set a SCSI address for the DAT drive. You can use /systest/ssr_util/scsi_info to find addresses that are not used. The following device files are provided on SR10.3.5, SR10.4: /dev/rmts8 = SCSI ID 1, rewind on close /dev/rmts9 = SCSI ID 2, rewind on close /dev/rmts10 = SCSI ID 3, rewind on close /dev/rmts11 = SCSI ID 4, rewind on close /dev/rmts12 = SCSI ID 1, no rewind on close /dev/rmts13 = SCSI ID 2, no rewind on close /dev/rmts14 = SCSI ID 3, no rewind on close /dev/rmts15 = SCSI ID 4, no rewind on close (2) Shutdown and power off node. (3) Connect DAT drive and turn it on. (4) When DAT lights show no activity, power on the node. (5) Test access to the DAT with tar or wbak. Detailed procedure: Say you set the DAT address at 1, so you can use /dev/rmts8. Insert a tape into the drive and then execute of the following commands. You should see and hear acitivity from the DAT. > mt -f /dev/rmts8 -scsi rewind or > tar cvf /dev/rmts8 /etc/passwd or > wbak -f 1 -dev mt0 /etc/passwd ================================================= Adding a SCSI DAT Drive to a Series 700 - HP-UX Last update: 2/17/92 ================================================= Use this procedure to add a SCSI DAT drive to an HP-UX Series 700 node. (1) Decide on and set a SCSI address for the DAT drive. The following device files are provided on HP-UX 8.07: /dev/rmt/0m = SCSI ID 3, rewind on close /dev/rmt/0mn = SCSI ID 3, no rewind on close (2) Shutdown and power off node. (3) Connect DAT drive and turn it on. (4) When DAT lights show no activity, power on the node. (5) If you need to create device files for the SCSI address you've set on the DAT, use mknod to do so. Detailed procedure: Use the command "/etc/mknod /dev/rmt/ c 54 0x201x0y" to create the device file for the SCSI DAT where: /dev/rmt/ = the device file name c = character device 54 = major number for SCSI DAT 0x201x0y = minor number for SCSI DAT where x is the SCSI address of the DAT drive, and y specifies operation characteristics (2 means rewind on close, 3 means no rewind on close) Example: For SCSI DAT whose address is 4, > /etc/mknod /dev/rmt/1m c 54 0x201402 > /etc/mknod /dev/rmt/1mn c 54 0x201403 (6) Test access to the DAT with tar. Detailed procedure: Say you set the DAT address at 3, so you can use /dev/rmt/om. Insert a tape into the drive and then execute of the following commands. You should see and hear acitivity from the DAT. > mt -t /dev/rmt/0m rew or > tar cvf /dev/rmt/0m /etc/passwd ============================ Setting up TCP/IP - Domain/OS Last update: 2/6/92 ============================ Use this procedure to configure basic TCP/IP networking on a Domain/OS node. This procedure assumes your node is already up and running. What you need to know before doing this: - Internet address of your node - netmask value for your subnet - Internet address of a gateway on your subnet (0) Login as root (1) Enable TCP/IP daemons and initialize network interface and default routing Detailed procedure: Edit /etc/rc.local Uncomment the line # (/etc/tcpd >/dev/console) and comment the line (/etc/tcpd -c >/dev/console) Using your netmask, change the line # /etc/ifconfig eth0 to /etc/ifconfig eth0 `/etc/hostname` netmask defaultmask To route to HP-UX nodes, you'll have to add a static route. Using your gateway's address, change the line # /etc/route add to /etc/route add default To start TCP/IP daemons, cd to /etc/daemons and > touch tcpd inetd routed Create a minimal /etc/hosts file and add the lines 127.0.0.1 localhost defaultmask (2) Reboot your system Detailed procedure: Execute "sync" a few times to flush system buffers - this makes sure that your /etc/rc.local modifications are saved before rebooting. You can use "/etc/reboot" or "shut" at the DM command prompt to reboot. (3) Test TCP/IP connections to another system and verify routing tables. Detailed procedure: Test your systems loopback interface - > /etc/ping localhost 64 2 PING localhost: 64 data bytes 72 bytes from 127.0.0.1: icmp_seq=0. time=9. ms 72 bytes from 127.0.0.1: icmp_seq=1. time=7. ms ----localhost PING Statistics---- 2 packets transmitted, 2 packets received, 0% packet loss round-trip (ms) min/avg/max = 7/8/9 Test connections to a node on your subnet, a node on another subnet, or your gateway. Specify the IP address for ping if you haven't yet configured host name resolution or /etc/hosts. > /etc/ping 15.2.23.45 64 2 PING 15.2.23.45: 64 data bytes 72 bytes from 15.2.23.45: icmp_seq=0. time=7. ms 72 bytes from 15.2.23.45: icmp_seq=1. time=6. ms ----15.2.23.45 PING Statistics---- 2 packets transmitted, 2 packets received, 0% packet loss round-trip (ms) min/avg/max = 6/6/7 Show your system's routing table and check your gateway - > netstat -r Routing tables Destination Gateway Flags Hops Ref Use Interface USG 1 0 5194 eth0 Trouble shooting hints: 1. If you can't ping your own system (i.e., your loopback interface), make sure your physical network connection is good and that the ifconfig commands in /etc/rc.local are correct. 2. If you can't ping your gateway (you get message like "Timed out (10 seconds) waiting for echo reply), make sure the output of netstat -r is correct and that the route command(s) in /etc/rc.local are correct. Make sure the gateway node is up. ======================================== Setting up TCP/IP services - HP-UX Last update: 2/12/92 ======================================== Use this procedure to configure basic TCP/IP services on a Series 700. What you need to know before doing this: - netmask value for your subnet - Internet address of a gateway on your subnet to a Domain network Reference manuals: "Installing and Administering LAN/9000" (0) Login as root Notes: If you just got your system, powered up and went through the Instant Ignition procedure, your system will be running the Internet Services daemon, inetd. However, there will be nothing configured for subnets or TCP/IP routing. (1) Initialize network interface and default routing Detailed procedure: Edit /etc/netlinkrc. Using your netmask, change the line *) /etc/ifconfig lan0 inet `hostname` up to *) /etc/ifconfig lan0 inet `hostname` netmask up Using your gateway's address, change the line *) # add route commands for specific nodes here to *) /etc/route add default 1 This will set up static routing. If you want to use dynamic routing, use gated. (See the ARPA reference manuals.) (2) Reboot your system Detailed procedure: Execute "sync" a few times to flush system buffers - this makes sure that your /etc/netlinkrc modifications are saved before rebooting. Execute "/etc/shutdown -r 0" or "/etc/reboot -q". (3) Test TCP/IP connections to another system and verify routing tables. Detailed procedure: Test your systems loopback interface - > /etc/ping localhost 64 2 PING localhost.fc.hp.com: 64 byte packets 64 bytes from 127.0.0.1: icmp_seq=0. time=3. ms 64 bytes from 127.0.0.1: icmp_seq=1. time=3. ms ----localhost.fc.hp.com PING Statistics---- 2 packets transmitted, 2 packets received, 0% packet loss round-trip (ms) min/avg/max = 3/3/3 Test connections to a node on your subnet, a node on another subnet, or your gateway. Specify the IP address for ping if you haven't yet configured host name resolution or /etc/hosts. > /etc/ping 15.2.23.45 64 2 PING hpother.fc.hp.com: 64 byte packets 64 bytes from 15.2.23.45: icmp_seq=0. time=5. ms 64 bytes from 15.2.23.45: icmp_seq=1. time=4. ms ----15.2.23.45 PING Statistics---- 2 packets transmitted, 2 packets received, 0% packet loss round-trip (ms) min/avg/max = 4/4/5 Show your system's routing table and check your gateway - > netstat -r Routing tables Destination Gateway Flags Refs Use Interface localhost localhost UH 5 60 lo0 default UG 2 19707 lan0 Trouble shooting hints: 1. If you can't ping your own system (i.e., your loopback interface), make sure your physical network connection is good and that the ifconfig commands in /etc/netlinkrc are correct. 2. If you can't ping your gateway, make sure the output of netstat -r is correct and that the route command(s) in /etc/netlinkrc are correct. Make sure the gateway node is up. Make sure that the tcpd, inetd, and routed processes are running. =============================== User Account Managment - Domain Last update: 2/14/92 =============================== User accounts are managed by the Domain/OS Registry. Please refer to "Administering the Domain/OS Registry" for more information. ============================== User Account Managment - HP-UX Last update: 2/14/92 ============================== Use this procedure to implement user account management on an HP-UX node. There are three ways to do this in a mixed Domain/HP-UX network: Method 1: /etc/passwd, /etc/group (default) Advantages - simple, easy for small networks Disadvantages - maintaining consistent files on all nodes can be a lot of work for a large network Method 2: Using Passwd Etc (Domain registry client software for HP-UX) Advantages - allows you to administer user account information from existing Domain nodes Disadvantages - must have at least one Domain registry server on the network, must still maintain /etc/passwd and /etc/group files for other programs not included in Passwd Etc. Passwd Etc does not manage other files such as /etc/hosts. You cannot use SAM to add or change user accounts if you are using Passwd Etc. It is a layered product and not shipped with HP-UX. Passwd Etc does not run on Sun Sparcstations or IBM workstations. Method 3: NIS (Network Information Services), also known as Yellow Pages Advantages - NIS is a general mechanism for administering files such as /etc/passwd, /etc/group, /etc/hosts, ... in a large network. NIS is available on many UNIX platforms. Disadvantages - ??? Method 1: /etc/passwd, /etc/group ---------------------------------- (0) Login as root (1) Create /etc/passwd and /etc/group files that contain user account information for all users. In a mixed Domain/HP-UX network, you must make sure that UID's and GID's of users are the same between both types of systems. Use SAM or your favorite editor. Detailed procedure: 1. Get files from data in Domain registry. If you have an existing Domain network that you are going to connect to, you can use the password and group files from the Domain registry. The registry generates these files OR 1. Use SAM to add a user > sam Choose "Users ->" Choose "Add a New User Account to the System ..." Fill in login name, primary group name, home directory, startup-up program (i.e., login shell), and optional info. Select "Perform Task" Enter a password - you'll be asked to confirm it. Otherwise, you can start out with a copy of /etc/newconfig/passwd and /etc/newconfig/group. 2. Use SAM to add a group > sam Choose "Groups ->" Choose "Add a New Group to the System ..." Enter group name and login names of users to be included in this group. Select "Perform Task" OR 1. Edit /etc/passwd and /etc/group to add users and groups ass appropriate. Create home directories for users and assign ownerships and groups to these directories. Method 2: Using Passwd Etc --------------------------- Requirements to use Passwd Etc: - HP-UX system must have TCP/IP connections to a Domain network - HP-UX system must be on HP-UX 8.0, 8.05, or 8.07 - Internet routing between the HP-UX system and the Domain network must be in place - Domain network must have at least one SR10.0 or later node which is reachable from the HP-UX system via UDP/IP. This Domain node must run llbd, rgyd, and tcpd daemons. - There must be at least one IP node in the network running a glbd. Known problems: - The vuelogin patch ignores the passwd_override file. - The vuelogin patch doesn't allow you to login with no windows. (0) Login as root (1) Install the Passwd Etc software. Detailed procedure: 1. Follow the Passwd Etc release notes procedure for installing the software. 2. Install patched copies of vuelogin and vuegreet in /usr/lib/X11/vue/etc. 3. Set up a cron script on the HP-UX system which will run the passwd_refresh program regularly. There are other programs which are not shipped with Passwd Etc ??? SUCH AS WHAT ??? which still need to use the /etc/passwd file. (2) Test login. Trouble shooting hints: 1. See the Passwd Etc release notes for some procedures. 2. If the netmask of your HP-UX system is different from that of the rest of the systems on your subnet, you may find that the Passwd Etc client cannot contact the Domain registry. Check your netmask in /etc/netlinkrc and make sure it is correct. Method 3: NIS -------------- TO BE ADDED ======================================== Host Name to Address Mapping - Domain/OS Last update: 2/6/92 ======================================== Use this procedure to implement host name to address mapping. There are three ways to do this: Method 1: /etc/hosts (default) Advantages - simple, easy for small networks Disadvantages - maintaining consistent files on all nodes can be a lot of work for a large network Method 2: Using BIND name server (named), which is part of Domain Name System Advantages - commonly used in Internets, easier to maintain than maintaining /etc/hosts on all nodes Disadvantages - configuring name servers isn't necessarily trivial Method 3: NIS (Network Information Services), also known as Yellow Pages Advantages - Disadvantages - Method 1: /etc/hosts --------------------- (0) Login as root (1) Create a /etc/hosts file that contains the Internet addresses and host names (and aliases) of all hosts that you are interested in. Detailed procedure: Copy an existing /etc/hosts file to your system and add appropriate entries. To maintain /etc/hosts, you could, for example, write cron scripts to synchronize the files on all hosts from a master host. (2) Test name resolution. Detailed procedure: > /etc/ping hp_other PING hp_other: 64 byte packets 64 bytes from 15.2.23.45: icmp_seq=0. time=5. ms 64 bytes from 15.2.23.45: icmp_seq=1. time=4. ms ----hp_other PING Statistics---- 2 packets transmitted, 2 packets received, 0% packet loss round-trip (ms) min/avg/max = 4/4/5 Trouble shooting hints: 1. If ping says "/etc/ping: unknown hosts hp_other", check your /etc/hosts file for hp_other. 2. Make sure you are NOT using the name server by checking that there is no "nmconfig" file in /etc/daemons. Also, execute "/etc/nmconfig -h hostent_ascii" to turn off use of the name server. Method 2: Using BIND name server, named ---------------------------------------- Find out the locations of hosts running the named name server at your site. Setting up a name server is beyond the scope of this document. Please refer to the following manuals: "Planning for TCP/IP" "Configuring and Managing TCP/IP" (0) Login as root (1) Create a /etc/resolv.conf file that contains your domain and name server location(s). Make sure you have TCP/IP connections to the name server. Detailed procedure: Edit /etc/resolv.conf. The format is as follows: domain nameserver nameserver ... Example /etc/resolv.conf: domain fc.hp.com nameserver 15.2.99.999 # hp_svr_1 nameserver 15.3.99.999 # hp_svr_2 (2) Enable use of the name server in /etc/rc.local and /etc/daemons. Detailed procedure: Touch /etc/daemons/nmconfig. At this point, you can reboot, or execute "/etc/nmconfig -h hostent_bind". (3) Test name resolution. Detailed procedure: > /etc/ping hp_other PING hp_other: 64 data bytes 72 bytes from 15.2.23.45: icmp_seq=0. time=7. ms 72 bytes from 15.2.23.45: icmp_seq=1. time=6. ms ----hp_other PING Statistics---- 2 packets transmitted, 2 packets received, 0% packet loss round-trip (ms) min/avg/max = 6/6/7 Method 3: NIS -------------- TO BE ADDED ==================================== Host Name to Address Mapping - HP-UX Last update: 2/6/92 ==================================== Use this procedure to implement host name to address mapping. There are three ways to do this: Method 1: /etc/hosts (default) Advantages - simple, easy for small networks Disadvantages - maintaining consistent files on all nodes can be a lot of work for a large network Method 2: Using BIND name server (named), which is part of Domain Name System Advantages - commonly used in Internets, easier to maintain than maintaining /etc/hosts on all nodes Disadvantages - configuring name servers isn't necessarily trivial Method 3: NIS (Network Information Services), also known as Yellow Pages Advantages - Disadvantages - Method 1: /etc/hosts --------------------- (0) Login as root (1) Create a /etc/hosts file that contains the Internet addresses and host names (and aliases) of all hosts that you are interested in. Detailed procedure: Copy an existing /etc/hosts file to your system or copy /etc/newconfig/hosts to /etc/hosts and add appropriate entries. To maintain /etc/hosts, you could, for example, write cron scripts to synchronize the files on all hosts from a master host. (2) Test name resolution. Detailed procedure: > nslookup hp_other Using /etc/hosts on: Name: hp_other Address: 15.2.23.45 Aliases: hp_other.fc.hp.com > /etc/ping hp_other PING hp_other: 64 byte packets 64 bytes from 15.2.23.45: icmp_seq=0. time=5. ms 64 bytes from 15.2.23.45: icmp_seq=1. time=4. ms ----hp_other PING Statistics---- 2 packets transmitted, 2 packets received, 0% packet loss round-trip (ms) min/avg/max = 4/4/5 Trouble shooting hints: 1. If ping says "/etc/ping: unknown hosts hp_other", check your /etc/hosts file for hp_other. Method 2: Using BIND name server, named ---------------------------------------- Find out the locations of hosts running the named name server at your site. Setting up a name server is beyond the scope of this document. Please refer to the following manuals: "Installing and Administering LAN/9000" "Installing and Administering ARPA Services" "Using ARPA Services" (0) Login as root (1) Create a /etc/resolv.conf file that contains your domain and name server location(s). Make sure you have TCP/IP connections to the name server. Detailed procedure: Edit /etc/resolv.conf. The format is as follows: domain nameserver nameserver ... Example /etc/resolv.conf: domain fc.hp.com nameserver 15.2.99.999 # hp_svr_1 nameserver 15.3.99.999 # hp_svr_2 (2) Test name resolution. Detailed procedure: > nslookup hp_other Name Server: hp_svr_1.fc.hp.com Address: 15.2.99.999 Name: hp_other.fc.hp.com Address: 15.2.23.45 Trouble shooting hints: 1. nslookup will give a message like the following if you specify a non-existent host name or one not in your domain. Name Server: hp_svr_1.fc.hp.com Address: 15.2.99.999 *** hpfcmgw.fc.hp.com can't find hp_unknown: Non-existent domain Method 3: NIS -------------- TO BE ADDED ============================== Setting up NFS 2.3 - Domain/OS Last update: 2/6/92 ============================== Use this procedure to configure NFS remote file access on a Domain node. What you need to know before doing this: - make sure that TCP/IP has been configured and is working between this system and those who will be NFS clients and servers for this system (0) Login as root (1) Install NFS 2.3 according to the release notes. Make sure you follow all procedures for modifying the /etc/rc* files, and for creating the daemons files in /etc/daemons (i.e., portmap, nfsd, mountd, ...) (2) Edit /etc/exports to allow local file systems to be NFS mounted. If you are going to NFS mount file systems to and from HP-UX nodes, make sure that you use recommended values for write buffer sizes (wsize option to mount). On HP-UX systems mounting Domain file systems, use wsize=8192. On Domain file systems mounting HP-UX file systems, use wsize=1024. On the Domain side, this will improve performance of the Domain NFS server for large file transfers. (3) Reboot your system Detailed procedure: Execute "sync" a few times to flush system buffers - this makes sure that your /etc/netlinkrc modifications are saved before rebooting. You can use "/etc/reboot" or "shut" at the DM command prompt to reboot. (3) Test NFS mounts. Detailed procedure: See if you can access files that are NFS-mounted! ====================== Setting up NFS - HP-UX Last update: 2/6/92 ====================== Use this procedure to configure NFS remote file access on a Series 700. What you need to know before doing this: - make sure that TCP/IP has been configured and is working between this system and those who will be NFS clients and servers for this system Method 1: Use SAM ------------------ (0) Login as root (1) Use SAM to configure the HP-UX system to be an NFS server and/or an NFS client. Detailed procedure: > sam Choose "File Systems ->" Choose "NFS (Network File System) Configuration ->" Choose "Allow Remote Systems to Access Local File Systems via NFS" Choose "Allow This System to Access Remote File Systems via NFS" Choose "View/Modify Which Systems Can Access Local File Systems" Add names of systems who will be allowed to NFS-mount local file systems. To mount remote file systems now or at boot time, chose "Add (Mount) an NFS File System ..." (2) If you are going to NFS mount file systems to and from Domain nodes, make sure that you use recommended values for write buffer sizes (wsize option to mount). On HP-UX systems mounting Domain file systems, use wsize=8192. On Domain file systems mounting HP-UX file systems, use wsize=1024. On the Domain side, this will improve performance of the Domain NFS server for large file transfers. (3) Reboot your system Detailed procedure: Execute "sync" a few times to flush system buffers - this makes sure that your /etc/netlinkrc modifications are saved before rebooting. Execute "/etc/shutdown -r 0" or "/etc/reboot -q". (4) Test NFS mounts. Detailed procedure: See if you can access files that are NFS-mounted! ================================================ Setting up BSD Print Services - Domain/OS SR10.4 Last update: 2/14/92 ================================================ **** THIS PROCEDURE IS FOR BSD PRINT SERVICES ON DOMAIN/OS SR10.4 **** Use this procedure to configure BSD print services on a Domain/OS SR10.4 node. THe Domain node can be a print server (i.e., it has a printer attached to it and can allow other nodes on the network to use that printer), or a print client ((i.e., it does not have a printer attached so it uses a print server on the network). NOTE: This procedure is currently written for the use of a Laserjet printer which is attached to the parallel port on a Series 400. This requires the optional software product Laserjet 2.0. Reference manuals: "Installing Software with Apollo's Release and Installation Tools" "LaserJet PCL Printer Interface Software Release Notes" "Printing in the Domain/OS Environment: System Administrator's and Programmer's Guide" Configuring a Domain/OS SR10.4 print server ------------------------------------------- (0) Shutdown system, connect printer, power up Detailed procedure: Make sure no one else will be affected by the shutdown. Execute "/etc/shutdown 0" and then "shut" at ")" prompt, or "shut" at DM command prompt. Turn off the system. Attach the printer to the PARALLEL port on the system. Power up the printer, then the system. Login as root. (1) Login as root, confirm that TCP/IP is running, and that the Laserjet software has been installed (this is required only for a Laserjet connected to the local node.) Detailed procedure: Look for the existance of the directory /sys/laserjet. > /etc/ping count 2 (2) Allow remote access to BSD print services from remote hosts. Detailed procedure: BSD print services authorize remote access using either /etc/hosts.equiv or /etc/hosts.lpd. If /etc/hosts.equiv doesn't exist, /etc/hosts.lpd is checked. For all nodes which are allowed access to print services, enter their host names in one or both of these files. >cat /etc/hosts.lpd interop2.fc.hp.com interop3.fc.hp.com hpglue.fc.hp.com (3) Configure daemons for BSD print services: llbd, lpd. Detailed procedure: To enable BSD printing, edit /etc/rc and change the line if [-f /usr/lib/lpd -a -f /etc/daemons/lpd -a $LLBD_ENABLED=true] to if [-f bsd4.3/usr/lib/lpd -a -f /etc/daemons/lpd -a $LLBD_ENABLED=true] and change the line /usr/lib/lpd & to /bsd4.3/usr/lib/lpd & Create the daemons files (if not already created). > touch /etc/daemons/llbd > touch /etc/daemons/lpd (4) Configure /etc/printcap and input filter for BSD print services (local and remote) Detailed procedure: Configure /etc/printcap file for remote printing to a print server. Here is an example /etc/printcap entry that a print client could use for printing to an HP-UX print server named hpglue which has a Laserjet II printer called lj_II. lj_II|lj_II at hpglue|HP Laserjet II printer:\ # 1 :lp=/dev/null:\ # 2 :rm=hpglue:rp=lj_II: # 3 :sd=/usr/spool/lpd/lj_II: # 4 1 - short, full, and descriptive names for printer 2 - device name 3 - system which has remote printer, remote printer name 4 - spool directory Here is an example /etc/printcap entry that a print server could use for printing to a Laserjet III printer called laser_III connected to a parallel port. laser_III|hp_laserjet_III|HP Laserjet III printer:\ # 1 :lp=/dev/pio1:\ # 2 :if=/sys/laserjet/ljp.sh:\ # 3 :sd=/usr/spool/lpd/laser_III:\ # 4 :af=/usr/adm/lpacct:lf=/usr/adm/lpd-errs:\ # 5 :sf:sh: # 6 1 - short, full, and descriptive names for printer 2 - device name (parallel port) ** NOTE ** 3 - This line specifies an input filter which is a script called /sys/laserjet/ljp.sh. Without this filter, you would have to explicitly preprocess files to be printed with the ljp program before printing them. For example, you would have to do "ljp | lpr -Plj_II". This might be okay for local printing, but if the printer is a remote printer for other, possibly non-Domain, systems, you can't do this. To work around this problem, a script that runs ljp is used as an input filter so that all files are preprocessed. See the example below. 4 - spool directory 5 - name of accounting file, name of error log file 6 - suppress form feeds, suppress banner page Create input filter script. For example, >cat /sys/laserjet/ljp.sh #!/bin/sh # This is a shell script to set printing for the LaserJet SW 2.0 # without piping for BSD 4.3 print enviroments. # Without this script you are required to do the following to # get output to a LaserJet with this software. # >ljp | lpr -P(printer_name) /sys/laserjet/ljp (3) Create unique spooling directory for each printer Detailed procedure: Create spooling directory. > cd /usr/spool/lpd > mkdir > chown daemon > chgrp daemon > chmod 755 (4) Start daemons by rebooting or start them from the command line Detailed procedure: If llbd is not running, start it on the command line. Note that /etc/ncs/llbd is a link to /etc/ncs/rpcd in SR10.4: > /etc/server /etc/ncs/rpcd & If lpd is already running, restart it, then start a new lpd: > kill > /bsd4.3/usr/lib/lpd Configuring a Domain/OS SR10.4 print client ------------------------------------------- (0) Make sure BSD print services have been configured and that client has /etc/printcap entries for remote printing. See above. (1) Test printing to print server Detailed procedure: > lpr -P ======================================== Setting up Print Services - HP-UX Last update: 2/17/92 ======================================== Use this procedure to configure print services on an HP-UX Series 700. The HP-UX node can be a print server (i.e., it has a printer attached to it and can allow other nodes on the network to use that printer), or a print client (i.e., it does not have a printer attached so it uses a print server on the network). NOTE: This procedure is currently written for the use of a Laserjet printer which is attached to the parallel port on a Series 700. Reference manuals: Configuring an HP-UX print server --------------------------------- (0) Shutdown system, connect Laserjet printer, power up Detailed procedure: Make sure no one else will be affected by the shutdown. Execute "/etc/shutdown -h 0". Turn off the system after it's okay to power off. Attach the printer to the PARALLEL port on the system. Power up the printer, then the system. Login as root. (1) In order for this node to be a print server, TCP/IP connections must exist between it and print client nodes. Detailed procedure: > /etc/ping 64 2 (2) Configure printing with SAM. Detailed procedure: > sam Select "Peripheral Devices" Select "Printers and Plotters" Select "Add a Local Printer" Enter the printer name, printer model/interface, printer device file name, and printer priority information. Let SAM test the printer connection. Exit SAM. (3) Allowing print client nodes to use this node as a print server by configuring print services in /etc/services and /etc/inetd.conf. Detailed procedure: Make sure the following line is in /etc/services (it usually is by default): printer 515/tcp spooler # remote print spooling Make sure the following line is in /etc/inetd.conf (it is usually commented out): printer stream tcp nowait root /usr/lib/rlpdaemon rlpdaemon -i If you changed /etc/inetd.conf, execute the following command to make inetd reread /etc/inetd.conf: > /etc/inetd -c (4) Test remote printing from a client node which has had print services configured on it for remote printing. A Domain node must have BSD print services running in order to use an HP-UX print server node, and its /etc/printcap file must have the printer server's host name and printer name specified. Detailed procedure: Login to another node such as a Domain node. Try printing a file: > lpr -P Configuring an HP-UX print client --------------------------------- (0) Login as root, confirm TCP/IP connections to print server. Detailed procedure: > /etc/ping 64 2 (1) Configure printing with SAM. Detailed procedure: > sam Select "Peripheral Devices" Select "Printers and Plotters" Select "Add a Remote Printer" Enter printer name (usually same as the name used on the remote node), the name of the print server node, and the name of the print server's printer. You can make this the default printer if you wish. If the print server is a Domain node, it must be running BSD print services. If this is the case, specify that the printer is on a BSD system. The Domain print server must also have the HP-UX client's host name specified in either the /etc/hosts.equiv or /etc/hosts.lpd file. (2) Test printing to print server Detailed procedure: Let SAM do the test, or > lp -d