[FreeNX-kNX] FreeNX: What is the file nxclient good for?
terander at guard.zapto.org
Fri Jul 6 18:26:44 UTC 2007
----- Melding fra ojkastl at gmx.de ---------
> On 07/05/2007 08:51 PM Johannes Kastl wrote:
>> Can somebody please shed some light on this issue, I would have
>> advised to delete the file in the packages, because of the above
>> mentioned problems.
> Thanks to everyone who answered, you really shed some light ;-)
> If I understand correctly, the file is necessary for the FreeNX
> nxserver to work. And, as Stefan changed the directories back to
> /usr/bin/, there should no longer be a problem, even when installing
> both FreeNX and nomachine nxclient on the same machine.
Correct. Actually if you want to have nicer/prettier dialog-boxes,
installing NoMachine NXClient on the server would actually achieve
this. FreeNX will automatically use the NoMachine NXClient for the
dialogs inside the sessions.
> Just my 2 cents:
> To avoid misunderstandings in the future, it might be good to think
> about renaming it, as it is very confusing to have two files with the
> same name doing different things. Especially newbies to NX could be
> easily confused.
I might agree with you on this, but it's easy to see why it was
named 'nxclient' when you read what its function is - to replace the
NoMachine NXClient. This nxclient-script is also not used when you
install the NoMachine NXClient on the server (as explained above).
In a retrospective view, I agree that the nxclient-script could be
named differently to avoid confusion.
Maybe something to think about for the next version, Fabian? Or is
it possible to include the NXClient from 2X (and maybe get someone to
work on NX3.0 compatibility for it? Is Rafael, or others from 2X,
reading this list, anyways?) ?
Clearly issues like this will have to be addressed in the
documentation for the upcoming release.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the FreeNX-kNX