1,122 karma · joined May 30, 2011
In case you're not sure what I'm talking about, read through the LuaJIT source code at some point. It's a thing of beauty - he's handcrafted assembly to make everything run as fast as possible, on all of x86, x64, PowerPC and now ARM.
General
- i386-softmmu is no longer named qemu but instead referred to as qemu-system-i386 for better consistency with other targets. A new tool is likely to be introduced that uses the qemu name so distributions are advised to not undo this change.
- QEMU now uses a separate thread for VCPU execution. This merges the biggest difference between the qemu-kvm tree and upstream QEMU.
- A new memory dispatch API has been added internally. A new monitor command "info mtree" can show the hierarchy of memory regions in the guest.
- QEMU now has a build dependency on glib and makes extensive use of glib.
- QEMU now can run on more hosts. Hosts without a native code generator can use the TCG interpreter (TCI). See Features/TCI for more information.
Block devices (disks)
- QEMU now supports I/O latency accounting in the monitor command "info blockstats".
- Errors are now tracked per device and are shown by the monitor command "info block".
- All image formats now support asynchronous operation. IDE and SCSI emulation will use this feature, while other devices (notably floppy and SD) will not.
IDE/ATAPI
- A large number of bugs were fixed regarding CD media change and tray locking.
SCSI
- Memory management errors could crash QEMU when scsi-disk encountered I/O errors. Many instances of this problem were fixed.
- The accuracy of error handling for SCSI emulation has been greatly improved.
- SCSI devices can now be addressed by channel, target (id) and LUN. Not all emulated HBAs will support this feature (in particular, the LSI controller will not).
- Block device pass through is now supported through a new scsi-block device. The scsi-block device works with block devices (like /dev/sda or /dev/sr0) rather than /dev/sgN devices, and is more efficient because it does not consume arbitrary amounts of memory when the guest does large data transfers.
- SCSI CD-ROMs now report media changed events.
- SCSI CD-ROMs now support DVD images.
- Bugfixes for IDE media change also apply to SCSI.
- SCSI devices now report a unit attention condition when the system is started or reset. This may cause problems with old firmware versions.
VDI
- Now supports discarded blocks in dynamically-sized images.
User-mode networking (SLIRP)
- SLIRP can process ARP replies and gratuitous ARP requests from the guest.
ARM
- QEMU now supports the new Cortex-A15 instructions in linux-user mode (via "-cpu any"): VFPv4 fused multiply-accumulate (VFMA, VFMS, VFNMA, VFNMS) and also integer division (UDIV, SDIV).
- The vexpress-a9, versatileab, versatilepb and realview-* boards now have audio support.
- QEMU is known not to work on ARM hosts in this release. (ARM target emulation is fine.)
pSeries
- sPAPR VIO devices can now be created with -device.
Xtensa
- QEMU now supports DC232b and FSF xtensa CPU cores.
- QEMU now supports sim (similar to Tensilica ISS) and LX60/LX110/LX200 machines.
Migration
- QEMU now supports live migration using image files like QCOW2 on shared storageWhen someone uses a mobile phone, they generally have the assumption that, unless they consent to it, third parties do not have access to their data (the government being a different story I won't go into). When I use GMail, I consent to Google reading my email via automated algorithms, and targeting ads at me through that. If I have anything important, I use email that I host myself or, if it's really top-secret, an anonymous throwaway account through Tor.
However, from what this video demonstrates, CarrierIQ is violating the basic principle of this by capturing and potentially logging your personal data without your knowledge or consent. Furthermore, it's violating the assumption that most people have that their passwords and such are not captured by applications other than the ones that they are entered into.
Now, we don't know for sure whether all this information is sent off to their servers and logged or not. However, in my personal opinion, the fact that this information is CAPTURED AT ALL is a serious problem, when combined with the fact that you are not informed of this!
However, an AV is pretty good at detecting stuff that you may get exposed to otherwise - exploits can pwn your Windows computer without you even knowing, and sometimes even run off legit ad networks. NoScript / AdBlock, running Google Chrome, and practicing safe browsing can help, but an AV is a good additional layer.
I guess my point is - an AV is NOT a panacea, but it should be used as an additional layer of defence.
I'm sure that Riak has bugs too - there are very few software products that DON'T (the provably-correct C compiler CompCert[1] being one that shouldn't). But it seemed to me that the post's author was simply trying to avoid getting sidetracked.
If you don't mind my asking, what's the license on this, if I'd like to use this in one of my projects?
Disclaimer aside, I think it'd be interesting to try - perhaps as an experiment, similar to the /classic you posted.
As for how to implement? Well, I'd imagine that the actual programming is relatively easy (disclaimer #2 - I'm no expert on Arc, so I could well be wrong), so I'm assuming you mean how to handle it. As I see it, you have two options. Firstly, submit link-bait and other detrimental submissions yourself, with a dummy account. Secondly would be to allow the admins/mods to actually mark something as detrimental, and retroactively modify each user that upvoted it.
Well, either that or the Windows error STATUS_OBJECT_NAME_NOT_FOUND.
1. Hash-based. This isn't as common nowadays, as there's a lot of malware that will generate a unique copy every hour or so.
2. Signature. This can be as simple as a byte sequence (i.e. anything with "C:\Badfile.exe" in it is a virus), to more complicated code using wildcards.
3. Heuristic. This can refer to anything from "files with an invalid digital signature are bad" to "files that have a high entropy and have no publisher are bad".
4. Emulation. The AV runs the file in a CPU emulator, tracks what it does, and attempts to determine if it's bad.
5. Behavioural. The AV lets the file run, tracks what it does, and then might stop it if it does enough "suspicious" actions.
So, in short, with all the various types of detection that modern antiviruses use, false-positives are almost inevitable. The teller is how fast the vendor reacts - and in this case, Microsoft seems to have reacted rather quickly.
The entire concept of MapReduce wouldn't exist without Google. And that's inspired a whole host of products. In the same vein, I don't find it unusual that they're NOT sharing the code for MapReduce et al., in that it's proprietary technology. I don't expect Amazon to share the source code behind AWS, and I don't expect Google to share the source code for MapReduce.