X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=febootstrap.pod;h=109f6a2c682b482d5cbcc0dcb8b0b8b7b1983539;hb=12ad502d1572727029fed3dd9d83c6a6837e9ef5;hp=1e4d9ffdb92faff92d5681095a2ebcfd61779e0f;hpb=0926817326843d6a61b28080ff7eb1180cfad746;p=febootstrap.git diff --git a/febootstrap.pod b/febootstrap.pod index 1e4d9ff..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 (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 @@ -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. +(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 utility to automate installing new files safely +into a filesystem). + +In most cases it's usually safest to use C. You can use the fakeroot logfile in a number of ways: