You can probably multiply the time by taking an image once a second, or a short clip every 30 seconds. Also the display needs to be active only on positive match, but I suppose that consumes very little electricity.
Once the police learns that there are false positives, I'm sure they will learn to put the proper weight for computer recognition.
It's performing a checksum of your entire system. That's going to be a CPU hog. BTRFS will be no different in this regard.
Well, my btrfs scrubs 1.3 gigabytes per second and chances are it's IO-bound on the RAID10 SSDs, so if ZFS scrubbing performance is comparable, I would say it's not a CPU hog.
You can add a new disk to a pool. You can add a new mirror or Z vdev to a pool.
You make it sound such a petty limitation. But if you do have 5-device raidz and a pool, you are not going to add a single device to the system without risking data durability, you need to add at least two so you can mirror them, and then you're wasting space compared to parity-raids.
I bet they could've bought the announcers to say they are Surfaces for less money.
Meh, I was hoping some kind of dim OLED MIP display that would display always, like in N9 (though I did notice it was not mentioned in the specs) - it would have explained why most of the clock displays had dark background.
There are accelerometers that can queue many samples and then pass them to the CPU in one go (ie. 100 samples) and in addition they can have thresholds for interrupts. If your CPU is going to be woken once a second - assuming 100 Hz sampling rate, which is quite nice - then it doesn't really sound that bad, unless you have bad power saving functionality either in the CPU or in the operating system.
I suppose BLE doesn't need to take that much energy either if you grant a few seconds latency from notifications to actually displaying them.
There's always hoping they can improve the battery usage with firmware upgrades..
Everyone keeps saying how this doesn't have the latest most powersaving CPU but how much CPU does this device even need? Once a second to update the hand? Or could even be a few times a minute for a smooth minute hand.
I would be surprised if the overwhelming majority of the amperage doesn't go to the display and the BLE radio (in that order), the CPU coming last.
The addressing of LCDs is inherently cartesian, but I don't see why it means the display itself must be as well. The space not on the display is not wasted, there are not physical pixels being hidden here. Instead, the device provides the user with more free physical space compared to one with square screen, not to mention nicer look.
Though the AsRock board I bought is able to download the BIOS upgrade itself from within the BIOS, so that works regardless the OS. (Also it has a switch for choosing from two BIOS flash regions, so it should be pretty safe.)
While there have been some Linux bugs due to the compiler, I can't really recall hardware problems that have caused security problems â" unless you already have physical access, and then all bets are off.
The compiler issue could be addressed by using a certified compiler, such as this: http://compcert.inria.fr/ . Sadly CompCert is not FOSS.
Are you familiar with ROS, http://www.ros.org/ ? It's basically a set of libraries for various robotics tasks and sounds like what you're describing.
Well, v4 doesn't require remembering IPv4 addresses either, but still it comes handy in a pinch to remember the gateway, the dns server, the WLAN access point, etc addresses. For some reason people really like to point out the Google's DNS server's IP, not its name.
Though remembering local gw and dns mostly comes to remembering the network prefix whcih won't be that large, assuming one has not used dynamic allocation for services in a network.
Not sure if trolling.. but I looked it up, and on the paper it seems interesting, but for use today it has limitations: 2 TB maximum device size, 8 TB maximum volume size. So that's a non-contender. Seems quite advanced for its day, though (introduced 1998).
Maybe the malware was deeply employed in all the install images, and now it is guaranteed that all the systems have it, even after re-deploying
Actually Google already gave the Wave to the Apache foundation, so I guess they're set from that point of view.
That aside, I don't think a company should be forced to provide any level of support for a ten-year-old product. They could even be up-front about ("this product will not be supported for longer than five years") and people still wouldn't care. Well, until the day came.
I think it would be more effective to time the attacks when the sums involved are significant. Now they mostly server as a cautious example that new exchanges will learn from.
And it's probably better they learn their lessons now rather than later.