diff options
| author | Richard Jones <rjones@redhat.com> | 2009-04-03 14:33:43 +0100 |
|---|---|---|
| committer | Richard Jones <rjones@redhat.com> | 2009-04-03 14:33:43 +0100 |
| commit | 467d77a9af3dbb1a4bcfbb9c7f97c8e300d6dca0 (patch) | |
| tree | 1b9441909a580011541a52e1788198c3ed8a8471 /febootstrap.pod | |
| parent | 2aecd64fe51659409760a2c1e15145325f09b7e6 (diff) | |
| download | febootstrap-467d77a9af3dbb1a4bcfbb9c7f97c8e300d6dca0.tar.gz febootstrap-467d77a9af3dbb1a4bcfbb9c7f97c8e300d6dca0.tar.xz febootstrap-467d77a9af3dbb1a4bcfbb9c7f97c8e300d6dca0.zip | |
On the need for "febootstrap-install".
Diffstat (limited to 'febootstrap.pod')
| -rw-r--r-- | febootstrap.pod | 12 |
1 files changed, 10 insertions, 2 deletions
diff --git a/febootstrap.pod b/febootstrap.pod index 1e4d9ff..a8f73ff 100644 --- a/febootstrap.pod +++ b/febootstrap.pod @@ -104,8 +104,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: |