X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=febootstrap-to-supermin.pod;h=123327ce732561f8dbbebf8eecc7999ac50d57d0;hb=8e6a3ac4051e639b9ef17c4049e6cc11dab1bc76;hp=6263f51d47cadedc9d39ca26dcd49315a5e79896;hpb=76b7711268a6b0c0929952ee261821825589a165;p=febootstrap.git

diff --git a/febootstrap-to-supermin.pod b/febootstrap-to-supermin.pod
index 6263f51..123327c 100644
--- a/febootstrap-to-supermin.pod
+++ b/febootstrap-to-supermin.pod
@@ -79,7 +79,8 @@ Use supermin appliances with caution.
 
 =head2 ANATOMY OF A SUPERMIN APPLIANCE
 
-A supermin appliance consists of two files:
+A supermin appliance consists usually of just two files, but can
+contain several files and directories from the list below:
 
 =over 4
 
@@ -90,6 +91,10 @@ call it anything you want) is the skeleton initramfs.  This is like an
 initramfs built by L<febootstrap-to-initramfs(8)>, but all libraries
 and binaries are removed.
 
+Note that this file is a cpio file in cpio "newc" format, and is
+I<not> compressed (unlike initramfs files which are compressed cpio
+files).
+
 =item hostfiles.txt
 
 This plain text file contains a list of files that we need to add back
@@ -106,6 +111,14 @@ the file contains
 
  lib64/libreadline.so.6.*
 
+=item any directory
+
+You can specify a directory which should contain image file(s)
+and hostfile(s).
+
+Using a directory is useful either to keep the appliance-related files
+together, or to make more complex appliances containing optional bits.
+
 =back
 
 =head2 RECONSTRUCTING AN INITRAMFS FROM A SUPERMIN APPLIANCE
@@ -175,8 +188,8 @@ Richard W.M. Jones <rjones @ redhat . com>
 
 =head1 COPYRIGHT
 
-(C) Copyright 2009 Red Hat Inc.,
-L<http://et.redhat.com/~rjones/febootstrap>.
+(C) Copyright 2009-2010 Red Hat Inc.,
+L<http://people.redhat.com/~rjones/febootstrap>.
 
 This program is free software; you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by