ceratopisan

I don't think I'll ever need to read one of these threads again, now.

I have the original Wolfenstein disk for the Apple ][, complete with typed label.

Out of curiosity, I did email people at id software asking about Castle Wolfenstein and what the copyright status was, in maybe... 1997?, and got a emailed shrug, effectively. Not the biggest issue on their radar at that point.

You are confusing principle with implementation. Reducing clock speed reduces power usage and you can compensate with more cores is indeed a truth. However, finding that option in consumer hardware has been relatively difficult. That is the surprise indicated.

Huge, multinational corporations with products in every house and business across the world also write a small minority of unpredictable, difficult-to-diagnose bugs. (Meltdown, Spectre, LazyFP, the next shoe that drops in a few days, for easy examples)

Pick whatever is more fun to use.

You are misinterpreting the sentence. Most people's exhaustive testing regimen is to try something a few times, shrug, and say "works for me". Not necessarily for file systems, but for a lot of software issues. When I wrote that sentence, I was entertained by the somewhat casual "retried this 500,000 times just to see" attitude.

For what it's worth: Sepherosa Ziehau spent some years serving out huge streams of video in a company similar to Netflix, in China. He used DragonFly. So, it may not have the same changes you are listing, but it may be closer than you think.

I generated them; what would you prefer, and why?

I know MD5 hash collisions are vaguely possible, but I would think they would be extremely unlikely here.

What Elhana said - mount_hammer2 isn't included in /usr/share/initrd so it's not copied into the image used there.

You can build a new initrd - cd into src/share/initrd/sbin, add it to the makefile, type 'wmake install' I think, and you may be good. I am guessing because I don't have an encrypted disk to test.

Otherwise, wait and there will be an updated 5.01 image soon, I'm sure - the recent KRACK vulnerability will prompt that, if nothing else.

It's not released; it's just tagged. Seriously, I haven't even finished building the release image yet.

This is a poor study. The "control" of NYC doesn't match Seattle in most every respect, and switching to Bellvue - well, you can read the paper where they say Bellvue followed the state minimums instead of the raises that Seattle implemented, and had the same increase in low-level health violations.

It's a poorly made case of correlation.

Refrigerating bread ruins it. Freezing does not. (Which the linked article does state.)

Outside of this not-really-helpful study, I can say that sourdoughs do tend to have a longer shelf life without preservatives; they resist staling and mold better than white bread, all things being equal. Commercial bread usually has preservatives added to balance this out, but it won't work out the same.

I've found sourdoughs, especially big miches, will actually taste better after 2 or 3 days. Commercial packaged breads are usually a straight downhill slope.

Source: direct experience, various baking books, historical info.

Really "gluten-free" means that someone with severe celiac disease could eat there, and the acceptable levels of flour/gluten/whatever have to be very, very low. So low that you will probably need two separate food prep and storage areas. That doubles the space and staff and work requirements.

That being said, gluten-free reheated frozen food out of a bag is just a more expensive version of ordinary reheated frozen food out of a bag, so I don't think it would help these places very much.

I hope - and I admit I am biased this way - that 'gluten-sensitive but not celiac disease' suddenly evaporates, sort of like MSG headaches turned out to be not a thing. Except I want it to happen faster.