Greetings,

And to all who helped (Jose S., A.V. Flinsch, kk1, Julia C., Joan T., and,
last but not least, Civileme), you made it happen, it is a team success.
Thank you so very much. This is open source and open sharing at its best.
And, yes kk1, if giving up was an option, we would still be making funny
little marks in clay for our communication (cunneiform).

Just to summarize: the new "j" switch in tar was indeed the last piece.
Because the new tar version was very close to my current version, I just did
an update to the newer tar package. The irony was, just as the newer version
of bind 9 needed glibc 2.2--the reason for this whole excursion in the first
place--the newer version of tar also needed glibc 2.2. But I was able to
rebuild the tar src file for my platform, and it installed without a hitch.
After the tar upgrade, the bind 9 src file worked very nicely, and created
three beautiful rpms, bind, devel, and utils.

Because of buffer overrun exploits in earlier versions of bind, this complete
exercise was absolutely essential to the protection of my production box.
And, hell, in the process, I did learn a lot of new info about working with
src.rpm files.

After I install the new bind packages, and insure their integrity, I will
offer them up for anybody that might be interested in obtaining these rpms
without having to go through all I went through. Keep in mind, I am on a
LMDK7.2 platform, I have re-compiled my kernel to 2.2.19-4.1mdk, and I have
upgraded my shared libraries to glibc 2.1.3-18.3mdk.

As an old hippy from the sixties, I can only say that this feels like the
"Summer of love" once again :-) Thanks to all.......

Thank you,
Craig Woods
UNIX SA

Reply via email to