kern/136865: NFS exports atomic and on-the-fly atomic updates

[Andrey Simonenko]

The following reply was made to PR kern/136865; it has been noted by GNATS.

From: Andrey Simonenko <simon at comsys.ntu-kpi.kiev.ua>
To: bug-followup at FreeBSD.org
Cc:  
Subject: Re: kern/136865: NFS exports atomic and on-the-fly atomic updates
Date: Mon, 12 Oct 2009 19:19:15 +0300

 Updated version nfse-20091012 can be used on 9.0-CURRENT and 8.0-RC1.
 with experimental and regular NFS server.
 
 Can be downloaded here http://comsys.ntu-kpi.kiev.ua/~simon/nfse/
 MD5 (nfse-20091012.tar.bz2) = 3562d449406ac0a728928de5d0583884
 
 List of changes:
 
     * Command "flush" can be combined with "add" commands.
 
     * Added new command "clear" -- clear configuration for the given
       pathname.
 
     * Added new command "show" -- show current configuration.
 
     * Now nfse recognizes shadowed mount points.  Manual page nfs.exports(5)
       was updated and contains information how nfse(8) works with mount
       points.
 
     * Now all settings (export specifications for file systems, export
       specifications for NFSv4 root directory and WebNFS settings) are
       updated atomically.  There is one exception for WebNFS settings
       for new exported file system, but this exception can be suppressed
       by the administrator.
 
     * Added support for NFSv4 root directory configuration
       (atomic and on-the-fly atomic updates are supported).
 
     * Added support for experimental NFS server.
 
     * Several mistakes were corrected, some parts were optimized and/or
       simplified.
 
     * Support for obsolete options was removed.
 
     * mountd(8) was renamed to nfse(8) (actually nfse uses only modified
       RPC and XDR related code from mountd), exports(5) was renamed to
       nfs.exports(5).
 
     * This distribution contains changes for FreeBSD 9.0-CURRENT and 8.0-RC1.
 
 List of open-questions:
 
 1. WebNFS settings cannot be updated by "-c command", it is necessary to
    discuss semantics for experimental NFS server.
 
 2. WebNFS settings are not protected by any lock in NFS server.
 
 3. NFSv4 root directory settings are not protected by any lock in NFS server.
 
 4. It is possible to make better integration of nfs_export.c with NFS server
    (see nfs_export.c:nfse_fs_check() and nfs_export.c:nfse_rd_check()),
    it is necessary to discuss this.