Actually, an BSD guy solved the problem for me in a different, possibly
better, way.  Take a look, and decide for yourself.

>As I thought, the FreeBSD GENERIC kernel does include COMPAT_4.  I
>rebuilt the system anyway with the latest 5.4-STABLE since it'd been a
>while.
>
>Then I think I got NetBackup taken care of with this change:
>
># /etc/libmap.conf
>#
># candidate             mapping
>#
>libstdc++.so.3          libstdc++.so.4
>libm.so.2               libm.so.3
>libc.so.4               libc.so.5
>libpam.so.1             libpam.so.2
>
>
>I made the mappings global, even though we could do this per program
>or per path, such as [/usr/openv/] or [bpcd].  I made it global
>because there were just too many programs; and it's convenient to call
>the program without the full path.  Anyhow, if you disagree with these
>libarary mappings being global, let me know.
>
-Andrew

Jason wrote:

>
> Actually compat4x didn't do the trick and compat3x won't build.  What
> I ended up doing was copying /usr/lib/compat/libc.so.3 from my 5.4
> system to the 5.5 and backups ran like a champ last night.  I'm still
> not sure why my older system had that library in /usr/lib/compat, but
> I'm glad that it did.  If you have any ideas I'd like to hear, er
> read, them.
>
> Thanks for the pointer, though - that did get me looking in the right
> direction.
>
> On Thu, 18 Aug 2005, Ruben de Groot wrote:
>
> <<<SNIP>>>


-- 
Andrew Stueve
andrew.stueve AT neovera DOT com
571-437-5754