X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=febootstrap.pod;h=109f6a2c682b482d5cbcc0dcb8b0b8b7b1983539;hb=b900dfdd10cab92a5c6978bc0f4db8f167ae82a9;hp=b2d7470aa56062880637f4f8484cf5599d3906f7;hpb=9cf3beefb865ea3e1a4bbe570d632649540788cc;p=febootstrap.git

diff --git a/febootstrap.pod b/febootstrap.pod
index b2d7470..109f6a2 100644
--- a/febootstrap.pod
+++ b/febootstrap.pod
@@ -64,6 +64,36 @@ RPMs and metadata.  However if you give the C<--no-clean> option, then
 the yum repository is left.  This is useful if you want to run further
 yum commands inside the filesystem by hand.
 
+=item B<-p "proxyurl">
+
+=item B<--proxy="proxyurl">
+
+URL to the proxy server that yum should use.
+
+=item B<-u source>
+
+=item B<--updates=source>
+
+Pull in updates from an additional updates repository.  The possible
+sources are:
+
+=over 4
+
+=item -u C<http://...> (a URL)
+
+Get updates from the specific URL.
+
+=item -u C<updates-released-fN> (an updates repository name)
+
+Get updates from the public mirrors of the named repository
+(eg. C<updates-released-f10>).  See REPOSITORIES below.
+
+=item -u C<none> (default)
+
+Don't add an updates repository.  This is the default.
+
+=back
+
 =back
 
 =head1 REPOSITORIES
@@ -104,8 +134,16 @@ files is usually safe.  Files should be replaced only by doing:
 
  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:
 
@@ -148,22 +186,24 @@ C<--foreign> installs - see previous point).
 
 =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).
 
- /sbin/ldconfig: Can't create temporary cache file /etc/ld.so.cache~: Permission denied
+=over 4
+
+=item C</sbin/ldconfig> (from many packages)
+
+=item C</usr/sbin/glibc_post_upgrade> (from C<glibc>)
 
-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/build-locale-archive> (from C<glibc-common>)
+
+=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