The AC in a prius runs directly off of the HV DC batter pack. Go find a junked prius and loot the AC if you need some DC powered cooling.
No, the Prius air conditioner compressor is AC. The Prius inverter electronics converts the HVDC to the correct AC frequency to run the motor. So you'd need both the compressor and inverter assembly, which also includes the inverters for the motor-generators that move the car. And a 200V DC power supply. And all the right computers to get the inverter assembly to do something useful.
You'd wind up with a whole bunch of a Prius just to get a silly air conditioner.
The Prius also uses an electric air-conditioning compressor motor so that cabin cooling is maintained even when running in electric mode only. A second dc/ac inverter, with circuits located on a second ICU controller circuit board ringed with TO-packaged IGBTs, is deployed to power the electric A/C compressor from the HV battery pack. The A/C inverter IGBT packages are bolted to one face of the substantial heat-sinking enclosure of the ICU.
You must be joking. We would be in deep trouble if flash memory held its information for only about a year.
Nope, not joking. It also depends on the process size. Nice big (i.e. low capacity in a large die size) SLC flash cells hold data for quite a long time. The higher-density they get (and the less electrons per bit used to store data) the worse it gets.
So a lot of device firmwares and BIOSes, which generally use nice big chunky flash cells, will last 10-20 years. High-capacity flash storage, not so much.
That's just the way it is. Flash is currently the least worst solid state storage solution we have, but it still sucks.
(Note that if your device is powered on occasionally the flash can error-check and rewrite itself, which at least partially "resets" the time for data loss. This is only an issue for devices that are constantly powered off or devices that will not rewrite themselves as required.)
Wait, so now we aren't setting read/write status in fstab anymore?
How do you set filesystem read/write status for just the ntpdate process in fstab?
The bloody MUSB driver/OMAP hardware combination caused me to have to write this horrible thing:
local kmsg = io.open('/proc/kmsg', 'r')
for line in kmsg:lines() do
--elseif line:match('USB IS HORKED %- HELP PLEASE!') then
----local reset_usb =
...because some (rare) USB devices would occasionally cause the harware to basically completely lock up when plugged in. I could identify this and cry for help from within the driver, but the only way I found to successfully unkludge it was to completely remove and reinstall the kernel device, thereby completely reinitializing the device and driver.
Fortunately(?) it looks like this product is unlikely to actually ship...
Youtube uses EME for 1080p streams, no EME and you only get 720p or lower
Theo claims OpenBSD is unaffected. http://undeadly.org/cgi?action...
Theo claims OpenSSH is unaffected, because it isn't. OpenSSL, even on OpenBSD, is quite affected.
And Git's hashes are not for the sake of security. Linus made that abundantly clear when he refused to allow SHA-2 to be used, even after people were able to manufacture a Git collision using SHA-1.
Citation needed. I can't find a published example of any actual SHA-1 collision, much less one from a Git repo.
The MongoDB core is AGPL. Its drivers are all Apache license, as explained here, therefore not polluting your web application code and forcing it under the AGPL.
BerkeleyDB, on the other hand, is linked in directly, and would force anything using it to be under the AGPL.
Something like a config option - 'Enable OS installation for one boot cycle.'
If the purpose of secureboot were just to secure the boot process, that's all it'd take.
That limitation isn't possible, because the UEFI/BIOS is not a hypervisor. Once something else is running in ring 0 there is no way to prevent it from doing whatever it wants. Implementing those kind of hardware locks would entail a much more serious change to many parts of the PC architecture.
The whole system of key signing is a rather obvious attempt to squeeze all the little players out of the game so the big boys can seize more power and profits.
Despite the above, this statement is probably quite accurate, though. It's certainly a convenient side-effect.
Be careful when a loop exits to the same place from side and bottom.