From owner-freebsd-questions Thu Oct 12 7:28:37 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp2a.ispchannel.com (smtp.ispchannel.com [24.142.63.7]) by hub.freebsd.org (Postfix) with ESMTP id 7C8FA37B502 for ; Thu, 12 Oct 2000 07:28:32 -0700 (PDT) Received: from ispchannel.com ([206.31.81.146]) by smtp2a.ispchannel.com (InterMail vK.4.02.00.00 201-232-116 license 7d3764cdaca754bf8ae20adf0db2aa60) with ESMTP id <20001012143101.JQUE382.smtp2a@ispchannel.com>; Thu, 12 Oct 2000 07:31:01 -0700 Message-ID: <39E5CA83.506E7109@ispchannel.com> Date: Thu, 12 Oct 2000 09:28:19 -0500 From: Mark Hummel Organization: Innovative Solutions X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Michael Joyner Cc: FSD Subject: Re: How can I boot directly into KDE? References: <39E4FD6E.44DFB4A7@rv1.dynip.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael, Thanks! As a newbie myself, it took me a couple of trys to figure out exactly what I was doing, but it works now. One thing though when the KDE login window comes up (very nice btw), there's also another text login window that opens up in KDE as well. It looks just like a KDE terminal window with the command prompt displayed. Is there any way of preventing that from opening so the only thing I see is the KDE login window? Thanks again, Mark Michael Joyner wrote: > cd /usr/local/etc/rc.d > cat > kdm.sh > #!/bin/sh > (sleep 10; /usr/local/bin/kdm &) > # > #the sleep gives login a chance to get started before KDM starts > #or else the keyboard sometimes becomes locked up... :( > # > #the & IS CRITICAL! if not there your keyboard gets locked out > #because the boot process STOPS and WAITS for the daemon you just > #started to disconnect from the controlling terminal and it DOESN'T > ^D > chmod +x kdm.sh > ./kdm.sh > > "ROTHENBERG, MICHAEL" wrote: > > > > /etc/profile (might have the exact file wrong) is read first and only once. > > Usually .login/.profile as your login continues. The user files, > > .cshrc/.shrc/.*rc depending on the shell, are read for every shell that is > > started unless otherwise specified. > > > > The book: Unix Shells By Example has a great set of diagrams explaining the > > subtle differences between c shell, borne and korn shells and what files get > > read when... > > > > FYI, I made an error when trying to get KDE to start as login prompt and > > ended up being stuk in X login screen. The secret kill keys didn't work nor > > could I actually log in. It was interesting and then I had to hard reboot > > without shutting down. That was not fun. After entering single user mode and > > fixing the problem along with the other things that happen when power is > > abruptly stopped I chose not to have a window login just to be safe. > > > > -Michael the Unix newbie > > > > -----Original Message----- > > From: Rick Hamell [mailto:hamellr@heorot.1nova.com] > > Sent: Tuesday, October 10, 2000 9:27 AM > > To: Mark Hummel > > Cc: FSD > > Subject: Re: How can I boot directly into KDE? > > > > > I am using KDE, but I have to run it by using the startx command. I'd > > > like to boot directly to KDE. I've been told that this is very > > > possible, but I still can't figure out the process. > > > > Well, I'd personally put startx into my .login for the primary > > user of KDE... I'm not sure what other problems may arise from that > > though. Like, is .login read every time a new shell is opened... or? > > > > Rick > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > -- > > === > Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. > === > --- > Michael Joyner > Systems Administrator > mjoyner@rv1.dynip.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message