The serial driver (more specifically, the PPP line discipline code) ia a bigger bottleneck than the IP code ever will be. There is plenty of work that can be done in this area. The biggest gain will be in flushing the completed frame as soon as it is available, rather than processing the entire TTY buffer, or even the entire UART buffer, for that matter.
However, you really don't want to have the PPP code in the serial interrupt handler, which is where it would have to live if one were watching each byte as it comes from the UART.
So, if it was shown in court that CSS does not stop bit-for-bit copying, and therefore does not stop content piracy, what was CSS designed for? It would seem that its only purpose is to control the fair use of the content. The only other plausible possibility is to control entry into the DVD player marketplace...
It seems that many of the posters here are relatively new to Linux. But, as someone who was in the market for a Unix-like OS in 1994, I can tell you that "the communities" were the most important factors in the decision of which OS to use. The Linux community was so utterly helpful that it was hard not to use it. A visit to #linux on EFNET would answer just about any question that anyone would have. And just watching the enthusiasm of the group was awe-inspiring.
On the other hand, the BSD users were the entrenched, holier-than-thou, get-outta-my-face-you-stinkin-newbie "gurus" who needed to deride the less knowledgeable in order to feel adequate. It was not a fun experience to be on the receiving end of the *BSD crowd in those days. The BSD crowd today is far different -- a really bright and helpful bunch. But the early days of the movement really hurt. It will haunt the BSD community for a long time to come.
The fact that Linux now has the largest market share and the strongest momentum is due to the outrageously helpful member of the community early on. This sense of community and willingness to help was inspired by the kernel developers themselves. Back when the daily volume on the linux-kernel list was under 30 messages a day (imagine!) it was quite common for the developers to very gently point the newbies in the right direction when they asked for help. ("This list is for kernel development... I'm sure if you ask on 'linux-foo' you're question will be answered.")
I just want to thank the Linux community for being such a helpful bunch. The early developers and users have inspired a large number of people (myself included) to continue the tradition of evangelizing the OS and helping the newbies get on their feet.
Always use the least appropriate language for the job at hand. Use C or C++ for parsing simple text files. Write huge applications in Perl. Use Bourne shell script to create a GUI framework. The opportunities for turning a small programming project into a lifelong commitment are endless here.
Another axiom to this rule is learn an obscure general purpose language and write everything in that. Your employers will have such a hard time finding experienced help, you should be able to demand a daily salary increase.
They own Avid, which makes SoftImage. They yanked all of their logos off of Avid's web site a while ago when they realized how badly it was hurting Avid's image. But they are still the second largest shareholder in Avid.
You miss a very distinct difference. "Us geeks" want to receive the information we request (singal). But we also must filter out information that we do not request (noise). Life is too short to live with low signal-to-noise ratio... a musician such as yourself should understand that concept.
Gee, sounds like you want...
on
GEEK Unions?
·
· Score: 2
Us SysAdmin types already have a trade organization in the form of SAGE, the System Administrators Guild, a part of USENIX. I think forming a SAGE lobbying group and/or PAC (political action commitee) would be one way to go. Of course we need a good portion of the SysAdmins out there to join and support us... It probably wouldn't hurt to have IEEE and ACM start PACs representing their members as well. I'm just surprised that all of these trade organizations were ignored by Katz *and* the Slashdot readership. I only saw one post mention the ACM! Wow.
That reasoning is flawed. You still have the same number of computer systems in place. The problem is that currently the most common OS is the least secure. Increase the mix and you can't help but to increase the security. That argument would hold only if all OSes had the same level of security.
...if one asks for and receives permission to create derived works from the copyright holder.
Quite a bit of the issues regarding fan generated derivative works can easily be resolved by just asking permission. This may be difficult to do if the original work is owned by a large faceless corporation. But individuals and small companies are often willing to grant permission to creators of derived works.
I recently used a copyrighted image in a logo I created for my web page. I assume it's enough of a derived work to constitute fair use, but I still asked for (and received) permission to use the image. The copyright owner was just happy to be asked!
Asking for permission is not that hard to do. And if more individuals did it, it would be much less of an issue.
Yeah, you'll probably have lots of trouble getting permissions to publishing fanfic based on the latest Star Wars movie (unless LucasFilms is a lot more cluefull than I give them credit for). I doubt George Lucas cares much about what Joe Random Geek has written based on his movie. But I am fairly sure that his lawyers care. Maybe that is a good reason to evaluate what one is a fan of...
Slashdot Mirror
The serial driver (more specifically, the PPP line discipline code) ia a bigger bottleneck than the IP code ever will be. There is plenty of work that can be done in this area. The biggest gain will be in flushing the completed frame as soon as it is available, rather than processing the entire TTY buffer, or even the entire UART buffer, for that matter.
However, you really don't want to have the PPP code in the serial interrupt handler, which is where it would have to live if one were watching each byte as it comes from the UART.
So, if it was shown in court that CSS does not stop bit-for-bit copying, and therefore does not stop content piracy, what was CSS designed for? It would seem that its only purpose is to control the fair use of the content. The only other plausible possibility is to control entry into the DVD player marketplace...
Or am I missing something here?
It seems that many of the posters here are relatively new to Linux. But, as someone who was in the market for a Unix-like OS in 1994, I can tell you that "the communities" were the most important factors in the decision of which OS to use. The Linux community was so utterly helpful that it was hard not to use it. A visit to #linux on EFNET would answer just about any question that anyone would have. And just watching the enthusiasm of the group was awe-inspiring.
On the other hand, the BSD users were the entrenched, holier-than-thou, get-outta-my-face-you-stinkin-newbie "gurus" who needed to deride the less knowledgeable in order to feel adequate. It was not a fun experience to be on the receiving end of the *BSD crowd in those days. The BSD crowd today is far different -- a really bright and helpful bunch. But the early days of the movement really hurt. It will haunt the BSD community for a long time to come.
The fact that Linux now has the largest market share and the strongest momentum is due to the outrageously helpful member of the community early on. This sense of community and willingness to help was inspired by the kernel developers themselves. Back when the daily volume on the linux-kernel list was under 30 messages a day (imagine!) it was quite common for the developers to very gently point the newbies in the right direction when they asked for help. ("This list is for kernel development... I'm sure if you ask on 'linux-foo' you're question will be answered.")
I just want to thank the Linux community for being such a helpful bunch. The early developers and users have inspired a large number of people (myself included) to continue the tradition of evangelizing the OS and helping the newbies get on their feet.
Always use the least appropriate language for the job at hand. Use C or C++ for parsing simple text files. Write huge applications in Perl. Use Bourne shell script to create a GUI framework. The opportunities for turning a small programming project into a lifelong commitment are endless here.
Another axiom to this rule is learn an obscure general purpose language and write everything in that. Your employers will have such a hard time finding experienced help, you should be able to demand a daily salary increase.
They own Avid, which makes SoftImage. They yanked all of their logos off of Avid's web site a while ago when they realized how badly it was hurting Avid's image. But they are still the second largest shareholder in Avid.
Microsoft *is* into 3D rendering.
You miss a very distinct difference. "Us geeks" want to receive the information we request (singal). But we also must filter out information that we do not request (noise). Life is too short to live with low signal-to-noise ratio... a musician such as yourself should understand that concept.
Us SysAdmin types already have a trade organization in the form of SAGE, the System Administrators Guild, a part of USENIX. I think forming a SAGE lobbying group and/or PAC (political action commitee) would be one way to go. Of course we need a good portion of the SysAdmins out there to join and support us... It probably wouldn't hurt to have IEEE and ACM start PACs representing their members as well. I'm just surprised that all of these trade organizations were ignored by Katz *and* the Slashdot readership. I only saw one post mention the ACM! Wow.
it will triple the chances of a smaller attack
That reasoning is flawed. You still have the same number of computer systems in place. The problem is that currently the most common OS is the least secure. Increase the mix and you can't help but to increase the security. That argument would hold only if all OSes had the same level of security.
...if one asks for and receives permission to create derived works from the copyright holder.
Quite a bit of the issues regarding fan generated derivative works can easily be resolved by just asking permission. This may be difficult to do if the original work is owned by a large faceless corporation. But individuals and small companies are often willing to grant permission to creators of derived works.
I recently used a copyrighted image in a logo I created for my web page. I assume it's enough of a derived work to constitute fair use, but I still asked for (and received) permission to use the image. The copyright owner was just happy to be asked!
Asking for permission is not that hard to do. And if more individuals did it, it would be much less of an issue.
Yeah, you'll probably have lots of trouble getting permissions to publishing fanfic based on the latest Star Wars movie (unless LucasFilms is a lot more cluefull than I give them credit for). I doubt George Lucas cares much about what Joe Random Geek has written based on his movie. But I am fairly sure that his lawyers care. Maybe that is a good reason to evaluate what one is a fan of...