Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:Still requires creation of user "nx"? Noooooo! (Score 2, Informative) 257

by kormat (#28688127) Attached to: Google Releases Open Source NX Server

Actually the "nx" user isn't required, neatx supports operating without. However, NoMachine's nxclient doesn't support this, as it assumes that it should always log in as the "nx" user. So, if you're using !M's nxclient, you need to do a small bit of modification client-side. Here's an example of what to do client-side (though the beginning of the post is specific to FreeNX): http://www.felipe-alfaro.org/blog/2009/01/18/freenx-usermode-authentication-and-mac-os-x/

Steve, Neatx project lead

Comment: Re:NIH (Score 4, Informative) 257

by kormat (#28688001) Attached to: Google Releases Open Source NX Server

Good question -) However, have a look at the different language breakdowns between the codebases.

FreeNX:
5.4k lines of bash
233 lines of C
102 lines of expect

Neatx:
5.7k lines of python
400 lines of C
54 lines of bash

The bash in neatx is there to provide wrapping of the python code, so that any unhandled errors etc are logged. It's a belt-and-britches approach.

Steve, Neatx project lead

The universe seems neither benign nor hostile, merely indifferent. -- Sagan

Working...