- remove sections added to the user doc

bochs/doc/docbook/misc.txt

@@ -1,4 +1,4 @@
-$Id: misc.txt,v 1.25 2003-05-03 16:39:35 cbothamy Exp $
+$Id: misc.txt,v 1.26 2003-10-29 01:15:13 cbothamy Exp $
 
 This is a temporary place to paste in stuff that should go into the docs one
 day.  When it is transferred into docbook, let's remove it from misc.txt.
@@ -543,70 +543,3 @@ sysctl net.inet.ip.forwarding=1
 sysctl net.link.ether.inet.proxyall=1
 
 
---------------------------------------------------
-This should be included in the user doc
-// This option enables "split hard drive" support, which means
-// that a series of partial hard disk images can be treated
-// as a single large image.  If you set up the partition sizes and
-// file sizes correctly, this allows you to store each partition
-// in a separate file, which is very convenient if you want to operate
-// on a single partition (e.g. mount with loopback, create filesystem,
-// fsck, etc.).
-// [[Provide example of partitioning]]
-
-----------------------------------------------------------------------
-Patch name: patch.sparsedisk-justinsb
-Author: Justin SB
-Date: 27 Jan 2003
-
-Detailed description:
-
-  This patch enables "sparse hard drive" support:
-
-  1) A large hard drive can be created, and only used space will be stored
-      in the file.  In practice this is not a large gain as Unix does this
-      anyway.
-  2) Multiple sparse drive images can be mounted on top of each other.
-      Writes go to the top image.  This allows several similar configurations
-      to share a master "base" file, and also allows filesystem rollback or
-      no-write options.  Up to 10 disk images can be layered on top of each other.
-
-  There is a need for supporting utilities:
-    1) to merge two sparse disk images into a single image
-    2) to defragment a sparse disk image and remove unused space
-
-  Examples:
-  Space Saving
-    1) Create a sparse disk image using bximage.  Set size to eg 10GB.  Only allocated space will be stored,
-      so your drive image should be only about as large as the files stored on it.
-
-  Disk Rollback:
-    1) Create a sparse disk image called "c.img.0".  Point .bochsrc at "c.img.0".
-        In bochs, install your favourite OS.  Switch off bochs.
-    2) Create a sparse disk image (of the same size) and name it "c.img.1".  Point .bochsrc at "c.img.1"
-        "c.img.0" is visible, but all writes go to "c.img.1".  After using bochs, you can simply delete
-        "c.img.1" to undo changes and go back to a clean OS install.
-
-  Disk Optional Commit:
-    1) Create a sparse disk image called "c.img.0".  Point .bochsrc at "c.img.0".
-        In bochs, install your favourite OS.  Switch off bochs.
-    2) Create a sparse disk image (of the same size) and name it "c.img.1".  Point .bochsrc at "c.img.1"
-        "c.img.0" is visible, but all writes go to "c.img.1".  After using bochs, if you want to keep the
-        changes, use the (currently non-existant) merge utility to make a single unified drive image.
-        Alternatively simply create a new partition on top called "c.img.3".
-
-  Common Base:
-    1) Create a sparse disk image called "base.img".  Point .bochsrc at "base.img".
-        In bochs, install your favourite OS.  Switch off bochs.
-    2) Create a sparse disk image (of the same size) and name it "www.img.1".  Make "wwww.img.0" a symlink to
-        "base.img".  Point .bochsrc at "www.img.1". Using bochs, install a webserver.
-    3) Create a symlink to "base.img" called "db.img.0".  Create a sparse disk image (of the same size)
-      and name it "db.img.1".  Point .bochsrc at "db.img.1".  Using bochs, install a database server.
-
-      Now both a database server and webserver can be run in separate virtual machines, but they share
-        the common OS image, saving drive space.
-
-
-
-  Disk Rollback and Optional Commit will probably be the most used of these options.
-