03:57:11 <Molnija> eeeeee
12:01:53 <neirac> Smithx10 flock has no logo now, that was quick
12:10:18 <neuroserve> nice
13:33:32 <Smithx10> YES
13:33:38 <Smithx10> WE DEFENDED THE ILLUMOS GLORY!
13:41:41 <tsoome> So, it was borrowed afterall.
13:42:05 <andyf> https://github.com/flock-lab/flock/issues/470
13:42:40 <andyf> The site that's mentioned in there as the source is interesting. Not a lot of those images looks free
13:42:44 <andyf> *look
15:35:05 <sjorge> Heh and the old HL logo too :O
15:58:48 <Molnija> HL?
15:58:52 <Molnija> Half Life?
16:38:17 <paulf> spose so https://half-life.fandom.com/wiki/Lambda_logo
16:47:59 <gitomat> [illumos-gate] 14251 operationalize bhyve dirty page tracking -- Luqman Aden <luqman⊙oc>
16:59:05 <jclulow> neirac: They were very helpful and responded quickly when I mentioned it to them.
19:35:52 <jbk> if i link something w/ libumem because I want the interposed malloc()/free()/..., is adding an exception in exception_lists the only way to keep check_rtime happy, or is there another method that can be limited to just libumem?
19:36:37 <jbk> (it complains because the app itself -- something simple -- doesn't itself do any actual allocations, but (system) libraries it uses do
19:37:08 <jbk> which is why i'd like to keep it using umem so DEBUG builds can set UMEM_DEBUG and the like
19:37:08 <richlowe> exception lists, or call something yourself, yes.
19:38:14 <richlowe> it's possible check_rtime (or really ldd I believe) could grow wisdom about objects with the interpose flags set
19:38:24 <richlowe> so that explicit, intentional, early, interposes didn't get that
19:38:29 <richlowe> (libumem is such a thing)