summaryrefslogtreecommitdiff
path: root/README.install
blob: 5933eae0fa656f49fc9edf98c9e6ac9102ae453f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
QUICK NOTES ON INSTALLATION/USE:

If you didn't compile Gnome yourself, make sure you have the appropriate
-devel packages installed.

============
If you want to install OVER RedHat or Ximian/HelixCode packages use,
following configure options:
--prefix=/usr --sysconfdir=/etc/X11 --localstatedir=/var
--enable-console-helper --with-pam-prefix=/etc
However, there is now a spec file so you can build an rpm by just doing

rpm -ta gdm-<version>.tar.gz

This should work on RedHat 6.x and maybe even 7.0, and if you're very
lucky then on your favourite other distribution, but no promises.  Gdm is not
a trivial package so it's more likely it won't work in other places out
of the box.

If building from CVS, there is a script gdm-build.sh in the root of the
tree that you can use to build gdm and then install it with "make install".
The setup is a a redhat like one.

-George
============

WARNING: gdm is a *daemon* -- not a common user application. It
requires extensive knowledge about your system setup to install and
configure. gdm isn't - and never will be - Plug and Play
(i.e. ./configure ; make install). 

For security reasons a dedicated user and group id are required for
proper operation! gdm assumes that both the user and the group are
called `gdm'. Create these before running make install.

You should run ``make install'' as root to get the permissions right
on the authentication directory.

Configuration is done by editing the gdm.conf file (located in
<prefix>/etc/gdm/gdm.conf). If no config file exists, make install
will create one for you.

Put your (jpg, gif, png, xpm) picture in ~/.gnome/photo to make it
appear in the face browser.

When reporting bugs you should first turn on debugging in
gdm.conf. Your syslog daemon might not log debug information per
default so you should make sure daemon.debug events are logged to a
file. Include the resulting log in your bug report.