1. | You'll need two Linux computers for this lab: one as an NFS server, and a second as an NFS client. Call these computers nfssvr.example.com and nfsclient.example.com. On the server, share the /home directories and provide write permissions to the client computer. On the client, set up the /home directory from the NFS server to be mounted the next time you boot that client computer. |
|
Answers
1. | This lab is the first step toward creating a single /home directory for your network. Once you get it working on a single client/server combination, you can set it up on all clients and servers. You can then use the NIS server described in Chapter 6 for a single Linux/Unix database of usernames and passwords for your network. On the NFS server, take the following steps:
|
2. | Configure an FTP server for your computer. Make sure to allow only anonymous access. Don't allow anonymous users to upload to your server. Enable messages when users access your /var/ftp and /var/ftp/pub directories. Add an appropriate one-line message to each directory. Test the result, preferably from a remote computer. Start the vsFTP server and see that it starts automatically the next time you reboot your computer. |
|
Answers
2. | The vsFTP server is part of a simple package group. So if you have not installed this server during the installation process, the quickest thing to do is to connect to your installation source (CD or network) and install it from that location. For example, if the source is mounted on /mnt/source, you'd install it with the following command:
# rpm --Uvh /mnt/source/Server/vsftpd-* This also installs configuration files in the /etc and /etc/vsftpd directories. The main configuration file is /etc/vsftpd/vsftpd.conf. Based on the RHEL default version of this file, you can make the following changes. To allow only anonymous access, comment out the following line:
local_enable=yes Anonymous users are already prevented from uploading files to your server. You could enable it by activating the anon_upload_enable=yes command. By default, messages are already enabled for directory access on an FTP server, courtesy of the following command:
dirmessage_enable=yes Actually configuring a message is a matter of creating a text file and saving it as .message in the desired directories, /var/ftp and /var/ftp/pub. You could add a simple line such as "root directory for the FTP server" or "main download directory." Finally, to configure the Red Hat FTP server to start, run the service vsftpd start command. To make sure it starts the next time you boot your computer, run the chkconfig vsftpd on command. |
3. | This is a multi-part lab. Part 1: Installing and Starting Samba
Part 2: Configuring Samba's Global Settings
Part 3: Configuring File Shares
Part 4: Setting Up Printer Shares
Part 5: Verifying the smb.conf File
Again, go back and make revisions if the test program indicates problems with the smb.conf file. Part 6: Starting the Samba Servers
Congratulations! You have just configured your Samba server to share files with your local workgroup. Part 7: Persistency Check It is important for your server (and critical to pass the RHCE exam) that any changes you make to your server should be persistent. This means that changes should be active when you reboot Linux. Perform an orderly reboot of your server now and verify that Samba starts when you boot Linux.
|
|
Answers
3. | The chapter lab on Samba is designed to be easy to follow. However, you'll need explicit Linux knowledge to complete some specific steps. Answers to these steps can be found in the following: Part 1
Part 2
Part 3
Part 4
Part 5
Part 6
Part 7
|