X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=febootstrap.pod;h=b1e512b9eb95c841af3918f8e1730a830d2b8409;hb=89e336ee166be538e376d288fb2b3fbbffd66d4c;hp=a8f73ffceee80f78f9c6684fc302c72406a6e32d;hpb=467d77a9af3dbb1a4bcfbb9c7f97c8e300d6dca0;p=febootstrap.git diff --git a/febootstrap.pod b/febootstrap.pod index a8f73ff..b1e512b 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 (a URL) + +Get updates from the specific URL. + +=item -u C (an updates repository name) + +Get updates from the public mirrors of the named repository +(eg. C). See REPOSITORIES below. + +=item -u C (default) + +Don't add an updates repository. This is the default. + +=back + =back =head1 REPOSITORIES @@ -99,8 +129,8 @@ so that yum thinks it is running as root. Fakeroot keeps track of directory as C/fakeroot.log>. This logfile is indexed by inode number, which makes certain -operations safe and other operations unsafe. For example, deleting -files is usually safe. Files should be replaced only by doing: +operations safe and other operations unsafe. +Files should be replaced only by doing: echo updated-content > old-file @@ -109,9 +139,12 @@ files is usually safe. Files should be replaced only by doing: 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 utility to automate installing new files safely -into a filesystem). +(eg. unreadable, or as a symbolic link). + +Deleting files is also usually unsafe, although the reasons are more +subtle. If you just use C then the inode number is not deleted +from C which means it can be reused by another file +later on. In most cases it's usually safest to use C. @@ -126,11 +159,21 @@ permissions. =item * +Use L to install a file with permissions +in the root filesystem. + +=item * + Generate an initramfs (compressed cpio) file containing the correct permissions using the tool C. =item * +Generate a supermin appliance using the tool +C. + +=item * + Apply the permissions to the target directory using the forthcoming tool C (requires root). @@ -181,13 +224,15 @@ we should provide a way to cache the repository. =head1 HOME PAGE -L +L =head1 SEE ALSO L, L, L, +L, +L, L, L, L, @@ -208,7 +253,7 @@ Richard W.M. Jones =head1 COPYRIGHT (C) Copyright 2009 Red Hat Inc., -L. +L. 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