On Tue, Apr 08, 2003 at 11:16:23AM -0500, Thomas Dodd wrote: > > > Ossama Khayaat wrote: > > Mike A. Harris wrote: > >> > > Actually, I think I'll try to give more details about what's happening: > > * First of all, the PCs are Compaq Evo desktop PCs with an Intel 845 > > dispaly, and we have RH Linux 8.0 installed and running successfully or > > all the machines with no problems at all. > > So is this a problem with RHL8 or RHL9? > > Worked fine for me. If X is not running, it starts a new Xserver. > Using --reconfig probes everything to create a completely new config file. And hence the problem. If the X config is invalid, you can't change it and the syntax of the command isn't properly documented. If X doesn't start up at all, a new XF86Config isn't generated (I've demonstrated this and even bugzilla'd it) if the user has to c-a-bs out of the command. All should be good if redhat-config-xfree86 probes everything correctly, but if there are any issues at all, debugging them is a royal pain in the arse. Suggestions: 1. XF86Config should be generated *first*, before X starts up, and kept around if the user has to c-a-bs out. 2. redhat-config-xfree --help should document what the set-resolution paramter accepts. I'm not near an RHL9 system now, so I can't tell if there is a man page for redhat-config-xfree86. -- Ed Wilts, Mounds View, MN, USA mailto:ewilts@xxxxxxxxxx Member #1, Red Hat Community Ambassador Program
