00:59:06 [illumos-gate] 18332 add test for 18300 zfs should always allow relaxing quota -- Matthew Ahrens 11:35:35 [illumos-gate] Revert "18333 stmf_sbd: get/load PP data ioctls must validate buffer sizes" -- Gordon Ross 17:13:41 I have a really dumb question. 17:15:26 go on. 17:18:30 Was there a historical reason to have the strip(1) binary to be 32-bit? I vaguely recall building -gate would break under a 64-bit strip(1). 17:18:40 (sorry, forgot to finish and hit RETURN) 17:19:55 I cannot find anything immediately in my old notes or email archives about it, however. 17:26:36 No memory. I know that our strip breaks go binaries, but also don't remember why. 17:39:15 https://www.illumos.org/issues/15091 17:39:16 → BUG 15091: strip(1) rips go binaries apart (New) 17:39:59 Thanks. Seems we do have /usr/bin/amd64/strip so we could just run a build and wsdiff 19:35:07 strip is also mcs, but I don't recall anything special 21:17:07 illumos is far better than k8s openstack shit 21:17:15 yeees i gotta POWER 21:17:56 progressive engineering lives there 21:19:31 I think guys like Cantrill are demigod 21:20:53 they are maybe human beung for someon but for me they are definetelly GODS of engineering 21:22:11 * Ellenor sigh 21:27:14 @richlowe @andyf --> okay so the tool-that-must-be-32-bit memory I'm having is either mistaken about what tool, or the memory is SO OLD that it's no longer pertinent. 21:27:43 And yes `strip` is a hardlink to `mcs` but SmartOS mis-manifested it (and others), possibly to its detriment. 21:35:52 danmcd: a number of things re-exec themselves to match their target, and libelf cannot be 32bit+largefile 21:36:00 are the big things I'd think you might be thinking