I have Shibby builds on an E3000 and an RT-AC66U. Great performance on both, although the AC throughput is a little erratic.
Yup. If tomato or dd-wrt had this as a simple on/off feature, I would happily share 1/4 of my bandwidth.
I've owned several e-readers, and I love them for what they are -- a book replacement. For me it's all about having a high contrast, readable screen with excellent battery life, and e-ink instead of any kind of light-emitting display. I've used one each of a Sony, Kindle, and Kobo.
In every case, I've loved the hardware, but the software drives me insane.
Mostly I want all my reader software to talk to Calibre (or some other central database) to sync the last page read, keep notes on which books I've read and when, and to record my star ratings. But it would be nice if the reader's "library" screen made good use of the screen to allow me to navigate through my books.
By the time you certified your system of a $5 CCD and a $30 LCD for aviation use, you'd have to sell it for $15,000 to make a profit. You can't install ANY equipment on a certificated aircraft that isn't certified.
The worst thing about the hiDPI support is that they clearly *thought* about multi-monitor mixed-DPI support, and then utterly failed in execution. The "let me choose different DPIs for different screens" is so horribly broken that I can't even tell how it's supposed to work.
Editor to the submission. Any available editor with a decent grasp of English vocabulary and grammar, please respond immediately.
Did you mean "exorbitant"?
That's the problem: they just bought most of the most popular platforms for those firmwares.
Do you have model numbers? I've never seen one.
I've had good success with 3 dissimilar monitors (small-wide-small) on Ubuntu 12.04 / fglrx. The irritations are pretty minor, and mostly involve the occasional dropdown dialog or maximize operation not going to the expected screen.
You neglect the fact that the manual was probably never rewritten in English. A machine-translation isn't necessarily comprehensible by even a technically literate English-speaker. EG, the installer's guide for my heat pump, which ambiguously instructs one to connect the 220V power lines to the 5VDC control input.
CFIT is nowhere near the leading cause of fatal accidents in general aviation.
It's pretty hard to find statistics for combined civil aviation, please post a link if you can find one.
I'll consider it fit as soon as I an drag an attachment to the desktop. It's been a bug for four years and counting now.
Oops. Meant to post under my userid:
Anyone here with recent experience trying to run "stereo" or other stereogrammetry software on linux? My last attempt petered out when I couldn't get a compile, but I'm still curious, in a casual sort of way.
A "minor" release (and don't state it like it's a fact just yet) from an earthquake more powerful than design criteria does not make me think "Nuclear Power is Safe" nor even "Nuclear Power is Unsafe." It makes me question the design assumptions. Never mind what was known at the time. With benefit of hindsight, the design assumptions were clearly wrong.
So. Given what we know now, is it a correct assumption to pay the extra required, such that at-risk plants be designed to tolerate common-cause failures devolving from a magnitude 9.0 quake and related tsunami? That's really one for risk analysis economists to decide, but the consequences of failure are so unbelievably expensive, that my knee-jerk assumption suggests that it is not. The big problem is that the consequences are so expensive that they cannot be other than mostly externalized.