At least Jim Gillogly claims to have cracked it. See the "KRYPTOS" thread in news:sci.crypt. This article announces the break. This one mentions an NY Times article (no URL). He says he plans to publish the solution in The Cryptogram, the journal of The American Cryptogram Association
It's a bit better than a brick or a flung rock - from the New Scientist article - "At a speed of 250 kilometres per hour, the engines produce only a tenth of the lift. Nearly half of the lift comes from the four nacelles---even the vanes that direct the airflow generate lift. Another 16 per cent comes from the fuselage and about a third comes from the rear wing." Anyway, it's got eight engines, which ought to be enough for a brick.
Or whoever you had to contact to get the export licence for your own software from. I think the important question is "how will your government interpret the regulations if you supply Linux". We can't answer that (at least I haven't seen any replies from Austrian government officials). For example, does the 10% rule apply to a distribution as a whole, or each package, or every individual file in it? Does "American" mean written in America? Supplied from America? Containing any American code at all? If you get an answer you don't like, you then have to worry about whether it is worth the cost of challenging it in court, if possible. The simplest answer, if it's commercially acceptable, would probably be to tell your customer that that you are happy to supply the Linux version of your software, but that they will have to get Linux themselves.
> We made mouse pads by laminating patterns we'd print on a standard laser printer. We just photocopied the original mouse pads. By enlarging or reducing the copy, you could change the mouse sensitivity.
> Sun used to ship optical mice (from Mouse House or Mouse Systems) that used two wavelengths of LED I think it was one visible (blue stripes) and one IR (looked very pale yellow stripes). If you had the pad the wrong way round, the mouse got confused. I've often wondered why the Xerox style ones never became more popular.
The author of a piece of code has always been able to release it under multiple licenses. The new MPL doesn't change that just because it explicitly points out the possibility - the possibility of dual licensing (e.g. with LGPL) was discussed when the first version of the MPL came out.
You might want to look at the University of Utah's work on recursive virtual machines. http://www.cs.utah.edu/projects/flux/ ftp://mancos.cs.utah.edu/papers/fluke-rvm-abs.ht ml
Slashdot Mirror
At least Jim Gillogly claims to have cracked it. See the "KRYPTOS" thread in news:sci.crypt. This article announces the break. This one mentions an NY Times article (no URL). He says he plans to publish the solution in The Cryptogram, the journal of The American Cryptogram Association
Are you sure about the two wheels at the back, one at the front? Otherwise it sounds like it might be a Mercedes F300 Life-Jet ( more photos)
It's a bit better than a brick or a flung rock - from the New Scientist article -
"At a speed of 250 kilometres per hour, the engines produce only a tenth of the lift. Nearly half of the lift comes from the four nacelles---even the vanes that direct the airflow generate lift. Another 16 per cent comes from the fuselage and about a third comes from the rear wing."
Anyway, it's got eight engines, which ought to be enough for a brick.
Or whoever you had to contact to get the export licence for your own software from. I think the important question is "how will your government interpret the regulations if you supply Linux". We can't answer that (at least I haven't seen any replies from Austrian government officials). For example, does the 10% rule apply to a distribution as a whole, or each package, or every individual file in it? Does "American" mean written in America? Supplied from America? Containing any American code at all?
If you get an answer you don't like, you then have to worry about whether it is worth the cost of challenging it in court, if possible.
The simplest answer, if it's commercially acceptable, would probably be to tell your customer that that you are happy to supply the Linux version of your software, but that they will have to get Linux themselves.
> We made mouse pads by laminating patterns we'd print on a standard laser printer.
We just photocopied the original mouse pads. By enlarging or reducing the copy, you could change the mouse sensitivity.
> Sun used to ship optical mice (from Mouse House or Mouse Systems) that used two wavelengths of LED
I think it was one visible (blue stripes) and one IR (looked very pale yellow stripes). If you had the pad the wrong way round, the mouse got confused.
I've often wondered why the Xerox style ones never became more popular.
The author of a piece of code has always been able to release it under multiple licenses.
The new MPL doesn't change that just because it explicitly points out the possibility - the possibility of dual licensing (e.g. with LGPL) was discussed when the first version of the MPL came out.
You might want to look at the University of Utah'st ml
work on recursive virtual machines.
http://www.cs.utah.edu/projects/flux/
ftp://mancos.cs.utah.edu/papers/fluke-rvm-abs.h