[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freenx-knx
Subject:    [FreeNX-kNX] nxconnect released
From:       LROUFAIL () nc ! rr ! com (LROUFAIL () nc ! rr ! com)
Date:       2005-03-02 12:47:25
Message-ID: 5e0ba15df80b.5df80b5e0ba1 () southeast ! rr ! com
[Download RAW message or body]

That's a good point about the .ssh config.  That would be a good patch for someone to \
provide.

The source for NXWin is available on the nomachine site and the source for Cygwin/X \
is also available (I think NXWin is just a fork of this with a few changes - very few \
based on the changelog).

The X Server on the client is just launched as a separate application.  It should be \
possible to launch the Cygwin X server instead, but based on the changelog you would \
not get very good suspend/terminate behaviour.  If you can get Cygwin/X compiled then \
you could apply the nomachine patches and use your enhanced server instead of NXWin.

The way that nxclient, kNX, nxconnect, etc. work is that they call all the OSS \
components as separate executables.  For Nomachine this is necessary to avoid having \
to GPL their proprietary client.  For the rest of us it is a convenience.  We can \
write our clients without having to link to or modify the OSS components.  Especially \
on Windows, I am not interested in modifying their code.

- L

----- Original Message -----
From: Ben Voigt <bvoigt at kas.com>
Date: Wednesday, March 2, 2005 3:04 am
Subject: RE: [FreeNX-kNX] nxconnect released

> I would very much like a Windows client that plays more nicely 
> with an
> existing cygwin installation.  Specifically, it should use the 
> (frequentlyupdated) X.org Cygwin/X server that is installed as a 
> cygwin package.  It
> should have an option to use the XWin_GL server with its advanced
> capabilities.  And, it should NOT mess with my cygwin mounts 
> table.  The !M
> client always changes /tmp, which means the permissions change and 
> servicesfail.
> 
> Furthermore, to avoid the complaints concerning different keys for 
> differentservers, it shouldn't specify an identity file (private 
> key) at all.  That
> should be handled by ~/.ssh/config as all my other ssh keys are.
> 
> These changes are minimal I think, and if I had the source to the
> Windows/cygwin client I'd try to make them myself... but I don't.  
> So maybe
> your linux script will be more promising.
> 
> ****************************
> 
> Ben Voigt
> University of Pennsylvania
> Electrical Engineering PhD Candidate
> 
> voigt at seas.upenn.edu <voigt at seas.upenn.edu>
> BVoigt at kas.com <BVoigt at kas.com>
> 
> Support a Constitutional Amendment to protect the Pledge of 
> Allegiance and
> National Motto.
> Click here for more information. <http://www.wepledge.com/>
> 
> ****************************
> 
> 
> -----Original Message-----
> From: LROUFAIL at nc.rr.com [LROUFAIL at nc.rr.com]
> Sent: Monday, February 28, 2005 10:53 PM
> To: nxdevelopers at nomachine.com; freenx-knx at kde.org
> Subject: [FreeNX-kNX] nxconnect released
> 
> 
> I have decided to release a command line client based on the moznx
> libraries.
> 
> I figured there may be people who are interested in an alternative 
> clientthat do not want to mess with a browser plugin.
> 
> It is essentially an update to the old nxrun client released by 
> nomachine.It is currently linux-only, so let me know if anyone is 
> interested in a
> win32 version.
> 
> It supports 1.4.0 encrypted sessions.  it also supports having 
> different key
> files for different servers by just adding one line to your 
> configurationfile.
> 
> Details are at http://home.nc.rr.com/moznx/
> 
> 
> 
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 266.5.1 - Release Date: 2/27/2005
> 
> 


[prev in list] [next in list] [prev in thread] [next in thread]