Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Eric Kimminau <eak@detroit.sgi.com>
To: ralf@uni-koblenz.de
Cc: Ariel Faigon <ariel@cthulhu.engr.sgi.com>,
	SGI/Linux mailing list <linux@cthulhu.engr.sgi.com>
Subject: Xwindows status?
Date: Tue, 21 Jul 1998 13:47:29 -0400	[thread overview]
Message-ID: <35B4D431.F77FB01B@detroit.sgi.com> (raw)
In-Reply-To: Pine.LNX.3.95.980721093249.5677D-100000@thebrain

Good morning!

We have wonderful news! linux.detroit.sgi.com is now online!

We are ready to progress to Xwindows are we are meeting a roadblock.

/usr/X11R6/bin/X is a link to Xwrapper. There is no link to an X server
in /etc/X11. On  a startx execution only results in the foloowing
messages:

_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2

waiting for X server to begin accepting connections .
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
..

upon killing the process we receive:
xinit:  No such file or directory (errno 2):  unexpected signal 2

waiting for X server to shut down 

[root@linux /root]# 

Obviously we are missing the actual XServer binary.
ANy chance I can get it from someone?

Thanks!
                      Eric.



-- 
---------1---------2---------3---------4---------5---------6---------7
Eric Kimminau                           FTA/RSA
eak@detroit.sgi.com                     Silicon Graphics, Inc
Voice: (248) 848-4455                   39001 West 12 Mile Rd.
Fax:   (248) 848-5600                   Farmington, MI 48331-2903

                 VNet Extension - 6-327-4455
              "I speak my mind and no one else's."
       http://www.dcs.ex.ac.uk/~aba/rsa/perl-rsa-sig.html

    When confronted by a difficult problem, solve it by reducing 
    it to the question, "How would the Lone Ranger handle this?"

  "I am a bomb technician. If you see me running, try to keep up..."
	
         "I am the great supportfolio, do you have http?"

        Copyright 1998, Silicon Graphics Computer Systems
        Confidential to Silicon Graphics Computer Systems
                ** -- not for redistribution -- **

  parent reply	other threads:[~1998-07-21 17:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-20 22:12 [Fwd: Proof Linux not just for geeks & nerds from IDG.net] Ariel Faigon
1998-07-20 22:12 ` Ariel Faigon
1998-07-21 13:58 ` ralf
1998-07-21 14:39   ` Ron G. Minnich
1998-07-21 15:02     ` Alan Cox
1998-07-21 15:02       ` Alan Cox
1998-07-21 16:34     ` Zach Brown
1998-07-21 16:53       ` Alan Cox
1998-07-21 16:53         ` Alan Cox
1998-07-21 17:47       ` Eric Kimminau [this message]
1998-07-21 17:54         ` Xwindows status? ralf
1998-07-21 17:58         ` Mike Shaver
1998-07-21 18:13           ` Eric Kimminau
1998-07-21 18:26             ` ralf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35B4D431.F77FB01B@detroit.sgi.com \
    --to=eak@detroit.sgi.com \
    --cc=ariel@cthulhu.engr.sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox