On the need for "febootstrap-install".

[febootstrap.git] / febootstrap.pod

diff --git a/febootstrap.pod b/febootstrap.pod
index b2d7470..a8f73ff 100644 (file)
--- a/febootstrap.pod
+++ b/febootstrap.pod
@@ -104,8 +104,16 @@ files is usually safe.  Files should be replaced only by doing:
 
  echo updated-content > old-file
 
 
  echo updated-content > old-file
 

-(since that preserves the original inode).  In most cases it's usually
-safest to use C<febootstrap-run>.
+(since that preserves the original inode).
+
+Deleting files and then creating new ones (even with a different name)
+is usually unsafe, because the new files might reuse inodes claimed by
+the old files, and so appear with peculiar permissions
+(eg. unreadable, or as a symbolic link).  (XXX We need an
+C<febootstrap-install> utility to automate installing new files safely
+into a filesystem).
+
+In most cases it's usually safest to use C<febootstrap-run>.

 
 You can use the fakeroot logfile in a number of ways:
 
 
 You can use the fakeroot logfile in a number of ways:
 


@@ -148,22 +156,24 @@ C<--foreign> installs - see previous point).
 
 =head1 OTHER RESTRICTIONS AND BUGS
 
 
 =head1 OTHER RESTRICTIONS AND BUGS
 

-Some C<%post> scripts do not run correctly.  The most common case is
-C</sbin/ldconfig>.  Since this binary is statically linked, fakeroot
-and fakechroot's LD_PRELOAD hack does not work, so effectively
-ldconfig tries to update the system cache.  You will see the following
-error:
+The following programs are not run during C<%post> scriptlets (because
+they are all statically linked, and fakechroot cannot run statically
+linked programs).
+
+=over 4
+
+=item C</sbin/ldconfig> (from many packages)
+
+=item C</usr/sbin/glibc_post_upgrade> (from C<glibc>)

 
 

- /sbin/ldconfig: Can't create temporary cache file /etc/ld.so.cache~: Permission denied
+=item C</usr/sbin/build-locale-archive> (from C<glibc-common>)

 
 

-This error is mostly harmless.  Just run C</sbin/ldconfig> the first
-time you boot into the newly created Fedora system.
+=item C</usr/sbin/libgcc_post_upgrade> (from C<libgcc>)
+
+=back

 
 

-Another error you will see is with C</usr/sbin/glibc_post_upgrade>
-which is caused for the same reason - this binary is statically
-linked.  We have examined what this binary does, and it is not really
-necessary for installs.  If it makes you happier, you can run it the
-first time you boot the new system.
+If you wish, you can run them the first time you boot into the new
+machine.

 
 febootstrap recreates the repository anew each time, and this causes
 yum to download all the RPMs every time.  This is very wasteful, and
 
 febootstrap recreates the repository anew each time, and this causes
 yum to download all the RPMs every time.  This is very wasteful, and