Hi all,
I'm really surprised that nobody uses vnc's rawhide module to X. Module was completely unusable since 2nd March (got sigsegv) and no bugreport came to me :( . So looks that no one uses rawhide vnc (unlikely) or all need RANDR support and have national-specific keyboards and for this use vino or krfb (unlikely too). Or vnc module users are disgusted with sometimes nasty bugs and bugreporting and they prefer slower, but sometimes more reliable servers? This isn't sounds good for me :( . I'm really interested in how can I reconquer prestige of vnc module again :)
Regards, -A-
On 27/03/07, Adam Tkac atkac@redhat.com wrote:
I'm really surprised that nobody uses vnc's rawhide module to X. Module was completely unusable since 2nd March (got sigsegv) and no bugreport came to me :( .
I do the occasional anaconda/vnc install, but after installation for remote sessions I tend to use X/SSH tunnels for improved security, and less hassle with other people's firewalls.
I'm really interested in how can I reconquer prestige of vnc module again :)
Does Fedora include an open version of NX?
On Tue, 2007-03-27 at 11:00 +0100, Andy Burns wrote:
On 27/03/07, Adam Tkac atkac@redhat.com wrote:
I'm really surprised that nobody uses vnc's rawhide module to X. Module was completely unusable since 2nd March (got sigsegv) and no bugreport came to me :( .
I do the occasional anaconda/vnc install, but after installation for remote sessions I tend to use X/SSH tunnels for improved security, and less hassle with other people's firewalls.
This uses the stand-alone vncserver, not the vnc X module.
Jeremy
On Mar 27, 2007, at 8:05 AM, Jeremy Katz wrote:
On Tue, 2007-03-27 at 11:00 +0100, Andy Burns wrote:
On 27/03/07, Adam Tkac atkac@redhat.com wrote:
I'm really surprised that nobody uses vnc's rawhide module to X. Module was completely unusable since 2nd March (got sigsegv) and no bugreport came to me :( .
I do the occasional anaconda/vnc install, but after installation for remote sessions I tend to use X/SSH tunnels for improved security, and less hassle with other people's firewalls.
This uses the stand-alone vncserver, not the vnc X module.
Jeremy
i'll chime in and state that we here at the MMT use the X vnc.so module heavily for remote engineering support of our systems on the mountain. it saves a lot of grief to be able to just connect in and see/manipulate the telescope operator's desktop exactly as they see it. the vnc.so module is a lot easier to set up once and forget whereas the other options require operators to modify a bunch of stuff within their desktop config. we tried those and they were not very reliable due to those user config issues. we, of course, keep the vnc ports we used well-firewalled and require ssh tunneling to connect.
i have not yet had a chance to try out vnc.so in FC7t* or rawhide, though. we have not had any problems with FC6 or any previous version that included vnc.so (since FC1 or 2?). i will certainly squawk if it does stop working or goes away before FC7. it, in fact, would likely be a deal-breaker for us that would prevent us from using FC7 if it did go away.
tim
-- +--------------------------------------------------------------------+ | T. E. Pickering, Ph.D. | MMT Observatory | | Assoc. Staff Scientist | 933 N. Cherry Ave. | | tim@mmto.org (520) 626-3755 | Tucson, AZ 85721 | +--------------------------------------------------------------------+ overflow error in /dev/null
Timothy Pickering wrote:
i have not yet had a chance to try out vnc.so in FC7t* or rawhide, though. we have not had any problems with FC6 or any previous version that included vnc.so (since FC1 or 2?). i will certainly squawk if it does stop working or goes away before FC7. it, in fact, would likely be a deal-breaker for us that would prevent us from using FC7 if it did go away.
I use vnc.so module extensively on the daily basis to control remote headless servers, including the latest development build (4.16.07). No problem so far, with the exception of the double mouse pointers when viewing a XEN guess OS (domU) within a XEN host (dom0) that is within a remote viewer (sort of like viewing X within an X within an X). Of course, the workaround and better solution to the above problem would be to enable vnc server within domU and view from remote directly.
eric
Timothy Pickering wrote:
i have not yet had a chance to try out vnc.so in FC7t* or rawhide, though. we have not had any problems with FC6 or any previous version that included vnc.so (since FC1 or 2?). i will certainly squawk if it does stop working or goes away before FC7. it, in fact, would likely be a deal-breaker for us that would prevent us from using FC7 if it did go away.
It a feature like that is important it would be better for you to try out the development version or one of the test releases and provide feedback in the form of bugzilla reports when things don't work.
Rahul