Changes

15 bytes removed ,  16:48, 30 April 2013
crtools -> criu
Line 5: Line 5:  
CRIU images can be in one of formats
 
CRIU images can be in one of formats
   −
* crtools specific images in google protocol buffer format (PB format)
+
* criu specific images in google protocol buffer format (PB format)
* crtools specific images with binary data in it
+
* criu specific images with binary data in it
 
* image files in 3rd party format (a.k.a. raw images)
 
* image files in 3rd party format (a.k.a. raw images)
   −
== Images in crtools-specific format ==
+
== Images in criu-specific format ==
   −
All crtools-specific image files begin with 32-bit magic cookie. Images in PB format are followed by zero or more entries of the same type (not size!), each entry is preceded with 32-bit entry size value (not including this 32-bit value itself). Optionally each entry may be followed by extra payload which depends on the entry type.
+
All criu-specific image files begin with 32-bit magic cookie. Images in PB format are followed by zero or more entries of the same type (not size!), each entry is preceded with 32-bit entry size value (not including this 32-bit value itself). Optionally each entry may be followed by extra payload which depends on the entry type.
    
IOW protocol-buffers image files look like
 
IOW protocol-buffers image files look like
Line 127: Line 127:  
== Raw images ==
 
== Raw images ==
   −
These images contain data that were collected by crtools with the help of some external tools. These are
+
These images contain data that were collected by criu with the help of some external tools. These are
    
{|class="wikitable sortable"
 
{|class="wikitable sortable"