[tlug] If you upgrade FreeBSD to CURRENT

[Scott Robbins <scottro@example.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I don't know how many people might be affected by this, but as FreeBSD
becomes more popular (trendy?) it might affect some people.

There has been a change in LC_CTYPE.  If you upgrade to CURRENT, and are
using, for example, kinput2 and canna or anything that requires setting
the locale to Japanese, you might run into problems. 

The suggested workaround is to copy your /usr/share/locale before
upgrading, then set the PATH_LOCALE environment variable to point to the
old locale directory. 

A riskier fix (though I didn't see it break anything) is to add to
/etc/libmap.conf (the file may have to be created)
libc.so.5	libc.so.6

That solution has the potential, however, to break other things, and I
just mention it because it's the quickest and easiest.    

The most tedious one is to reinstall all programs that use libc.so.5,
starting with perl.  The easiest way to do this is with portupgrade -f. 

On a fresh install, that is, where I put in 5.4 from the CD, and
immediately upgraded via cvsup to CURRENT, then did portupgrade -f perl,
and only then installed X and the various Japanese programs I would
want, I didn't run into this problem. So I assume it will be fixed by
itself in the near future, or at least when CURRENT becomes STABLE>

Again, I don't know how many FreeBSD users there are here, and out of
them, how many are planning an upgrade to CURRENT, but thought I'd toss
the info out on this list.




- -- 

Scott Robbins

PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6


Buffy: She's playing you. She tried to kill you.
Angel: That was just. . . That was just a cry for help.
Buffy: A cry for help is when you say Help in a loud 
voice.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFCm75c+lTVdes0Z9YRAkQsAJ92ZhnhML36GYOUJtXaAp+1u34z6ACfeBO0
nm3rJl7Kddn8xHkwr6iucGo=
=A5V+
-----END PGP SIGNATURE-----