From owner-freebsd-questions Thu Apr 5 7:51:39 2001 Delivered-To: freebsd-questions@freebsd.org Received: from yertle.kciLink.com (yertle.kciLink.com [208.184.13.195]) by hub.freebsd.org (Postfix) with ESMTP id 2566437B43F for ; Thu, 5 Apr 2001 07:51:34 -0700 (PDT) (envelope-from khera@kciLink.com) Received: from onceler.kciLink.com (onceler.kciLink.com [208.184.13.196]) by yertle.kciLink.com (Postfix) with ESMTP id 84CF02E45E; Thu, 5 Apr 2001 10:51:32 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.11.3/8.11.1) id f35EpWp59002; Thu, 5 Apr 2001 10:51:32 -0400 (EDT) (envelope-from khera@kciLink.com) X-Authentication-Warning: onceler.kciLink.com: khera set sender to khera@kciLink.com using -f To: Wyatt Banks , questions@freebsd.org Newsgroups: ml.freebsd.questions Subject: Re: using KDM to boot a visual login shell References: From: Vivek Khera Date: 05 Apr 2001 10:51:31 -0400 Message-ID: Organization: Khera Communications, Inc., Rockville, MD Lines: 68 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Posted-To: ml.freebsd.questions Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following message is a courtesy copy of an article that has been posted to ml.freebsd.questions as well. >>>>> "WB" == Wyatt Banks writes: WB> I use KDM to boot into a visual login shell, and this works fine when I WB> log in as root, but logging in as a user I added to the machine, I don't WB> get the K desktop Environment even though it is specified in the selection What KDM does is replace XDM. If you're using the same configuration for running KDM that you do for XDM, then you will have such problems. This is how the process works. kdm starts up and reads /usr/X11/lib/X11/xdm/xdm-config. This file definds what scripts get run and when. Pay particular attention to the 'DisplayManager*session' setting. It should point to a program such as Xsession, which is what does the real work. On my system, this is: --cut here-- #!/bin/sh # $XConsortium: Xsession /main/10 1995/12/18 18:21:28 gildea $ # redirect errors to a file in user's home directory if we can for errfile in "$HOME/.xsession-errors" "${TMPDIR-/tmp}/xses-$USER" "/tmp/xses-$USER" do if ( cp /dev/null "$errfile" 2> /dev/null ) then chmod 600 "$errfile" exec > "$errfile" 2>&1 break fi done case $# in 1) case $1 in failsafe) exec xterm -geometry 80x24-0-0 ;; kde) exec startkde ;; esac esac startup=$HOME/.xsession resources=$HOME/.Xresources if [ -f "$startup" ]; then exec "$startup" else if [ -f "$resources" ]; then xrdb -load "$resources" fi exec xsm fi --cut here-- Notice the line starting with "case $# in" and the case statement below it. You see the options there? Those must match the options in the kdm login window dialog box. This script is what implements those selections. You need to make sure that your Xsession script does the right thing. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message