On Wed, 30 Jan 2002 [EMAIL PROTECTED] wrote: > Greetings- > This is what I get when I type startx: > execve failed for /usr/x11r6/bin/x (errno2) > _x11transSocket unixconnect: can't connect: errno=2 > xinit: no such file or directory (errno2): unable to connect to x server > xinit: no such process (errno3) server error
In 'nix, capitalization is important. For instance, when you type "/usr/x11r6/bin/x" it should be "/usr/X11R6/bin/X". That sounds like it might be petty nitpicking, but if someone copy'n'pastes your error message, like maybe to see if he has that file, then he'll "discover" he doesn't have it either. Could lead to confusion. To the error itself... I'm not sure about BasicLinux, but /usr/X11R6/bin/X used to be a link to the correct XFree86 driver in the old days, and more modern distributions link X to Xwrapper, giving it more security from prying eyes. To be more specific, if you type $ ls -l $(which X) you should get something like one of these: (permissions snipped for line width) 1 root root 4 Jun 128368 23:05 /usr/X11R6/bin/X -> twm 1 root root 8 Sep 5 23:05 /usr/X11R6/bin/X -> Xwrapper The major point here is that "X" isn't an executable in and of itself, but simply an alias for whatever your system is really running, and if BasicLinux doesn't do it for you, then you need to manually make the link. # ln -s /usr/X11R6/bin/twm /usr/X11R6/bin/X or in generic terms, # ln -s <real file name> <alternative> > Well it sure looks pretty scary to rookie like me, but I am sure there > is a simple solution....like maybe downloading ?? x332bin.tgz again?? In many distributions, there's an MD5 sum on the download site. Once you download the file, you can issue this command to make sure the file wasn't corrupted during transmission. $ md5 sum x332bin.tgz Since the md5sum executable is only ~14k maybe that's something Steven might consider... (or for that matter, it might already be included). - Steve
