I agree with you Alexander, you're damn right.<br>Supporting a package wich provides remote access with security packages becomes a nigthmare,<br>if there is duplicated code.<br>Right now I use the proprietary nomachine's package, but I'd like to use a GPL version.
<br><br>Alexander, I didn't know that the GPL version of freenx had so many "implementation problems".<br>But it's still a great technology and it's worthy using ( a stable and without duplicated code version ).
<br><br>So, what would be the solution?<br>Creating a fork project?<br>Because, by what I've learned in this discussion, the actual freenx version will be very dificult to support in the future, and maybe the project could even be dropped in the future or totally rewritten.
<br><br>I think that if you guys feel like we can handle this chalenge, the first step would be creating a todo list and study the viability of a fork project.<br><br>What do you guys think?<br><br><br><div><span class="gmail_quote">
2008/1/9, Emilio Scalise <<a href="mailto:emisca@rocketmail.com">emisca@rocketmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So the only solution is to switch to xrdp + vnc4server (that on lan is good<br>enough for my needs), or nomachine proprietary packages if I really want to<br>use nx (on low bandwidth links, nx is unbeatable).<br>This is sad, but there are no other alternatives.....
<br><br>I hope that sometime the nx protocol will be implemented as an clean xorg<br>extension or an alternative with similar performance will be developed.<br><br>Il Wednesday 09 January 2008 10:22:07 Alexander Wirt ha scritto:
<br>> Emilio Scalise schrieb am Tuesday, den 08. January 2008:<br>> > There was a google summer of code about the integration of nx and xorg.<br>> > Nobody did it :-(<br>> ><br>> > I understand all the concerns about creating a "clean" package. But what
<br>> > about<br>><br>> Its not about clean, its about supporting and code duplication.<br>><br>> > a semi-ufficial package (maybe for experimental) until things will<br>> > change?<br>><br>> This package will never be accepted by the ftp-master. He told me that
<br>> personally. So - no - there is no chance.<br>><br>> > As all of you already said on the pkg-nx-group mailing list, Suse and<br>> > redhat do this, and event support it with security patches.<br>> >
<br>> > So why we can't do it? I don't want to start a religious flame.<br>><br>> You can do if you want. I'm personally not interested if the package won't<br>> go into main. And I don't want to do security support for such a nightmare
<br>> on my own.<br>><br>> > Like we do with ati and nvidia closed drivers we could write on the<br>> > description why freenx and nx is bad. Then the user will choose to use it<br>> > or not.<br>>
<br>> Its a nightmare to support. The debian security team will not.<br>><br>> Alex<br><br><br><br>_______________________________________________<br>Pkg-nx-group mailing list<br><a href="mailto:Pkg-nx-group@lists.alioth.debian.org">
Pkg-nx-group@lists.alioth.debian.org</a><br><a href="http://lists.alioth.debian.org/mailman/listinfo/pkg-nx-group">http://lists.alioth.debian.org/mailman/listinfo/pkg-nx-group</a><br></blockquote></div><br><br clear="all">
<br>-- <br>Meus cumprimentos,<br><br>Israel VinÃcius Nogueira Miranda