freebsd-ports/x11/gdm2/pkg-message
Joe Marcus Clarke 9c0caae1c2 Update to GNOME 2.4.0. For all the goodies on what's changed, known issues,
future plans, etc., please see http://www.gnome.org/start/2.4/.

This commit represents work done by adamw, bland, and myself as well as
many other contributers:

Koop Mast <einekoai@chello.nl>
Akifyev Sergey <asa@gascom.ru>
Franz Klammer <klammer@webonaut.com>
Øyvind Kolbu <oyvind@kebab.gaffel.nu>
Thomas E. Zander <riggs@rrr.de>
Jeremy Messenger <mezz7@cox.net>

Without these contirbuters, and our faithful users, GNOME 2.4.0 would not
be possible.

Please check the FreeBSD GNOME site for any FreeBSD gotchas, as well as
general FAQs and documentation (GNOME 2.4 updates to be posted soon).  The
best way to upgrade so that you get all shared library dependencies is:

portupgrade -rf -m BATCH=yes atk
portupgrade -R -m BATCH=yes gnome2

Approved by:	portmgr (kris, will, myself implicitly)
Requested by:	re as well as many other users
2003-09-18 06:49:37 +00:00

25 lines
1.1 KiB
Text

GDM is installed.
Do _NOT_ use /etc/ttys to start gdm at boot time. This will result in gdm
hanging or restarting constantly. Instead, copy the included gdm.sh.sample
script to gdm.sh, and restart. This script is found, by default, in
/usr/X11R6/etc/rc.d.
GDM uses its own locale.alias file to determine its language and especially
the GNOME-2 fontencoding. This file is located, by default, in
/usr/X11R6/etc/gdm/locale.alias. By default, the character set for every
county using the EURO currency is set to ISO8859-15 in order to enable the
EURO sign. If you don't feel comfortable with this, edit this file according
to your preferences.
If you are running 5.x and you are running 5.1-RELEASE or earlier, GDM will
fail to work due to a bug in OpenPAM. You can download a patch from
http://www.FreeBSD.org/~marcus/pam_get_user.c.diff. You must also have the
FreeBSD src tree on your system. Do the following to apply the patch:
# cd /usr
# patch -p < /path/to/pam_get_user.c.diff
Then rebuild and install world. Note, this bug does _NOT_ affect FreeBSD
4.x.