01:50:31 <linext> does freebsd support usb ethernet adapters?
02:28:05 <RhodiumToad> yes
03:01:04 <mason> meena: There was an interesting article on AI models today on SlashDot: https://slashdot.org/story/23/06/13/2057209/researchers-warn-of-model-collapse-as-ai-trains-on-ai-generated-content
03:01:05 <VimDiesel> Title: Researchers Warn of 'Model Collapse' As AI Trains On AI-Generated Content - Slashdot
03:40:09 <last1> ai must be the most (incorrectly) abused of 2023
03:40:17 <last1> abused *word
03:40:28 <mason> acronym
03:40:30 <mason> but yeah
05:09:08 <whoami> hello - i'm trying to find some magic numbers. specifically, FIODGNAME on arm64 freebsd...
05:09:15 <whoami> i found these - https://github.com/pkg/taptun/blob/master/taptun_freebsd_386.go#LL8C2-L8C11 & https://github.com/pkg/taptun/blob/master/taptun_freebsd_amd64.go
05:09:16 <VimDiesel> Title: taptun/taptun_freebsd_386.go at master · pkg/taptun · GitHub
05:09:20 <whoami> but i'm not sure where they came from
05:09:41 <whoami> it's used for finding an interface name given its fd - https://github.com/pkg/taptun/blob/master/taptun_freebsd.go#L15-L23
05:09:42 <VimDiesel> Title: taptun/taptun_freebsd.go at master · pkg/taptun · GitHub
05:23:13 <RhodiumToad> it seems to be defined in /usr/include/sys/filio,h
05:23:50 <RhodiumToad>  /usr/include/sys/filio.h
05:28:13 <RhodiumToad> I'm not sure why that code isn't using fdevname(), but whatever
05:55:28 <grahamperrin> To anyone who subscribes to the freebsd-current list: did you receive my email with the following title?
05:55:29 <grahamperrin>  > Directory 1002/ missing from /var/run/user/
05:56:17 <angry_vincent> Yes.
05:58:13 <grahamperrin> Oops that was an old draft message, just resent …
05:58:55 <angry_vincent> i have  Directory 1002/ missing from /var/run/user/ without >
05:58:59 <angry_vincent> is this fine?
05:59:54 <grahamperrin> angry_vincent: did you receive (via the list) two emails with the same subject line? I can see replies to the second. The first one had a screenshot
06:01:16 <angry_vincent> i received only 1 email
06:01:42 <grahamperrin> Yeah the first one is missing from <https://lists.freebsd.org/archives/freebsd-current/2023-June/>.
06:01:43 <VimDiesel> Title: freebsd-current⊙Fo
06:02:09 <grahamperrin> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268719>
06:02:11 <VimDiesel> Title: 268719 – Inform the sender when an email to a FreeBSD list is rejected
06:09:06 <whoami> RhodiumToad: i don't think go has an fdevname in stdlib, so it'd probably require a bit of cgo?
06:10:13 <whoami> i'm unclear on how to interpret this - #define FIODGNAME_32    _IOC_NEWTYPE(FIODGNAME, struct fiodgname_arg32)
06:13:37 <whoami> hmm, looks to be the same on arm64 as amd64. i compiled a test program to print it out
06:16:17 <grahamperrin> meena0: do you mean, space strangeness with <https://gist.github.com/igalic/1fca3daeb7dc625b94d373a21ff51da5>?
06:16:18 <VimDiesel> Title: gist:1fca3daeb7dc625b94d373a21ff51da5 · GitHub
06:16:22 <RhodiumToad> see sys/ioccom.h for how the macros work
06:16:32 <RhodiumToad> whoami: ^^
06:23:19 <RhodiumToad> whoami: specifically, FIODGNAME is defined as _IOW('f', 120, struct fiodgname_arg) which means command 120 of group 'f', passing sizeof(struct fiodgname_arg) bytes into the kernel
09:09:09 <parv> Does anyone know if there is some Perl|Python module with a better access via C|C++ API than me executing "sysctl" to read|set various MIBs?
09:11:41 <meena> parv: https://github.com/gronke/py-freebsd_sysctl still don't bugs tho
09:11:42 <VimDiesel> Title: GitHub - gronke/py-freebsd_sysctl: Native FreeBSD Sysctl bindings for Python 3
09:14:13 <parv> meena, Thanks much. What do you mean by "still don't bugs tho"?
09:14:27 <meena> that's just for get, not set :(
09:14:49 <meena> https://github.com/gronke/py-freebsd_sysctl/issues
09:14:50 <VimDiesel> Title: Issues · gronke/py-freebsd_sysctl · GitHub
09:15:05 <parv> That is still improvement over what I had
09:15:33 * yuripv fails to parse "still don't bugs tho"
09:16:06 <meena> https://github.com/gronke/py-freebsd_sysctl/issues/20 actually, this is the only bug
09:16:08 <VimDiesel> Title: Sysctl.value is truncated for some structures · Issue #20 · gronke/py-freebsd_sysctl · GitHub
09:16:08 <VimDiesel> 20 – No rules for libtermlib https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=20
09:20:19 <meena> yuripv: but, if you add setting of values, I'll prod groenke to merge it
09:20:36 <meena> (we're in contact via signal)
09:22:54 <parv> No wonder I could not find "py-freebsd-sysctl" via "pkg search -x [-c] mib". Oh, look at that! "pkg search -x sysctl" brought also a Perl module too (p5-BSD-Sysctl)!
09:23:51 <parv> Sorry too many toos
09:33:07 <parv> meena, What is blocking work|progress on "set" functionality?
09:42:25 <parv> (mind I am curious; cannot develop that for lack of both knowledge, interest in non-Python side of Python)
09:49:10 <meena> parv: it wasn't needed so far, so nobody has implemented it
09:52:19 <parv> meena, Ah, ok. Thanks much
11:25:59 <danel1> Hey there :) OpenSSL 1.1.1 - which is the default for the latest RELENG-Releases - is soon going to be end of life. The RELENG-Releases are longer supported then OSSL 1.1.1. What are the plans for these releases and FreeBSD 13 in general? Will OSSL 3.0 get backported?
12:19:53 <debdrup> OpenSSL 3 almost certainly won't get backported, since it'd break POLA.
12:20:43 <debdrup> As for what'll become 14-STABLE, there's at least one mailing list thread on it, that should answer most of your questions.
12:21:13 <debdrup> Thread starts here: https://lists.freebsd.org/archives/freebsd-current/2023-January/003101.html
12:21:14 <VimDiesel> Title: Version of OpenSSL included in upcoming 14.0-RELEASE
12:23:06 <debdrup> Oh, sorry - it's these ones: https://lists.freebsd.org/archives/freebsd-arch/2023-May/000386.html abd https://lists.freebsd.org/archives/freebsd-current/2023-June/003823.html
12:23:07 <VimDiesel> Title: OpenSSL 3.0 for 14.0-RELEASE: issues with 1.x/3.x symbol clashing, ports linking against base OpenSSL, ports that don't compile/link against OpenSSL 3, etc
12:23:11 <debdrup> s/abd/and/
12:24:13 <debdrup> https://lists.freebsd.org/archives/freebsd-arch/2023-May/000384.html is also tangentially related
12:24:14 <VimDiesel> Title: Delay in 14.0-RELEASE cycle and blocking items
12:59:50 <danel1_> Thanks debdrup for the links. I'll take a look at them!
13:00:14 <debdrup> No worries.
13:02:51 <alian5687> hello all! Can I use the "discard" option in fstab for the root filesystem and the swap partition like I do on linux?  Thanks in advance!
13:03:24 <alian5687> I found nothing in fstab man page
13:03:26 <alian5687> ...
13:03:57 <CmdLnKid> then its not available
13:06:19 <alian5687> CmdLnKid: heck nothing in man mount either...
13:11:15 <CmdLnKid> thats an ext4 only option if i understand it correctly. not sure why you could think its neccesary here
13:16:22 <alian5687> CmdLnKid: nothing equivalent? does fsck_ffs -E / trim the partition when mounted, my tests haven't been conclusive so I can't really confirm...
13:18:39 <CmdLnKid> im'a ufs as root(/) zfs for every other writable area kinda guy with spinning disks for / and a variety of disks for everything else so i may not be best to answer that
13:26:23 <alian5687> CmdLnKid: spinning disks here too. One needs to trim virtual machines disks from the OS running in the vm in order to save space. FreeBSD running in a VM using ufs and backed by a zfs dataset used as raw disk on the proxmox host
13:27:09 <CmdLnKid> ah i see what your getting at there
13:31:14 <alian5687> CmdLnKid: well, writing zeros to free space would work too, at least if you have zfs compression on :)
13:32:07 <CmdLnKid> lol
17:38:32 <tmtt> Hi! I'm  my C library using bmake's bsd.lib.mk
17:38:34 <tmtt> oops
17:38:43 <tmtt> 2s
17:41:50 <tmtt> So, I'm making a C library and building it using bmake's <bsd.lib.mk> include and I noticed that - when using the install target - it copies all .a files to /usr/local/lib. Is there a way to install only the shared object (like `libtest.so.1.3') to /usr/local/lib, without installing the rest? Thanks a lot in advance :)
17:43:06 <tmtt> (I've read through the bsd.*.mk docs and tried to find something interesting in bsd.lib.mk particularly, with no luck)
18:19:04 <temp64> gm
18:19:50 <temp64> is there a way to speed up key repeat rate in the tty?
18:27:11 <Demosthenex> temp64: in x?
18:27:32 <yuripv> tmtt: try specifying SHLIB instead of LIB?
18:28:00 <temp64> Demosthenex, no, I mean the non-X terminal
18:28:34 <temp64> the one that meets me when I don't have any display managers running on boot :P
18:29:33 <Demosthenex> are you on a serial console?
18:31:35 <Demosthenex> temp64: kbdcontrol
18:32:43 <temp64> that's what I was looking for, thanks
19:25:38 <Demosthenex> so i need to check a running process, what's the alternative to linux's perf?
19:26:16 <RhodiumToad> check it for what?
19:26:26 <llua> what does perf do?
19:28:19 <cpet> vmstat
19:30:57 <cpet> Post in thread 'FreeBSD perf stat equivalent' https://forums.freebsd.org/threads/freebsd-perf-stat-equivalent.54328/post-306108
19:30:58 <VimDiesel> Title: FreeBSD perf stat equivalent | The FreeBSD Forums
19:31:08 <Demosthenex> cpet: yeah, that was a deadend
19:31:11 <Demosthenex> https://www.brendangregg.com/perf.html
19:31:12 <VimDiesel> Title: Linux perf Examples
19:31:34 <Demosthenex> trying to find what C functions a running process is spending time in
19:31:36 <Demosthenex> so runtime profiling
19:31:48 <cpet> Dtrace then
19:33:21 <Demosthenex> dtraceis show syscalls
19:33:59 <cpet> I'm sure you can Google something then
19:38:33 <Demosthenex> yeah, trying to get symbols from emacs.
19:38:58 <Demosthenex> so how can i tell a port not to strip debug data?
19:39:14 <cpet> Edit the makefile and rebuild
19:39:50 <CrtxReavr> Does our /bin/sh only supports a login config file, not an execution config file, akin to .bashrc, correct?
19:40:15 <cpet> You can exe shit in the config
19:41:04 <xtile> CrtxReavr: look for the mentions of the "ENV file" in the man page
19:41:10 <xtile> you can have something like .bashrc with any name you want
19:41:21 <xtile> the man page uses .shrc as an example, but it's just an example
19:45:03 <RhodiumToad> Demosthenex: there's a WITH_DEBUG flag in the framework (I think that's the right name)
19:46:48 <Demosthenex> RhodiumToad: nice
19:47:11 <RhodiumToad> Demosthenex: WITH_DEBUG=yes  will enable debug symbols for all ports, WITH_DEBUG_PORTS="foo/bar ..."  will enable it for specific ports
19:47:55 <RhodiumToad> of course this assumes that the port makefile is written according to project standards
19:48:28 <Demosthenex> well, its emacs ;]
19:54:17 <tmtt> yuripv: I'll try that
20:00:02 <cpet> Used to run erc in emacs that was fun
20:00:48 <foxiepaws> weechat.el was my favourite way to pretend to work back in the day >_>
20:59:22 <debdrup> Demosthenex: https://wiki.freebsd.org/DebuggingPorts
20:59:23 <VimDiesel> Title: DebuggingPorts - FreeBSD Wiki
21:03:30 <Demosthenex> debdrup: ty!
21:41:11 <tercaL> https://bsd.to -> SSL expired?
23:11:15 <markmcb> yep, i get a 526 error
23:33:34 <grahamperrin> It's been like it for a couple of weeks or so, I think
23:43:32 <markmcb> i'm on day ~25 of freebsd now. really liking it (headless server). is there any sort of user-contributed documentation aside from the forums? i feel like the excellent man pages and handbook would be complimented nicely with a few use case oriented docs. trivial example, i found sesutil quite by chance in a forum, but i could see that being a key callout for a "headless NAS" guide, which i imagine
23:43:34 <markmcb> might flow quite different than a "gnome laptop" guide (which would have no need to mention such a utility)
23:51:36 <meena> markmcb: there's a quite disorganised mess in the wiki, and then there's just plain old blogs
23:51:59 <meena> but, if there's anything we can do to make man pages better discoverable that would be great
23:52:16 <markmcb> yeah, the wiki seems like it doesn't know what it wants to be
23:52:55 <markmcb> exactly, i think a practical guide(s) that directly connects to man pages would be super useful
23:53:08 <markmcb> especially for someone new
23:54:36 <markmcb> i'd be up for hacking on docs like this, but doesn't seem like there's a home for it