diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-01-26 19:35:29 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-01-26 19:35:29 -0400 |
| commit | ff3c12725502451c8ab7da72797b2d69c4a66900 (patch) | |
| tree | 9dd9cbf99c180353826e48bd6cd2784e931cecbd | |
| parent | 6b48f740f1e55b8461757bed670f29bc87e186a4 (diff) | |
wording
| -rw-r--r-- | doc/walkthrough.mdwn | 20 |
1 files changed, 12 insertions, 8 deletions
diff --git a/doc/walkthrough.mdwn b/doc/walkthrough.mdwn index f375d4e44..231c3e543 100644 --- a/doc/walkthrough.mdwn +++ b/doc/walkthrough.mdwn @@ -394,15 +394,19 @@ For more details about the numcopies setting, see [[copies]]. ## untrusted repositories -Suppose you have a portable USB drive and are using it as a git annex +Suppose you have a USB thunb drive and are using it as a git annex repository. You don't trust the drive, because you could lose it, or -just because portable USB drives don't tend to last very long. You can -let git-annex know about this, and it will adjust its behavior to avoid -relying on that drive's continued availability. +accidentially run it through the laundry. Or, maybe you have a drive that +you know is dying, and you'd like to be warned if there are any files +on it not backed up somewhere else. Maybe the drive has already died +or been lost. + +You can let git-annex know that you don't trust a repository, and it will +adjust its behavior to avoid relying on that repositories's continued +availability. - # cd /media/usb - # git annex untrust . - untrust . ok + # git annex untrust usbdrive + untrust usbdrive ok Now when you do a fsck, you'll be warned appropriately: @@ -414,7 +418,7 @@ Now when you do a fsck, you'll be warned appropriately: failed Also, git-annex will refuse to drop a file from elsewhere just because -it can see a copy on the untrusted drive. +it can see a copy on the untrusted repository. It's also possible to tell git-annex that you have an unusually high level of trust for a repository. See [[trust]] for details. |