proven@eng.umd.edu (Christopher Provenzano) (09/09/89)
Please, no flames. This is my first posting ever.
I have X11/R3 running under SUNOS4.0.1 on a 3/110. I'm using xdm as the
startup and have turned off the getty in /etc/ttytab. In the kernel I have
both the bwtwo and cgfour frame buffers so I can use either a color or b+w.
My question is, how do I get xdm to recognize the color so that
I come up in color as default and not b-w? (If you've got it use it.)
X recognizes the color as display 0.1 on the computer.
Thanks
--
Christopher A. Provenzano Computer Aided ____ _ ____
System Manager Life Cycle Engineering / /| / /
Department of Mech. Engr. / / | / /
email: Merryversity of Uniland / /__|___ /___/
proven@abyss.eng.umd.edu College Purgatory / / | /
phone: (301) 454-7705 College Park MD 20742 /_______/ |__/ @keith@EXPO.LCS.MIT.EDU (Keith Packard) (09/09/89)
> I have X11/R3 running under SUNOS4.0.1 on a 3/110. I'm using xdm as the > startup and have turned off the getty in /etc/ttytab. In the kernel I have > both the bwtwo and cgfour frame buffers so I can use either a color or b+w. > My question is, how do I get xdm to recognize the color so that > I come up in color as default and not b-w? (If you've got it use it.) > X recognizes the color as display 0.1 on the computer. The obvious answer is to modify the entry in Xservers by changing the display name xdm uses for the server: :0.1 local /usr/bin/X11/X Unfortunately, this doesn't work as xdm makes the assumption that the display number is everything following the last colon in the name. When we wrote the new color frame buffer code and discovered that many operations are now faster in color than monochrome on our sun, we wanted to do the same thing, only to discover this bug. "Fixed in R4" Keith Packard MIT X Consortium