[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Getting KDE up and running.



-----BEGIN PGP SIGNED MESSAGE-----

On Sun, 10 Jan 1999 MallarJ@aol.com wrote:

> 1) Renamed /user/X11/bin/xdm to old.xdm and created a link from
> /usr/local/kde/bin/kdm to xdm in it's place.  According to the KDE docs, this
> is no problem - and in practice, it works like a champ.

Remember that if you ever upgrade your xbase package (planning on moving
to slink when it comes out?) that it will blow away kdm to replace it with
the new version of xdm.

> 3) Edited /etc/X11/window-managers and put /usr/local/kde/bin/kwm as the first
> line.  This brings up kwm when X starts the window managers.
> 
> 5) Edit /etc/X11/xdm/Xstartup_0 and right before the 'exit 0' statement, added
> all of the lines from the startkde script, except the 'kwm' line (since kwm
> was already started).  These lines start all the KDE applications after the
> user logs in.  

I don't think you should do it this way.  Assume for a moment that you
machine will have more than one user, and possibly one of your users wants
to run another window environment like Window Maker or Afterstep.  The kde
clients would still get run.  Plus (this is a biggie) you'll notice, if
you read the Xstartup and Xstartup_0 files, that THEY ARE RUN AS ROOT!  Do
you really want all your users to be running kfm with root privilages?
That would be BAD.

noah

  PGP public key available at
  http://lynx.dac.neu.edu/home/httpd/n/nmeyerha/mail.html
  or by 'finger -l frodo@ccs.neu.edu'




-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNpmCPIdCcpBjGWoFAQE3rAP/fDQygqO+r99Y2nGZJMGOVm8ZrtW+yerK
7MVg1msaLLKcB+Br2C0jKgTe8/VJzhiU5j4BrtQOyO3PAXyaSMW7OApVCIMZHd5h
nnO5GRxagFHKSJcm+CE5hO907cdq5J2L0BWoakP2OnkyElWtb+XbThRLVbwwBSoH
eySlkIThXus=
=pBwW
-----END PGP SIGNATURE-----


Reply to: