docs/66481: [patch] share/examples/diskless/README.TEMPLATING tyops

[Michel Lavondès]

>Number:         66481
>Category:       docs
>Synopsis:       [patch] share/examples/diskless/README.TEMPLATING tyops
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon May 10 10:40:15 PDT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Michel Lavondès
>Release:        4.8-RELEASE-p13
>Organization:
Ecdysiasts United For Overdressing
>Environment:
>Description:
      
>How-To-Repeat:
more /usr/share/examples/diskless/README.TEMPLATING
>Fix:
Patch also available at: http://www.livejournal.com/users/pauamma/1231.html

--- share/examples/diskless/README.TEMPLATING.orig	Wed May  5 09:17:25 2004
+++ share/examples/diskless/README.TEMPLATING	Wed May  5 09:19:47 2004
@@ -184,7 +184,7 @@
     file in / or /usr on a target machine instead of the template machine.
     If the target machine is updated once a night from cron, the sysop
     quickly learns not to do this ( because his changes get overwritten
-    overnight ).  With a manual update, these sorts of mistakes can propogate
+    overnight ).  With a manual update, these sorts of mistakes can propagate
     for weeks or months before they are caught.

                             TEMPLATE COPYING AND SAFETY
@@ -195,7 +195,7 @@
     softlinks, hardlinks, files, modification times, uid, gid, flags, perms,
     and so forth.  The program incorporates several major features:

-        *   The program refuses, absolutely, to cross partition boundries.
+        *   The program refuses, absolutely, to cross partition boundaries.
             i.e. if you were copying the template /usr from an NFS mount to
             your /usr, and you had a mount point called /usr/home, the
             template copying program would *NOT* descend into /usr/home on
@@ -204,7 +204,7 @@
             This is a safety.

         *   The program accesses a file called .cpignore in each directory
-            it descending into on the source to obtain a list of exceptions
+            it descends into on the source to obtain a list of exceptions
             for that directory -- that is, files not to copy or mess with.

             This is a templating function.

>Release-Note:
>Audit-Trail:
>Unformatted: