[FreeNX-kNX] Upgrading my Debian Freenx server
Tim Jordan
tim at pcs-alaska.com
Wed Jul 13 19:44:25 UTC 2005
Fabian Franz wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Am Mittwoch, 13. Juli 2005 02:25 schrieb Tim Jordan:
>
>
>>Hello,
>>
>>Using:
>>
>>
>>> deb http://debian.tu-bs.de/project/kanotix/unstable/ ./
>>>
>>>
>>>
>>>> deb-src http://debian.tu-bs.de/project/kanotix/unstable/ ./
>>>>
>>>>
>>as my new sources, I did an apt-get install and apt reported it was
>>going to upgrade freenx to Version: 0.4.1-0alpha2. After it did I
>>
>>restarted the nxserver and did:
>>
>>
>>>mail:~# nxserver --status
>>>NX> 100 NXSERVER - Version 1.4.0-04-CVS OS (GPL)
>>>NX> 110 NX Server is running
>>>NX> 999 Bye
>>>
>>>
>>Should the Version show 0.4.1-0alpha2?
>>
>>
>
>Nope, version used is compatibility version with NoMachine.
>
>The -04 is the FreeNX version, which means 0.4.x tree.
>
>cu
>
>Fabian
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.4 (GNU/Linux)
>
>iD8DBQFC1F9yI0lSH7CXz7MRAp7KAJ42RUJyZVrArz8eEWuFhjFlf4qKuACfRUGQ
>dQVOOYLuDsn9PWObrffbDRQ=
>=bqQX
>-----END PGP SIGNATURE-----
>
>_______________________________________________
>FreeNX-kNX mailing list
>FreeNX-kNX at kde.org
>https://mail.kde.org/mailman/listinfo/freenx-knx
>
>
I found that I had to remove the .nx directory for my user account on
the server and client side before I could reconnect after upgrading.
I'm guessing this is because of the version change.
Is this standard procedure?
Thanks,
Tim
More information about the FreeNX-kNX
mailing list