In the following guide, we are going to have a look at a convenient way of creating an NFS server from behind Fedora’s built-in iptables firewall.

Setting up the NFS Configuration files

/etc/exports

The /etc/exports file is for storing information about your NFS shares: the name of the folder to share, the IP address(es) of hosts to access your share and the rights connected to your share.

A typical /etc/exports file should look like this:

/usr/local   192.168.0.1(ro) 192.168.0.2(ro)
/home        192.168.0.1(rw) 192.168.0.2(rw)

An exports file consists of 2 columns and at least 1 row.

Each row corresponds to a folder (a share, if you like), where the columns contain the settings to the folder of their row.

The first column contains the full path on the computer to the folder you wish to share, the second column is for the IP addresses of the hosts you are sharing to. The letters in brackets are for the privileges. For example, ro stands for “read only” and rw is for “read and write”. For further options, you might want to visit http://nfs.sourceforge.net/nfs-howto/ar01s03.html.

In the example, you are sharing your /usr/local and your /home folder to 192.168.0.1 and 192.168.0.2. Both machines have read-only privileges on the first, and read and write priviliges on the second folder.

/etc/hosts.deny

This file is for listing the hosts that are not allowed to access your shares. As the /etc/hosts.allow (see the next title) overwrites this file it is best to list all servers here. Enter the following to this file:

portmap:ALL
lockd:ALL
mountd:ALL
rquotad:ALL
statd:ALL

With your /etc/hosts.deny set like this and without an /etc/hosts.allow, no machines are allowed to see your NFS shares.

/etc/hosts.allow

To allow your machine(s) to access your NFS shares, add the following lines to your file, and replace the IPs with the IP(s) of your machine(s).

portmap: 192.168.0.1 , 192.168.0.2
lockd: 192.168.0.1 , 192.168.0.2
rquotad: 192.168.0.1 , 192.168.0.2
mountd: 192.168.0.1 , 192.168.0.2
statd: 192.168.0.1 , 192.168.0.2

If you have only one machine to grant access to, delete the comma and the numbers behind.

Setting up NFS to work from behind Fedora’s iptables firewall

/etc/sysconfig/nfs

This file controls the ports which NFS is going to use. Copy the following lines into the file. Doing so is not a security risk, as you are likely to be behind a router (if you want to use network file sharing), and this doesen’t (yet) mean opening the ports in the firewall.

LOCKD_TCPPORT=48620
LOCKD_UDPPORT=48620
MOUNTD_PORT=48621
STATD_PORT=48622
RQUOTAD=no
RQUOTAD_PORT=48623

Getting configuration files (tested on Fedora Core 5)

Download and save these configuration files to a tool folder in your home.

• nfs_firewallopen (used to open your firewall for nfs and portmap ports)
• nfs_servicestart (used to start nfs services)
• nfstart (to execute the 2 scripts above)
• nfs_firewallclose (used to close your opened nfs and portmap ports)
• nfs_servicestop (used to stop nfs services)
• nfstop (to execute the 2 scripts above)

To get NFS working on your server, init the nfstart script by typing with root privileges

sh ~/tool/nfstart

For setting up an NFS client, see http://nfs.sourceforge.net/nfs-howto/ar01s04.html.

For example on my absolutely normal IDE machine it felt my hard drive as a RAID device. At first, I experienced no further problems apart from having my drives called dm1, dm2 instead of hda1, hda2 etc. But the worst thing was yet to come: when kernel series 2.6.17 were introduced, the new kernels didn’t even boot.

That was the point when I decided to reinstall, but this time I started anaconda with the

linux nodmraid

option.

When a Fedora Core computer is turned on, the default log-in manager to appear is GNOME’s GDM, as the folks at Fedora are having a crush on everything that is related to GNOME. Though it is pretty nice, and it can log you in to KDE (or any other installed Desktop Environment) as well, you might want to use KDE’s own greeter, KDM.

KDM has a lot of advantages, still it’s greatest hit is that the log-in themes at KDE-Look are designed for KDM, not GDM.

Setting your Fedora Core 5 computer to work with KDM is rather… interesting, but not difficult if you know what to do. It’s just a few steps, overall.

1. Add to following line to your /etc/sysconfig/desktop file:
   DISPLAYMANAGER=”KDM”
   additionally, remove all
   DISPLAYMANAGER=”GDM”
   lines, if there are any.
2. Save your file, and do log out.
3. When seeing the log-in screen, press Ctrl+Alt+F1.
   Warning: This will make you unable to get back to this guide, so I suggest you to print my post or put the remaining part down to a piece of paper.
4. Log in as root, and enter
   init 3
5. After doing so, enter
   init 5
   This should take you back to your KDM login screen.
6. If you can’t see a log-in screen, try pressing Ctrl+Alt+F7, Ctrl+Alt+F8, or reboot your computer.

The above steps were for making KDM the default greeter. For a convinient way of switching between KDM themes, you might want to install the KDM Theme Manager.

1. Download the rpm from KDE-Apps (exact path of rpm file) to your home folder
2. Install it by entering
   rpm -ivh ~/kdmtheme-1.1-FC3.i386.rpm
   into a terminal

After you have done so, the KDM Theme Manager is avalible from the KDE Control Center (kcontrol), under System Administration. Here, you can add, remove and switch between KDM themes.

You don’t need to remove the rpm to use GDM again, it is enough to rewrite the
DISPLAYMANAGER=”KDM”
line to
DISPLAYMANAGER=”GDM”.