I'm still not good with disk management on FreeBSD

I install lsblk to try to cheat a bit

SponiX: gpart list might be useful - has uuids

Hahaha

die_you_gravy_sucking_pig_dog() in shutdown.c

Steve Martin fans are everywhere.

heh, cgit.freebsd.org/src/commit/sbin/sh…d57b68ed9ce138617489f573d1ad48be6eb sorry i pasted that github link, don't want to give github any more credence or legitimacy than it somehow amassed

I'll just note Jeff Atwood's commentary on it from 2004: blog.codinghorror.com/die-you-gravy-sucking-pig-dog

" painful, dangerous concepts of pointers and explicit memory allocation" already started off terrible

The C programmer says that memory is too important to be left to the system. The Lisp programmer says that memory is too important to be left to the programmer.

Ha

The program knows how to best utilize the memory

sure, but also, look at the 2 code examples. for some reason one is magically better than the other because FUD said so even though they're the same. Oh no, I have to ask for `m` number of `double`s.

The lisp programmer actually isn't interested in creating a program, he is interested in creating an algorithm, and the "statefulness" part is just incidental

Gravy! Nice read!

When I have a pass rule in pf, with various limits and 'log (all)', should it not log also the packets it is blocking when the limits are exceeded?

Isn't that what the 'reason' described in e.g. pflogd(8) should tell me - that packets have been blocked due to e.g. bad-state or whatnot?

I'm also logging on the default block rule, but that always gives reason=0 (match), which makes sense but isn't helpful.