svn commit: lorikeet r180 - in trunk/white-papers: .

[abartlet at samba.org]

Author: abartlet
Date: 2005-01-09 20:26:13 +0000 (Sun, 09 Jan 2005)
New Revision: 180

WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=lorikeet&rev=180

Log:
More clarifications, based on comments by jht.

Andrew Bartlett

Modified:
   trunk/white-papers/samba3-samba4.lyx


Changeset:
Modified: trunk/white-papers/samba3-samba4.lyx
===================================================================
--- trunk/white-papers/samba3-samba4.lyx	2005-01-09 09:52:14 UTC (rev 179)
+++ trunk/white-papers/samba3-samba4.lyx	2005-01-09 20:26:13 UTC (rev 180)
@@ -33,8 +33,8 @@
 \layout Abstract
 
 This paper explores some of the options, both practical and otherwise, for
- integration between the production Samba 3.0 release and the Samba4 development
- code.
+ close integration between the production Samba 3.0 release and the Samba4
+ development code.
  It examines integration attempts that have been successful, and those that
  have failed, and provides recommendations to Samba implementors on how
  best to proceed.
@@ -43,12 +43,14 @@
 Introduction
 \layout Standard
 
-At many stages during the development of Samba4, developers and users have
- suggested that Samba4 would be developed faster, better or released sooner
- if there was close integration possible between Samba4 and the existing
- Samba 3.0 release.
+As developers, vendors and large-scale implementors look for increasing
+ features in their Samba installations, many are looking with interest at
+ the Samba4 development project.
+ While still unfinished, many have suggested that Samba4 would be developed
+ faster, better or released sooner if there was close integration possible
+ between Samba4 and the existing Samba 3.0 release.
  Likewise, Samba 3.0 is showing its age, and could potentially benefit quite
- substantially from some of the  Samba4 technologies.
+ substantially from some of Samba4's impressive new technologies.
 \layout Subsection*
 
 Samba 3.0
@@ -74,8 +76,8 @@
  long history of suitability for `enterprise' use.
  Samba 3.0 is not comprehensive, and Samba4's testing has shown how much
  further there really is to go.
-  For the features it provides, however, it is a very solid product.
- 
+  For the features it provides, however, it is a very solid product that
+ clearly will be deployed and supported for a number of years yet.
 \layout Subsection*
 
 Samba4
@@ -417,8 +419,10 @@
 Samba 3.0's nmbd
 \layout Standard
 
-While a new nmbd is proposed for Samba4, currently Samba 3.0's is sufficient
+While a new nmbd is proposed for Samba4, currently Samba 3.0's nmbd is sufficient
  for use in developing Samba4.
+ For particular situations, some patches are available from the Samba4 source
+ tree.
 \layout Section*
 
 Ideas for Samba 3.0 / Samba4 Integration
@@ -583,9 +587,9 @@
 
 Samba4 promises to be the same; while Jeremy and others (particularly those
  contracted to `enterprise' customers) will almost certainly continue to
- `fix' Samba 3.0 as best as they can, the Samba4 development program will
- provide new and significant functionality, that will simply not be available
- on the old platform.
+ fix Samba 3.0 as best as they can, the Samba4 development program will provide
+ new and significant functionality, that will simply not be available on
+ the old platform.
  While it may be tempting to try and back-port functionality, we have already
  shown that this is not viable for any significant functionality.
 \layout Section*