IN  WHICH Ross Rheingans-Yoo—a sometime economist, trader, artist, expat, poet, EA, and programmer—writes on things of int­erest.

# Reading Feed (last update: May 17)

A collection of things that I was glad I read. Views expressed by linked authors are chosen because I think they’re interesting, not because I think they’re correct, unless indicated otherwise.

### (16)

Blog: Marginal Revolution | Ask and they shall deliver — "Companies in the [EU] would be allowed to build wind and solar projects without the need for an environmental impact assessment, according to draft proposals obtained by the Financial Times that call for the fast-track permitting of renewable projects in designated “go-to” areas."

Comic: xkcd | Health Data

### (15)

Blog: Marginal Revolution | I favor bird consequentialism — Environmental conservation opposes radical climate

My Faults My Own (and other rossry.net and r-y.io subdomains) are now available over HTTPS, with certificates from Let's Encrypt. (cf. https://blog.rossry.net/https)

The setup took nontrivial effort, so I've narrated it here for my or your future reference. I don't think there's anything technically novel here, and there may even be an HTTPS-setup guide for 2019 somewhere else that dominates mine for usefulness, but there wasn't one easy-to-find enough that I found it, so here we are.

### (0)

First, the dramatis personae:

Let's Encrypt (hereafter "LE"), a project of the nonprofit Internet Security Research Group, issues free TLS (née SSL) certificates; they recommend that site administrators with shell access use the LE client Certbot, a project of the Electronic Frontier Foundation.

My Faults My Own, and other rossry.net and r-y.io subdomain services, are happily hosted by Digital Ocean (this turns out not to matter), running nginx on Ubuntu 14.04. (Certbot supports many other servers and OS setups as

# [Meta] My Faults My Own is now (happily) hosted by Digital Ocean

discount code: If you sign up for Digital Ocean with my referral link, you get $10 of credit and I get$25 of credit after you've spent your first \$25. This link should be good indefinitely, and I'm getting no compensation for this review.

Amongst all of the large transitions happening in my life about now, I found it necessary to move my blog server from "some borrowed machine on the Harvard network" to a real-adult location, like "the cloud". After asking a few friends for recommendations, I decided to rent server time from Digital Ocean, at least as a stopgap measure until the end of the summer, when I'd be able to pick out my own internet plan.

I'm glad to report that I couldn't be happier with DO's service. Spinning up a new virtual server and migrating Faults to it was probably the easiest piece of system administration that I've done. I gave them my credit card number, told them that I wanted

# [CS161] The Classic CV Error

This is a very technical post, largely for the benefit of the students of CS161: Operating Systems, for which I am a Teaching Fellow this semester. It may be useful to you if you're interested in operating systems for some reason, but if you're not in a CS mood today, maybe just move along.

From what I've seen as a TF for this course, it is very, very normal to write condition-variables code that looks like this:

struct cv {
struct semaphore *sem;
volatile int waiters;
}

void cv_wait(struct cv *cv, struct lock *lock) {
KASSERT(lk_do_i_hold(lock));

cv->waiters++;
lk_release(lock);
P(cv->sem);
lk_acquire(lock);
}

void cv_broadcast(struct cv *cy struct lock *lock) {
KASSERT(lk_do_i_hold(lock));

for (; cv->waiters > 0; cv->waiters--)
V(cv->sem);
}


This code is wrong (or, more specifically, badly synchronized). And it is such a common error that I'm choosing to dub it The Classic CV Error. It's subject to a race condition in e.g.

# [CS161] On Scheduling

This is a very technical post, largely for the benefit of the students of CS161: Operating Systems, for which I am a Teaching Fellow this semester. It may be useful to you if you're interested in operating systems for some reason, but if you're not in a CS mood today, maybe just move along.

# Why Do We Schedule, Master Bruce?

A scheduler, as you know, is responsible for determining which threads run, for how long, and in what order. As much as possible, it should give the shared illusion that each process is running constantly to completion, using the entire processor. To this end, there are three major desiderata: