...

...

What's SuperX ? a X server ? In that case, it has nothing to do with SaMBa...

[snipped]

Hi. I think, with all my respects, that you are wrong. There's no need to install samba in the linux box. An X server works under tcp/ip. Samba is for the windows net (nothing to do with tcp/ip; you can have both or any of them working good separately). Exactly, Samba is used for communication with the netbios protocol, the windows net protocol. Am I wrong? Santi

To add my useless 2 cents of kibitz (hopefully it will clear things up), SAMBA allows Linux to properly deal with and manage the Windows network filing system (SMB). It also provides the necessary pieces to speak the windows NetBIOS layer, which can run on top of other protocols, such as TCP/IP, IPX, or NetBEUI. An X-server is TOTALLY INDEPENDANT. In order for machines to send X protocol messages back and forth, they have *no need* to access each other's files. This would be analogous to installing SAMBA just so that you can telnet in. The X server, in case you were wondering, is the component of software that receives the lowest level of GUI protocol messages and decides how to raster them to the screen. On a local unix box, this is rather equivalent to a video card driver. On a windows box, it is generall software that translates the X messages into windows GDI calls (or maybe even directX these days, which is of course the totally unrelated and poorly named 'low level access' API in 95). Anyway, I don't have the answer, although I do know the DISPLAY env variable on the linux box should be something like 163.65.23.101:0 where 163.65.23.101 is your PC's IP address. The X server may have restrictions on which IPs are allowed to connect to it. You should investigate this. The X server will most likely have more than one method of connecting and authenticating. Investigate trying different options. Be sure of your password! Do you have some Super X docs? They may have some tips. If none of this gets you anywhere, try to at least narrow down where it's failing, and come back with what you do and what messages you get and where it fails (probably send the same message to super X). -josh -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Joshua Rodmanius wrote:

...

To add my useless 2 cents of kibitz (hopefully it will clear things up), SAMBA allows Linux to properly deal with and manage the Windows network filing system (SMB). It also provides the necessary pieces to speak the windows NetBIOS layer, which can run on top of other protocols, such as TCP/IP, IPX, or NetBEUI.

An X-server is TOTALLY INDEPENDANT. In order for machines to send X protocol messages back and forth, they have *no need* to access each other's files. This would be analogous to installing SAMBA just so that you can telnet in.

I see, I thought an x-server was just the local display server.

Yes. It is. This is what i said. The X server displays graphics locally on the machine it is running on. An X server running on a windows box displays output from X applications (X clients) on the Windows display. The point is you can connect to your linux box, and tell the X apps to direct their output to your Win95 box, thus using guis and whatnot on another machine. The programs will run on linux, but you will be able to use them from 95. Think of it as a GUI telnet. If you have further questions about how X works, feel free to e-mail me (although I am certainly not an expert), but I think you, and I and the readers of this list would be better served by a good source of information on X. Perhaps starting with the XFree86 howto and attendant documentation.

Also, is this the source of the security breach in X-windows, which I have been hearing about?

I believe this is about how X servers generally run as root, and setuid programs can be tricked into misbehaving at times. -josh -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e