On Fri, May 12, 2000 at 10:23:07AM -0400, Mental wrote: > On Fri, May 12, 2000 at 03:11:56AM -0700, Ed Slocomb wrote: > > I just installed the frozen potato, and the cold spud tried to make me use > > xf86config to generate my XF86Config file. I outsmarted the icy tuber by > > hitting ctl-C and then saying "no" every time it asked me again, and then > > I used the bronze tool known as XF86Setup to get a suboptimal but perfectly > > functional XF86Config file in place. On the way, I had to get rid of the > > electric yo-yo known as gpm, because it was hijacking my mouse. If I were > > in charge, I'd drop gpm's priority to "optional" before releasing 2.2, but > > then I always purge the dratted package anyway. > > > > If I run out of ways to kill time at work, I'll do what other debian users > > do when they want a thorough X config-- I'll go out on the net and beg users > > of other distros and similar hardware for relevant snippets of their > > XF86Config files. > > > You know, you CAN use gpm and have it work quite nicely with X. This > issue has come up and been answered several times while I've been on > this list (about 3 weeks). > > Hint: use /dev/gpmdata as your Pointer for X.
Why? I've got gpm running to use the mouse on the console, and in my XF86Config the pointer section uses /dev/mouse, which is linked to /dev/psaux. And everything works just fine. Worked just fine when I was running slink, worked just fine when I was running potato, and still works just fine running woody. -- Mike Werner KA8YSD | "Where do you want to go today?" ICQ# 12934898 | "As far from Redmond as possible!" '91 GS500E | Morgantown WV | Only dead fish go with the flow.
