backups with grsync, second update

wiki/src/blueprint/backups.mdwn

@@ -77,7 +77,7 @@ The documentation for the creation of the encrypted device [[is already written|
 
 * create an encrypted device.
 * install the grsync package.
-* paste [those lines](http://dustri.org/p/38e76b) in a `.grsync` file, then double-click on it.
+* paste [those lines](https://paste.debian-facile.org/view/raw/a7a7fe3c) in a `.grsync` file, then double-click on it.
 (grsync ask you first to confirm the profile you want to use. Just click on "Open")
 * define the destination (i.e your encrypted device)
 * test wildly! and please report your results
@@ -91,7 +91,9 @@ The documentation for the creation of the encrypted device [[is already written|
 
 ### Features to request
 
-* grsync should check if enough space is available on the destination before running
+* grsync should check if enough space is available on the destination before running.
+  Update: rsync 3.1.0 [introduces](https://rsync.samba.org/ftp/rsync/src/rsync-3.1.0-NEWS) a `--preallocate` option.
+  (Tails actually ships rsync 3.0.9)
 * grsync should ask for confirmation when the option "Delete on the destination" is activated
 * when user double-click on a `.grsync` file, a window appears to confirm which file to open. This may be confusing.
 
@@ -104,6 +106,7 @@ The documentation for the creation of the encrypted device [[is already written|
 * test restoration (see File → Invert source and destination). Then, at least, check files permissions.
 * test backup + restoration with symlinks and hardlinks in the Persistent folder.
 * eventually test remote backups.
+* see the [thread on tails-dev](https://mailman.boum.org/pipermail/tails-dev/2015-January/007931.html)
 
 rdup
 ----