Minor formatting cleanup.

Fork: 0

tundra / tbku

Browse code Minor formatting cleanup. master
1 parent a96f5ef commit 53588b094fb1bdb1949e227c8f1a0fc1b1462e95 tundra authored on 14 Mar 2008

Patch

Unified Split

Showing 1 changed file

                Ignore Space
               Show notes
              View
            
          
          30 ■■■■■
          Imaging-SUSE-Linux-With-tbku.txt
               /usr
              /var
 
          Notice that we do *not* backup the dynamic kernel-created
          filesystems like ``/dev`` or ``/proc``, nor do we
          backup utility mountpoints like ``/mnt`` or ``/tmp``.
 
          Also, if you have ``tbku`` writing your backup to
          the local disk, make sure that directory is *not*
          included in the fileset.  Doing so would create
          a recursive backup wherein the backup would be
          copied to itself.
 
          The exact fileset you use will vary somewhat depending
          on how you've laid out your directory tree and
          just what you want included in your image, so use
          the fileset above as a point of departure.
          filesystems like ``/dev`` or ``/proc``, nor do we backup
          utility mountpoints like ``/mnt`` or ``/tmp``.
 
          Also, if you have ``tbku`` writing your backup to the local
          disk, make sure that directory is *not* included in the
          fileset.  Doing so would create a recursive backup wherein
          the backup would be copied to itself.
 
          The exact fileset you use will vary somewhat depending on
          how you've laid out your directory tree and just what you
          want included in your image, so use the fileset above as a
          point of departure.
 
       3. Save the resulting ``.tar.gz`` (tarball) file somewhere
          it can be retrieved later when you want to image another
          machine.  This can be a network server, a USB drive,
disseminate this document without charge, so long as you do so without
modifying it in any way.
 
 
``$Id: Imaging-SUSE-Linux-With-tbku.txt,v 1.112 2008/03/14 21:39:20 tundra Exp $``
``$Id: Imaging-SUSE-Linux-With-tbku.txt,v 1.113 2008/03/14 21:40:32 tundra Exp $``
               /usr
               /var
           Notice that we do *not* backup the dynamic kernel-created
+          filesystems like ``/dev`` or ``/proc``, nor do we
+          backup utility mountpoints like ``/mnt`` or ``/tmp``.
+          Also, if you have ``tbku`` writing your backup to
+          the local disk, make sure that directory is *not*
+          included in the fileset.  Doing so would create
+          a recursive backup wherein the backup would be
+          copied to itself.
+          The exact fileset you use will vary somewhat depending
+          on how you've laid out your directory tree and
+          just what you want included in your image, so use
+          the fileset above as a point of departure.
+          filesystems like ``/dev`` or ``/proc``, nor do we backup
+          utility mountpoints like ``/mnt`` or ``/tmp``.
+          Also, if you have ``tbku`` writing your backup to the local
+          disk, make sure that directory is *not* included in the
+          fileset.  Doing so would create a recursive backup wherein
+          the backup would be copied to itself.
+          The exact fileset you use will vary somewhat depending on
+          how you've laid out your directory tree and just what you
+          want included in your image, so use the fileset above as a
+          point of departure.
 . Save the resulting ``.tar.gz`` (tarball) file somewhere
           it can be retrieved later when you want to image another
           machine.  This can be a network server, a USB drive,
 disseminate this document without charge, so long as you do so without
 modifying it in any way.
+``$Id: Imaging-SUSE-Linux-With-tbku.txt,v 1.112 2008/03/14 21:39:20 tundra Exp $``
+``$Id: Imaging-SUSE-Linux-With-tbku.txt,v 1.113 2008/03/14 21:40:32 tundra Exp $``

Show line notes below