Message-ID: <3A24D212.A44181BA@cfl.rr.com>
Date: Wed, 29 Nov 2000 04:53:22 -0500
From: Mark Hounschell
Is SuSE planning to update /sbin/init.d/xdm , /sbin/SuSEconfig and /sbin/conf.d/SuSEconfig.kdm, and probably a few more, to make SuSE Linux 7.0 more aware of KDE 2.0?
I installed KDE 2.0 over RC2, using YaST on SuSE Linux 7.0. The version I installed was from the KDE 2.0 RPMs for SuSE 7.0 on the KDE site:
After much searching around for documentation, I came to the conclusion that there are a number of undocumented post-installation steps needed for KDE 2.0 on SuSE Linux. This is because SuSE is aware of old KDE but not KDE 2.0. In particular, xdm and SuSEconfig are set up for old KDE and old kdm.
In particular, to get the new kdm to substitute for the old one, I needed to make the following changes to /sbin/init.d/xdm , /sbin/SuSEconfig and /sbin/conf.d/SuSEconfig.kdm Summary: 1. Change some instances of /opt/kde/bin to /opt/kde2/bin 2. Add /opt/kde2/bin to some paths before /opt/kde/bin 3. Change SuSEconfig.kdm to use "," as a delimiter rather than ";" See detailed diff output below. Please note that since I am a dumb user and not a SuSE developer, I probably have done something wrong.
Is SuSE planning to update these three files, and probably a few more, to make SuSE Linux 7.0 more aware of KDE 2.0?
I hope so. In fact, I hope that SuSE has updates for these files, as well as detailed post-installation steps, either as part of an updated FAQ at http://www.suse.com/us/support/download/kde2/faq.html , or at the very least, as part of the update package mentioned at http://www.suse.com/us/support/download/kde2/index.html
Detailed diff output -------------------- /sbin/init.d/xdm: 35c35 < kdm|kde|KDM|KDE) DISPLAYMANAGER=/opt/kde/bin/kdm ;; ---
kdm|kde|KDM|KDE) DISPLAYMANAGER=/opt/kde2/bin/kdm ;;
/sbin/SuSEconfig: 532a533,537
if test -d $r/opt/kde2 ; then echo "KDEDIR=/opt/kde2" >> $r/etc/SuSEconfig/profile.SuSEconfig echo "export KDEDIR" >> $r/etc/SuSEconfig/profile.SuSEconfig echo "setenv KDEDIR /opt/kde2" >> $r/etc/SuSEconfig/csh.cshrc.SuSEconfig fi 616c621 < PATH =$PATH:$r/usr/X11R6/bin:$r/opt/kde/bin:$r/opt/gnome/bin:$r/usr/openwin/bin
PATH =$PATH:$r/usr/X11R6/bin:$r/opt/kde2/bin:$r/opt/kde/bin:$r/opt/gnome/bin:$r/usr/openwin/bin 618c623 < PATH=$PATH:/usr/X11R6/bin:/opt/kde/bin:/opt/gnome/bin:/usr/openwin/bin
PATH =$PATH:/usr/X11R6/bin:/opt/kde2/bin:/opt/kde/bin:/opt/gnome/bin:/usr/openwin/bin 623c628 < test -z "$WINDOWMANAGER" && WINDOWMANAGER=/usr/X11R6/bin/kde
test -z "$WINDOWMANAGER" && WINDOWMANAGER=/usr/X11R6/bin/kde2
/sbin/conf.d/SuSEconfig.kdm: 114c114 < KDEDIR="$r/opt/kde" ---
KDEDIR="$r/opt/kde2"
195,196c195,196 < type -p $wm &> /dev/null || continue < nWM="$nWM;$wm" ---
type -p $wm &> /dev/null || continue nWM="$nWM,$wm"
199c199 < nWM="$nWM;failsafe" ---
nWM="$nWM,failsafe" 213c213 < KDM_NOUSERS="nobody;"
KDM_NOUSERS="nobody," 222c222 < KDM_NOUSERS="$KDM_NOUSERS$USER;"
KDM_NOUSERS="$KDM_NOUSERS$USER,"
229c229 < USERSCMD="$USERSCMD$i;" ---
USERSCMD="$USERSCMD$i,"
250,251c250,251 < fi < ---
fi
261c261 < KDM_SHUTDOWN=None;; ---
KDM_SHUTDOWN=None;;
Are there any advantages to using kde2's kdm over kde1's kdm if you're using bothe kde1 and kde2?
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- Mark Hounschell dmarkh@cfl.rr.com