zsh won't be KDE startup shell

heh  {:}  You totally got these points.. but my new HD running only freebsd and I messed up
and made partitions instead of slices so the MBR comes up {:P  maybe if there is a way to
merge them back, but that wasn't really a priority I was sorta googling it..

but anyway.. so taking your advice.. umm.. The new KDE is acting different than the gnome I
had on the other HD.  Gnome sorta took over and gave me a GUI right from startup.. not so
with KDE.. I get a character based login.  KDE has taken over.. I tried to 'exec gnome-session'
but it still comes up KDE.. not a super big deal as I feel I have adequately done my Nessus junk
on the command line now.  

Anyway, though. so your advice changed the behavor.. I think I had put a line in .login or
.profile I forget

startx; startkde

and It starts up reallly slow.. When I took your advice and got my zsh on startup, I never got into
a GUI.  So I edited .zshrc and added the same startx; startkde.. so now I get a KDE after
login.. but there is a bad side effect.. When I want to open a terminal window in my KDE GUI I
get these same error messages that come in the character based as the shebang slooowly boots up..
if this is all too complex I could ask another question.  Here is  the error messages:

xauth:  creating new authority file /home/kayve/.serverauth.1219
^C
^C

Fatal server error:
Server is already active for display 0
        If this server is no longer running, remove /tmp/.X0-lock
        and start again.

^C
xinit:  unexpected signal 2.
^CKDE seems to be already running on this display.
^C
[13:00 kayve@kv_bsd~]


As you can see, I ctrl-C'ed out of it.. maybe I could have let it go.  Oh jeez.. Trying a second terminal
window.. got a couple dialog boxes that say "KDE seems to be already running on this display."

Okay. ctrl-c wasn't necessary, but this is sorta irritating behavior to deal with:

xauth:  creating new authority file /home/kayve/.serverauth.1332
xauth: (argv):1:  bad display name "kv_bsd.sfsu.edu:0" in "list" command
xauth: (stdin):1:  bad display name "kv_bsd.sfsu.edu:0" in "add" command


Fatal server error:
Server is already active for display 0
        If this server is no longer running, remove /tmp/.X0-lock
        and start again.

xauth: (argv):1:  bad display name "kv_bsd.sfsu.edu:0" in "remove" command
GOT SIGHUP
KDE seems to be already running on this display.
KDE seems to be already running on this display.
[13:10 kayve@kv_bsd~]

I already had such a file:

[16:21 kayve@kv_bsd~]cat .xinitrc
startkde
[16:22 kayve@kv_bsd~]

is the PATH my problem.

on the kdm and or gdm question, I am not exactly sure what I did, but I had my root prompt goin' on..
I got my wire up, and then I started trying stuff like "pkg_add -r kde" and "pkg_add -r gnome2" I think
I did both.. It wasn't working super kewl I might have went back into sysinstall by typing "sysinstall"
at the root prompt, and then I realized that the command 'startx' got me into that crazy older type
feel windowing stuff, and then it occured to me to run  the two pkg_add commands mentioned above
from there. KDE gave me a bunch of Uncle BIll style selection dialogs and at some point gnome put a
big leafy thing in my background but it seems like I am somehow all KDE now.. umm..

kv_bsd# pkg_info | grep gdm
gdm-2.20.1_1        GNOME 2 version of xdm display manager
kv_bsd# pkg_info | grep kdm
kv_bsd#  

hmm.. does that answer your question?  I remember feeling like gnome took over, but then all I get now
is "K" windows.

heh.. {:} maybe I should ask more questions.. I'm at the school lab right now instead of home..
it seems I don't really have to mess with /etc/resolv.conf that's supposed to mess with itself or
be autgenerated or something.. we added some lines to /etc/rc.conf:

# DHCP client (e.g. SFSU)
dhclient_program="/sbin/dhclient" # PATH to DHCP client program
dhclient_flags="bge0"  # additionalflags to DHCP client
background_dhclient="NO" # start DHCP client in the background
######

I don't have to take that out when I go home.. and to make it go I have to do this
command from root now:

kv_bsd# dhclient bge0
DHCPREQUEST on bge0 to 255.255.255.255 port 67
DHCPACK from 130.212.3.254
bound to 130.212.223.19 -- renewal in 3600 seconds.
kv_bsd#

is that something I could make happen on startup too?

Heh  {:}  I'm finally reading this page now:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-devices.html

maybe I can fix the mouse in the kernel better than we have it now?

http://www.monkeyview.net/id/965/fsck/fb7/kde/p5250022.vhtml

kv_bsd# cd /usr/local/etc/rc.d
kv_bsd# ls
001slpd.sh              gdm                     snmpd
avahi-daemon.sh         hald                    snmptrapd
avahi-dnsconfd.sh       mdnsd                   svnserve
cupsd                   nessusd                 system-tools-backends
dbus                    nessusd.sh              xfs
ffserver                polkitd
kv_bsd# cat /etc/rc.conf

# -- sysinstall generated deltas -- # Mon May 26 16:02:04 2008
# Created: Mon May 26 16:02:04 2008
# Enable network daemons for user convenience.
# Please make all changes to this file, not to /etc/defaults/rc.conf.
# This file now contains just the overrides from /etc/defaults/rc.conf.
hostname="kv_bsd.sfsu.edu"
ipv6_enable="YES"

#######
# home DSL
defaultrouter="192.168.0.1"
ifconfig_bge0="inet 192.168.0.2 netmask 255.255.255.0"
######

# DHCP client (e.g. SFSU)
dhclient_program="/sbin/dhclient" # PATH to DHCP client program
dhclient_flags="bge0"  # additionalflags to DHCP client
background_dhclient="NO" # start DHCP client in the background
######

ntpdate_flags="ntp1.mainecoon.com"
ntpdate_enable="YES"
moused_enable="YES"
# -- sysinstall generated deltas -- # Tue May 27 10:03:31 2008
ntpdate_flags="ntp.ucsd.edu"
ntpdate_enable="YES"
gdm_enable="YES"
kv_bsd#

umm.. I already  had gdm_enable are you saying the DHCP stuff is messing things up?

I get a character based nice looking prompt at startup.  startx needs to be ctrl -c'ed to work I think.

anyway.  .. right now I can ping freebsd but I can't browse the webserver