Next Knoppix Release to Feature GPL'd FreeNX
linuxtag-reporter writes "The first day of LinuxTag, Europe's biggest Free Software event (expecting 25,000 visitors) already has one big highlight. It seems that Fabian Franz from the Knoppix Project hacked up a 'FreeNX Server' based on NoMachine's NX technology (poor NoMachine might lose business now). Fabian Franz presented a first preview of the 'GPL Edition' in a live demo together with Kurt Pfeifle. The demo showed sessions going from Germany to Italy just based on a slow WLAN connectivity (shared with hundreds of visitors). A connection lost due to bad network conditions was easily re-connected to, and a deliberately suspended session was revitalized too -- it was just like 'screen' with a GUI! A report on the official LinuxTag webpage says FreeNX will be publically released for the first time as part of the upcoming Knoppix-3.6 release. The Kalyxo project is building and hosting Debian packages of FreeNX and NX/GPL for everyone to use."
Besides being part of a future Knoppix release, what is NX?
Please assume that some readers (me, others?) don't know what "screen" is.
Maybe I should google for "linux screen knoppix" - that would be useful...
I could click on the nomachine.com link, but why should I have to?
-ac
But an F/OSS hacker has taken a company's proprietary work and made it available for free, even giving it a similar name.
Why is this a good thing?
If F/OSS developers want to speed up Linux, the corporate environment is where they should be looking. By doing this they have enabled corporations to get something for free which could cause a company (and a lot of potential Linux users) to go out of business.
How are the developers supposed to feed their children if they're unemployed?
LOL They got "NoMachine" now that it is a smoking pile of rubble.
(poor NoMachine might lose business now).
This is compounded by higher bandwidth charges due to their present Slashdotting. They'll be tits up in no time.
For the rest of us, gnoppix is the best bet. On a side note - what's the real benefit for gnoppix / knoppix outside of a kiosk or classroom environment?
It seems that Knoppix doesn't stop surprising everyone, being probably the most innovative Linux distro (introduced LiveCD and great hardware detection).
It would be great if other distro's developers tried going the same way - be innovative, be creative!. Now it's quite boring to have hundred of Kno* and *pix distros, every one built with philosophy "take Knoppix and replace two apps with your favourite ones".
Is there any way to financially support Knoppix?
First, free GPL'ed version of their chief product. Now, their server is slashdotted. Damn, what a bad day for them
How's NX any different/better? When it first came out, I gave it a look but didn't think speed was overly impressive...
VNC performance has always been unacceptable to me, even on LAN's. NX uses the X11 protocol, but it encrypts (via SSH) and compresses by itself so you don't have to open an SSH tunnel, etc. It can also play the sound on the local host.
NoMachine had opensourced the NX products, so anybody has the legal right of forking and renaming it.
Nothing particularly new: firms will continue to give money to NoMachine for support and administration tools.
Have fun...
Ciao, Renato
NoMachine opening the specification of what they do just will have a different market if the use of they technology standarizes enough. That will open doors to they own extensions, support, being anyway as the visible head of that technology, etc. I think that some of the ESR writings explain a bit better the advantages of doing that.
As far as I remember, NoMachine's NX software is based on GPL code, which means they had no choice but to release the source code.
I remember trying to build it from source when it first came out, but it proved rather tricky. It's nice that someone's now put in the time to make an easy-to-compile distribution of it.
A quick Google search led to interesting results. What do RMS and these ladies have to do with a server?
& ie =UTF-8&oe=UTF-8&q=freenx
http://www.google.com/search?sourceid=navclient
People who disagree with you are not automatically evil, greedy, or stupid.
It's great that this technology can now be incorporated directly into distributions, but I'm sorry that this couldn't be done with NoMachines rather than against them.
The vast majority of companies don't create Linux products, they create Windows products, so any company that creates new software for Linux should be appreciated, even if that software is closed source.
I'm definately not suggesting that any company involved in Linux should be given a free ride, I'm just saying that we shouldn't celebrate having outflanked a company that was contributing something to Linux.
BTW, I don't know anything about NoMachines in particular. Also, generally I think that the necessity of software being open source and free depends on where it fits into your system. Personally I don't mind close source applications, but I like to have my GUI toolkit open and free.
Newsforge article
Potential source for FreeNX Server
emacs can do that! what other apps do you need anyway?
This was linked from NoMachine's site, somehow I got to it before it died.7 .shtml?tid=11
http://www.newsforge.com/software/03/07/10/214624
from the article:
Thin client computing lets users run applications on a remote server and display the results locally. NX Client works something like VNC (see our recent story), but instead of using Remote Frame Buffer protocol, NX Client acts as an X Window server. Thin clients help contain costs by eliminating the need to install applications at each user's desktop, and improve security by limiting the availability of applications and data. The clients themselves can be dedicated hardware devices or regular computers running thin client software.
Like anything else, it depends upon what you're trying to do and how much performance you need/want.
Me, I use TightVNC over a VPN tunnel (cable modem) and it has acceptable performance. I do pay a performance hit when I use a graphical program such as a place & route tool (I'm an ASIC engineer) but it's by no means unusable.
Of course, I have been forced to use that same place & route tool over a 128Kbit ISDN line (years ago) so I'm quite pleased with what VNC allows me to do, both in terms of speed but more importantly in terms of freedom. When you do ASIC layout work for a living, you sacrifice a lot of family time if you can't detach/reattach ala VNC. So I'm pretty damned thankful.
That's not to say I don't welcome new applications if they better meet my needs. I'll be delighted to learn more about what NX offers just as soon as I can actually visit the proferred links!
- Leo
You don't use science to show that you're right, you use science to become right.
http://www.newsforge.com/software/03/07/10/21462 47.shtml?tid=11
NX is about networking - high latency/long distance(many hops) - are enough to run X applications.
....
Printing support. Connect to remote NX server - and print on your local printer.
Multimedia support - launch xmms remotely and hear the sound in your headphones
Introduction to NX technology
NX uses CUPS for printing support so you can print from remote servers to your local printers using the IPP 1.1 protocol. It's possible also to use my local printers exported by SAMBA which is quite useful ...
TightVNC is still horrifically slow (and somewhat bandwidth-consumptive) compared to RDP -- try them side-by-side some time.
...when it was called Citrix.
I'm against picketing, but I don't know how to show it.
There was nice article about the NX:
http://www.orangecrate.com/article.php?sid=677
argh I forgot to mention the disk shareing - so you export your local disk/home directory to the remote server trough SMB that is encapsulated in NX protocol and here it comes - you can use your files on remote server copy them/edit them and do whatever you want in secure way without the need to scp every few minutes.
NX is even mildly supportive of an open-source complete solution -- on the source download page (their site is ./'ed right now) it clearly says something to the effect that they expect a community-created packages will be assembled.
It's not obvious from what I've been able to connect to so far that isn't slashdotted as to whether you can connect to a Windows box from a Linux box (the orangecrate.com article linked further down shows a connection going from a windows box to a linux box)
That's actually 2 questions, though - "Does the technology support it" AND "does the LICENSE allow it?"
I'm assuming that the technical capability is there (just as it is in VNC)...
Last time I saw the EULA for a recent Windows version I saw in infamous "you may not connect with 3rd-party tools" clause in the license. Is that still there? Is using FreeNX (or VNC or anything else) to connect to a windows box remotely still a violation of the license?
Hacker Public Radio is our Friend
Think stateless migratable multiuser VNC sessions (last time I checked VNC was not multiuser...only one desktop after all). NoMachines product gets a lot closer to Citrix, which is one of three killer apps on Windows that does not have a decent analog in Linux (also Quark XPress [Scribus doesn't come close], Citrix [no X11 isn't even the same type of idea, neither is VNC], and unfortunately, Exchange (although SuSe's OpenExchange server is very, very close).
[RIAA] says its concern is artists. That's true, in just the sense that a cattle rancher is concerned about its cattle.
I wonder how this affects the proposed KDE/NX integration supposedly under development by Aaron Seigo? If you'll remember, this was mentioned way back in December in response to UserLinux shipping Gnome, but I haven't heard anything about it since... let's hope this FreeNX is desktop-independent.
For those still mystified as to what NX is, it is essentially X11 tunneled through SSH, with some clever caching to drastically limit the number of connections an X server/client need to make, to make the connection feel much quicker.
untechnical explanation: Normally a remote X session will have to make many hundreds/thousands of trips between the server and client, but NX uses a cache at both ends, only making the most necessary trips, and usually just sending a diff of the changes rather than the whole stream of data. (roughly speaking, of course, as I have absolutely no idea what I am talking about.)