Gene, > So in a roundabout way, tar's mouthyness coaxed me into buying a better > printer. And if the excludes work tonight, I'm happy, camping or...
If I may... I think the solution suggested by Nathan does not lean toward the excludes. Solving your problem by using a crafted exclude list that makes tar avoids all mount point directories and synlinks pointing to other filesystems has several drawnbacks. - most of the time, when you will upgrade your system, you may have to upgrade your update list, wondering once more why tar is spitting an error at you. - in the future, a system upgrade may result in merging two file systems into one, your exclude will still apply, that part will silently be ignbored in your backup My uinderstanding is that you should not play with the exclude list, let tar complain, let complains be logged (usefull for later debuging) but ignore these complains in the finale report (now I have no clue on how to do that). This looks like a more sustainable solution to me. Best regards, Olivier --
