On Sat, 28 Dec 2002 08:28, Brian May wrote: > - The Author recommends linking with -static, so restoration programs > will work without extra libraries. I haven't decided if this is a good > idea or not, if it needs to be applied to all binaries. lintian > gets upset if my package contains static binaries.
I suggest having a separate "dar-restore-static" package for that. > - My version is compiled with ATTR (EA) support, however, DAR gets very > verbose if the filesystem doesn't support ATTRs (IMHO errors of type > "Operation not supported" need to be ignored). These warnings > will disappear if the -Uu flags are used (don't archive ATTRs). Maybe you could patch it to check for ATTR support on backup at the start of each file system. If a file system does not support ATTR then display a single message "File system /var does not support ATTR." and continue on with no further messages. Of course it's a bit more serious if you do a restore with ATTR support and the file system doesn't like it... > - ssh can be used for backups (just pipe the data via ssh to the > destination file), for incremental backups (generate catalog at server > and send it to client first). However, I am not certain about restores > (client requires 2 pipes to server, one in each direction; this makes > me nervous about potential deadlocks). Shouldn't be a problem, just do "ssh client restore-comand" and then the client's stdin and stdout are the two pipes you need. Gotta test it first of course, but I expect it to work. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page