From d52fcf7521b8f9b1ec7bbeaaf93840af37d363cf Mon Sep 17 00:00:00 2001 From: Richard Jones Date: Mon, 11 May 2009 14:51:22 +0100 Subject: Be more careful about removing files in fakeroot during minimization. Added febootstrap-install program. --- febootstrap.pod | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) (limited to 'febootstrap.pod') diff --git a/febootstrap.pod b/febootstrap.pod index 109f6a2..e208603 100644 --- a/febootstrap.pod +++ b/febootstrap.pod @@ -129,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 @@ -139,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. @@ -156,6 +159,11 @@ 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. @@ -218,6 +226,7 @@ L L, L, L, +L, L, L, L, -- cgit