These caps are super anti-competive in areas where companies like Comcast have exclusive franchise agreements that prevent other companies from offering uncapped high speed cable based internet. Sounds like a good reason to quit bitching to the FCC and start complaining about the uncompetitive behavior to the cable franchise boards instead...
Really, the problem isn't so much the caps as we are letting the ISPs not count the traffic for the other services they offer as part of their cap.
Do you really think companies like comcast would be so gung ho to enforce caps if we made them count their traffic for the digital tv and phone services as part of the user's internet quota...
Sure they needed to enforce their copyright, but they didn't have to send their flying monkey lawyer minions after a high profile community developer.
They could have worked with the developer community on a workable compromise that wouldn't interfere with the mod-rom community but would allow users to use their existing licensed software.
The real issue is they didn't try to work with the community for a win-win solution instead they did the evil thing and went for a solution that benefits google to the detriment of their users and developers.
Bottom line most developers are going to care less about why google is sending lawyers after their community than the fact that they may have to deal with that crap if they develop for Android. Since there are groups producing similar mods to Windows Mobile firmwre, this Cease and Desist has the potential to make the open source mod community around android less vibrant than the community around the Microsoft's closed source OS. Which is a real shame.
If Google doesn't do some rapid damage control they're liable to find their development community moving over to other Open Source phone OSes that don't send lawyers after their development community.
I got to wonder if making an unauthorized copy is illegal than listening to the CD would be illegal since the CD player makes a copy of the music from the CD into an internal memory buffer.
Solaris zones are ok, but they are significantly less flexible than virtual machines.
One Solaris 10 machine can not run multiple versions of Solaris on the same machine like a true virtual machine can.
All the zones share the same kernel and in the case of lightweight zones they also share the same OS executables and libraries. This means, you can have an application that requires a kernel patch that will conflict with another application running in a different zone on the same machine. If this is the case, the only option under Solaris 10 is pick which application to move off.
Under User Mode Linux or VMWare this wouldn't be an issue, even if the different applications required totally different versions of the operating system.
Solaris 10 zones are certainly going to be useful but they are not anywhere as useful as having true virtual machines.
Most of those boards have CPUs with wimpy floating point units that can't handle mpeg encoding of video and suck up most of the processor just doing decoding.
I see lots of post that various stuff is better or good enough. I think that's missing the big picture. A truly secure system doesn't rely on only one security methodology.
I think VMs are a very useful and valuable for setting up secure servers. But like most other aspects of security they don't make a secure system on their own.
They provide another method of isolation of individual applications that potentially have buffer overflows. There's no reason for example a user mode linux install couldn't be built that has named built with stackguard running in a chroot session.
Hack detection is much harder to fool. I.E. have the main OS run tripwire against the VM. So the tripwire database isn't stored on the VM disk image...
Recovery from a hacked system is easier. It's just a matter of taking the backup copy of the original VM image, installing a patch to fix the exploit and putting the service back into operation. This is certainly much easier than rebuilding a server.
Using multiple VM sessions also means that installing patches, security or otherwise to one VMs services isn't going to screw up the other services. This is of course real handy for testing.
Slashdot Mirror
These caps are super anti-competive in areas where companies like Comcast have exclusive franchise agreements that prevent other companies from offering uncapped high speed cable based internet. Sounds like a good reason to quit bitching to the FCC and start complaining about the uncompetitive behavior to the cable franchise boards instead...
Really, the problem isn't so much the caps as we are letting the ISPs not count the traffic for the other services they offer as part of their cap.
Do you really think companies like comcast would be so gung ho to enforce caps if we made them count their traffic for the digital tv and phone services as part of the user's internet quota...
Sure they needed to enforce their copyright, but they didn't have to send their flying monkey lawyer minions after a high profile community developer.
They could have worked with the developer community on a workable compromise that wouldn't interfere with the mod-rom community but would allow users to use their existing licensed software.
The real issue is they didn't try to work with the community for a win-win solution instead they did the evil thing and went for a solution that benefits google to the detriment of their users and developers.
This begs the question, could a functional Maemo rom be made for the G1 as an alternative to Cyanogen??
Bottom line most developers are going to care less about why google is sending lawyers after their community than the fact that they may have to deal with that crap if they develop for Android. Since there are groups producing similar mods to Windows Mobile firmwre, this Cease and Desist has the potential to make the open source mod community around android less vibrant than the community around the Microsoft's closed source OS. Which is a real shame.
If Google doesn't do some rapid damage control they're liable to find their development community moving over to other Open Source phone OSes that don't send lawyers after their development community.
I got to wonder if making an unauthorized copy is illegal than listening to the CD would be illegal since the CD player makes a copy of the music from the CD into an internal memory buffer.
If being informed is such a big issue, see if you can vote by mail.
That way if there is anything on the ballot you don't understand you can go research the candidate or issue.
Solaris zones are ok, but they are significantly less flexible than virtual machines.
One Solaris 10 machine can not run multiple versions of Solaris on the same machine like a true virtual machine can.
All the zones share the same kernel and in the case of lightweight zones they also share the same OS executables and libraries. This means, you can have an application that requires a kernel patch that will conflict with another application running in a different zone on the same machine. If this is the case, the only option under Solaris 10 is pick which application to move off.
Under User Mode Linux or VMWare this wouldn't be an issue, even if the different applications required totally different versions of the operating system.
Solaris 10 zones are certainly going to be useful but they are not anywhere as useful as having true virtual machines.
The functionality to handle changing channels on a remote cable/sat box via an external channel changing script is already in mythtv and supported.
Most of those boards have CPUs with wimpy floating point units that can't handle mpeg encoding of video and suck up most of the processor just doing decoding.
I see lots of post that various stuff is better or good enough. I think that's missing the big picture. A truly secure system doesn't rely on only one security methodology.
I think VMs are a very useful and valuable for setting up secure servers. But like most other aspects of security they don't make a secure system on their own.
They provide another method of isolation of individual applications that potentially have buffer overflows. There's no reason for example a user mode linux install couldn't be built that has named built with stackguard running in a chroot session.
Hack detection is much harder to fool. I.E. have the main OS run tripwire against the VM. So the tripwire database isn't stored on the VM disk image...
Recovery from a hacked system is easier. It's just a matter of taking the backup copy of the original VM image, installing a patch to fix the exploit and putting the service back into operation. This is certainly much easier than rebuilding a server.
Using multiple VM sessions also means that installing patches, security or otherwise to one VMs services isn't going to screw up the other services. This is of course real handy for testing.
Heck, the Handyman segment of the Red Green show had this concept a good 3 years ago.