A question about how dvipsk workd (if you have a moment to spare)

[Daniel Arden Ost]

Is there some way to make dvipsk look for pk fonts before
it looks for vf fonts?

The reason I'm asking is because we have no .vf fonts installed
in our texmf tree and lots of .pk fonts. Since the texmf tree
lives on a NFS mounted drive, dvipsk is taking a hideously
long time searching through the entire texmf tree only to
discover that no .vf files exist before it looks for the pk
files (which it usually finds in about 5 tries according
to truss).

When dvips is run on the machine that hosts the texmf tree,
behavior is better, but still painfully slow.

What I'd like to do is reverse the search order so that
dvipsk looks for pk files before looking for vf files, but
after looking through the source, I've realized that it will
be no trivial exercise to figure out what's happening well
enough to be able to make the necessary changes.

If you have a moment to spare on such a puzzle, could you
please tell me where to start my search in the source to
make the necessary changes?

Thanks for your time.

Dan Ost

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Do noT ADjuSt yoUr minD
iT IS rEAliTy tHaT Is maLfUNctIoNIng
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.vuse.vanderbilt.edu/~ostda/homepage.htm