I use a few of these in different place. It won't get you to the 10 watt range of the reflashed routers, but you save much time in wrestling fringe distributions in to working the way you want them to. (I have wrtsl54gs boxes running OpenWRT too, Atoms are more convenient.)

Do replace the motherboard fan if you get the intel motherboard. It will probably fail soon and cause your CPU to start thermal throttling. I just took it off and placed a full sized fan on the case vents over the motherboard blowing down. It runs cooler, quieter, and longer.

They have made a material which could if you designed a suitable chip and associated circuitry, and figured out how to manufacture it at large scale, would let you store a terabyte of data on a fingernail sized chip.

The whoever wrote the article title should be embarrassed, as should timothy for propagating it.

I should add, my copy of Illustrator for Mac is 5 years old and works like a champ. So, depending what you do with CS you may not even care.

No, but Adobe is. They have a long history of doing stupid things, then waiting until the actual consumer release to "discover" that their product has a problem and not fixing it until the next major release thereby preventing their users from upgrading OS.

In this case CS3 may actually work, they just aren't going to promise it so people will pay to upgrade and Adobe doesn't have to do any support on CS3.

They are asking about radio, not noodles.

The significance of SMM buried rootkits is that you can remove and shred the hard drive of your compromised machine, replace it with a new one, do a fresh install, and still be compromised.

The workaround (flushing everything to disk before the rename) is a disaster for laptops or anything else which might wish to spin down a disk drive.

The write-replace idiom is used when a program is updating a file and can tolerate the update being lost in a crash, but wants either the old or the new to be intact and uncorrupted. The proposed sync solution accomplishes this, but at the cost of spinning up the drive and writing the blocks at each write-replace. How often does your browser update a file while you surf? Every cache entry? Every history entry? What about your music player? Desktop manager? All of these will be spin up your disk drive.

Hiding behind POSIX is not the solution. There needs to be a solution that supports write-replace without spinning up the disk drive.

The ext4 people have kindly illuminated the problem. Now it is time to define a solution. Maybe it will be some sort of barrier logic, maybe a new kind of sync syscall. But it needs to be done.

Don't worry about your recommendation. All a large company will do is confirm that you were employed.

Your numbers are likely off by several orders of magnitude. 100W/m2 is 1/10th the energy density of direct sunlight. i.e. you can do ten times better than that with a flat mirror, no concentration.

Who says it has to a be a centimeter wavelength? How about the 95GHz pain beam? (I haven't checked to see what the atmosphere does at that wavelength, I would suspect clouds block it at the very least, but given that light is shorter wavelength and it penetrates well, I'm fairly certain there will be something between cm and nm that also works well.)

Of course in normal operation your 1000 units would beam to 1000 different reception sites at a safe level, it is only when you want to destroy someone that you divert them all to your enemy.

I can only use my nuclear power plants against my own people. The solar death ray can be targeted anywhere on the planet.

Whenever you read "spaced based solar power", just replace that with "municipal scale death ray". Now decide who should be in control of it.

Reading the article, this doesn't seem to be about real HTTP authentication passwords, but rather about the interaction of form autofilling and fields that an application might consider to be a password. (Like slashdot uses.)

Granted, somewhere the HTTP standards committee failed the community making ad hoc form based passwords more common than real authentication. I suspect the lack of a "logout" concept has a lot to do with that, though designers' desire to spread their "look and feel" over all elements also contributes.

If you use HTTP authentication this does not apply. If you use <input type=password ...> then, yeah, autofillers may autofill.

fail2ban will watch your log files and when it sees probing will firewall ban the offender. It has virtually eliminated probing attacks on my networks of machines. Sure, a distributed botnet can still probe you, but I haven't seen that happening.

Do be careful though...

• Have two different IPs you can come from. You will eventually ban yourself by being stupid. It took me a year, but I finally banned myself while working on some backup scripts.
• It is written in python and uses 3M of RAM plus maybe 20M more virtual memory. Sure, you high end gamers have 100 times that in your video card alone, but if you are running on a 64M VPS or a 32M router it is something to think about.
• You can have it watch much more than ssh if you wish.
• If you forward the syslogs of all your machines to your firewall and run fail2ban out there you can protect all of your machines at the first transgression and only have to manage one copy of fail2ban.
• If you are running virtual servers, consider running their syslogs out to the host box and running fail2ban there. Works well.
• There should be a memory efficient alternative, maybe I'll have to write that.