[svnbook] r5548 committed - branches/1.8/zh/book/ch05-repository-admin.xml

[wuzhouhui at users.sourceforge.net]

Revision: 5548
          http://sourceforge.net/p/svnbook/source/5548
Author:   wuzhouhui
Date:     2017-12-21 12:47:30 +0000 (Thu, 21 Dec 2017)
Log Message:
-----------
1.8/zh: translation of chapter 5 in progress

Modified Paths:
--------------
    branches/1.8/zh/book/ch05-repository-admin.xml

Modified: branches/1.8/zh/book/ch05-repository-admin.xml
===================================================================
--- branches/1.8/zh/book/ch05-repository-admin.xml	2017-12-20 12:01:22 UTC (rev 5547)
+++ branches/1.8/zh/book/ch05-repository-admin.xml	2017-12-21 12:47:30 UTC (rev 5548)
@@ -225,9 +225,11 @@
       -->
     </note>
 
+      <!--
     <para>Of course, when accessed via the Subversion libraries, this
       otherwise unremarkable collection of files and directories
       suddenly becomes an implementation of a virtual, versioned
+      ### TODO
       filesystem, complete with customizable event triggers.  This
       filesystem has its own notions of directories and files, very
       similar to the notions of such things held by real filesystems
@@ -236,10 +238,21 @@
       revisions, keeping all the changes you've ever made to them
       safely stored and forever accessible.  This is where the
       entirety of your versioned data lives.</para>
+      -->
+    <para>当然, 当我们通过 Subversion 库函数访问仓库时, 这些文件与目录就成为
+      了一种虚拟的, 版本化的文件系统的实现. 这个文件系统对文件和目录的概念都
+      有自己的理解, 和真正的文件系统 (例如 NTFS, FAT32, ext3 等) 非常类似,
+      但它又比较特殊—它把文件和目录悬挂在版本号上, 安全地记录用户曾经
+      对它们做出的修改, 并保证这些修改是永远可访问的. 这就是存放用户所有的
+      版本化数据的地方.</para>
 
     <sidebar id="svn.reposadmin.basics.backends">
+      <!--
       <title>Speaking of Filesystems…</title>
+      -->
+      <title>文件系统</title>
 
+      <!--
       <para>When the initial design phase of Subversion was in
         progress, the developers decided to use Berkeley DB (BDB) as
         the storage mechanism behind the virtual versioned filesystem
@@ -247,9 +260,16 @@
         variety of reasons, including its open source license,
         transaction support, reliability, performance, API simplicity,
         thread safety, support for cursors, and so on.</para>
+      -->
+      <para>在设计 Subversion 的开始阶段, 开发人员使用 Berkeley DB (BDB) 实现
+        虚拟版本化文件系统的后端存储机制. 选择 Berkeley DB 基于多种理由, 包
+        括它的开源授权, 事务支持, 可靠性, 高性能, 简单的 API, 线程安全, 支持
+        游标等.</para>
 
+      <!--
       <para>In the years since, the
         newer <firstterm>FSFS</firstterm><footnote><para>While it is
+            ### TODO
         often pronounced <quote>fuzz-fuzz,</quote> per Jack
         Repenning's rendition, this book assumes that the reader is
         thinking <quote>eff-ess-eff-ess.</quote></para></footnote>
@@ -263,6 +283,14 @@
         coming, and ultimately the FSFS storage layer surpassed the
         Berkeley DB one in nearly every meaningful metric, from
         performance to scalability to reliability and beyond.</para>
+      -->
+      <para>后来, 引入了新的后端存储机制—<firstterm>FSFS</firstterm>.
+        这个所谓的 <quote>文件系统的文件系统</quote> 并不是一个在不透明的
+        数据库容器中实现的版本化文件系统, 而是一个由大量文件组成的集合,
+        这些文件更加透明, 存放在操作系统的文件系统中. 随着软件的成熟, FSFS
+        最终成为了 Subversion 默认的后端存储机制. FSFS 并没有因此停止前进的
+        脚步, 后来, 几乎在每一项指标上—从性能, 到可扩展性, 再到可靠性
+        —FSFS 都超越了 Berkeley DB.</para> 
 
       <para>These days, it is generally assumed that if you are using
         the open source Subversion product, you are using the FSFS