I didn't like mine. The main reason was that with the DVD player, you typically want seperate "navigation" (up/down/left/right/enter) and "play" (play, pause, stop, rewind, ff, etc) buttons. With my SL-9000, I had to reprogram the number pad to do the navigation, which was a royal pain.
My new receiver (Denon) came with a very nice remote that is very similar to the SL-9000, but has a seperate navigation circle and play control keys. Highly programmable as well. So that's my current universal remove.
The NT Emacs FAQ has a number of simple solutions for generically swapping Ctrl/CapsLock under WinNT/2kXP, either permanently (no driver needed, just a registry hack) or per-user (needs a driver). Go here.
clearly points out that they provided *NOTHING* to the virus writer, and in fact the virus writer used another virus as a template. The criticism in this
case is quite unfounded.
Re:someone should make a code red three
on
Code Redux
·
· Score: 1
This is a really good question, I haven't even seen any discussion about it. Really, how hard would it be to write another virus/worm that acts like Code Red II, but instead of the exploits does something like:
a) shuts off IIS
b) downloads the patch and installs it
c) puts a big notice on the screen about what it just did
Seems appropriate to fight fire with fire, so to say.
Got one. It's awesome. Has 8 different device modes, and presets for just about everything. And anything it doesn't have presets for, it can learn from your old remote. Now, if I can only rember what buttons I program where...
You can try and think about it as just another optimization, but it won't work very well. Many programmers (especially younger ones) do a *very* poor job of writing code that can be easily adopted for parallel executions: loads of globals, poor structure, etc, etc, etc. When you try to automatically parallelize this, you end up with lots of locks all over the place, and performance, even in a distributed system, will certainly go down. Everything ends up serialized anyway, and now you have the communications and locking overhead on top of everything else.
Plain and simple fact is that parallel programming is not easy to get right even now (I *know* this, having spent *way* too much time debugging such things), and automating it is NOT going to help anyone. Garbage in, parallel garbage out. You *have* to think about parallel execution, from the beginning, if you want to have any chance at decent parallel performance, either explicitly or via some kind of automatic conversion. I know that optimizing compilers can do a lot of good, but no one has yet convinced me that they the can make up for poor, serialized, designs.
Slashdot Mirror
Really?
Really:
http://slashdot.org/submission/1222248/Microsoft-gets-its-FAT-Patent-back-in-Germany
I didn't like mine. The main reason was that with the DVD player, you typically want seperate "navigation" (up/down/left/right/enter) and "play" (play, pause, stop, rewind, ff, etc) buttons. With my SL-9000, I had to reprogram the number pad to do the navigation, which was a royal pain.
My new receiver (Denon) came with a very nice remote that is very similar to the SL-9000, but has a seperate navigation circle and play control keys. Highly programmable as well. So that's my current universal remove.
The NT Emacs FAQ has a number of simple solutions for generically swapping Ctrl/CapsLock under WinNT/2kXP, either permanently (no driver needed, just a registry hack) or per-user (needs a driver). Go here.
Nuke the space, cut and paste and there you go. Same article posted back in march.
Sigh... One more try, link here
Damn formatting... here's the URL: http://www.realworldtech.com/page.cfm?AID=RWT03100 2214227
This is the same article the same author wrote
1 00 2214227
back in March in Real World Tech:
http://www.realworldtech.com/page.cfm?AID=RWT03
Some nice pictures, but it looks the same.
eEye's response,
http://lwn.net/2001/0816/a/eeye.php3
clearly points out that they provided *NOTHING* to the virus writer, and in fact the virus writer used another virus as a template. The criticism in this
case is quite unfounded.
This is a really good question, I haven't even seen any discussion about it. Really, how hard would it be to write another virus/worm that acts like Code Red II, but instead of the exploits does something like:
a) shuts off IIS
b) downloads the patch and installs it
c) puts a big notice on the screen about what it just did
Seems appropriate to fight fire with fire, so to say.
It's all the arp requests from all the Code Red
probes for non-existant IP addresses.
tcpdump -i eth0 -n
(or whatever your external ethernet interface is).
I was seeing 2000/minute ARP requests on Monday,
don't know what it is now...
http://st2.yahoo.net/e-town/theatunrem.html
Got one. It's awesome. Has 8 different device
modes, and presets for just about everything.
And anything it doesn't have presets for, it
can learn from your old remote. Now, if I can
only rember what buttons I program where...
You can try and think about it as just another optimization, but it won't work very well. Many programmers (especially younger ones) do a *very* poor job of writing code that can be easily adopted for parallel executions: loads of globals, poor structure, etc, etc, etc. When you try to automatically parallelize this, you end up with lots of locks all over the place, and performance, even in a distributed system, will certainly go down. Everything ends up serialized anyway, and now you have the communications and locking overhead on top of everything else.
Plain and simple fact is that parallel programming is not easy to get right even now (I *know* this, having spent *way* too much time debugging such things), and automating it is NOT going to help anyone. Garbage in, parallel garbage out. You *have* to think about parallel execution, from the beginning, if you want to have any chance at decent parallel performance, either explicitly or via some kind of automatic conversion. I know that optimizing compilers can do a lot of good, but no one has yet convinced me that they the can make up for poor, serialized, designs.
Pete