Btw, you are not the "cranky" responder - any similarities to your "name" are coincidental...:-) I have libcom_err.so.2 in /lib so I went there and created a link to this with libcomm_err.so.3. Should I have done something else? Thanks! --- Andy 'Cranky' Green <fedora@xxxxxxxxxxx> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thursday 13 November 2003 15:16, Globe Trotter wrote: > > > Yes, I meant libcom_err.so.3. Sorry! The cranky responder basically > > suggested looking up the posts which had symlink as a hack. Which did not > > work. The other solution, getting the openafs source rpms did not do much > > either. > > What exactly did you do to link what to where, and what were the 'don't work' > > symptoms before and after? I ask because I suffered similar complaints about > > the same library and the symlink made the most definite fix for it. > > - -Cranky > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.2 (GNU/Linux) > > iD8DBQE/s678jKeDCxMJCTIRAgtAAJ0fH2CNr0B60x1FV6Xn+X/T9+UKUQCfQyFw > Wouo0+VIf8gNsCPUCUBxcdc= > =CEj3 > -----END PGP SIGNATURE----- > > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > http://www.redhat.com/mailman/listinfo/fedora-list __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
