In Theory, there is no Practice.

Ubuntu: How to setup an nfs server

Pretty much as described, with the following additions:

1. hosts.allow:
   
# /etc/hosts.allow: list of hosts that are allowed to access the system.
# See the manual pages hosts_access(5), hosts_options(5)
# and /usr/doc/netbase/portmapper.txt.gz
#
# Example: ALL: LOCAL @some_netgroup
# ALL: .foobar.edu EXCEPT terminalserver.foobar.edu
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper, as well as for
# rpc.mountd (the NFS mount daemon). See portmap(8), rpc.mountd(8) and
# /usr/share/doc/portmap/portmapper.txt.gz for further information.
#
portmap: 192.168.1. , 127.0.
lockd: 192.168.1. , 127.0.
rquotad: 192.168.1. , 127.0.
mountd: 192.168.1. , 127.0.
statd: 192.168.1. , 127.0.

2. hosts.deny
   
   # /etc/hosts.deny: list of hosts that are _not_ allowed to access the system.
   # See the manual pages hosts_access(5), hosts_options(5)
   # and /usr/doc/netbase/portmapper.txt.gz
   #
   # Example: ALL: some.host.name, .some.domain
   # ALL EXCEPT in.fingerd: other.host.name, .other.domain
   #
   # If you're going to protect the portmapper use the name "portmap" for the
   # daemon name. Remember that you can only use the keyword "ALL" and IP
   # addresses (NOT host or domain names) for the portmapper. See portmap(8)
   # and /usr/doc/portmap/portmapper.txt.gz for further information.
   #
   # The PARANOID wildcard matches any host whose name does not match its
   # address.

   # You may wish to enable this to ensure any programs that don't
# validate looked up hostnames still leave understandable logs. In past
# versions of Debian this has been the default.
# ALL: PARANOID
portmap:ALL
lockd:ALL
mountd:ALL
rquotad:ALL
statd:ALL


Now I have all my machines mounting the same home dir. And created a ‘windows’ in my home, and use that dir as my H:\ via the SAMBA PDC.

Minor Problems:

• Mounting Subddirs of shares: can smbmount access paths in shares?

Major problems:

• WHS saves everything as root / Administrator. I.e., the user / group is always Adminsitrator / Administrator that is mapped to root / root, and uses ACL to allow access to the files. Why this bad? Because Amanda always uses a umask=600 for files, so that it is, read / write for Administrator / root user and blocked for everyone else. But Amanda will not run as root, so it cannot read / modify the files it creates. Bah.

Oddly, for a long time I didn’t realize how broken it was. I thought it was doing Spamassassin (Anti-Spam) and ClamAV (Anti-virus) . I was wrong. It was doing neither. After a mutli-hour fight, I think it works. And for a side benefit, the aliasing seems to work now. Weird.

Here are the useful links, mostly in order of how much I used it:

1. How to set up a mail server on a GNU / Linux system
2. Integrating amavisd-new in Postfix
3. Tips and FAQ — spam scanners (Mail::SpamAssassin)
4. PostfixAmavisNew
5. TestingInstallation (Spamassassin)
6. Configuration file for amavisd-new

I should have better e-mail from now on. Wheee. It only took me 8 hours to figure out.

Bah.

I used BeOS for a while. Haiku is the open source descendant. I think I am going to resurrect one of the computer corpses to play with this. See also: Haiku at Wikipedia.