"der.hans" wrote:
>
> moin, moin,
>
> doing a couple of filesystems lists and then diffing them to make sure
> they contain the same files. I'm running into a prob with files that have
> either special chars or spaces embedded in the name/path.
>
> find wants to turn special chars into gobbly-gook, whereas tar renders the
> escapes sequences. Use ls -b to turn the special chars into escape
> sequences it also adds escapes for spaces, which tar doesn't do.
>
> Either of these probs trips up diff when verifying that the file lists are
> the same.
>
> Anyone know a solution that doesn't require brute forcing with tools like
> perl or sed/awk?
>
Also, don't quite understand how your assembling your lists of files, but
having trouble with 'name/path'. But...
If your working with lists of files, and able to sort them, check out 'comm'.
If not able to sort, article 2.14 in 'Unix Power Tools' has a trick with grep
and diff.
There's also a 'dircmp', but it's not on my Linux. Unix P. Tools says it's a SysV
thing.
Mike D.
From
wlindley@wlindley.com" <
wlindley@wlindley.com Thu Aug 24 15:02:28 2000
From:
wlindley@wlindley.com" <
wlindley@wlindley.com (William Lindley)
Date: Thu, 24 Aug 2000 08:02:28 -0700
Subject: Oops
Message-ID: <
01C00DA1.AB6088A0.wlindley@wlindley.com>
J.L.Francois wrote:
> Your line breaks are greater than 75 characters per line.
Why, in this day and age, should messages have to contain hard newlines?
Why are long lines a problem for modern e-mail systems or viewers? Text
wrapping is not that difficult an algorithm... or is anybody out there
still reading messages on a dumb terminal?
\\/
http://www.wlindley.com
(text/plain)