On Fri, 14-Jun-2002 at 05:17PM -0400, Victor Roberts wrote:

|> What is the difference between XF86Config and XF86Config-4 ? From man
|> XF86Config it seems that if XF86Config exists then XF86Config-4 is not read.
|> Is that correct?

I doubt it unless Mandrake is quite different from RedHat.  I've just
been investigating this matter after being confused for a long time,
and have found out that if you do a

X -version 

and you get a 4 in the version number, your XF86Config file is not
being read at all.  If you haven't made major changes to your default
installation, it's highly likely that you're using Version 4.x.x.  It
appears that some people could have reason for wanting to use an older
version so the older format file is there for them to use.

Lots of stuff is now built into the X server so it doesn't need to
look for it in the config file as it did before.  It will get
additional information from the XF86Config-4 file (which you'll notice
is much smaller), but has its ideas as to what is a correct Modeline,
for instance.

|> Also, using Mandrake 8,2 I am unable to create a new XF86Config file that
|> works after I run xf86config. I always get an error message hat there is
|> something wrong with the XF86Config file. The only way to get X started is
|> to save the old file under a different name and then copy it back over
|> XF86Config. Is this a Mandrake problem of a general problem with xf86config?


I've not used xf86config, so I can't say.

best


______________________________________________________
The contents of this e-mail are privileged and/or confidential to the
named recipient and are not to be used by any other person and/or
organisation. If you have received this e-mail in error, please notify 
the sender and delete all material pertaining to this e-mail.
______________________________________________________
_______________________________________________
Newbie mailing list
[EMAIL PROTECTED]
*** To unsubscribe , or change message options, see:
http://XFree86.Org/mailman/listinfo/newbie

Reply via email to