>>(comments about making configure.in changes)
>>...
>I haven't, but it should not be too hard
>(famous last words ;0 )
No kidding! :-)
As I said, poke around for how readline is handled, and steal, steal,
steal :-).
And remember that when you need to make mods to a Makefile, they need to
be to Makefile.am (which is only in the CVS), not Makefile.in. Which,
in turn, means you need to be conversant with automake (another of life's
adventures :-).
>Calcsize works fine for ufsdump, xfsdump and the dump on Sunos 4.1.
>(though xfsdump is faster [when I tested it (a year ago orso)])
When I suggested disabling calcsize for dump, it was because I was not
sure it would be faster, especially when only two estimates are requested
(dump can estimate a level 0 very, very quickly). Also, calcsize alters
the access time on the directories it traverses. That's not nearly as
big a deal as altering the file access times, but still might be an issue
for some folks. I realize the final answer is probably close enough
(it better be :-).
So I guess since the default will be "no" (don't use calcsize), we
can leave the program test alone and allow it to be used for "DUMP"
without warning.
Speaking of getting the right answer, I haven't looked at the calcsize
code, but I assume it handles files with multiple links and files with
holes properly?
> Gerhard
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
