Date: Sat, 22 Jul 2000 00:20:52 -0500 From: "Mark A. Hummel" <mhumm@ispchannel.com> To: Glenn Johnson <glennpj@bayouhome.net> Cc: freebsd-questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Can't start xdm on boot ??? Message-ID: <39792F33.B7F7FFF4@ispchannel.com> References: <3978E49A.9BC088C0@ispchannel.com> <20000721222444.A65216@gforce.johnson.home>
next in thread | previous in thread | raw e-mail | index | archive | help
Glenn, My fault, I should've provided more information. I'm running FBSD 4.0 Stable. You're right, according to the FAQ, the changeover occurred with ver 3.2. My comments are below. I'm trying it now. Mark Glenn Johnson wrote: > On Fri, Jul 21, 2000 at 07:02:34PM -0500, Mark A. Hummel wrote: > > > I've followed the instructions in FAQ (How do I start XDM on boot?) > > to the letter and I still can't get to xdm on boot. What am I doing > > wrong? > > First, what version of FreeBSD are you using? The tty to use could be > different from what you read. I am not sure at what version the change > over occurred but older versions use ttyv3 and newer versions use ttyv8 > > > I used the /etc/ttys method by adding: > > > > xdm > > So you should have a line in /etc/ttys that reads: > ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm on secure Yes I do > The line is there by default, you uncomment it and change the off to on. Okay I'll try this. > > Then, in /usr/X11R6/lib/X11/xdm/Xservers I added: > > > > :0 local /usr/X11R6/bin/X vt4 > > This does not look right. Remove the vt4. According to the FAQ instructions there is a chance of a conflict between xdm and getty. One way to avoid this is to add the vt number in the Xservers file. I think I should've added vt9 since the X server counts the vty from one, while FBSD kernel numbers the vty from zero. > > It's as if I made no changes at all. I still have to startx to bring > > up KDE. > > After you have verified that the line in /etc/ttys is correct and have > fixed the line in /usr/X11R6/lib/X11/xdm/Xservers then at a command > prompt (as root) type the following to test it: > > xdm -nodaemon > > The xdm login screen should appear. Switch back to your console screen > (e.g. Alt-F1) then type Ctrl-C to kill the xdm process. If all is > well you will see xdm at your next reboot. However, you do not have to > reboot. You can do the following (as root): > > kill -1 1 > > This will cause the init process to rescan the /etc/ttys file and will > activate xdm. Note that you need to have a .xsession file in your home > directory and it must have the executable flag set. The .xsession file > contains whatever programs you want to start; man xdm(1). > > Since you mention KDE, you may want to try out kdm after you get > familiar with xdm. > > Hope this helps. > > -- > Glenn Johnson > glennpj@bayouhome.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39792F33.B7F7FFF4>