Domain: hexonet.de
Stories and comments across the archive that link to hexonet.de.
Comments · 13
-
Re:VNC / Remote action
x0rfbserver. Run it in your main X session and it will make it remotely accessible by other RFB clients (such as xrfbviewer and vncclient). Oh, and you want version >= 0.6.1 (google for rfb-0.6.1.tar.gz if necessary)
. -
XMX - windown multiplexor
There's always XMX - An X Protocol Multiplexor, but I couldn't get it to work when I tried it (though I didn't waste too much time). The only "fault" is that you must run your primary session through it if you want to later have windown appear on many desktops. Dunno about its overhead. I just use x0rfbserver when I'm in a bind.
-
Re:Linux is catchings up...
The Unix VNC server does not mirror the current display. It provides a seperate remote display. On Windows VNC lets you use the current display which can be very usefull. I wish the Unix VNC server could provde this feature.
Try x0rfbserver This does what you want. It's been around for years and years.
VNC's approach of setting up a separate display is a design feature, designed to take advantage of X's natural ability to support more than one output display. You can also start the regular old AT&T VNC server such that it also starts X in the same session, giving you the same effect as x0rfbserver. This has been there since day one with VNC.
I only wish the Windows and Mac versions of VNC let you start a session that *didn't* control the current display. This is a failure of the design of the windowing systems under Windows and MacOS. Please don't attribute your lack of knowledge of VNC as a failure in the design of the X Window System or the Unix version of VNC.
-
Re:Linux is catchings up...* vnc (or other RFB) server support, so I can view my desktop -- the one shown on the monitor -- from another computer.
This has already been done, it's called x0rfbserver and it's linked to under the contrib section of the official VNC page.
From the page:
Description: x0rfbserver is a software application that is able to export an X desktop to another machine. It exports the framebuffer of the X server to one or more clients using strong compression and injects keyboard and mouse inputs from the clients into the server. The protocol used is the well documented RFB 3.3 protocol, so x0rfbserver should be compatible with every client speaking that protocol too, e.g. it should work together with the vnc viewers of AT&T. x0rfbserver provides a complete remote control of the desktop on the computer it is running on.
-
Re:Linux is catchings up...
Here is what you are looking for
x0rfbserver -
Hexonet rfb software (x0rfbserver etc)
See Hexonet's RFB software page, I just discovered them thanks to their package being included in Mandrake 8.2 (rfb-0.1.2-7mdk.i586.rpm).
Seems like a good follow-up to (seemingly dead) AT&T's VNC project...
BTW, if you have Mandrake 8.2, be sure to check out the rfbdrake utility (rfbdrake-0.8.2-13mdk.i586.rpm)! It looks awesome!
-
Re:VNC
What does x0rfbserver provide that plain VNC doesn't? Or why do you use it instead of VNC or with VNC?
-
Re:VNC
vnc is suppossed to be good and it works for free
VNC rawks. I just compiled x0rfbserver for a Debian Woody box (you'll also need the xclass libraries) and I can even see my
:0 display and use Win2VNC (Think x2x, but using Windows 2000 and some VNC frippery). Plain ol' VNC on a *NIX machine spawns an additional display. -
Re:Different is not easy for grandma
Yes and no. The discussion veered to what happens when you become the extended family's resident Tech Support department. This can as easily happen with Windows as with Linux (actually, it is more likely to happen with Windows, since it is more common and it breaks more frequently...)
As for VNC vs. SSH, I did remember one advantage of using VNC (to access a Windows machine, anyway), is that the person at the other end gets to see the cursor moving to the appropriate places (Control panels, etc.) and thus learns a thing or two about their machine (if they're paying any attention, that is). For Linux, though, you need to use a different program, which you can get here. I haven't personally tried it on Linux, but I've been told it works really well. -
x0rfbserver
I should make a caveat to this: The Windows98 VNC server will export the current user's desktop to the internet. So some of you windows users can do this already.
There's a modified VNC server for Unix (Linux only?) called x0rfbserver that exports the "real" desktop. It reads the system frame buffer and exports that using the VNC protocols.
Performance isn't quite as good as regular VNC but should be fine on a decent LAN. You find it here -
Re:Why not just use LBX, DXPC or X11-over-SSH?Sure, that's possible -- but VNC doesn't do this by default. You need to install something like x0rfbserver to do it. Basically, x0rfbserver captures the regular X framebuffer and serves it out using the RFB (Remote Framebuffer) protocol. Thus, you can bring up a presently running X session remotely using a regular VNC client -- more in the style of WinVNC. By default, Xvnc does not behave like this...
VNC is great for a lot of things: for instance, if you want to connect and control a presently running session (a la WinVNC or VNC through x0rfbserver), or if you want to, say, control an X desktop from a Mac or Windows machine that doesn't have (and you can't install) an X server. It all depends what you want to do, I suppose.
BRx.
-
Re:Still no support for resumable desktops
1
.Use my same desktop from anywhere in the house
2. Access my home's desktop from the computer laboratory in town
x0rfbserver. A Unix/Linux VNC server that acts like a Windows one, where the remote user takes over the desktop. -
I had a dream......And they did make it : (speak of free software magic !) The RFB server .
Now, you have the virtues of having both an X and VNC server at the same time. Port it to windows, get rid of that stupid explorer shell (is that possible ?), put gnome there...
And you end up with a big mess. That is, a ***ix UI on a M$ operating system. At least, it's going to give you a good april fish : tricking you friend into believe you'r runnig linux, but having windows instead (look at them jumpin' when they ain't no root). Moreover, with vnc, you will be able to screw up a lot more behind their back.More seriously anyway : one of the big advantage of that port is that you get an unified M$/Linux GUI, so you get GNOME applications across both OSes. IS that better that VMware ? I'm not so sure !
Another question : is that porting of gnome something more to credit to their U/WIN POSIX infrastructure than the GNOME code itself ? Granted, GNOME is clearly written in a well-portable way, but what else ?