We all know that the USPTO aren't exactly fantastic at finding prior art and reviewing patent applications particularly well, especially in the software arena. Whatever the reason for this, passing it off onto the applicant isn't going to improve this situation much. Whilst the USPTO might not find any prior art in checking an application, the applicant has no real incentive to find prior art either.
The only way it will make any significant difference is if an applicant doesn't submit an obvious piece of prior art, the USPTO find it in the accelerated review process, and then reject the patent on lack of detail in the application.
Seriously people, this article is simply an install and usage guide, without much of a comment on the timeline etc. Since most distros ship this stuff already (e.g. Debian), and have been for a while, it would seem to me that this code was written from scratch, unless MS was handing off code to Novell before the agreement.
So therefore we have not a copyright issue at all, but a software patent issue. Let the patent discussion begin!
Should be careful when you fling around names. Atheros do have a binary blob for their wireless chisp. But guess what, so does intel with their firmware. Atheros cards (supported by the madwifi driver) don't have firmware as such, most of it is done on the host PC. So they're pretty much equivalent.
Red lasers are the easiest to create of all. The issue is probably due more to the fact that red lasers don't have the same intensity for a similar powered blue laser and also focal for different wavelengths.
I wish I could describe it as well as done here http://monolith.sourceforge.net/, but what is the situation in terms of sending music encrypted, or as part of another file? For example, a part of a Britney Spears song might also be present in a Word doc, or the Britney Spears song, when in ASCII, might represent my password for my home computer. At what point is it illegal to actually transfer/upload/download these files? Is it only in the playing?
I know that's more than one question, but they're all related, and pretty critical when it comes to the concept of ownership/copyright in the digital space.
I think that this is an opportunity for people to quickly get help for a specific problem, but it REALLY depends upon the quality of the people on the other end of the line. It seems to me like an attempt at replacing the multitude of IRC channels that are out there to support all the open source projects.
Another factor is that none of the solutions will be archived, which means that a google won't turn up solutions, which is the first place almost everybody goes when looking for a solution.
I must say, I think Office vulnerabilities, especially in Powerpoint (the purveyor of all e-mail presentations), have the potential to be a lot more persistent. By that I mean, I know people who religiously update Windows, but don't give a second thought to updating Office. So it means that these vulnerabilities can hang around as unpatched for a lot longer.
The machine in question wasn't security.debian.org and it wasn't a distribution machine either. I'm pretty sure it was an old development machine, with no access to anything important, so the only real major concern is whether the same password was being used anywhere else (which could very much be possible).
You're probably better off using a VMWare offering on Linux with Win guests. Less reboots due to security updates of the host OS and no licensing costs.
Slashdot Mirror
nothing.
We all know that the USPTO aren't exactly fantastic at finding prior art and reviewing patent applications particularly well, especially in the software arena. Whatever the reason for this, passing it off onto the applicant isn't going to improve this situation much. Whilst the USPTO might not find any prior art in checking an application, the applicant has no real incentive to find prior art either.
The only way it will make any significant difference is if an applicant doesn't submit an obvious piece of prior art, the USPTO find it in the accelerated review process, and then reject the patent on lack of detail in the application.
Just wanted to point out that qemu can also do virtualisation on Linux, just like Vmware, with a closed-source kernel module. It works quite well too. http://fabrice.bellard.free.fr/qemu/qemu-accel.htm l
Seriously people, this article is simply an install and usage guide, without much of a comment on the timeline etc. Since most distros ship this stuff already (e.g. Debian), and have been for a while, it would seem to me that this code was written from scratch, unless MS was handing off code to Novell before the agreement.
So therefore we have not a copyright issue at all, but a software patent issue. Let the patent discussion begin!
Should be careful when you fling around names. Atheros do have a binary blob for their wireless chisp. But guess what, so does intel with their firmware. Atheros cards (supported by the madwifi driver) don't have firmware as such, most of it is done on the host PC. So they're pretty much equivalent.
Just keeping people informed.
Red lasers are the easiest to create of all. The issue is probably due more to the fact that red lasers don't have the same intensity for a similar powered blue laser and also focal for different wavelengths.
I wish I could describe it as well as done here http://monolith.sourceforge.net/, but what is the situation in terms of sending music encrypted, or as part of another file? For example, a part of a Britney Spears song might also be present in a Word doc, or the Britney Spears song, when in ASCII, might represent my password for my home computer. At what point is it illegal to actually transfer/upload/download these files? Is it only in the playing?
I know that's more than one question, but they're all related, and pretty critical when it comes to the concept of ownership/copyright in the digital space.
...need I say more?
I think that this is an opportunity for people to quickly get help for a specific problem, but it REALLY depends upon the quality of the people on the other end of the line. It seems to me like an attempt at replacing the multitude of IRC channels that are out there to support all the open source projects. Another factor is that none of the solutions will be archived, which means that a google won't turn up solutions, which is the first place almost everybody goes when looking for a solution.
I must say, I think Office vulnerabilities, especially in Powerpoint (the purveyor of all e-mail presentations), have the potential to be a lot more persistent. By that I mean, I know people who religiously update Windows, but don't give a second thought to updating Office. So it means that these vulnerabilities can hang around as unpatched for a lot longer.
will this be enough to run Vista?
The machine in question wasn't security.debian.org and it wasn't a distribution machine either. I'm pretty sure it was an old development machine, with no access to anything important, so the only real major concern is whether the same password was being used anywhere else (which could very much be possible).
You're probably better off using a VMWare offering on Linux with Win guests. Less reboots due to security updates of the host OS and no licensing costs.