18:33:18 <richlowe> I tried to fix this, and it didn't seem like it was going to be possible
18:34:41 <sommerfeld> richlowe: I don't think it's impossible, but it would be a royal PITA to do it.
18:39:10 <sommerfeld> compat versions of the functions that touch "struct tm" get the old external names (to keep the ABI intact); new ones get revised external names for linkage, and never let the streams cross..
18:47:30 <danmcd> "struct tm" changing between old ABI and new ABI is your biggest PITA, but with that model I *think* it's doable.  See the large-files examples from times past, I think.
18:48:18 <sommerfeld> if there are other structs which have embedded "struct tm" it gets hairier.
18:48:47 <richlowe> my recollection is that largefile isn't a great example, because FILE is (just about) opaque, and off_t is integral
18:48:53 <richlowe> but it's been a while
18:49:24 <richlowe> making the basics work along sommerfeld's lines worked, but actual software -- especially if not all rebuilt together -- was hairy  
18:49:52 <richlowe> if you a 'foo' with a new tm, but a libfoo with an old-tm.
18:51:28 <rmustacc> Yes. The problem is passing a foo between things. Particularly an old one to a new thing.
19:00:24 <alanc> things like this are much easier to fix when you first establish a new ABI, like amd64 or aarch64
19:01:01 <alanc> like FILE becoming opaque in the Solaris 64-bit ABI to avoid the mistakes of the 32-bit ABI
19:09:52 <richlowe> alanc: believe me, I have thought about it, but then we have "it only works on aarch64"
20:09:42 <jclulow> Yeah I wouldn't want to make that sort of change just on one architecture
20:10:15 <jclulow> I think it would do more harm than good with downstream software
20:11:37 <jclulow> I _do_ think we could specifically address this in the manual page with example code though
20:11:52 <jclulow> like, "oh, you want tm_gmtoff, sorry, do this...'
20:12:30 <jclulow> I actually wonder if you could do something _utterly horrendous_ with a _macsro_
20:12:33 <jclulow> *macro
20:12:42 <jclulow> probably not, I guess
20:13:23 <richlowe> adding _apologia_ to our manual pages is a fine tradition, _apologies_ might be new though.
20:13:41 <jclulow> I think time.h(3HEAD) should also mention the things that are missing and redirect to how to get them
20:16:43 <gitomat> [illumos-gate] 17231 DMU: Fix lock leak on dbuf_hold() error -- Alexander Motin <mav⊙Fo>
20:19:31 <gitomat> [illumos-gate] 16796 loader: allow fs modules to use ioctl -- Toomas Soome <tsoome⊙mc>
20:21:53 <gitomat> [illumos-gate] 16797 loader: dosfs should be able to work with different sector sizes -- Toomas Soome <tsoome⊙mc>
20:27:21 <gitomat> [illumos-gate] 17280 Tidy up grpck references in the manual -- Peter Tribble <peter.tribble⊙gc>
20:30:16 <sjorge> danmcd I think it ws you that mentioned it on mastodon a while ago, did you get one of those PCIe Gen 4 x1 10Gbit ethernet adaptors?
20:30:26 <sjorge> If so, was that one that worked on illumos?
20:30:43 <gitomat> [illumos-gate] 17198 stream_runservice() eagerly helps us deadlock -- Andy Fiddaman <illumos⊙fn>
20:30:46 <sjorge> I only have 1x PCIe Gen 4 x1 left so can't fit my usual Intel X510 DA-1
20:30:57 <rmustacc> IIRC it's not supported and it's an AQC113 or similar.
20:38:56 <sjorge> Ah yes that model nummer seems vaguely familier
20:39:05 <sjorge> OK, no point in grabbing one if it's not supported.
20:46:51 <richlowe> unless you have the time to add support!
20:47:42 <sjorge> *sweats* I have 2 failed attempts of adding a CH320 serial support
20:47:51 <sjorge> I don't think a NIC will fair much better
20:54:28 <alanc> richlowe: I'm boring and stick notes like that under Usage instead of trying to teach people how to spell Apologia
20:55:26 <alanc> USAGE
20:55:27 <alanc>        This command is primarily used  by  the  Service  Management  Framework
20:55:27 <alanc>        (SMF).  For an equivalent to the killall command found on other systems
20:55:27 <alanc>        that allows specifying criteria to determine which processes to signal,
20:55:27 <alanc>        see pkill(1).
23:22:54 <richlowe> do any of you use pcitool much, and want to confirm what it means by "bank" in the usage?
23:23:56 <richlowe> or a general usage of `-n`
23:24:20 <richlowe> it doesn't help when a command tells me it already knows it might panic the system, when I'm trying to stop it panicking the system