Network+ 2005 In Depth (P16) pps

Like Windows Server 2003, modern UNIX-type of systems support SMP symmetric processing.. Virtual memory in a UNIX server can take the form of a disk partition, or it can be in a file muc

Table 9-1 Minimum hardware requirements for Solaris 10

Platform Sun UltraSPARC 64-bit and Fujitsu Solaris x86 also supports AMD

SPARC64 or AMD or Intel Pentium class Opteron and Intel 64-bit

for better system performance Hard disk 5 to 7 GB

NIC A NIC supported by Solaris (included with

SPARC systems) CD-ROM/

DVD-ROM A CD-ROM or DVD-ROM drive supported

by Solaris (included with SPARC systems)

Linux Hardware Requirements

Linux hardware requirements vary to some extent based on the version of Linux you areinstalling However, all Linux servers adhere to certain minimum hardware requirements, asshown in Table 9-2 You may find more current lists of supported hardware on the HCL

(Hardware Compatibility List) at www.tldp.org/HOWTO/HOWTO-INDEX/hardware.html.

Adding high-performance video cards, sound cards, and other I/O devices to your Linux server

is also optional

Table 9-2 Minimum hardware requirements for a Linux server

Processor Intel-compatible x86 Recent versions of the Linux kernel (2.0

and later) include support for as many as 32 Intel processors.

per-formance; most network administrators opt for 256 MB of RAM or more for servers Hard disk A hard drive supported by Linux Most server implementations require

with a minimum of 2 GB of free additional free hard drive space; 10 GB of

NET+

3.1

Table 9-2 Continued

CD-ROM A CD-ROM drive listed on Recent versions of Linux support SCSI,

Floppy disk One or two 3.5-inch floppy disks, Floppy disks can be useful for creating

if no bootable CD-ROM drive is emergency repair disks during installation available

Pointing device Optional A pointing device is only necessary if you

install the GUI component.

Mac OS X Server Hardware Requirements

Mac OS X Server runs only on Apple hardware As with Solaris and Linux, your choices ofRAM, secondary storage, and other hardware considerations are driven by the number and type

of applications you will run on the server Table 9-3 shows Apple’s recommended hardware forMac OS X Server

Table 9-3 Apple hardware recommendations for Mac OS X Server

System Xserve Power Mac G3, G4,

or G5, iMac or eMac

per-forming multiple tasks.

Hard disk 4 GB available disk space Consider using larger hard drives for server

applications.

NIC Included with all Mac servers

CD-ROM/ Included with all Mac servers

DVD-ROM

A Closer Look at UNIX

UNIX is the second major network operating system discussed in this book In some ways, it

is similar to NetWare (discussed in the next chapter) and Windows Server 2003, and in someways it differs This section compares UNIX-type of systems with these other network oper-ating systems

UNIX Multiprocessing

As you have learned, a process represents an instance of a program running in memory (RAM)

In addition to processes, UNIX-type of systems also support threads, which are self-containedsubsets of a process Any modern NOS must handle multiple processes and threads in an effi-cient manner UNIX-type of systems allocate separate resources (such as memory space) to eachprocess as it is created They also manage all programs’ access to these resources This approachenables partitioning of processes in memory, thereby preventing one program from disruptingthe operation of the entire system When one program ends unexpectedly on a UNIX-type ofsystem, it doesn’t cause the whole computer to crash

Like Windows Server 2003, modern UNIX-type of systems support SMP (symmetric processing) Different flavors of UNIX support different numbers of processors:

multi-◆ Solaris supports up to 128 processors per server (although Sun does not make anyhardware containing that many processors)

◆ Linux supports SMP using a maximum of 32 processors per server

◆ Mac OS X Server supports up to two processors per server

You must know how your servers will be used and plan for multiprocessing servers according

to your estimated application-processing loads

The UNIX Memory Model

From early on, UNIX-type systems were created to use both physical and virtual memory ciently Like Windows Server 2003, UNIX-type of systems allocate a memory area for eachapplication They attempt to decrease the inefficiency of this practice, however, by sharingmemory between programs wherever they can For example, if five people are using FTP onyour UNIX server, five instances of the FTP program will run In reality, only a small part ofeach FTP program (called the private data region—the part that stores the user name, forexample) will receive its own memory space; most of the program will remain in a region ofmemory shared by all five instances of the program In this case, rather than using five timesthe memory required by one instance of the program, a UNIX-type of system sets aside only

effi-a little more memory for five FTP users theffi-an it does for one FTP user

Most current UNIX-type of systems use a 32-bit addressing scheme that enables programs toaccess 4 GB of memory Most of these systems also run on CPUs that employ 64-bit addresses,enabling programs to access more than 18 exabytes (264bytes) of memory That’s more than 18billion billion bytes of data—by one estimate, three times the total number of words ever spo-ken by human beings! Virtual memory in a UNIX server can take the form of a disk partition,

or it can be in a file (much like the virtual memory file pagefile.sys in Windows Server 2003).The UNIX Kernel

The core of all UNIX-type of systems is called the kernel The kernel is loaded into memory

and runs when you turn on your computer Its primary function is to coordinate access to all

NET+

3.1

your computer’s hardware, such as the disks, memory, keyboard, and monitor You can add orremove functionality on a running UNIX-type of system by loading and unloading kernel mod-

ules A UNIX kernel module is a file that contains instructions for performing a specific task

such as reading data from and writing data to a hard drive

The Solaris kernel is derived from the original AT&T UNIX software from Bell Labs TheLinux kernel is the software Linus Torvalds wrote and released to the public in 1991 The Mac

OS X Server kernel (called XNU) is derived from an operating system called Mach, which

was developed at Carnegie Mellon University in the 1990s

UNIX System File and Directory Structure

The UNIX system was one of the first operating systems to implement a hierarchical file tem (a method of organizing files and directories on a disk in which directories may contain

sys-files and other directories) The notion of a file system organized in this way was consideredrevolutionary at the time of UNIX’s inception Today, most operating systems, including allMicrosoft operating systems and Novell NetWare, use hierarchical file systems Figure 9-1shows a typical UNIX file system hierarchy

Chapter 9 425

A CLOSER LOOK AT UNIX

FIGURE 9-1 UNIX file system hierarchy

On a UNIX-type of system, the /boot directory contains the kernel and other system ization files Applications and services are stored in the /binand/sbindirectories (Theapplications and services in the /sbindirectory support the system initialization process; you’llrarely use these programs.) The /var directory holds variable data (such as log files, users’unread e-mail, and print jobs waiting to be printed) The file /var/log/messages, for exam-ple, stores system log messages, such as a notification of a disk drive that is running out of space.Users’ login directories typically appear in /home Mac OS X Server creates users’ login direc-tories in /Users When you create a new user account, the system assigns a directory in /home

initial-to that user (/Usersin Mac OS X Server) The login (or home) directory matches the account’suser name Thus,/home/jonesis the login (or home) directory for the user name jones on aUNIX system./Users/jones is the login (or home) directory for the user jones on a Mac OS

X Server system

NET+

3.1

UNIX System File Services

UNIX file services fall into two broad categories: disk file systems and network file systems.Disk file systems are used to organize the information on a hard drive Network file systemsenable users to access files on other servers via the network

Disk File Systems

The UNIX disk file system is the operating system’s facility for organizing, managing, andaccessing files through logical structures and software routines Just as Windows Server 2003supports FAT, NTFS, and other file systems, UNIX-type systems also support multiple file sys-

tem types The native file system type on Linux, called ext3, is the “third extended” file system

for Linux Solaris employs the file system called UFS (for “UNIX File System”) for its native file system type Apple’s HFS+ (for hierarchical file system) is the native file system for Mac

OS X Server On UNIX-type of systems, you can access disk partitions formatted with theDOS FAT file system as well as Windows Server 2003 NTFS This applies to partitions ondisks that are physically attached to computers that are running a UNIX or UNIX-type of sys-tem UNIX systems have access to nonnative file system types, such as NTFS, over the net-work with network file systems

Network File Systems

UNIX-type of systems also support network file systems, which are analogous to Windowsshares or NetWare network volumes From a UNIX-type of host, the network file systemallows you to attach shared file systems (or drives) from Windows, NetWare, or other UNIX

servers and share files with users on other computers Sun Microsystems’ NFS (Network File System) is a popular remote file system type supported by UNIX Sun Microsystems pub-

lished the specification for NFS, and most vendors of UNIX and UNIX-type systems includeNFS applications for sharing and accessing files over a network Another network file system,

called Samba, is an open source application that implements the Windows SMB and CIFS

file system protocols Samba is included with Solaris, most Linux distributions, and Mac OS

X Server systems by default

Apple’s Macintosh computers have long had a built-in network file system called AFP(AppleTalk Filing Protocol or Apple File Protocol) Though Mac OS X Server includes com-plete support for NFS and Samba network file systems, AFP remains its primary network filesystem You must use AFP on a Mac OS X Server system to share files with computers run-ning older versions of the Macintosh operating system

A UNIX Command Sampler

The command line is the primary method of interacting with a UNIX-type of system Evenwhen you’re running a GUI, the GUI actually executes commands in response to your mouseclicks This section discusses some of the basics of the UNIX user interface, interaction withthe UNIX command line, and some fundamental UNIX commands

The program that accepts the commands you type on the keyboard and runs the commands

for you is called a command interpreter Also known as a shell, a command interpreter

trans-lates your typed commands into machine instructions that a UNIX-type of system can stand In other words, the command interpreter is a program that runs other programs UNIXcommand interpreters also perform file globbing (described later) and keep track of whatcommands you’ve entered previously The primary UNIX command interpreter is the file/bin/sh To use the shell effectively, you should be familiar with at least some basic commands

under-Every UNIX-type of system contains full documentation of UNIX commands in the manual pages (or man pages) The manual pages describe each command’s function and proper exe-

cution Although their organization differs slightly in various flavors of UNIX, manual pagesare typically arranged in nine sections:

◆ Section 1 covers the commands that you most typically enter while typing in a

com-mand window

◆ Sections 2 through 5 document the programmer’s interface to the UNIX system.

◆ Section 6 documents some of the amusements and games that are included in the

UNIX system

◆ Section 7 describes the device drivers for the system.

◆ Section 8 covers the commands used by administrators to manage the system.

◆ Section 9 documents the UNIX kernel functions programmers use when writing

device drivers

You can access manual pages by entering the mancommand in a UNIX command window Forexample, to read the manual page entry for the telnetcommand, you would type man telnet

in a command window, and then press Enter

Although the UNIX manual pages are accurate and complete, UNIX newcomers often plain that they can’t find the appropriate manual page if they don’t know the name of the com-mand they want to use That’s why the aproposcommand exists It enables you to find possiblemanual page entries for the command you want to use For example, you might type apropos listto search for a command that lists files The aproposcommand would then display all

com-commands and programming functions that include the keyword list in their manual page

entries Type man <command>(where <command> is a command name displayed by apropos),and press Enter when you find a command name that looks like it might do what you want.Commands function in much the same way as sentences in ordinary language Some of thesesentences are one-word directives to the system requesting that it perform a simple task on yourbehalf (such as datefor “tell me the current date and time”) Other sentences are detailedinstructions to the system containing the equivalent of nouns, adjectives, and adverbs and cre-ating a precise description of the task you want the system to perform For example, to instructthe system to “display the names of all files in the current directory that have been accessed inthe past five days,” you would type:find –type f –atime -5 -print

Chapter 9 427

A UNIX COMMAND SAMPLER

NET+

3.1

A few rules exist to guide your use of UNIX commands and, as you might expect, exceptions

to most of the rules also exist Most commands (though not all) are lowercase alphabetic acters Using the analogy of a sentence, the command itself would be the verb—that is, theaction you want the system to take (for example,lsto list information about files) The things

char-on which you want the system to operate (often files) would be the nouns (So, for example,you would type ls index.htmlto list a file named index.html.) Options to the commands areanalogous to adjectives and adverbs—that is, modifiers that give more specifics about the com-mand To specify an option, you usually type a hyphen (-) followed by a letter (For example,

if you want to list files in a directory and also list details about the files, such as their size andcreation date, you type ls -l.) You can make commands even more specific by using file glob- bing—the equivalent to using wildcards in Windows and DOS On a UNIX-type system, this

operation is also called filename substitution (For example,ls -la*would produce a detailedlisting of all files beginning with the letter “a”.)

A significant (and perhaps initially confusing) difference between the UNIX and Windowscommand-line interfaces relates to the character you use to separate directory names when youtype in a command window The Windows separator character is “\” (backslash) The equiva-lent UNIX directory separator character is “/” (forward slash) For example, in a WindowsCommand Prompt window, you type the telnet command as \windows\system32\ telnet.exe The telnetcommand in UNIX is /usr/bin/telnet

Table 9-4 lists some common UNIX commands and provides a brief description of each

Table 9-4 Commonly used UNIX commands

ls -la Display with details all the files in the current directory.

ps -ef Display details of the current running programs.

find dir filename -print Search for filenamein the directory dirand display the path to the

filename on finding the file.

cat file Display the contents of file.

cd /d1/d2/d3 Change the current directory to d3, located in /d1/d2.

Table 9-4 Continued

cp file1 file2 Make a copy of file1, named file2.

rm file Remove (delete) file (Note that this is a permanent deletion; there

is no trash can or recycle bin from which to recover the deleted file.)

mv file1 file2 Move (or rename) file1tofile2.

mkdir dir Make a new directory named dir.

rmdir dir Remove the directory named dir.

who Display a list of users currently logged on.

vi file Use the “visual” editor named vi to edit file.

lpr file Print fileusing the default printer.lpractually places filein the

printer queue The file is actually printed by lpd (line printer mon), the UNIX printer service.

dae-grep "string" file Search for the string of characters in stringin the file named file ifconfig Display the network interface configuration, including the IP address,

MAC address, and usage statistics for all NICs in the system.

netstat -r Display the system’s TCP/IP network routing table.

sort filename Sort alphabetically the contents of filename.

man "command" Display the manual page entry for "command".

chmod rights file Change the access rights (the mode) of filetorights.

chgrp group file Change the group to which the filebelongs to group.

telnet host Start a virtual terminal connection to host(where hostmay be an

IP address or a host name).

ftp host Start an interactive file transfer to (or from) hostusing the FTP

protocol (where hostmay be an IP address or a host name).

startx Start the X Window system.

kill process Attempt to stop a running program with the process ID process.

tail file Display the last 10 lines of file.

exit Stop the current running command interpreter Log off the system if

this is the initial command interpreter started when logging is on.

The most frequently used UNIX command is ls By entering ls(and specifying -l, the detailedlisting option), you learn everything about a file except its contents UNIX-type of systems keepquite a bit of information about each file, including:

◆ The filename

◆ The file size (in bytes)

◆ The date and time that the file was created

◆ The date and time that the file was last accessed (viewed or printed)

◆ The date and time that the file contents were last modified (created, edited, orchanged in any way)

◆ The number of “aliases” or links to the file

◆ The numeric identifier of the user who owns the file

◆ The numeric identifier of the group to which the file belongs

◆ The access rights for the owner, the group, and all others

For each file, the system stores all of this information (except the filename) in a file i-node (information node) The beginning of each disk partition contains reserved space for all i-

nodes on that partition I-nodes also contain pointers to the actual file contents on the disk.The file’s name is stored in the directory that contains the file To learn about the i-nodeinformation, use the lscommand Figure 9-2 shows a sample list generated by ls -l

In Figure 9-2, the letters in the leftmost column (for example, “drwxr-xr-x”) make up the accesspermissions field The first character in the access permissions field (on the far left) indicatesthe file type Files type designations include the following:

copy, cat for concatenate, and so on), and name commands with the “initials” of their

intended use (grepfor general regular expression parser andftpfor File Transfer

Protocol) Refer to the relevant manual pages when you encounter command names

that you don’t understand The synopsis section usually indicates the origin of thecommand name

NOTE

◆ “b” for block device files (such as disk partitions)

◆ “c” for character device files (such as serial ports)

The remaining letters in the access permissions field (for example, “rwxr-xr-x”) represent thepermissions that users and groups have to access each file The meaning of these letters isdescribed in Figure 9-3’s interpretation of the output of ls -l

Windows and UNIX-type of systems share the powerful ability to direct output from one

com-mand to the input of another comcom-mand In UNIX, you combine comcom-mands using a pipe, which

is entered as a vertical bar “|” (Think of data “flowing” through a pipe from one command to

another.) Two or more commands connected by a pipe are called a pipeline UNIX pipes make

it possible to create sequences of commands that might require custom programming on othersystems For example, you can learn the process ID number assigned to a running program bycombining two simple UNIX commands as follows:ps-ef|grep "/bin/sh" In UNIX, mostcommands that display output in a command window allow you to direct the output to another

Chapter 9 431

A UNIX COMMAND SAMPLER

FIGURE 9-2 Example of output from ls -l

FIGURE 9-3 Anatomy of ls –l output

NET+

3.1

command Most commands that accept typing from your keyboard also accept input from othercommands.

Now that you have learned about commands commonly used by UNIX network tors, you are ready to plan the installation of a UNIX-type of system In many cases, you willnot need to worry about installing UNIX For example, Sun Microsystems ships its SPARCservers with Solaris already installed and Apple Computer ships Xserve servers with Mac OS

administra-X Server already installed However, if you are setting up a Linux system, chances are you willhave to install and configure it from scratch The following example of installing Linux uses apopular, free version of Linux called Fedora Core

Installing Linux

This section describes the prerequisites for and the process of installing Fedora Core, the

ver-sion of Linux packaged and distributed by Red Hat, Inc., on a PC Most PC manufacturersship their systems with Windows already installed, so it is usually necessary to install Linuxfrom CD or DVD As with other network operating systems, a successful Fedora Core instal-lation begins with planning

Planning a Linux Installation

In the preceding chapter, you learned about the importance of thorough planning in the lation of a new Windows Server 2003 server These considerations apply to Linux as well.Although making changes to the server setup after you install a Linux system is simple, youshould nevertheless plan as carefully as possible to avoid service interruption after a Linux server

instal-is running

Before installing Linux, be prepared to answer the following questions:

◆ What is the new server’s name? This name is a less important issue for Linux systems

than for Windows Server 2003 or NetWare systems, but it’s still a good idea tochoose it before beginning installation You can add the server’s name to your net-work name service (DNS, for example) as soon as you choose it (Using DNS namesrather than using IP addresses makes it easier for users to remember how to accesscomputers on the network.) You may use any name containing a maximum of 32alphanumeric characters, except the following:

> < [ ] _ : ; | = , + * ´ ?

◆ What is the server’s IP address? You’ll need this address to enable the network on the

new server Network administrators usually configure workstations to obtain an IPaddress automatically upon start-up Servers, however, are usually configured withreserved or static IP addresses because some client applications require configurationwith a server’s IP address rather than a server’s name You’ll also need the subnetmask, the IP address of the server’s primary gateway (in other words, the defaultgateway), and the IP address of the new server’s domain name server

NET+

3.1

NET+

3.1

◆ What kind of video card is installed in the server? The Linux setup program

(com-monly referred to as the “installer”) attempts to detect the video card and installs thecorrect driver if possible Otherwise, it will prompt you to choose the type of videocard from a list Either way, you should know what kind of video card your servercontains

◆ What do you want the administrative user’s password to be? Like Windows Server 2003,

Linux assigns the system a default administrative user name In Linux, this user

name is called root Choose a difficult-to-guess password for the Linux

administra-tor account Chapter 14 provides advice on choosing good passwords

◆ How can I remember all of this information? After you have answered these questions,

you should create a server installation form and keep the form with you duringinstallation Appendix D offers an example of such a form

This list highlights only the most significant installation options In addition, you should beprepared to identify your keyboard and mouse type, choose a time zone, and specify a new username After gathering the information described in this section, you’re ready to begin

Installing and Configuring Fedora Core

Although you can install Fedora Core over the network, this installation summary assumes atypical installation using DVD-ROM First verify that your computer’s BIOS configuration

is set to boot from the DVD-ROM, and then boot your system with the Fedora Core 3 disk

in your server’s DVD-ROM drive After booting, the system presents you with a welcomescreen that prompts you to press Enter to perform a check of the medium, or to skip it andbegin the installation The Fedora Core installation program leads you through the processstep-by-step Help is available in the left-hand panel Be certain to pay close attention to eachoption on each screen of the installation process During this procedure, you’re prompted toperform the following:

◆ Select the language the system will use

◆ Confirm the keyboard layout

◆ Select Server as the installation type (you could also choose Personal Workstation,Desktop, or Custom)

◆ Select disk drive partitioning options

◆ Choose booting options (to allow for more than one operating system on the drive)

◆ Configure the network interface (or interfaces)

◆ Configure the network firewall and security level options for the server

◆ Add support for additional languages

◆ Set the time and time zone for the server

◆ Enter (and confirm) the root (administrator) password

After entering the administrative “root” password, the Fedora Core installer presents you withthe Package Group Selection dialog box This dialog box includes a list of packages in several

Chapter 9 433

INSTALLING LINUX

NET+

3.1

categories You may refine your choices by clicking the Details link in the package group tion dialog box For the purpose of this installation, do not select any of the graphical desktopenvironments in the Desktops category of the Package Selection Group dialog box.

selec-The Fedora Core installer then formats the hard drive and copies the software to your server.This process may take as long as 60 minutes depending on the speed of your hardware To com-plete the installation, the Fedora Core installer prompts you to confirm the server’s auto-detected video card and monitor type When you confirm these settings, the server reboots thenew operating system When it reboots, the server is nearly ready to offer services to networkusers

The following section addresses some general system administration tasks common to type of systems These tasks must be completed before users can share resources via the server

UNIX-Administering a UNIX-Type of Server

Like Windows Server 2003 and NetWare, UNIX-type of systems require the use of user namesand passwords to connect clients to the network Also like these operating systems, UNIX-type

of systems assign access rights to groups, and allow users to be members of multiple groups

For example, the UNIX group named mail can access the electronic mail programs and

elec-tronic mail files Without user accounts, a UNIX server is little more than a powerful station This section introduces you to the setup process for administering a UNIX-type ofsystem You’ll learn:

work-◆ The basics of adding users and groups

◆ The basics of modifying file access permissions

To add users and groups to Linux and UNIX systems, you must rely on two commands:groupaddanduseradd Both are explained in their own manual pages Their names implytheir function:groupaddenables you to add a new group to the system, and useraddenablesyou to add a new user to the system The process of adding users and groups on a Mac OS XServer system is different On Mac OS X Server, you use the GUI Workgroup Manager appli-cation The following sections explain how to add users and groups on Linux or Solaris and onMac OS X Server computers

Establishing Groups and Users on Linux and Solaris

On a Linux or Solaris system, the groupaddcommand creates a new group ID and makes thegroup available for use Linux and Solaris assign a unique identification number to each group.Note that creating a new group does not automatically assign access rights to that group; you’lllearn how to accomplish that task later in this section

The steps described in this section assume that you are logged on to a Solaris or a Linux tem as the administrative user (root) and that your system has presented you with a commandprompt

sys-NET+

3.1

NET+

3.1

To add the group teachers to your Linux or Solaris system:

1. Type groupadd teachers and then press Enter at the command prompt The group

Chapter 9 435

ADMINISTERING A UNIX-TYPE OF SERVER

NET+

3.1

UNIX commands provide no response if they successfully complete the operation

You will see a response only if the command experienced an error

NOTE

Logon passwords on UNIX-type of systems are case sensitive and can include any ofthe characters on the keyboard

NOTE

To add a new user, add the user to an existing group, and assign the user a password:

1. Type useradd -m –g users -G teachers thomas and then press Enter.

2. Type passwd thomas and then press Enter.

3. Linux prompts you to type the new password As you type the password, notice thatthe characters do not appear on the screen and the cursor remains stationary Thissecurity precaution prevents people from peering over your shoulder and seeing the

password as you type it After typing the password, press Enter.

4. Linux prompts you to retype the user’s password Enter the same password again; thisconfirmation helps ensure that you type the new password accurately

To learn more about the passwd command, read the passwdmanual page, which you canaccess by typing man passwd, and press Enter at the shell prompt

Establishing Groups and Users on Mac OS X Server

You use the Workgroup Manager application to add groups and to assign users to groups on

a Mac OS X Server system Workgroup Manager is a GUI application included with Mac OS

X that allows you to manage users and groups As with Linux and Solaris, creating a newgroup on a Mac OS X Server does not assign users to that group, but makes it available foruse When you create a new group on Mac OS X Server, you assign a unique name and numeric

ID to the group As with Windows Server 2003, Solaris, and Linux, to manage users andgroups in Mac OS X Server, you must be logged on to the system as a user with administra-tive rights The following steps use the same example user account and group used in the pre-vious section

To create the group teachers on a Mac OS X Server:

1. Click on the Workgroup Manager icon in the Dock The Workgroup Manager nect window opens

Con-2. Make certain your server’s address appears in the Address text box Enter a user namewith administrator-equivalent privileges in the User Name text box and the correct

password in the Password text box, then click Connect The Workgroup Manager

window opens, with the user account selected by default

3. Click the group account icon (which depicts three people and is located above thesearch box) The group account window opens

4. Click the New Group icon.

5. In the Name text box, type teachers By default, the word “teachers” will also appear

in the Short Names text box

6. Click Save to save the new group you created.

You also use Workgroup Manager to create new user accounts on a Mac OS X Server

To create a new user account:

1. If you do not already have Workgroup Manager open, launch it by following Steps 1and 2 in the previous exercise The user account window will open by default If youdid not close Workgroup Manager after creating a group in the previous exercise, clickthe user account icon (the picture of a single person located above the search box)

2. Click the New User icon in the Workgroup Manager toolbar The user options

win-dow opens with the Basic pane selected, with default values entered for the Name,User ID, and Short Names text boxes Delete these default values Your user optionswindow will look like the one shown in Figure 9-4

3. In the Name text box, enter the user’s full name—for this example, type Thomas Day In Mac OS X Server, long user names are case sensitive when used to log on to

the server and can be no longer than 255 characters

4. In the User ID text box, enter the ID 1025 for this user In Mac OS X Server, the

user ID is a number associated with a user that the NOS uses to identify that user’sresources and privileges It can be any number between 100 and 2,147,483,640 andshould be unique for each user

NET+

3.1