I wrote about that. Luckily, each card vendor can write driver(s) for their range of cards and get them signed. These drivers would work in any OS that uses the microkernel.
This is pure speculation. You don't know. If it will be profitable to use it by locking content, it will be used this way. If more money is waiting to be made with unlocked content, then unlocked content will be produced. I personally don't know anyone who would consider buying unmovable content, but merely uncopyable content is not perceived as a problem by lots of people. So presumably producers of unmovable content will go bely up because nobody will buy their wares.
about how TCPA will kill open source. This outcome is very probable. But they can also work fine together. There is a solution, and open source people would do good by pursuing it instead of blindly fighting the inevitable.
TCPA needs an agreed-upon, standard microkernel around which different OSes could be built. A whole bunch of new open source OSes and, yes, new Microsoft OSes. This microkernel would be developed by an independent body and signed by DRM-loving vendors. Because it would be very small, and change very rarely, there should be little problem with it. Yes, end-users won't be able to modify it; that's the price one pays. They won't want to do it very much because the microkernel provides very little functionality.
Hardware vendors would release drivers for their wares that would work with this microkernel. These drivers would be otherwise OS-independent and would include decryptors and decoders needed for playing content. The vendors would get their drivers signed, too. (And open-source OSes will get closed-source drivers for free: a nice bonus!)
The rest of the OS and the entire universe of user apps would need not be trusted at all. They would run in user space and be totally unprivileged.
So I think open-source people should approach TCPA and offer to work together along these lines. There's nothing to lose, and much to gain, so why not at least try it?
You cannot copy the keys inside TCPA hardware. True.
Every time you buy a new PC with TCPA you will not be able to copy the old TCPA keys on your old PC to your new PC. True.
This means you will completely lose access to your videos and your music which you legally purchased and used on your old PC. Not necessarily true, because TCPA hardware doesn't directly contain keys to these items. It only contalins keys to your OS. Your OS contains keys to your DRM-enabled apps. Your apps have the keys to your multimedia.
If your apps are able to move keys from one computer to another, there's no problem. If they are not, do not use these applications. Moving (not copying) keys from place to place is a basic function that should be supported by every DRM-enabled app.
Web pages are already rated -- by other web pages. Ever noticed these blue underlined chunks of text? They are called links. Each link is a rating that says "Lookie here, I liked it and you might too!" And somebody already uses this rating system in a search engine. Bonus points for correctly guessing who.
I remember seeing it somewhere but can't seem to find any trace. In short, there was a robotic hand much like these guys use, but connected to a stereoscopic vision sensor. It was able to catch golf balls and paper airplanes thrown at it. Does somebody have a link?
So the record is 707k TPM on 64 CPUs, but Linux scores ~600k TPM on 32 CPUs, right? This is impressive, but I wonder why Intel didn't use a 64 CPU system for its tests. Maybe Linux scales poorly beyond 32 CPUs?
I wrote about that. Luckily, each card vendor can write driver(s) for their range of cards and get them signed. These drivers would work in any OS that uses the microkernel.
This is pure speculation. You don't know. If it will be profitable to use it by locking content, it will be used this way. If more money is waiting to be made with unlocked content, then unlocked content will be produced. I personally don't know anyone who would consider buying unmovable content, but merely uncopyable content is not perceived as a problem by lots of people. So presumably producers of unmovable content will go bely up because nobody will buy their wares.
TCPA needs an agreed-upon, standard microkernel around which different OSes could be built. A whole bunch of new open source OSes and, yes, new Microsoft OSes. This microkernel would be developed by an independent body and signed by DRM-loving vendors. Because it would be very small, and change very rarely, there should be little problem with it. Yes, end-users won't be able to modify it; that's the price one pays. They won't want to do it very much because the microkernel provides very little functionality.
Hardware vendors would release drivers for their wares that would work with this microkernel. These drivers would be otherwise OS-independent and would include decryptors and decoders needed for playing content. The vendors would get their drivers signed, too. (And open-source OSes will get closed-source drivers for free: a nice bonus!)
The rest of the OS and the entire universe of user apps would need not be trusted at all. They would run in user space and be totally unprivileged.
So I think open-source people should approach TCPA and offer to work together along these lines. There's nothing to lose, and much to gain, so why not at least try it?
They have zero bugs, right?
Every time you buy a new PC with TCPA you will not be able to copy the old TCPA keys on your old PC to your new PC. True.
This means you will completely lose access to your videos and your music which you legally purchased and used on your old PC. Not necessarily true, because TCPA hardware doesn't directly contain keys to these items. It only contalins keys to your OS. Your OS contains keys to your DRM-enabled apps. Your apps have the keys to your multimedia.
If your apps are able to move keys from one computer to another, there's no problem. If they are not, do not use these applications. Moving (not copying) keys from place to place is a basic function that should be supported by every DRM-enabled app.
With a spell checker, you would've written 'resurrected'.
Not yet, but he's showing some hope.
GTK+ is the underlying widget set of X?
are native widgets on X?
Web pages are already rated -- by other web pages. Ever noticed these blue underlined chunks of text? They are called links. Each link is a rating that says "Lookie here, I liked it and you might too!" And somebody already uses this rating system in a search engine. Bonus points for correctly guessing who.
If you just change the spelling a little bit and call it "e-chair", people will line up to try it.
Starship.
Then buy one.
All your codebase are belong to us.
It's blatantly obvious that this so-called "IBM code" is, in fact, a stolen Microsoft intellectual property. szCompanyName? Gimme a break.
It's a dispute over a trade mark, not any real name.
Just compile KDE. Good luck :)
yagi antenna (he calls it cantenna, too :)
with random access to CDs? Preferably scalable to a few thousand disks?
It explains. Honestly.
And Gentoo. In the recommended configurarion anyway :)
are horribly inefficient, and just plain wrong. I hope they don't make it into the standard.
These are not Linux drivers. These are Red Hat 7.3 drivers. I'll stick with NVidia for now, thankyouverymuch.
I remember seeing it somewhere but can't seem to find any trace. In short, there was a robotic hand much like these guys use, but connected to a stereoscopic vision sensor. It was able to catch golf balls and paper airplanes thrown at it. Does somebody have a link?
So the record is 707k TPM on 64 CPUs, but Linux scores ~600k TPM on 32 CPUs, right? This is impressive, but I wonder why Intel didn't use a 64 CPU system for its tests. Maybe Linux scales poorly beyond 32 CPUs?