[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-commits
Subject:    svn commit: r1787216 - /subversion/site/publish/faq.html
From:       julianfoad () apache ! org
Date:       2017-03-16 16:18:18
Message-ID: 20170316161818.C40EB3A086E () svn01-us-west ! apache ! org
[Download RAW message or body]

Author: julianfoad
Date: Thu Mar 16 16:18:18 2017
New Revision: 1787216

URL: http://svn.apache.org/viewvc?rev=1787216&view=rev
Log:
Clarify the NFS FAQ a little.

* faq.html
  (nfs): Clarify by moving FSFS before BDB, adding emphasis to keywords,
    and removing a historical link.

Modified:
    subversion/site/publish/faq.html

Modified: subversion/site/publish/faq.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/faq.html?rev=1787216&r1=1787215&r2=1787216&view=diff
 ==============================================================================
--- subversion/site/publish/faq.html (original)
+++ subversion/site/publish/faq.html Thu Mar 16 16:18:18 2017
@@ -1073,7 +1073,12 @@ server?
     title="Link to this section">&para;</a>
 </h3>
 
-<p>If you are using a repository with the Berkeley DB back end
+<p>If you are using the <b>FSFS repository back end</b> (which has
+been the default since Subversion 1.2), then storing the repository on
+a modern NFS server (i.e., one that supports locking) should be
+fine.</p>
+
+<p>If you are using a repository with the <b>Berkeley DB back end</b>
 (default for repositories created with Subversion 1.0 and 1.1, not the
 default thereafter), we recommend <i>not</i> storing the repository on
 a remote filesystem (for example, NFS).  While Berkeley DB databases
@@ -1083,12 +1088,7 @@ repository may be safely accessed by onl
 and not all Subversion functionality will be available to even that
 one client.</p>
 
-<p>If you are using the <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/notes/fsfs">FSFS</a>
-repository back end, then storing the repository on a modern NFS
-server (i.e., one that supports locking) should be fine.</p>
-
-<p>Working copies can be stored on NFS (one common scenario is when
+<p><b>Working copies</b> can be stored on NFS (one common scenario is when
 your home directory is on a NFS server).  On Linux NFS servers, due to
 the volume of renames used internally in Subversion when checking out
 files, some users have reported that 'subtree checking' should be


[prev in list] [next in list] [prev in thread] [next in thread]