Isn't Nintendo's inability to keep it on the shelf a sign that the excitement is still there? If the excitement were gone, would stores still sell out within days of recieving a shipment?
Nobody goes there anymore; it's too crowded.
- Yogi Berra
I'm a bit confused about the orginal article. What I _think_ he is claiming is that if connects to a swarm that is downloading an illegal file, but doesn't actually downlaod or upload anything, he still gets a notice.
While I understand that he may have a technical argument to avoid conviction, I don't think this means you have much of a chance for getting caught if you share a legitimate file.
I'd say his analogy that it's akin to hanging out with drug dealers isn not apt. It's more like hanging around on street corners intentionally taking something that looks like money for something that looks like drugs and complaining that you got arrested.
There are a couple reasonas I can think of. First of all, most "failures" would include not meeting the specified rating, which wouldn't necessarily cause a noticible devices problem. Also, those numbers are probably for maximum load at maximum temp. If your caps are less than 100C, they'll last much longer.
Finally, the 3 year figure may be the amount of time you expect to see one failure out of a thousand (or some other arbitrary number).
Which brings us to an important point. Quoting specs without definitions can be very misleading, especially for failure ratings.
Hey mods, just because you don't agree doesn't make it flamebait.
Apple has shown some very litigious behavior for many years, I think it's a valid point if a bit overblown (and not really relevant if you RTFA, but heck this _is_ slashdot).
If you think it's not a valid point, why not refute it?
If it were possible to take short positions on these stocks, and people would chort rather than buy the stocks that are pumped, then the financial incentive for the pump and dumpers would go away, as would the spam.
It _might_ happen if the number of possible machine configuartions drops to say 100, or until all hardware manufacturers make a serious effort to insure that their hardware works with a number of distributions.
Neither situation will ever occur, so it will never happen.
The reality is that _Windows_ hardware rarely works out of the box, it's just been pre-installed and and tested most of the time. If you build your own machine you will end up spending a lot of time tracking down and playing with drivers.
I exclusively use Linux, and the hardware problem is a pain, but get used to it; it will never go away.
My EE thesis was written in latex. Having the style file to conform to their guidelines made things quite a bit easier.
On the other hand, by the end I was not so impressed with Latex's syntax. The way whitespace gets handled can be really frustrating.
e.g. given a macro \degree:
\degree foo and {\degree}foo
are different. I tore quite a bit of hair trying to accomplish the results of the latter. On the other hand I don't think I'd be too happy with an XML-like language.
I also recall mucking with Bibtek's title capitalization rules quite a bit to get what I wanted.
To get the make dependencies correct for images and such, I created my own build system, which ended up being unspeakably hairy. I wouldn't suggest going that route.
If the roles had been reversed Steve Jobs would have just been _so_ thankful that Creative "grown the market for.mp3 players." He'd be just _gushing_ about what a great bunch of guys they were.
He might even loan them his reality distortion field device.
The patent case may be without merit, but we certainly don't have to feel sorry for Apple, or even be particularly mad a Creative.
There are quite a few drivers out there to support weird hardware (like webcams and such) that are just not fully stable. It would be nice to be able to choose that a driver be run in kernel mode, at full speed, or in a sort of DMZ with reduced performance. This could also make it easier to reverse engineer non-GPL kernel drivers, as well facilitate driver development.
Let's put aside the possibity that the 60% figure is probably total hogwash, because that's not what you're arguing.
Rewriting over half the code of a project that you've spent years working on and are supposed to release in about a year is a desperate situation. It's not possible to acomplish. If they said they had to rewrite 10% of the code, I'd say they were in a bad situation, since that last 10% of the code often takes the most time.
I don't believe the 60% figure, because if it were true, the project leaders would be looking for new jobs already.
Keep your friends close, and your enemies closer.
--Sun-tzu
I think in this case Sony sees a threat from Microsoft, and wants to gang up as much as possible. For Sony, DRM and patents are largely orthogonal. DRM has to do with copyright and the enforcement mechanism is primarily the DMCA.
I think it's worth noting that if Sony had to choose between ditching DRM and protection from death by patent litigation, it would choose the former. Content, especially music, just isn't as big a business as consumer electronics.
Either way, you can still hate Sony if it suits you. It's a pretty big company, it's probably OK to like one division and hate the other.
The reason why this worm exist is due to the wide deployment of Windows Desktops with this specific vulnerability. There just aren't many Linux Desktops out there to bother with them.
Call me a heretic, but this is roughly correct, with some caveats.
OSS systems tend to have patches availible faster, so the bugs that lead to worms _can_ be fixed. It's just not realisitc to expect that they will be _always_ fixed (or even _often_ fixed). There's also really nothing you can do about the "I love you" strain of worms other than user education.
Perhaps the most interesting thing is that a Mac *could* be vulnerable to this attack. Yet 99.9% of the Macs out there aren't, because the system doesn't ship with the web server running by default. In other words, Linux is making Microsoft's mistakes all over again.:-(
As far as I can tell, a default Linux distro isn't vulnerable until you install a vulnerable php or cgi script. I don't think many Linux system ship in this configuration. The reason why this worm exist is due to the wide deployment of Linux http servers with this specific vulnerability. There just aren't many Mac OS X web servers out there to bother with them.
Slashdot Mirror
Isn't Nintendo's inability to keep it on the shelf a sign that the excitement is still there? If the excitement were gone, would stores still sell out within days of recieving a shipment?
Nobody goes there anymore; it's too crowded.
- Yogi Berra
I'm a bit confused about the orginal article.
What I _think_ he is claiming is that if connects to a swarm that is downloading an illegal file, but doesn't actually downlaod or upload anything, he still gets a notice.
While I understand that he may have a technical argument to avoid conviction, I don't think this means you have much of a chance for getting caught if you share a legitimate file.
I'd say his analogy that it's akin to hanging out with drug dealers isn not apt. It's more like hanging around on street corners intentionally taking something that looks like money for something that looks like drugs and complaining that you got arrested.
Again, I might be missing something.
I've wondered about this before...
Could something like this happen if your electrical outlet had hot and neutral reversed?
I'm fairly certain that the right type of transformer failure in a power supply brick can cause this too.
There are a couple reasonas I can think of.
First of all, most "failures" would include not meeting the specified rating, which wouldn't necessarily cause a noticible devices problem.
Also, those numbers are probably for maximum load at maximum temp. If your caps are less than 100C, they'll last much longer.
Finally, the 3 year figure may be the amount of time you expect to see one failure out of a thousand (or some other arbitrary number).
Which brings us to an important point. Quoting specs without definitions can be very misleading, especially for failure ratings.
will power this green light?
Hey mods, just because you don't agree doesn't make it flamebait.
Apple has shown some very litigious behavior for many years, I think it's a valid point if a bit overblown (and not really relevant if you RTFA, but heck this _is_ slashdot).
If you think it's not a valid point, why not refute it?
Accessiblity for one.
Try reading one of those cards when you've had your pupils dialated sometime.
No responsible physician sees 50 patients a day.
30 is the max and is pushing it.
If you are routinely seen for 5 minutes, get another doctor.
I've heard that Kaiser doctors have see patients in that amount of time, which is pretty irresponsible.
If it were possible to take short positions on these stocks, and people would chort rather than buy the stocks that are pumped, then the financial incentive for the pump and dumpers would go away, as would the spam.
That's probably about right.
My wife worked for a community health center that had about 15 providers and they payed something like $20,000 a year for their EMR.
They're a rather poor organization, so I suspect they got a serious discount.
And that didn't include any of the IT support or equipment, just the software.
Linux hardware will never work out of the box.
It _might_ happen if the number of possible machine configuartions drops to say 100, or until all hardware manufacturers make a serious effort to insure that their hardware works with a number of distributions.
Neither situation will ever occur, so it will never happen.
The reality is that _Windows_ hardware rarely works out of the box, it's just been pre-installed and and tested most of the time. If you build your own machine you will end up spending a lot of time tracking down and playing with drivers.
I exclusively use Linux, and the hardware problem is a pain, but get used to it; it will never go away.
My EE thesis was written in latex. Having the style file to conform to their guidelines made things quite a bit easier.
On the other hand, by the end I was not so impressed with Latex's syntax. The way whitespace gets handled can be really frustrating.
e.g. given a macro \degree:
\degree foo
and
{\degree}foo
are different. I tore quite a bit of hair trying to accomplish the results of the latter. On the other hand I don't think I'd be too happy with an XML-like language.
I also recall mucking with Bibtek's title capitalization rules quite a bit to get what I wanted.
To get the make dependencies correct for images and such, I created my own build system, which ended up being unspeakably hairy. I wouldn't suggest going that route.
Way too late:
m l
This is what I was referring to:
http://www.infoplease.com/ce6/history/A0812484.ht
There is nothing illegal about operating this way.
There certainly can be, if the company cutting prices is a monopoly, and they are lowering prices to drive competition out of business.
Wow you're right.
.mp3 players." He'd be just _gushing_ about what a great bunch of guys they were.
If the roles had been reversed Steve Jobs would have just been _so_ thankful that Creative "grown the market for
He might even loan them his reality distortion field device.
The patent case may be without merit, but we certainly don't have to feel sorry for Apple, or even be particularly mad a Creative.
What I'd like to see is a compromise.
There are quite a few drivers out there to support weird hardware (like webcams and such) that are just not fully stable. It would be nice to be able to choose that a driver be run in kernel mode, at full speed, or in a sort of DMZ with reduced performance. This could also make it easier to reverse engineer non-GPL kernel drivers, as well facilitate driver development.
You're right, I get 80 devices to get a 50/50 chance.
OTOH, since the addition rules are public, you can target your cracking to devices that have the types of keys you want.
I don't think they need to scramble.
Are you kidding?
Let's put aside the possibity that the 60% figure is probably total hogwash, because that's not what you're arguing.
Rewriting over half the code of a project that you've spent years working on and are supposed to release in about a year is a desperate situation. It's not possible to acomplish. If they said they had to rewrite 10% of the code, I'd say they were in a bad situation, since that last 10% of the code often takes the most time.
I don't believe the 60% figure, because if it were true, the project leaders would be looking for new jobs already.
Mu.
The memory usage problems have been related to the image cache. (I've heard that this is often caused by an old version of the adblock extension)
Using SQLite to store profile information will probably have little impact the memory usage problems people see.
Whenever a new technology is promised by a certain time, they're never right.
If history is any guide, it'll take at least _two_ weeks.
Isn't it racist to assume a Chinese person couldn't be a ninja?
ditching DRM and protection from death by patent litigation
Sorry, that should read:
ditching DRM and death by patent litigation
Or maybe even:
Sony is more intereseted in protection from patent lawsuits than DRM
Keep your friends close, and your enemies closer.
--Sun-tzu
I think in this case Sony sees a threat from Microsoft, and wants to gang up as much as possible. For Sony, DRM and patents are largely orthogonal. DRM has to do with copyright and the enforcement mechanism is primarily the DMCA.
I think it's worth noting that if Sony had to choose between ditching DRM and protection from death by patent litigation, it would choose the former. Content, especially music, just isn't as big a business as consumer electronics.
Either way, you can still hate Sony if it suits you. It's a pretty big company, it's probably OK to like one division and hate the other.
The hive mind has spoken.
The reason why this worm exist is due to the wide deployment of Windows Desktops with this specific vulnerability. There just aren't many Linux Desktops out there to bother with them.
Call me a heretic, but this is roughly correct, with some caveats.
OSS systems tend to have patches availible faster, so the bugs that lead to worms _can_ be fixed. It's just not realisitc to expect that they will be _always_ fixed (or even _often_ fixed). There's also really nothing you can do about the "I love you" strain of worms other than user education.
Perhaps the most interesting thing is that a Mac *could* be vulnerable to this attack. Yet 99.9% of the Macs out there aren't, because the system doesn't ship with the web server running by default. In other words, Linux is making Microsoft's mistakes all over again.
As far as I can tell, a default Linux distro isn't vulnerable until you install a vulnerable php or cgi script. I don't think many Linux system ship in this configuration. The reason why this worm exist is due to the wide deployment of Linux http servers with this specific vulnerability. There just aren't many Mac OS X web servers out there to bother with them.