02:09:37 I'm still not good with disk management on FreeBSD 02:10:13 I install lsblk to try to cheat a bit 03:07:40 SponiX: gpart list might be useful - has uuids 04:17:43 Hahaha 04:17:50 die_you_gravy_sucking_pig_dog() in shutdown.c 04:28:01 Steve Martin fans are everywhere. 04:29:48 https://github.com/freebsd/freebsd-src/commit/39faed57b68ed9ce138617489f573d1ad48be6eb 04:33:10 heh, https://cgit.freebsd.org/src/commit/sbin/shutdown/shutdown.c?id=39faed57b68ed9ce138617489f573d1ad48be6eb sorry i pasted that github link, don't want to give github any more credence or legitimacy than it somehow amassed 04:49:16 I'll just note Jeff Atwood's commentary on it from 2004: https://blog.codinghorror.com/die-you-gravy-sucking-pig-dog/ 05:03:58 " painful, dangerous concepts of pointers and explicit memory allocation" already started off terrible 05:06:29 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. 05:08:23 Ha 05:09:09 The program knows how to best utilize the memory 05:09:16 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. 05:09:37 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 06:47:22 Gravy! Nice read! 22:47:49 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? 22:48:51 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? 22:49:36 I'm also logging on the default block rule, but that always gives reason=0 (match), which makes sense but isn't helpful.