MFC of bump in libcom_err.so another mistake?

[Doug Barton]

Sean McNeil wrote:

> This is EXACTLY what I am saying.  I am not a -current user, I am a
> -stable user and this happened about a week ago or so.  It was
> libcom_err.so.2.1 until just recently.

I don't see how it could be libanything.so.2.1 on a FreeBSD system, given
that we dropped minor revision numbers on shared libs back at the elf
conversion. Also:

ls /usr/lib/*.[0-9].[0-9] /lib/*.[0-9].[0-9]
ls: /lib/*.[0-9].[0-9]: No such file or directory
ls: /usr/lib/*.[0-9].[0-9]: No such file or directory


I don't know where you got libcom_err.so.2.1, but I don't think it's from a
FreeBSD system.

Also, to make things clear, if you are using 7-current, this is the right
list to continue asking for help on. If you're using 6.0, you should ask for
help on freebsd-stable at freebsd.org. Before doing so however, if I were you
I'd take the following steps:

1. cvsup the latest sources for RELENG_6 (6-stable).
2. cd /usr/src ; make cleanworld
3. make buildworld ; make kernel
4. Follow the upgrading instructions in src/UPDATING
5. Go into /lib and /usr/lib, and do 'ls -lr', then mv any old libraries out
of those directories.
6. cd /etc/ ; mv libmap.conf libmap.conf.bak (it's ok if this file doesn't
exist)
7. reboot
8. Rebuild any ports that don't work, even if that means all of them.

Then I'd say you're in pretty good shape to start asking for help again,
presumably on freebsd-stable at .

Good luck,

Doug


-- 

    This .signature sanitized for your protection