📄 unx33.htm
字号:
<HTML>
<HEAD>
<TITLE>UNIX Unleashed unx33.htm</TITLE>
<LINK REL="ToC" HREF="index.htm">
<LINK REL="Next" HREF="unx34.htm">
<LINK REL="Previous" HREF="unxpt7au.htm"></HEAD>
<BODY TEXT="#000000" LINK="#0000FF" VLINK="#800080" bgcolor=white>
<P><A HREF="unxpt7au.htm"><IMG SRC="bluprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>
<A HREF="index.htm"><IMG SRC="blutoc.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>
<A HREF="unx34.htm"><IMG SRC="blunext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>
<A HREF="index.htm"><IMG SRC="bluprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Home"></A>
</P><UL>
<LI>
<A HREF="#I1">33</A></LI>
<UL>
<LI>
<A HREF="#I3">UNIX Installation Basics</A></LI>
<UL>
<LI>
<A HREF="#I4">What Do I Need to Know from the Start?</A></LI>
<UL>
<LI>
<A HREF="#I5">Who Is Going to Use This System?</A></LI>
<UL>
<LI>
<A HREF="#I6">Which Type of Users</A></LI>
<LI>
<A HREF="#I7">For What Purpose?</A></LI></UL>
<LI>
<A HREF="#I8">What Other Systems Are Located on This Segment of the LAN?</A></LI>
<UL>
<LI>
<A HREF="#I9">Determining Suitable Servers</A></LI>
<LI>
<A HREF="#I10">Determining Suitable Clients</A></LI>
<LI>
<A HREF="#I11">Managing Network Traffic</A></LI></UL>
<LI>
<A HREF="#I12">Summarizing What You Need to Know Before Starting</A></LI></UL>
<LI>
<A HREF="#I13">Planning for the Installation</A></LI>
<UL>
<LI>
<A HREF="#I14">From Where Am I Going to Install?</A></LI>
<UL>
<LI>
<A HREF="#I15">Media Distribution Type</A></LI>
<LI>
<A HREF="#I16">Using a Local Device or a Remote Device for Installation</A></LI></UL>
<LI>
<A HREF="#I17">Diskless, Dataless, or Stand-Alone Server System?</A></LI>
<LI>
<A HREF="#I18">Naming the System</A></LI>
<UL>
<LI>
<A HREF="#I19">Host Name</A></LI>
<LI>
<A HREF="#I20">Domain Name (DNS/Mail)</A></LI></UL>
<LI>
<A HREF="#I21">Choosing Which Packages to Install Locally</A></LI>
<LI>
<A HREF="#I22">Laying Out the Disk Slices</A></LI></UL>
<LI>
<A HREF="#I23">Why Multiple File Systems?</A></LI>
<UL>
<UL>
<LI>
<A HREF="#I24">The root Slice</A></LI>
<LI>
<A HREF="#I25">The swap Slice</A></LI>
<LI>
<A HREF="#I26">The usr Slice</A></LI>
<LI>
<A HREF="#I27">The var Slice</A></LI>
<LI>
<A HREF="#I28">The opt Slice</A></LI>
<LI>
<A HREF="#I29">The home Slice</A></LI>
<LI>
<A HREF="#I30">The tmp Slice</A></LI>
<LI>
<A HREF="#I31">Assigning Slices to Disk Drives</A></LI></UL>
<LI>
<A HREF="#I32">Assigning IP (network) Addresses</A></LI>
<UL>
<LI>
<A HREF="#I33">Do You Have the Needed Network Connections?</A></LI></UL>
<LI>
<A HREF="#I34">Using NIS/NIS+</A></LI></UL>
<LI>
<A HREF="#I35">Performing the Installation</A></LI>
<UL>
<LI>
<A HREF="#I36">Booting the Installation Media</A></LI>
<UL>
<LI>
<A HREF="#I37">Booting from Floppies</A></LI>
<LI>
<A HREF="#I38">Booting Directly from the CD-ROM</A></LI></UL>
<LI>
<A HREF="#I39">Installing the Master System</A></LI>
<LI>
<A HREF="#I40">Installing Optional or Additional Packages</A></LI>
<UL>
<LI>
<A HREF="#I41">Using pkgadd and pkgrm</A></LI>
<LI>
<A HREF="#I42">Using swmtool</A></LI></UL>
<LI>
<A HREF="#I43">Adding a Diskless Client to a Server</A></LI>
<UL>
<LI>
<A HREF="#I44">Installing the Diskless Client Operating System Support Files</A></LI>
<LI>
<A HREF="#I45">Adding the Diskless Client</A></LI></UL></UL>
<LI>
<A HREF="#I46">Summary</A></LI></UL></UL></UL>
<H1 ALIGN="CENTER">
<CENTER><A ID="I1" NAME="I1">
<BR>
<FONT SIZE=5><A ID="I2" NAME="I2"></A><B>33</B>
<BR></FONT></A></CENTER></H1>
<H2 ALIGN="CENTER">
<CENTER><A ID="I3" NAME="I3">
<FONT SIZE=5><B>UNIX Installation Basics</B>
<BR></FONT></A></CENTER></H2>
<P>Installing a UNIX system requires a bit more planning than does installing a PC. You need to decide whether the system is autonomous (able to run without any other systems being present on a network) or how dependent it would be on the other systems on
its network. You also have to decide which parts of the UNIX system and its various utilities and application programs each user of this system will need.
<BR></P>
<P>Why? MS-DOS is a system that takes less than 10 MB of disk space. MS-Windows takes a bit more, but it's still a rather small amount. UNIX is a large system. The complete installation of just the operating system and all that comes with it for Sun's
Solaris 2.3 release, as an example, is about 300 MB. With that much disk space in use, it's often wise to share it across several systems. In addition, there are few options in installing DOS or Windows that can be made by the installer. UNIX splits the
install into many different sections, called packages. Each package consists of files that provide a specific set of features. Many packages can be installed locally, remotely on a server, or not at all, depending on your needs.
<BR></P>
<P>Whereas DOS and Windows are not designed to easily share large sections of the installation, UNIX (especially because of its disk needs) almost expects that some sharing will occur. The degree of disk space sharing leads to the definition of
stand-alone, server, dataless, and diskless systems.
<BR></P>
<P>A stand-alone system is one that is capable of operating without a connection to a local area network (LAN) and other UNIX systems. It's not that it cannot be connected; it's capable of booting and operating without any connection. This means that it
does not need to access any other UNIX system's disk for boot or operating system files and for swap space.
<BR></P>
<P>A server is also a stand-alone system. It is capable of operating without a connection to other systems. But it also generally contains some extra files, which are used by its clients.
<BR></P>
<P>The clients may only have part of the operating system installed—just enough to boot the system—and depend on the server for the remainder of the commands, utilities, and library files. Such a client is called a dataless system. It has a boot
disk and local swap space, and it is missing the remainder of the utilities and operating system.
<BR></P>
<P>If the client system has no disk drive at all, it is considered diskless. It depends on its server for booting, for the entire operating system, and for swap space.
<BR></P>
<P>In addition to sharing the operating system, UNIX systems can share other disks, such as drives containing databases or user files. Sharing these disks does not make a system a server in the "install" sense. The "server" name is
reserved for serving the operating system or its utilities. A system might be an NFS server (sharing via Network File System user files) and still be considered a stand-alone system for the installation of the UNIX operating system.
<BR></P>
<P>As an example, Sun's Solaris 2.3 requires either 27 MB, 101 MB, 158 MB, or 213 MB just to install the operating system and its utilities and documentation.
<BR></P>
<P>A diskless system does not require that any of these files be installed, as it uses them from the server. A dataless system requires that the core system support files be installed. A stand-alone system could be set up with either end-user packages or
with developer packages, whereas a server traditionally needs the entire distribution.
<BR></P>
<P>So far this chapter just touches on the disk installation. There is much more to it: planning for users, the network and its traffic, applications, printers, remote access, and much more.
<BR></P>
<P>Thus, planning for a UNIX installation requires planning not only for this one system, but for all the systems in this segment of the network.
<BR></P>
<H3 ALIGN="CENTER">
<CENTER><A ID="I4" NAME="I4">
<FONT SIZE=4><B>What Do I Need to Know from the Start?</B>
<BR></FONT></A></CENTER></H3>
<P>The first think you need to do is decide what you are going to install on this system. You decide this by looking not only at this system, but at all the systems on this segment of the network.
<BR></P>
<HR ALIGN=CENTER>
<NOTE>
<IMG SRC="note.gif" WIDTH = 35 HEIGHT = 35><B>NOTE:</B> A network segment is a group of machines all plugged into the same EtherNet, a type of LAN which uses a bus topology. Because the EtherNet uses a bus topology, each of the machines sees all the
traffic on the network. Each is local to each other and is immediately accessible via the network. Since the EtherNet LAN is only able to handle a finite amount of traffic, the network is broken into segments connected by routers or bridges. Traffic to
systems within the segment is not repeated, or retransmitted, into the other segments. Only traffic that is for systems outside the segment is repeated. With proper planning, almost all of the traffic will be internal to the segment, and more systems can
be placed on the overall network before everyone bogs down from trying to put more bytes out over the LAN than it can handle.
<BR></NOTE>
<HR ALIGN=CENTER>
<P>You base your decision about what to install on the intended usage of the system, what systems it can be served by, and for which systems it will have to provide services.
<BR></P>
<H4 ALIGN="CENTER">
<CENTER><A ID="I5" NAME="I5">
<FONT SIZE=3><B>Who Is Going to Use This System?</B>
<BR></FONT></A></CENTER></H4>
<P>Just as a PC for a user to run a spreadsheet and a word processor needs a much smaller disk and less of UNIX and its applications installed, such a UNIX system will also require less to be installed. However a power user or application developer needs
much more to be installed, perhaps including compilers and development libraries. To decide what to install on this segment of the LAN, let alone on this system, you need to determine which type of users are going to be using this system.
<BR></P>
<HR ALIGN=CENTER>
<NOTE>
<IMG SRC="imp.gif" WIDTH = 68 HEIGHT = 35><B>TIP: </B>Not only will the type of user dictate what gets installed, it will also dictate how many systems can be put on this segment of the LAN, server capacity (sizing), and swap space requirements.
<BR></NOTE>
<HR ALIGN=CENTER>
<H5 ALIGN="CENTER">
<CENTER><A ID="I6" NAME="I6">
<FONT SIZE=3><B>Which Type of Users</B>
<BR></FONT></A></CENTER></H5>
<P>UNIX users generally fall into one or more of several categories:
<BR></P>
<UL>
<LI>Application users
<BR>
<BR>These users run commercial or locally developed applications. They rarely interact with the shell directly and do not write their own applications. These users might be running a database application, a word processor or desktop publishing system, a
spreadsheet, or some in-house developed set of applications. They spend most of their time in "think" mode, where they are deciding what to do with the results the application has presented them, or in data entry mode, typing responses or data
into the system. Their need for large amounts of local disk access is minimal, and they do not change applications frequently, nor are they running many applications simultaneously. (They might have them open, but they are generally interacting with only a
couple of them at a time—the rest are waiting for the user to provide input.) Although application users might put a large load on their database servers, they do not normally put large disk loads on their own systems.
<BR>
<BR></LI>
<LI>Power users
<BR>
<BR>These users run applications, just like the application users, but they also run shell scripts and interact more closely with the system. They are likely to be running multiple applications at once, with all these applications processing in parallel.
These users keep several applications busy and access the disk more frequently and use more CPU resources than does the normal application user.
<BR>
<BR></LI>
<LI>Developers
<BR>
<BR>Developers not only run applications, they also run compilers, access different applications than do users, require access to the development libraries, and generally use more components of the operating system than do users. Furthermore, they tend to
use debugging tools that require more swap space and access to more disk resources than the application user generally needs. The UNIX operating system has packages that are only needed by developers, and if a developer is on this segment of the LAN, these
files must be installed and accessible to the systems used by these developers.
<BR>
<BR></LI></UL>
<HR ALIGN=CENTER>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -