diff options
author | Richard Jones <rjones@redhat.com> | 2009-03-30 15:14:29 +0100 |
---|---|---|
committer | Richard Jones <rjones@redhat.com> | 2009-03-30 15:14:29 +0100 |
commit | 9cf3beefb865ea3e1a4bbe570d632649540788cc (patch) | |
tree | 8374a2b0efeac0c8ab1eb301ffea118e0c96f937 /febootstrap.pod | |
parent | 14a8be81fc7a87fcdb0dd2ba7cbe2128f01705d9 (diff) | |
download | febootstrap-9cf3beefb865ea3e1a4bbe570d632649540788cc.tar.gz febootstrap-9cf3beefb865ea3e1a4bbe570d632649540788cc.tar.xz febootstrap-9cf3beefb865ea3e1a4bbe570d632649540788cc.zip |
Added febootstrap-run command.
Examples need more VM RAM when run in Rawhide. Also use 'set -e' in example
scripts.
Diffstat (limited to 'febootstrap.pod')
-rw-r--r-- | febootstrap.pod | 45 |
1 files changed, 35 insertions, 10 deletions
diff --git a/febootstrap.pod b/febootstrap.pod index dfc93fc..b2d7470 100644 --- a/febootstrap.pod +++ b/febootstrap.pod @@ -75,27 +75,46 @@ L<http://mirrors.fedoraproject.org/mirrorlist?repo=help&arch=i386> (If necessary replace C<i386> with your architecture, but it seems unlikely that this list will change based on architecture). -=head1 FAKEROOT LOGFILE +=head1 RUNNING EXTRA COMMANDS IN THE ROOT FILESYSTEM + +If you want to run further commands inside the root filesystem, for +example additional C<yum> installs, then use C<febootstrap-run>. See +the L<febootstrap-run(8)> manual page for more details. + +You have to be careful about modifying files in the root filesystem +directly (without using C<febootstrap-run>). It's easy to confuse +fakeroot and end up with the wrong permissions on files (see FAKEROOT +LOGFILE below). + +C<febootstrap-run> runs the command inside the root filesystem, which +means it won't normally have access to files outside the root. You +can use C<FAKECHROOT_EXCLUDE_PATH> environment variable (see +L<fakechroot(1)>) or copy files into the root first. + +=head2 FAKEROOT LOGFILE When febootstrap is run as non-root (the normal case) we use fakeroot so that yum thinks it is running as root. Fakeroot keeps track of "real" file permissions in a log file which is saved into the target directory as C<I<TARGET>/fakeroot.log>. -You can use the fakeroot logfile in a number of ways: +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: -=over 4 + echo updated-content > old-file -=item * +(since that preserves the original inode). In most cases it's usually +safest to use C<febootstrap-run>. -Run +You can use the fakeroot logfile in a number of ways: - fakeroot -i fakeroot.log command +=over 4 -in order to run a command with the faked file permissions. If the -command will make updates, then do: +=item * - fakeroot -i fakeroot.log -s fakeroot.log command +Use L<febootstrap-run(8)> to run a command with the faked file +permissions. =item * @@ -109,7 +128,12 @@ tool C<febootstrap-fix-root> (requires root). =back -=head1 COMPARISON TO debootstrap +=head1 RUNNING FEBOOTSTRAP AS ROOT + +There is some rudimentary support for running C<febootstrap> as root. +However it is not well-tested and generally not recommended. + +=head1 COMPARISON TO DEBOOTSTRAP febootstrap cannot do cross-architecture installs (C<debootstrap --foreign>). The reason is that C<%pre> and C<%post> scripts cannot @@ -153,6 +177,7 @@ L<http://et.redhat.com/~rjones/febootstrap> L<febootstrap-to-initramfs(8)>, L<febootstrap-minimize(8)>, +L<febootstrap-run(8)>, L<fakeroot(1)>, L<fakechroot(1)>, L<yum(8)>, |