Amoeba Reference Manual

Amoeba Reference Manual

The Amoeba Reference Manual System Administration Guide AMOEBA Amoeba is a registered trademark of the Vrije Universiteit in some countries. AMOEBA is a trademark of the Vrije Universiteit. Sun-3, Sun-4, NFS, SPARCclassic, SPARCstation, MicroSPARC, SunOS and Solaris" are trademarks of Sun Microsystems, Inc. SPARC is a registered trademark of SPARC International, Inc. UNIX is a trademark of Unix International. Irix and Personal Iris are trademarks of Silicon Graphics Corporation. DEC, VAX, MicroVAX, Ultrix and DEQNA are registered trademarks of Digital Equipment Corporation. Intel 386, Pentium, Multibus and Intel are trademarks of Intel Corporation. Ethernet is a registered trademark of Xerox Corporation. IBM and PC AT are registered trademarks of International Business Machines Corporation. X Window System is a trademark of the Massachusetts Institute of Technology. WD, EtherCard PLUS and EtherCard PLUS16 are trademarks of Standard Microsystems Corporation. Logitech is a trademark of Logitech, Inc. Novell is a trademark of Novell, Inc. 3Com and Etherlink II are registered trademarks of 3Com Corporation. MS-DOS is a trademark of Microsoft Corporation. Amoeba includes software developed by the University of California, Berkeley and its contributors. Copyright ! 1996 Vrije Universiteit te Amsterdam and Stichting Mathematisch Centrum, The Netherlands. All Rights Reserved. Contents Chapter 1. Using This Manual 1 Chapter 2. Installing Amoeba 2 2.1. Introduction 2 2.2. Supported Hardware Configurations 4 2.2.1. General Requirements 4 2.2.2. Supported Hardware 6 2.3. Upgrading an Amoeba Distribution 8 2.3.1. Installing the Binaries 8 2.3.2. Installing the Source Code 8 2.3.3. Installing the Kernels 9 2.3.4. Installing the New Soap and Boot Servers 9 2.4. The Binary Distribution 11 2.4.1. Installing Amoeba on Intel 80386 Systems 12 2.4.2. Installing Amoeba on the SPARCstation 18 2.4.3. Installing Amoeba on the Sun 3/60 21 2.5. Setting The Time 24 2.6. Installing the Source Code 25 2.6.1. Installing the On-line Manuals 25 2.6.2. The /super Directory Graph Structure 26 2.6.3. Amoeba Distribution Directory Structure 27 2.7. Installing Third-party Software 36 2.7.1. Installing X Windows 36 Amoeba 5.3 iii 2.7.2. Installing MMDF II 37 2.7.3. Installing TEX 37 Chapter 3. Configuring an Amoeba System 38 3.1. Introduction 38 3.2. Configuring Amoeba Hosts 38 3.2.1. Adding New Hosts 38 3.2.2. Deleting a Host 40 3.2.3. Replacing a Host 41 3.3. Server Configuration 41 3.4. Adding New Users 43 Chapter 4. Building Amoeba Configurations 45 4.1. Introduction 45 4.2. Building the Amoeba Utilities 46 4.2.1. Building X Windows 46 4.2.2. Building MMDF II 47 4.3. Building Amoeba Kernels 48 4.3.1. Configuring a Kernel 48 4.4. Building the Amoeba Documentation 54 Chapter 5. Amoeba and UNIX 55 5.1. Loading the Source Tape 56 5.2. Building the UNIX Utilities 57 5.3. Building the Amoeba Utilities under UNIX 58 5.4. The Unix Amoeba Driver 59 5.4.1. Adding Amoeba RPC to a SunOS 5.x/Solaris 2.x kernel 59 iv Amoeba 5.3 5.4.2. Adding Amoeba RPC to a SunOS 4.1.1 kernel 61 5.4.3. Adding Amoeba RPC to an Irix 3.3 Kernel 62 5.4.4. Adding Amoeba RPC to an Ultrix kernel 64 Chapter 6. Routine Maintenance 68 6.1. Backup 68 6.2. Garbage Collection 68 Chapter 7. Trouble-shooting 69 7.1. Installation Failure 69 7.2. Kernel Crashes 69 7.3. Amoeba Ð UNIX Communication 70 Chapter 8. Manual Pages 71 Chapter 9. Index 271 Amoeba 5.3 v vi Amoeba 5.3 1 Using This Manual Intended Audience This manual is intended for use by system administrators. Scope It is assumed that the reader is familiar with the introductory material in the User Guide. This manual explains how to install, configure and maintain an Amoeba system. Security, hardware, resource management and user management are all described. Advice on Using this Manual The manual is divided into several major sections. The first chapter describes how to install Amoeba or upgrade an existing Amoeba system to a new version. Check the release notes to see if the latter is possible. The introductory material explains basic things such as the supported hardware and how to build configurations. This material is necessary for understanding the installation instructions. Next come the installation instructions for the various supported architectures. It is vital that you read the introductory material and the installation guide completely before beginning so that you have an overview of the entire process and do not get any surprises on the way. The sections on adding new hosts and new users are largely self-contained but you should read the manual pages of the utilities mentioned before using them since they offer more detail about the various options. The section on porting Amoeba is for the very brave. The target machine may be the subject of a port by somebody else so ask around before beginning. It can save a lot of effort. There is a short chapter on Routine Maintenance and another on Trouble-shooting which identifies some common problems during installation and day to day runnning and how to solve them. The manual pages for utility programs are before the index. They are intended as a reference work for system administrators and should be thoroughly read to gain a good overview of the available possibilities. Throughout the manual there are references of the form prv(L), ack(U) and bullet(A). These refer to manual pages at the back of the various guides. The following table explains what each classification refers to and in which guide the manual page can be found. ¡ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ £ £ £ £ £ £ £ Letter £ Type Location ¡ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ £ £ £ (A) £ Administrative Program System Administration Guide £ £ £ (H) £ Include file Programming Guide £ £ £ (L) £ Library routine Programming Guide £ £ £ £ £ £ £ (T) £ Test Program System Administration Guide £ £ £ (U) £ User Utility User Guide ¡ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ There is a full index at the end of the manual providing a permuted cross-reference to all the material. It gives references to both the manual pages and the introductory material which should direct you to enough information to clarify any difficulties in understanding. Amoeba 5.3 1 2 Installing Amoeba 2.1. Introduction The Amoeba software consists of four major parts: The Amoeba kernel. The servers and utility programs for native Amoeba. The Amoeba FLIP driver for various UNIX kernels. The servers and utilities that run under UNIX and use Amoeba RPC. In addition to these there is documentation and a suite of test software. The distribution comes with binaries for various Amoeba configurations and the SunOS version of UNIX. Amoeba runs on various hardware platforms which are described in section 2.2. It is often possible to upgrade an existing Amoeba system to a new version. Section 2.3 describes how to do this. Check the release notes to see if it is possible to upgrade your current version to the new release. If this is not possible or if installing Amoeba for the first time then follow the instructions in section 2.4. Section 2.4 and following describes how to install Amoeba directly from the distribution medium onto the computers that will run it. The installation of the UNIX-based software, including the Amoeba network protocol in the UNIX kernel and the UNIX-based Amoeba utilities is described in the chapter Amoeba and UNIX. Installing Amoeba is not a trivial task and should be assigned to someone with some experience of system management. An understanding of how computer networks function is a great asset to understanding the process of installation. It is important to understand network structuring when configuring a system. For example, if possible, Amoeba hosts should be separated by a bridge from other systems on the same network or put on a separate network behind a gateway. This is due to the ability of Amoeba to consume the entire network bandwidth. There are some important concepts which must be understood before beginning the installation process. The most important is that Amoeba is a distributed system. Furthermore, the name server and the file server are two separate servers. The domain of an Amoeba system is effectively defined by the name server for that system, since it defines the name space for Amoeba. Therefore normally only one name server should be installed. The installation process automatically installs one file server and one name server, so it should only be run once for a local area network, unless more than one name space is explicitly desired. If additional file servers are desired they should be installed later using disklabel(A), mkfs(A), mkbootpartn(A), etc. In general it is a bad idea to put workstations or file servers in the processor pool. This will degrade their performance and therefore the performance of the entire system. If possible, try to ensure that there are enough hosts running Amoeba to leave workstations and file servers free to do their specialized tasks. Note that it is essential that you have some hosts in your processor pool. If sufficient processors are available it may also be interesting to have more than one processor pool, and so divide the available CPU power between various groups of users. It is possible to have processors of more than one architecture in a pool (so called heterogeneous pools). See run(A) for details on how to set this up. 2 Amoeba 5.3 The rest of this chapter is structured as follows.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    283 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us