Actually, it should be pointed out that while Adobe has a copywrite on Postscript, they have made PDF an open standard.
PDF guidlines are freely availabe, and they make no requirements as for liscensing. There was an article some time back that mentioned a system that was using Display PDF rather than Display Postscript due to this very reason.
Besides which, I've got xpdf or gv, or any number of other PDF viewers not made by Adobe.
The headline here is totally misleading. Yes, what they are doing is indeed an inovation. I hate that fact, but still it is.
It is an automated feature of the server that automatically merges identical files into links. This is done transparently to the user. The innovation isn't from the fact it's symlinks, but from the fact it's an automated system. I'd imagine a part of it is a "copy-on-change" as well. Automatically copying the file to a new location when a change is made.
So yes... Throw them a bone, it is an innovation. Now.... Let's get it running under Linux.:)
Actually, Transmeta is very explicit that their programming efforts in VLIW for the Crusoe halts at full implementation of exact x86 compatibility. This question was asked of them during launch and the person speaking (CEO?) said that if Windows blue screened on an Intel chip, the Crusoe would faithfully duplicate it. The idea of fixing MS's code at the microcode level causes me to shudder no end. Consider what the VLIW instruction set is. It is effectively microcode. Never intended to be coded for directly. Someone did make the suggestion that Transmeta produce a translation layer for an "optimal" processor. That may indeed be worth looking at.
Slashdot Mirror
PDF guidlines are freely availabe, and they make no requirements as for liscensing. There was an article some time back that mentioned a system that was using Display PDF rather than Display Postscript due to this very reason.
Besides which, I've got xpdf or gv, or any number of other PDF viewers not made by Adobe.
It is an automated feature of the server that automatically merges identical files into links. This is done transparently to the user. The innovation isn't from the fact it's symlinks, but from the fact it's an automated system. I'd imagine a part of it is a "copy-on-change" as well. Automatically copying the file to a new location when a change is made.
So yes... Throw them a bone, it is an innovation. Now.... Let's get it running under Linux. :)
Actually, Transmeta is very explicit that their programming efforts in VLIW for the Crusoe halts at full implementation of exact x86 compatibility. This question was asked of them during launch and the person speaking (CEO?) said that if Windows blue screened on an Intel chip, the Crusoe would faithfully duplicate it. The idea of fixing MS's code at the microcode level causes me to shudder no end. Consider what the VLIW instruction set is. It is effectively microcode. Never intended to be coded for directly. Someone did make the suggestion that Transmeta produce a translation layer for an "optimal" processor. That may indeed be worth looking at.