Help with using a remote xserver

[bewhite]

Hello all,

I'm posting here because this used to work when I was using Slackware.  I
have a mac (my wife won't migrate to Linux ... yet!) and a linux box
connect by ethernet.  I run X11 on the linux machine, and because the
monitor on the mac is so much nicer, I like to use a X server on it.
There is a free xserver for the mac called MI/X.  Worked fairly well
before I migrated to debian, but now when I try to start a client on that
display I get the following errors:

whitehouse$ xterm -display powermac:0.0 
_X11TransSocketINETConnect: Can't connect: errno = 111
_X11TransSocketINETConnect: Can't connect: errno = 111
_X11TransSocketINETConnect: Can't connect: errno = 111
_X11TransSocketINETConnect: Can't connect: errno = 111
_X11TransSocketINETConnect: Can't connect: errno = 111
_X11TransSocketINETConnect: Can't connect: errno = 111
Error: Can't open display: powermac:0.0
whitehouse$

It also doen't work when invoked with

whitehouse$ xterm -display 192.168.1.2:0.0

This gives the same error.  So what gives.  I seem to have everything set
up on my mac the same as before.  I've gone through the docs about X11 in
/usr/doc and yes I have Anybody as my secondline in /etc/X11/Xserver.

Any help with this would be greatly appreciated.

Thanks,

Ben


Benjamin T. White, M.D. | [EMAIL PROTECTED]
Dept of Neurosurgery| http://members.aol.com/benmd/home.html
Bowman Gray SOM |




--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Year 2000

[bewhite]

Arran,

Although linux may be year 2000 safe,  You also must assure that all
application programs are also clean.  It much more likely that an
application program will will have the fatal hidden flaw that will bring
you down.

Ben


Benjamin T. White, M.D. | [EMAIL PROTECTED]
Dept of Neurosurgery| http://members.aol.com/benmd/home.html
Bowman Gray SOM |


On Sun, 2 Nov 1997, Bruce Perens wrote:

 There is a year-2000 problem we know of that is connected to your PC's
 BIOS and clock chip. The BIOS and clock chip of many systems store a
 two-digit year. This is a separate issue from the Linux kernel clock,
 which is all software. Linux uses a program to read the hardware clock
 into the software one at boot time, and then does not refer to the
 hardware clock again except to set it or to measure its drift over time
 and correct for that. A patch to the hardware clock reader is necessary
 to achieve year-2000 compliance even if your BIOS and clock chip think
 it's 1900. We expect to be distributing this with Debian 2.0 . Since we
 publish all source code, anyone can fix it sooner if necessary.
 
 Unix and Linux store time as a count of seconds since New Year's day
 1970 in a signed 32-bit integer. This was chosen to make the system
 time-zone-independent. This form of time storage does not have a
 year-2000 problem, but it will overflow in the year 2036. By that time
 we expect to have converted to a 64-bit variable, which will not
 overflow for around 274877906944 years. Hopefully, by that time
 something better than Unix will have come along.
 
 Several other year-2000 issues have already been found and repaired.
 We've run our systems with the clock set to various future dates to test
 them. We can't guarantee there are not any problems left, but we are sure
 they would be minor ones, and rapidly repaired. Because we publish all
 source code, you are guaranteed that you can get any problems fixed quickly.
 
   Thanks
 
   Bruce Perens
 -- 
 Can you get your operating system fixed when you need it?
 Linux - the supportable operating system. http://www.debian.org/support.html
 Bruce Perens K6BP   [EMAIL PROTECTED]   NEW PHONE NUMBER: 510-620-3502
 
 
 --
 TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
 [EMAIL PROTECTED] . 
 Trouble?  e-mail to [EMAIL PROTECTED] .
 
 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? 
e-mail to [EMAIL PROTECTED] .