Parents (Total: 29)

The searched file hash is included in 29 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	5B783D0DED424F207AD1D0E328E0C3AE
PackageArch	x86_64
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageName	x11vnc
PackageRelease	3.3
PackageVersion	0.9.16
SHA-1	046D1AB7FD6D4E9C49530F7D2FE9777AC473F9F5
SHA-256	C173C6C1B433A5517955F2344184A91280FE27729807F8D6513CCAD0E12F5324

Key	Value
MD5	1DC3F6CBA537608B45FFA2C8357C0031
PackageArch	i586
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageName	x11vnc
PackageRelease	3.47
PackageVersion	0.9.16
SHA-1	0C428C15537603209FF5B83BFAE7F1EE11DD9355
SHA-256	DFC0CCD5C7ED2099C0934C644FA5E9765C8950E2171A35C3DDDC08A1F2F464D4

Key	Value
MD5	B37C62298F204F9D9472D7DBE63FB176
PackageArch	x86_64
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageMaintainer	https://bugs.opensuse.org
PackageName	x11vnc
PackageRelease	bp153.1.13
PackageVersion	0.9.16
SHA-1	18217A11BC2E5B382135A455A72FC8C572FF3EC8
SHA-256	194075ED4B52E30C92141C92B853AD289258C9D907F56A82D327888F8AF560A3

Key	Value
MD5	6F5E0C433C02AFBB7057A958F6B70B48
PackageArch	x86_64
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageMaintainer	https://bugs.opensuse.org
PackageName	x11vnc
PackageRelease	2.9
PackageVersion	0.9.16
SHA-1	1FA3BCA886449E85B2CB2D4AE8CF858E70BFA69F
SHA-256	796B3D9A1F23F859F1A7025CFA2C51D955EBB1FF1C5BF7D25AB3767D8782C2AD

Key	Value
MD5	A077A38C5D8432CD1D31FFF1C241D089
PackageArch	s390x
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageMaintainer	https://bugs.opensuse.org
PackageName	x11vnc
PackageRelease	bp156.3.8
PackageVersion	0.9.16
SHA-1	342ABC33E45CAE7714C724C9EB7F3EC97201D116
SHA-256	F528ED111BC37E9D41EE64119571B822C97120C58A5DBDB52EFCA3A600F09D65

Key	Value
MD5	132647055C18F6CA977D832852CE1F6E
PackageArch	x86_64
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageName	x11vnc
PackageRelease	lp152.3.3
PackageVersion	0.9.16
SHA-1	3CF4271433463AB356E04CF1F9512B574CA0605C
SHA-256	CA745869EF2A7A75432EF07627B1847CE8EA314A7C53967E1BF5C2AF2F93A8AE

Key	Value
MD5	8401224B84F8BBE9AAF416F47468F268
PackageArch	i586
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageMaintainer	https://bugs.opensuse.org
PackageName	x11vnc
PackageRelease	2.9
PackageVersion	0.9.16
SHA-1	3D06FC4C3228AE2D4C1B0E265AC9471DBF38C722
SHA-256	E5B7FBB47A1431D2C1A6F90F655E76855B5523E999206A205A53AF652CD830CA

Key	Value
MD5	F6F0C5EFE04DB5539CA1529B2985EB0A
PackageArch	x86_64
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageName	x11vnc
PackageRelease	lp152.3.3
PackageVersion	0.9.16
SHA-1	484A4E1D2B2E4F70204C2B4CADB833018AFF01FE
SHA-256	BC04CC950130BAABAD409688DCFA9537D20EA96B8823B99852DE0D203AFF4EAB

Key	Value
MD5	865E5A1D89FE232E59476A41FB3D8E23
PackageArch	x86_64
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageName	x11vnc
PackageRelease	lp153.3.3
PackageVersion	0.9.16
SHA-1	4864EF6685CFEB0225131B32DA404C023509CF8F
SHA-256	28871E91A7CA22D39EC77F1C3C04BC2D74830100FB754640EF15BDFE3B825C7C

Key	Value
MD5	24D94D6179AB611900005DD7D113D5FF
PackageArch	x86_64
PackageDescription	x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageMaintainer	https://bugs.opensuse.org
PackageName	x11vnc
PackageRelease	2.9
PackageVersion	0.9.16
SHA-1	4F3BA8F6EE0EBB4DD7A5F0EE598814145ADE76CD
SHA-256	A0C70373467CFE5F2708D2CE98158285DA7ACD7D0F9136875DFD3D998880468E