Ah. Found it. Under the privacy tab, towards the top. The checkbox is "Acquire licenses automatically for protected content". Uncheck. I'm assuming that'll take care of this attack.
No, really. It's like peeing in your own pool. You need DRM in order to sell music to people and to "control the rights". But at the same time, they're using DRM to attack people who are outside the system. So it kind of makes you feel unsafe about using DRM in the first place. Life is better outside of the DRM system.
BTW, I remembered the option for something like "automatically download rights management software" when installating Windows Media Player, what, 10 is it now? I hesitantly clicked yes. Now that I've done so, I can't find an option inside of the program to say no. Odd.
The TI TMS 9900 had a strong beginning, but was packaged in a large (for the time) ceramic 64-pin package which pushed the cost out of range compared with the much cheaper 8-bit Intel 8080 and 8085. In March 1982, TI decided to start ramping down TMS 9900 production, and go into the DSP business instead. TI is still in the chip business today, and in 2004 it came out with a nifty TV tuner chip for cell phones.
Completely glosses over their involvement and production of SPARC chips for Sun. SPARC is relegated to a footnote of IBM's POWER architecture, and that now Sun is outsourcing SPARC to Fujitsu. Nevermind, of course, that Sun never produced SPARC chips in the first place.
Let's not just leave it to IBM to write the annals of microprocessor history, shall we?
I have been sysadmin'ing 'big iron' type UNIX configurations since 1997. Still do today. I think your question makes some assumptions that don't totally apply.
What sells big iron usually isn't the performance. Well, it is, but it isn't. Usually you go for big iron because you can only scale your application veritcally and not split it out horizontally. You're more forced into a big iron situation than it being a choice.
The number one issues with big iron seem to be more cost, system availability and reliability, redundancy, vendor support, ability to deal with troublesome situations (failing disks, CPU or RAM goes bad, applications going out of control, etc etc). I'm ignoring clustering as another layer on top of that, of course.
So, I guess I'm really going back to my earlier point in that performance specs don't mean as much to me as do all the less measurable items. Like, say, binary compatibility. But really it is more vendor comparison than an iron comparison.
One could do performance runs on large UNIX configurations, but then, you end up with something that is likely to be abstract and/or malleable. You might as well quote TPC specs.
My gameroom is filled with arcade games, and there is UV lighting from overhead. But I experimented with different designs and patterns to put on the walls (for what little wall-space remains visible).
The interesting combination I came across, which could apply to PC case mods as well, is by using regular paint, UV reactive paint, and glow-in-the-dark paint.
By using the three different types, you can create an image under normal everyday light. Then, when the lights go off and the UV light goes on, you can have a different image (caused by both the UV reactive paint and the photoluminescent paint).
Finally, once the UV light is off, you are left with the images created only by the photoluminescent paint colors.
So you can create some interesting changes in a picture based on the timing of regular and blacklight exposure.
Ben Brown was an early videoblogger
on
Videoblog Revolution
·
· Score: 2, Insightful
Anyone remember Ben Brown by chance? He was an early videoblogger with his Ben Brown show that went on for a number of episodes. (It seemed like a creative outlet for an unemployed techie.) It was pretty well known to the Metafilter/Fark crowd, at least.
He went away, but I have to say, that was a pretty good archetype for the video blogger. Just I think that video bloggers have even more of a problem in that they're not easily searchable, and one has to dedicate time to see the content more than pictures or text. It is far easier to turn people off than to turn them on because of the time a viewer needs to invest.
Its almost scary that someone has decided that my story was so outrageous that it was a troll! But things have gotten that insane.
Using MySQL? Shut down its TCP/IP ports and make it use SSH to communicate instead! Your Oracle backups? Why can't you dump those locally and then SFTP them to a central server?
They can't get anything done because they themselves are cluess (with a manager who doesn't understand security micromanaging security issues), and they're thugs who try to bully everyone into converting everything into SSH.
"You there! You're running SAP, aren't you? You have two weeks to convert this to SSH, or we're shutting you down!"
What's odd is that a whole house surge protector was listed as an impractical idea. I think they sell them at Home Depot. Somewhere around $100? Attaches to your incoming power line, protects the whole house, eliminates the need for in'duh'vidual surge protectors. There were a few other impractical ideas that caught my eye as being somewhat practical.
This is the section I liked best. The [a href="http://www.dilbert.com/comics/dilbert/duh/im practical_ideas.html"]impractical ideas[/a]. One that I really liked the idea of is the [a href="http://www.whispergen.com/"]whipsergen[/a] on the second page.
It would be interesting to see the cost of a natural gas powered electrical generator for the home. If not for everyday use, then at least as a whole or partial house generator to be switched over to during outages. It looks as small as a dishwasher. It looks like an indoor device though, and not something you'd put next to the outside AC unit.
I'm up to page 22. Page 22! I started to read this to find ways that I could save money on my energy (gas/electric) bills. Instead, I'd bombarded with page after page after page of introductory material.
Mind you, this is good background information that seems really thought out, but you really have to WANT to read this thing in order to get it done.
I'm just hoping the end of this is better than a standard energy saving pamphlet, or I'll feel like I was bait-and-switched to read some environmentalist's propaganda.
I think what most people are taking exception with is Microsoft's overall security model. I won't call this pro-Linux as much as I would call it anti-Microsoft. And there is nothing wrong with a healthy anti-Microsoft position if it is well founded.
I have to say, this has all of the elements for a funny story. You've got NASA, you've got a probe named Genesis [for your Star Trek Genesis Device reference], you've got sand [for your Star Wars reference -- sand people, probe looking like Luke's home from a distance, etc]. You've got space dust [for your Andromeda Strain reference]. You've got helicopters [for a military reference]. You've got an impled "mission accomplished!" presidental reference.
I think the people at fark.com have all the angles covered.
I see some of this as quite true. The onion metaphor was quite true. Issues of reproducing the problem was quite true. Making minimal changes to localize disruptions is true. Minimizing ability to hit is true. Minimizing impact of a hit is true.
The problem is that their debugging methodology is just plain bad. They don't have any leads to follow? You're NOT policeman. You can create more leads. You have an unlimited budget on a computer except for time.
While you're in the process of identifying the problem, you're not limited by minimal changes. Change the world! Put in debugging output all over the place. Directly set variables while the code is running. Break the rules. Run it against every OS tool in the book (examples on Solaris would be truss, pfiles, lsof).
I like truss because I can see the direct OS calls and their result codes as they are being made by the code. (Also you can get some visibility with BSM enabled.) Yes, I'm primarily a systems administrator. But I help my application team debug a live production system problem all of the time. And we've got an SLA that puts the pressure on to fix the problem quickly and perfectly.
Just by looking at things from the OS perspective, and having no visibility to the code, I can many times tell them what is going wrong with their binary. (Of course, this particular problem would have been so terribly easy to find in a Solaris environment.) I could have got it with truss, lsof, or pfiles.
I guess I'm just surprised that the debugging tools aren't that great. But I do understand, as they pointed out, that it didn't reproduce with the debugger quite the same way. And that'd have me asking what the debugger does different to the environment. (But again, that's why I like lsof. I run it against a live production bionary that was never set for debugging in the first place.)
People copy success. And if people can copy what Microsoft is doing, without going head-to-head with Microsoft, they're going to do it. And patents are a potential way to mimic Microsoft without going head-to-head. (Or, if you ARE already going head-to-head with Microsoft, having your own patent portfolio could offer some defense.)
The larger impact won't be Microsoft's patents, but their position as a trend setter in the industry. This sets the tone for a software world of greater patents.
"Because we all know that, without at least 20 years of protection, Apple would be sunk." Seriously, each time, they're patenting a fad. I think that's probably good for a five year period, but after that, its just overkill. It is like patenting parachute pants. And by the time the patent is granted, so is the interest in the fad that was patented.
Yes, their website says "Colossal Storage nanoTechnology will push the bandwidth limits beyond 1000 GB/sec". Of could, a transfer technology isn't good without hardware and a computer bus (of whatever type/configuration) that can push or translate that kind of data.
Of course, that doesn't say they're going to hook their new data transfer mechanism to their new storage medium, or that it'll even be able to read/write anywhere near 1000GB/second (1 terabyte/second).
If that were so, they could fill up their 10TB disk in 10 seconds. That's not what they're going to be able to deliver right now.
It looks like spinning media, so my guess is that it is going to approach something close to the best CDROM speeds in the real world. If they make a hard drive out of the same technology, I'd imagine it would approach your best hard drive transfer capabilities in the real world.
They're great. I've installed the Bugmenot plug-in for mozilla. I just right-click on a news page that requires a login, and I use one of the publicly shared usernames and passwords. Perfect!
I wonder how stable or redundant FTTP will actually be? For example, a month or two ago, we had a major storm blow through the city. Lots of power outages everywhere. Happily, the cable company has battery backups built into their signal distribution units way up on some of the poles in the field. Result? No instant Internet outage.
Then, sometime later, the batteries WERE exhausted. What did the cable company do? They got their trucks with generators and parked them by the distribution nodes and fed them power until the mains were restored. And that kept analog cable, digital cable, and Internet connectivity alive.
I'm no shill for the cable company, but I'm a lot less on their case after COX took over my local provider (who hated ever fiber of their customer base). COX runs a tight ship and I know that they've got the means to support this stuff, because it is everyday technology that they use.
I'm not so confident with FTTP from the local telco. A new offering isn't usually the most robust.
Slashdot Mirror
Ah. Found it. Under the privacy tab, towards the top. The checkbox is "Acquire licenses automatically for protected content". Uncheck. I'm assuming that'll take care of this attack.
No, really. It's like peeing in your own pool. You need DRM in order to sell music to people and to "control the rights". But at the same time, they're using DRM to attack people who are outside the system. So it kind of makes you feel unsafe about using DRM in the first place. Life is better outside of the DRM system.
BTW, I remembered the option for something like "automatically download rights management software" when installating Windows Media Player, what, 10 is it now? I hesitantly clicked yes. Now that I've done so, I can't find an option inside of the program to say no. Odd.
The part about TI is interesting...
The TI TMS 9900 had a strong beginning, but was packaged in a large (for the time) ceramic 64-pin package which pushed the cost out of range compared with the much cheaper 8-bit Intel 8080 and 8085. In March 1982, TI decided to start ramping down TMS 9900 production, and go into the DSP business instead. TI is still in the chip business today, and in 2004 it came out with a nifty TV tuner chip for cell phones.
Completely glosses over their involvement and production of SPARC chips for Sun. SPARC is relegated to a footnote of IBM's POWER architecture, and that now Sun is outsourcing SPARC to Fujitsu. Nevermind, of course, that Sun never produced SPARC chips in the first place.
Let's not just leave it to IBM to write the annals of microprocessor history, shall we?
I have been sysadmin'ing 'big iron' type UNIX configurations since 1997. Still do today. I think your question makes some assumptions that don't totally apply.
What sells big iron usually isn't the performance. Well, it is, but it isn't. Usually you go for big iron because you can only scale your application veritcally and not split it out horizontally. You're more forced into a big iron situation than it being a choice.
The number one issues with big iron seem to be more cost, system availability and reliability, redundancy, vendor support, ability to deal with troublesome situations (failing disks, CPU or RAM goes bad, applications going out of control, etc etc). I'm ignoring clustering as another layer on top of that, of course.
So, I guess I'm really going back to my earlier point in that performance specs don't mean as much to me as do all the less measurable items. Like, say, binary compatibility. But really it is more vendor comparison than an iron comparison.
One could do performance runs on large UNIX configurations, but then, you end up with something that is likely to be abstract and/or malleable. You might as well quote TPC specs.
Too bad you're AC'd. I would have posted the same comment myself. The NSF/NFS switch is an easy one to make. Nice joke, too!
PS: I wonder if they're a hard mount, or a soft mount?
If they discovered that a subversive person was actually aware of the similar URL, and _intentionally_ provided it for publication.
My gameroom is filled with arcade games, and there is UV lighting from overhead. But I experimented with different designs and patterns to put on the walls (for what little wall-space remains visible).
The interesting combination I came across, which could apply to PC case mods as well, is by using regular paint, UV reactive paint, and glow-in-the-dark paint.
By using the three different types, you can create an image under normal everyday light. Then, when the lights go off and the UV light goes on, you can have a different image (caused by both the UV reactive paint and the photoluminescent paint).
Finally, once the UV light is off, you are left with the images created only by the photoluminescent paint colors.
So you can create some interesting changes in a picture based on the timing of regular and blacklight exposure.
Anyone remember Ben Brown by chance? He was an early videoblogger with his Ben Brown show that went on for a number of episodes. (It seemed like a creative outlet for an unemployed techie.) It was pretty well known to the Metafilter/Fark crowd, at least.
He went away, but I have to say, that was a pretty good archetype for the video blogger. Just I think that video bloggers have even more of a problem in that they're not easily searchable, and one has to dedicate time to see the content more than pictures or text. It is far easier to turn people off than to turn them on because of the time a viewer needs to invest.
Its almost scary that someone has decided that my story was so outrageous that it was a troll! But things have gotten that insane.
Using MySQL? Shut down its TCP/IP ports and make it use SSH to communicate instead! Your Oracle backups? Why can't you dump those locally and then SFTP them to a central server?
You get the idea.
They can't get anything done because they themselves are cluess (with a manager who doesn't understand security micromanaging security issues), and they're thugs who try to bully everyone into converting everything into SSH.
"You there! You're running SAP, aren't you? You have two weeks to convert this to SSH, or we're shutting you down!"
What's odd is that a whole house surge protector was listed as an impractical idea. I think they sell them at Home Depot. Somewhere around $100? Attaches to your incoming power line, protects the whole house, eliminates the need for in'duh'vidual surge protectors. There were a few other impractical ideas that caught my eye as being somewhat practical.
This is the section I liked best. The [a href="http://www.dilbert.com/comics/dilbert/duh/im practical_ideas.html"]impractical ideas[/a]. One that I really liked the idea of is the [a href="http://www.whispergen.com/"]whipsergen[/a] on the second page.
It would be interesting to see the cost of a natural gas powered electrical generator for the home. If not for everyday use, then at least as a whole or partial house generator to be switched over to during outages. It looks as small as a dishwasher. It looks like an indoor device though, and not something you'd put next to the outside AC unit.
No.. no... the whole presidential erections thing had to do with the LAST president.
I'm up to page 22. Page 22! I started to read this to find ways that I could save money on my energy (gas/electric) bills. Instead, I'd bombarded with page after page after page of introductory material.
Mind you, this is good background information that seems really thought out, but you really have to WANT to read this thing in order to get it done.
I'm just hoping the end of this is better than a standard energy saving pamphlet, or I'll feel like I was bait-and-switched to read some environmentalist's propaganda.
I think what most people are taking exception with is Microsoft's overall security model. I won't call this pro-Linux as much as I would call it anti-Microsoft. And there is nothing wrong with a healthy anti-Microsoft position if it is well founded.
Now... if only I could figure out _how_ to get my users classified as a storage device...
And the post-crash thread, too.
Did I forget the Peter Gabriel, Genesis reference?
I have to say, this has all of the elements for a funny story. You've got NASA, you've got a probe named Genesis [for your Star Trek Genesis Device reference], you've got sand [for your Star Wars reference -- sand people, probe looking like Luke's home from a distance, etc]. You've got space dust [for your Andromeda Strain reference]. You've got helicopters [for a military reference]. You've got an impled "mission accomplished!" presidental reference.
I think the people at fark.com have all the angles covered.
I see some of this as quite true. The onion metaphor was quite true. Issues of reproducing the problem was quite true. Making minimal changes to localize disruptions is true. Minimizing ability to hit is true. Minimizing impact of a hit is true.
The problem is that their debugging methodology is just plain bad. They don't have any leads to follow? You're NOT policeman. You can create more leads. You have an unlimited budget on a computer except for time.
While you're in the process of identifying the problem, you're not limited by minimal changes. Change the world! Put in debugging output all over the place. Directly set variables while the code is running. Break the rules. Run it against every OS tool in the book (examples on Solaris would be truss, pfiles, lsof).
I like truss because I can see the direct OS calls and their result codes as they are being made by the code. (Also you can get some visibility with BSM enabled.) Yes, I'm primarily a systems administrator. But I help my application team debug a live production system problem all of the time. And we've got an SLA that puts the pressure on to fix the problem quickly and perfectly.
Just by looking at things from the OS perspective, and having no visibility to the code, I can many times tell them what is going wrong with their binary. (Of course, this particular problem would have been so terribly easy to find in a Solaris environment.) I could have got it with truss, lsof, or pfiles.
I guess I'm just surprised that the debugging tools aren't that great. But I do understand, as they pointed out, that it didn't reproduce with the debugger quite the same way. And that'd have me asking what the debugger does different to the environment. (But again, that's why I like lsof. I run it against a live production bionary that was never set for debugging in the first place.)
People copy success. And if people can copy what Microsoft is doing, without going head-to-head with Microsoft, they're going to do it. And patents are a potential way to mimic Microsoft without going head-to-head. (Or, if you ARE already going head-to-head with Microsoft, having your own patent portfolio could offer some defense.)
The larger impact won't be Microsoft's patents, but their position as a trend setter in the industry. This sets the tone for a software world of greater patents.
"Because we all know that, without at least 20 years of protection, Apple would be sunk." Seriously, each time, they're patenting a fad. I think that's probably good for a five year period, but after that, its just overkill. It is like patenting parachute pants. And by the time the patent is granted, so is the interest in the fad that was patented.
Yes, their website says "Colossal Storage nanoTechnology will push the bandwidth limits beyond 1000 GB/sec". Of could, a transfer technology isn't good without hardware and a computer bus (of whatever type/configuration) that can push or translate that kind of data.
Of course, that doesn't say they're going to hook their new data transfer mechanism to their new storage medium, or that it'll even be able to read/write anywhere near 1000GB/second (1 terabyte/second).
If that were so, they could fill up their 10TB disk in 10 seconds. That's not what they're going to be able to deliver right now.
It looks like spinning media, so my guess is that it is going to approach something close to the best CDROM speeds in the real world. If they make a hard drive out of the same technology, I'd imagine it would approach your best hard drive transfer capabilities in the real world.
If it doesn't have Kirk _AND_ Spock, it doesn't have me! ;)
They're great. I've installed the Bugmenot plug-in for mozilla. I just right-click on a news page that requires a login, and I use one of the publicly shared usernames and passwords. Perfect!
I wonder how stable or redundant FTTP will actually be? For example, a month or two ago, we had a major storm blow through the city. Lots of power outages everywhere. Happily, the cable company has battery backups built into their signal distribution units way up on some of the poles in the field. Result? No instant Internet outage.
Then, sometime later, the batteries WERE exhausted. What did the cable company do? They got their trucks with generators and parked them by the distribution nodes and fed them power until the mains were restored. And that kept analog cable, digital cable, and Internet connectivity alive.
I'm no shill for the cable company, but I'm a lot less on their case after COX took over my local provider (who hated ever fiber of their customer base). COX runs a tight ship and I know that they've got the means to support this stuff, because it is everyday technology that they use.
I'm not so confident with FTTP from the local telco. A new offering isn't usually the most robust.