#2
|
||||
|
||||
We're aware of the fifos and devices not passing. It's something we'll look at in the future, but they -- unlike the other items -- tend not to be the kinds of things you'd want to copy.
Device entries in general shouldn't be copied (they're created and bound during the boot process). FIFOs are used to allow multiple programs can communicate through a "pipe" -- they're usually created every time programs launch, and don't really have "meaning" across an execution (they don't even have any contents), so we decided not to handle them (they're kind of like VM swap files and temporary files, to our mind). It's really not clear what you should do with them, really. I do not have plans to contribute to or extend the suite at present, at least: we have our own testing tools that we've developed internally, but they're not things we'd want to release to the public (and our competitors).
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Server drive won't mount after backup | rhennosy | General | 1 | 11-09-2007 03:49 PM |
Long Hang While Copying | BackerUpper | General | 4 | 06-12-2006 08:26 AM |
How to verify a Scheduled Backup? | tuqqer | General | 3 | 12-06-2005 06:50 PM |
(Zero-length) File caused SuperDuper to abort backup | alancfrancis | General | 7 | 08-31-2005 10:42 AM |
Smart Backup Error | bill s | General | 20 | 02-04-2005 09:46 AM |