So the only solution is to switch to xrdp + vnc4server (that on lan is good enough for my needs), or nomachine proprietary packages if I really want to use nx (on low bandwidth links, nx is unbeatable). This is sad, but there are no other alternatives.....
I hope that sometime the nx protocol will be implemented as an clean xorg extension or an alternative with similar performance will be developed. Il Wednesday 09 January 2008 10:22:07 Alexander Wirt ha scritto: > Emilio Scalise schrieb am Tuesday, den 08. January 2008: > > There was a google summer of code about the integration of nx and xorg. > > Nobody did it :-( > > > > I understand all the concerns about creating a "clean" package. But what > > about > > Its not about clean, its about supporting and code duplication. > > > a semi-ufficial package (maybe for experimental) until things will > > change? > > This package will never be accepted by the ftp-master. He told me that > personally. So - no - there is no chance. > > > As all of you already said on the pkg-nx-group mailing list, Suse and > > redhat do this, and event support it with security patches. > > > > So why we can't do it? I don't want to start a religious flame. > > You can do if you want. I'm personally not interested if the package won't > go into main. And I don't want to do security support for such a nightmare > on my own. > > > Like we do with ati and nvidia closed drivers we could write on the > > description why freenx and nx is bad. Then the user will choose to use it > > or not. > > Its a nightmare to support. The debian security team will not. > > Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]