RE: amrecover/amindexd problems, 242p1

[Carey Jung]

>
> We've gotten it working now, by going back to 2.4.2, applying the
> /dev/root
> fix, rebuilding, reinstalling, etc.  I'll look at amrecover diffs between
> 2.4.2 and 2.4.2p1 and see if I can track the problem down.
>

I misspoke.  We have it working now, running 2.4.2p1 plus the /dev/root
patch.  It's a reverse resolution problem.  Our temp fix is to create an
/etc/hosts entry, and we're tracking down the reverse resolution problem
now....

Carey