00:22:59 <richlowe> typod 'embeded' as 'impeded', and I'm not even sure it was wrong.
00:23:34 <richlowe> jclulow, andyf: so yeah, my system, no seeds, no magic, with my bug fixed just starts importing manifests happy as anything.
00:23:56 <richlowe> not exactly pleasant, because time, so the seed is definitely good
00:24:29 <richlowe> I have suspicions I am just getting radically lucky, radically often.
00:24:44 <richlowe> which, you can imagine, was not at the top of my list of theories, for reasons.
08:47:25 <LXGHTNXNG> a
13:44:57 <gitomat> [illumos-gate] 15139 loader: avoid duplicate load for environment and console-font -- Toomas Soome <tsoome⊙mc>
13:59:17 <KungFuJesus> ugh, just got bit by this guy again: https://www.illumos.org/issues/15024
13:59:19 <fenix> → BUG 15024: NFS can exhaust pool threads getting RPCSEC_GSS credentials (In Progress) | https://code.illumos.org/c/illumos-gate/+/2402
13:59:32 <KungFuJesus> all it takes is one misadventure with one kerberized NFS session to deadlock the whole system
14:16:33 <jbk> oh there are other fun ways too :)
17:37:21 <gitomat> [illumos-gate] 15136 want unit test for bhyve dirty page tracking -- Patrick Mooney <pmooney⊙pc>
18:15:01 <gitomat> [illumos-gate] 15128 libnsl: variable is used uninitialized -- Toomas Soome <tsoome⊙mc>
20:37:56 <LXGHTNXNG> can we just evict NFS forever?
20:39:55 <jclulow> NFS is my favourite
20:40:46 <richlowe> hot pursuit was best
20:48:08 <jclulow> ha
21:25:12 <Smithx10> Underground
21:27:32 <Smithx10> All time favorite car was from Grant Turismo PS1 -  Mitsubishi GT3000 ... what a good time
21:40:12 <yuripv> weird, both gcc7 and gcc10 say "error: a label can only be part of a statement and a declaration is not a statement" about https://github.com/omniosorg/kayak/blob/ddb788dc0691d17e44e7e636eacbf0a3eb8a4f53/src/mount_media.c#L330 despite -std=gnu99 being specified
22:41:59 <richlowe> that's talking about labels, not variable declarations
22:42:10 <richlowe> I'd presume somehow you're conflicting with the name of one
22:43:39 <yuripv> declaring the variable above the label (at the start of the function) gets rid of the error, but i wonder what's wrong with my gccs as apparently it works when building omnios
22:43:40 <richlowe> labels as in the things you goto to
22:44:40 <richlowe> I don't know, that's weird.  I can see why it would seem odd to try to put a local on the stack in a label-dependent way, but it should get hoisted regardless
22:45:34 <richlowe> so I can see why the compiler would think that was odd, or possibly not ok, but I can't work out why it would choose to do so only for you
22:46:41 <richlowe> I'm looking at the code in 10.3 that does that, and I definitely can't see how it would depond on anything. 
22:46:47 <yuripv> actually tried with gcc on omnios and clang on freebsd, all of them are not happy
22:47:05 <yuripv> not sure how it builds while building kayak in omnios :)
22:47:10 <jclulow> I would definitely not expect that to work
22:47:35 <richlowe> I was assuming it worked as a GNU extension, or by chance, since as I said, the variable would get hoisted anyway.
22:47:56 <richlowe> but looking at the code, definitely not.
22:48:05 <jclulow> I think there's some question of when the initialisation occurs
22:48:10 <jclulow> and whether it occurs again
22:48:27 <richlowe> yuripv: were I you, I'd assume it doesn't work on omnios either, and fix it.
22:48:31 <jclulow> yeah
22:48:42 <richlowe> declare the variable at the top of the block, initialize it at the label or whatever
22:48:47 <jclulow> I feel like case labels also have this issue
22:49:05 <richlowe> case labels you traditionally just introduce a block
22:49:09 <richlowe> doing that for other labels looks horrible
22:49:49 <jclulow> case label blocks make me grumpy because there is no good thing to do for the last arm
22:50:32 <LXGHTNXNG> œ
22:50:33 <jclulow> Which I suppose is an artefact of our otherwise delightful choice to align the labels under the `switch`
22:50:52 <richlowe> C's block structure is kind of a convenient lie anyway
22:51:45 <jclulow> I think that's probably what we would put on C's tombstone
22:51:52 <jclulow> RIP C, a convenient lie
22:55:37 <LXGHTNXNG> sometimes I wonder what it would be like to write a compiler that understood the peculiar Plan 9 dialect of C, on Unix.
22:56:07 <LXGHTNXNG> anonymous members of structs. What?
22:56:41 <richlowe> I'm pretty sure GCC does
23:00:08 <LXGHTNXNG> hm
23:00:22 <LXGHTNXNG> Idk. Maybe I just have Plan 9 brain poison.
23:02:21 <yuripv> richlowe: yep, done, https://github.com/omniosorg/kayak/pull/236
23:10:46 <jclulow> LXGHTNXNG: I suspect the early Go source history probably has compilers like that?
23:11:03 <jclulow> Also presumably 9port etc
23:13:25 <richlowe> I'm pretty sure p9p just relies on gcc having the extensions
23:16:01 <LXGHTNXNG> richlowe: the Venti file server in 9port at least removes using Avl anonymously. Instead of that, though, it appears to rely on struct members being in the order specified (something the ?c compilers on Plan 9 do not guarantee)
23:16:39 <LXGHTNXNG> It also relies on the C compiler not adding padding to the beginnings of structs.
23:19:53 <jclulow> You keep calling it a "C compiler" haha
23:20:08 <jclulow> I feel like it compiles Something Else though
23:21:07 <jclulow> It must be hard to have any kind of ABI if the compiler can just reorder all your fields
23:21:13 <jclulow> I suppose Plan 9 didn't care about that
23:21:46 <richlowe> or read blocks off data from a device
23:22:25 <jclulow> perhaps they had a `#pragma less_esoteric`
23:22:38 <jclulow> for that
23:22:51 <richlowe> I could see them doing it to minimize padding, and exempting structures with no padding or bitfields or something 
23:23:02 <LXGHTNXNG> everything is statically linked. Also I think I lied about the reordering
23:24:24 <jclulow> even if things are statically linked, they had all this "I read structs from files everything is a file" stuff
23:24:44 <jclulow> You have to imagine that some of that was done with a read(2) into a struct
23:25:47 <gitomat> [illumos-gate] 14978 ZFS autoexpand property should work for root pools -- Joshua M. Clulow <josh⊙so>
23:40:57 <richlowe> jclulow: they're very big on everything being strings, too
23:41:13 <richlowe> process exit stuff, signals...
23:42:00 <jclulow> That's possible.  I vaguely remember looking at how some of the window drawing stuff worked and I had felt like there were some structs in there -- but perhaps I am misremembering