Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!wanderer.nsi.nasa.gov!root From: root@wanderer.nsi.nasa.gov (Michael C. Newell) Subject: Re: X dropping characters when usin xdm Message-ID: <1993Jul9.000642.8384@news.arc.nasa.gov> Sender: usenet@news.arc.nasa.gov Organization: NASA Ames Research Center, Moffett Field, CA References: <1993Jul3.222820.9549@news.weeg.uiowa.edu> <21fjti$hlp@st-james.comp.vuw.ac.nz> Date: Fri, 9 Jul 1993 00:06:42 GMT Lines: 37 In article <21fjti$hlp@st-james.comp.vuw.ac.nz>, duncan@comp.vuw.ac.nz (Duncan McEwan) writes: |> In article <1993Jul7.121717.24764@news.arc.nasa.gov> root@wanderer.nsi.nasa.gov (Michael C. Newell) writes: |> I'm not sure that this is the full answer though. I think it may only |> apply when you run xdm from the command line. Even then, some quick tests |> I have just run have not resulted in the keyboard locking up (although |> I think I do remember this happening in the past). |> |> When you are running xdm from within /etc/rc.local, I don't think the |> nodaemon mode is applicable. I think you have to completely disable the |> getty on the console by turning it off in /etc/ttys. It's not. I was just being brief. The full story is in the docs that come with XFree86 (that's how *I* found out!) That's what happens when you throw together a prototype answer on the fly... The REAL answer is to dilligently read the documentation. Of course, nobody wants to; we all Just Want To Get Things Up Fast. That's the fun of having your own system. My real point was that it qualifies as a FAQ. It's a question, and it is VERY frequently asked. The real debate is *which* FAQ. It DEFINATELY belongs in the X FAQ. Does it belong in the 386bsd one? I think so, but there is a serious danger of too much information [which people don't read anyway because the JWTGTUF.] |> |> This sounds like a reasonable explanation, although I found that even when |> running xdm from /etc/rc.local, I had to kill the getty causing init to |> spawn a new one before the keyboard locked up. Presumably others are |> having keyboard locking problems without doing this? Absolutely. That's what the docs say to do!! Michael C. Newell NASA Advanced Network Applications mnewell@nsipo.nasa.gov