And guess what, you can apt-get JDK the whole Java stack from Sun! Isn't it fantastic? At the same time downloading Feisty Fawn, you may also want to check out more informations about Java on Ubuntu here, or here.
My guess is that there's some route issue inside kernel. Linux or USAGI guru out there, any hints?
...The most successful key telephone system in the world has a design limitation... when you determine the number of times your phone will ring before it forwards to voicemail, you can choose from 2, 3, 4, 6, or 10 ring cycles. Have you any idea how many times people ask for five rings? Yet the manufacturers absolutely cannot get their heads around the idea that this is a problem. That's the way it works, they say, and users need to get over it.And another story:
...the name you program on your set can only be seven characters in length. Back in the late 1980s, when this particular system was built, RAM was pretty dear, and storing those seven characters for dozens of sets represented a huge hardware expense. So what's the excuse today? None. Are there any plans to change it? Hardlyâthe issue is not even officially acknowledged as a problem.Funny. Comparing to that situation, customers today are a little spoiled ^_^
P.S. is that the same Boehm who developed a GC for C++?
P.P.S. There're several applet showcases of the library. I love the new Java applet splash when a applet lodaing.
For your convenience, I also post the poem here:
Tiger, Tiger Burning Bright Like a geek who works all night What new-fangled bit or byte Could ease the hacker's weary plight? To the most despised cast We'll bid a fond farewell at last With generics' burning spear The need for cast will disappear While Iterators have their uses They sometimes strangle us like nooses With enhanced-for's deadly ray Iterator's kept at bay When from collections ints are drawn Wrapper classes make us mourn When Tiger comes, we'll shed no tears We'll autobox them in the ears The int-enum will soon be gone like a foe we've known too long With typesafe-enum's mighty power Our foe will bother us no more And from the constant interface we shall inherit no disgrace With static import at our side, our joy will be unqualified O joyless nights, o joyless days Our programs cluttered with arrays With varargs here, we needn't whine; We'll simply put the args inline And as for noble metadata I'll have to sing its praises later Its uses are so numerous To give their due, I'd miss the bus Tiger, Tiger burning bright Like a geek who works all night What new-fangled bit or byte Could ease the hacker's weary plight?
A physicist, an engineer, and a computer scientist were discussing the nature of God. "Surely a physicist," said the physicist, "because early in the Creation, God made light; and you know, Maxwell's equations, the dual nature of electromagnetic waves, the relativistic consequences..." "An Engineer!," said the engineer, "because before making Light, God split the Chaos into Land and Water; it takes a hell of an engineer to handle that big amount of mud, and orderly separation of solids from liquids..." The computer scientist shouted:" And the Chaos, where do you think it was coming from, hmm?"
_________________
ps. discovered Sun Net Talk Program. It's a must to visit.
In general, a character is reserved if the semantics of the URI changes if the character is replaced with its escaped US-ASCII encoding. -- section 2.2or
Implementers should be careful not to escape or unescape the same string more than once, since unescaping an already unescaped string might lead to misinterpreting a percent data character as another escaped character, or vice versa in the case of escaping an already escaped string. -- section 2.4.2These can be real bugs in specific implementation! RFC is RFC. If one get to read it, read it very carefully :-)
The on-board Apollo Guidance Computer (AGC) was about 1 cubic foot with 2K of 16-bit RAM and 36K of hard-wired core-rope memory with copper wires threaded or not threaded through tiny magnetic cores. The 16-bit words were generally 14 bits of data (or two op-codes), 1 sign bit, and 1 parity bit. The cycle time was 11.7 micro-seconds. Programming was done in assembly language and in an interpretive language, in reverse Polish. Scaling was fixed point fractional. An assembly language ADD took about 23.4 micro-seconds. The operating system featured a multi-programmed, priority/event driven asynchronous executive packed into 2K of memory." -- Apollo 11: 25 Years Later by Fred H. Martin, Intermetrics, Inc., July 1994For short it's about an OS within 2K memory! Totally crazy from today's point of view :-)