As well as the IMA Appraisal feature that mjg59 mentioned, you can also integrity check your entire filesystem with verity[1]. Android uses it to make sure the system partition isn't tampered with.

[1] https://www.kernel.org/doc/Documentation/device-mapper/verit...

Because God forbid you tamper with the system partition.

The security features of android are the best argument for the stance Linus takes on these things.

The embedded version of CLFS (Cross-Compiled Linux From Scratch) covers building a musl + busybox system: http://clfs.org/view/clfs-embedded/x86/ But the more resources available on this kind of thing the better IMHO, there's not really a one size fits all :)

As somebody who uses numerous keyboard layouts on a daily basis, this is an interesting idea!

I wonder how hard it'd be to make a script where you specify which keyboard layouts you're likely to encounter and it finds the common symbols...

Of course, if you specify dvorak it'd wreck everything :)

> Also note the lead weights used here to make the product feel more substantial

Are these weights really made of Lead? Or is "lead weight" just an industry term for anything heavy? If they're actually Lead, how do toys like this conform to RoHS?

I'd be surprised if it was. Children's toys get tested for lead and just breathing it in is dangerous for kids.

Also, lead has a certain look and feel to it. When I open up toys and gadgets, the weight in there doesn't look like lead to me. No idea what it is, but I'd guess a zinc or iron alloy.

Google Apps has a few more knobs at least: https://support.google.com/a/answer/2368132?hl=en

I believe all NTSC equipment is required to support Black&White System M signals, which are exactly 60Hz[1]. It probably made their equipment much simpler to forget about colour encoding entirely. (And it made the 44,100Hz fit too)

[1] http://en.wikipedia.org/wiki/CCIR_System_M

Small correction: The MinnowBoard MAX only has 8MB of on-board flash, not 8GB. (It's an SPI chip to hold the firmware)

Whoops, you are right. Reading comprehension fail on my part.

While I agree that they likely store much less data than five zettabytes, your assumption that all their storage is on constantly spinning hard disks seems flawed.

(Tape libraries and various other offline/nearline storage solutions would be viable for most of their data)

Which other solutions do you suggest? Interestingly, tape libraries have also capacity limitations.

Indeed it's rare, but not unheard of. For example the "nocash" series of emulators has extensive debug support (breakpoints, memory viewers, disassemblers, hardware traps, etc)

http://nocash.emubase.de is the website if you want to check them out.