01:17:08 <jbk> pmooney: are you good with the sata fixes?
01:19:54 <Smithx10> How do I see what kernel params i booted with?
01:20:34 <Smithx10> in Linux I can see it via cat /proc/cmdline
01:27:39 <nomad> I thought it would be in dmesg but my hosts have all been up long enough that dmesg has lost the boot info so I can't check it.
01:31:43 <nomad> I see a bunch of interesting things in /var/log/kern.log and /var/adm/messages but nothing stands out as kernel params. You might find what you're looking for in /etc/system and /etc/system.d, though.
01:32:55 <Smithx10> just trying to see like  "BOOT_IMAGE=(hd3,gpt2)/vmlinuz-6.2.2-1.el8.elrepo.x86_64 root=UUID=3db685da-2072-45c5-b380-ed5e27f7b647 ro crashkernel=auto rhgb quiet console=tty0 console=ttyS1,115200n8" 
01:35:08 <jbk> there's bootargs
01:37:10 <pmooney> jbk: go ahead
01:39:11 <Smithx10> ahhh, its bootparams
16:05:56 <gitomat> [illumos-gate] 15070 dtrace could batch work during probe setup/teardown -- Bryan Cantrill <bryan⊙oc>
17:21:20 <gitomat> [illumos-gate] 15614 SMB server should use ksocket_sendmblk -- Gordon Ross <gordon.ross⊙tc>
18:58:00 <jbk> https://github.com/illumos/illumos-gate/blob/master/usr/src/uts/common/io/kbtrans/kbtrans_streams.c#L1473-L1474
18:58:03 <jbk> whoops :)
18:58:43 <andyf> It's been there for at least 18 years, must be fine!
18:59:13 <jbk> well it's not wrong, but i'm guessing it wasn't the intention to include the newline and leading space
19:12:13 <alanc> "cstyle says my line's too long?  fine, insert a \ and newline!"
19:13:56 <jbk> alanc could see how long that's actually been there :)
19:19:20 <alanc> looks like since 1998
19:27:12 <jbk> so it could rent a car :)
19:59:54 <sjorge> not sure i'd let code drive a car
20:58:57 <alanc> I wouldn't either, but plenty of others let code drive cars around here (SF Bay Area)
21:27:42 <Smithx10> awesome..... https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license
22:16:04 <sjorge> i wonder if we'll get a
22:16:10 <sjorge> fork like with elastic