Rakhesh Sasidharan <rakhesh@cse.iitd.ernet.in> writes:

>Yes, that's what I ususally use to start X.  My XF86Config file is the one
>I use on my Free and OpenBSD partitions on the same machine, and that for
>the same version of XFree86.  SO I am assuming that my XF86Config file is
>working right.  I had tried startx first, but that gave some error of not

check device names etc. in your xfree config.  you can't expect
to simply copy an xfree config file and have it work right away.
if you made your own kernel, also check that you didn't comment out
the INSECURE option (I assume that you aren't running with the
aperture driver, otherwise you'd probably have mentioned it.)
it would also have been beneficial if you included the error text
the server spit out, since we might have some trouble guessing it.

>being able to find any screens (I am not on that machine now ... I shall
>run startx once more, and send the error after I get to it).  So I tried
>xinit, but that too failed.  Assuming they all call X in the end, I tried
>X to see whether that works, and that is when I got the above problem.

now.  so the problem is not "X", since it's working as expected (telling
you that you have not the appropriate privileges since it is not setuid)
but rather a configuration error on which the properly started X-server
(via Xwrapper via startx) barfs.

mkb