It's actually a pretty good weight for measuring humans (14lb). Your weight in pounds varies from day to day but your weight in (half-)stones is much more stable.

https://www.scientificamerican.com/article/cats-are-perfect-...

Eventually the cause was narrowed down to that, randomly when the machine was stressed, the second half (actually, the final 2052 bytes) of some physical page in memory would get zeroed out. This wasn't great for the indexservers but they survived due to the defensive way that they accessed their data. But when we tried to use these new machines for Gmail, it was disastrous - random zeroing of general process code/data or even kernel data meant things were crashing hard.

We noticed from the kernel panic dumps (Google had a feature that sent kernel panics over the network to a central collector, which got a lot of use around this time) that a small number of pages were showing up in crash dump registers far more often than would statistically be expected. This suggested that the zeroing wasn't completely random. So we added a list of "bad pages" that would be forcefully removed from the kernel's allocator at boot time, so those pages would never be allocated for the kernel or any process. Any time we saw more than a few instances of some page address in a kernel panic dump, we added it to the list for the next kernel build. Like magic, this dropped the rate of crashes down into the noise level.

The root cause of the problem was never really determined (probably some kind of chipset bug) and those machines are long obsolete now. But it was somehow discovered that if you reset the machine via poking some register in the northbridge rather than via the normal reset mechanism, the problem went away entirely. So for years the Google bootup scripts included a check for this kind of CPU/chipset, followed by a check of how the last reset had been performed (via a marker file) and if it wasn't the special hard reset, adding the marker file and poking the northbridge to reset again. These machines took far far longer than any other machines in the fleet to reboot due to these extra checks and the double reboot, but it worked.

I coined the term "Xenoserver" back in 1999, for a paper in IEEE HotOS proposing an architecture for allowing systems in core networks to safely accept and execute code from untrusted users (for a fee, of course!): https://www.cl.cam.ac.uk/research/srg/netos/papers/1999-hoto...

I was inspired by the word "xenos" (meaning both stranger and guest, or in combination a stranger who you invited into your home) rather than the word "xenia" for the general concept of hospitality extended to such a stranger [EDIT: since I wasn't familiar with the word "xenia"].

The Xenoserver project at Cambridge University developed this idea, and eventually focused around the hypervisor, which took on the name Xen.

And even within Celiac disease there are a lot of variations. My mother has been diagnosed as Celiac for 50 years (back before most doctors had heard of it, and she almost died from malnutrition pre-diagnosis). She obviously avoids anything that has any mention of wheat, or has been cooked in the same oil as glutenous food; she generally avoids anything that mentions "possible cross-contamination" on the label but doesn't have to be a total stickler. I don't think she's had a serious attack in many years. A friend of mine was diagnosed as Celiac maybe 10 years ago, and is incredibly sensitive - despite his best efforts he seems to end up with horrible symptoms every couple of months or so just through tiny amounts of contamination.

The FDA limit for claiming something is "gluten-free" is 20 ppm; I believe that level exists partly because it's very hard to detect anything less than that anyway, but it also fits in well with what most Celiac sufferers can tolerate.