From 945d94cc4ee3c6be7b2c66675c8e46aa73f9ba89 Mon Sep 17 00:00:00 2001 From: Casey Bodley Date: Tue, 11 Oct 2011 15:46:23 -0400 Subject: [PATCH] readme: added vc2010 library dependency, updated known issues removed indications that the x86 build is untested under Installing Binaries, added requirement for visual c++ libraries removed known issue for AUTH_SYS and multiple users Signed-off-by: Casey Bodley --- README.html | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/README.html b/README.html index 19a5416..e4a7f4c 100644 --- a/README.html +++ b/README.html @@ -27,8 +27,8 @@
-

1. Building

+

1. Building from Source

Requirements

    -
  • Windows Vista x64, Windows Server 2008 R2 x64, or Windows 7 x64. (Windows XP and previous versions are not supported. 32-bit builds have not been tested.)
    • +
  • Windows Vista, Windows Server 2008 R2, or Windows 7 (Windows XP and previous versions are not supported)
  • Microsoft Visual Studio 2010
  • Windows Driver Development Kit (WinDDK 6000 or later)
  • ms-nfs41-client source code: @@ -52,24 +52,25 @@
  • Make a copy of env.props.example, and rename it to env.props.
  • Open env.props in a text editor, and verify that the value in <WDKPATH>C:\WinDDK\7600.16385.0</WDKPATH> points to your WinDDK installation.
  • Open the solution file ms-nfs41-client.sln in Visual Studio 2010.
    • -
  • Select the Debug configuration and x64 platform (accessible via Build->Configuration Manager).
    • +
  • Select the desired configuration and platform (accessible via Build->Configuration Manager).
  • Right-click on the daemon project and select Build. The project and its dependencies should build without errors. The resulting binaries, nfsd.exe and libtirpc.dll, can be found under ms-nfs41-client\build.vc10\x64\Debug\.

    • Building the driver and utilities

      -
    1. From the Start menu, open the WinDDK 'x64 Checked Build Environment' for the target platform.
      2. +
    2. From the Start menu, open the WinDDK 'Checked Build Environment' for the target platform.
    3. Change directory to ms-nfs41-client and type build. All projects should build without errors.
    -

    2. Installation

    +

    2. Installing Binaries

    Requirements

    • ms-nfs41-client binaries: nfs41_driver.sys, nfs41_np.dll, libtirpc.dll, nfs_install.exe, nfsd.exe, nfs_mount.exe
    • ms-nfs41-client configuration files: nfs41rdr.inf, install.bat, uninstall.bat, etc_netconfig, ms-nfs41-idmap.conf
      • +
    • Microsoft Visual Studio 2010, or Microsoft Visual C++ 2010 Redistributable Libraries (x86 or x64). An installer for the redistributable libraries are included with binary releases.

    Instructions

    1. Copy or extract all ms-nfs41-client binaries and configuration files into a directory that's convenient for testing.
      2. -
    2. Open a WinDDK 'x64 Checked Build Environment' as Administrator in this directory (right click and 'Run as administrator').
      3. +
    3. Open a WinDDK 'Checked Build Environment' as Administrator in this directory (right click and 'Run as administrator').
    4. Create a certificate for test-signing the driver (Creating Test Certificates):
      > makecert /pe /ss PrivateCertStore /n CN=nfs41_test nfs41_test.cer
    5. Use the certificate to sign nfs41_driver.sys (Test-Signing a Driver File): @@ -141,7 +142,6 @@

    7. Known Issues

      -
    • AUTH_SYS does not handle multiple users, so all operations are sent as the user that established the mount.
    • krb5p security has only been tested with DES, as the linux server does not support gss krb5 v2 tokens with rotated data.
    • When recovering opens and locks outside of the server's grace period, client does not check whether the file has been modified by another client.
    • If nfsd.exe is restarted while a drive is mapped, that drive needs to be remounted before further use.