00:26:46 lw: I think that's the main goal of some WIP by markj: https://github.com/markjdb/bricoler 00:26:47 Title: GitHub - markjdb/bricoler 09:46:23 hello, I'm using unbound as a local resolver here with some static zone. Is there a way when I'm creating a jail to automatically register it's DNS name without having to modify the unbound file? 10:01:05 mage unfortunately not that i know of 10:01:28 the hostname is had by dhcp and with ipv6 you don't really want dhcp 10:02:18 the good news is that since your working with jails you can create a custom script to extract the internal ip of each jail and update your zone file 10:02:37 if you do this let me know, i'd like a copy of the script too 10:35:46 why is that necessary? 10:59:58 mage: yes, you can do that with dynamic DNS updates - except i'm not sure if that works with unbound, since it's not intended to be an authoritative server; bind or knot might work better 11:06:12 although it would probably be easier to just do this once rather than configure ddns, unless you're creating a lot of new jails 12:30:53 compiling freebsd over ssh, yay or nay 12:31:06 actually is there a way to speed this up, we'll be doing this a lot... 12:36:48 presumably meta mode should help 12:47:24 Soni: over ssh or sshfs 12:48:44 dstolfa: over ssh, we're not *that* masochistic 12:49:07 Soni: why would that not work? people ssh into build machines for freebsd all the time 12:49:16 you just ssh in, fire up something like tmux and kick off a build 12:49:21 just run the build in tmux in case your ssh connection dies. and yes, use meta mode 12:49:25 because we're not using tmux 12:49:43 well, if your connection is stable it doesn't matter 12:49:52 tho, to be fair, mosh -> ssh -> vm is probably fine 12:50:12 alternatively you can probably hack something up with nohup 12:50:30 is "running on the same machine" stable enough? 12:50:52 unless you plan on killing the connectivity from the vm to the host or vice-versa, probably :P 12:51:41 alright, btw, when rebuilding libc... 12:52:18 is there a way to avoid rebuilding everything? 12:52:27 -DNO_CLEAN, WITH_META_MODE, ccache for the most part 12:52:37 beware of edge cases and all that 12:52:59 (did we pick the worst project) 12:53:50 i recommend not using NO_CLEAN if you're using meta mode, it's not really necessary and it does break things sometimes 12:55:08 (basically the point of meta mode was to make NO_CLEAN unnecessary) 12:55:18 all 3 of those break in some edge cases, so just generally beware 12:56:53 also check the various WITHOUT_* options in src.conf (if you're not using pkgbase) as not building things you don't need can improve build time a bit 12:57:34 best build time improvement: Not building LLVM, but that might building things more difficult. 12:57:50 meena: how do you do that 12:58:06 lw: i'm not sure it's possible lol 12:58:10 i'm annoyed at having to build 20 identical copies of llvm for every src tree, ccache doesn't even seem to help with this 12:58:11 oh 13:00:22 zroot/src 169G 475G 61.3G /src 13:17:24 to not build llvm - WITHOUT_TOOLCHAIN 13:18:37 the system's not terribly usable if you do that, however 13:18:50 it's useful for some deployments but i think you'll struggle on a regular server/desktop 13:19:24 it will be bad if you do delete-old and delete-old-libs after that, yes 13:33:47 noted 13:45:47 lw: thanks, I'll look into dynamic dns updates 13:46:39 (the use case is Gitlab CI/CD which creates jails on the fly when a push/merge is made) 13:47:23 i'm not sure if you're using DHCP for this (someone else mentioned it?) but if you are, most DHCP servers can do this for you 13:48:00 yes, I'm still using ISC DHCPD 13:48:19 but I was wondering on the unbound side 13:49:06 i'm fairly sure unbound can't do this, you need a real authoritative server for the zone. but you could run both on one host and have unbound forward queries 13:49:28 does NSD supports this? 13:50:52 i don't think nsd can do dynamic dns 13:51:24 it seems like there are some third-party options that can update the zone file on disk in response to dynamic updates so nsd can reload it 13:51:58 (in that case, you could also keep using unbound...) 13:52:06 yeah.. 13:52:28 I'm using Saltstack under the hood so maybe I could just add this to my orchestration script 13:53:21 thanks 13:53:38 i have never used this and know nothing about it but: https://rubygems.org/gems/dyndnsd/versions/3.8.0 13:53:39 Title: dyndnsd | RubyGems.org | your community gem host 13:54:08 oh wait, i think this is a client, never mind 14:19:56 * lw builds another copy of llvm 14:24:58 the fun never ends 14:25:43 there should be a video game in 'make buildworld' where you have to complete a level to build the next directory, that would make it more fun 14:26:03 good grief 14:53:10 does modifying libc require rebuilding llvm? 15:01:34 no 15:01:43 assuming you already built llvm once for the initial build 15:21:38 ugh, i wanted to stop FreeBSD-utilities from depending on FreeBSD-zfs, but fstyp(8) needs libzfs_core... 15:27:19 i recently started using bhyve-vm and set up a windows 10 vm with "cpu=8" in the config file, but it only shows me and uses 2 threads, anyone got an idea what's up with that? 15:35:25 phryk: I'm not too familiar with bhyve, but does the "cpu=8" parameter specify the amount of CPU sockets? Because due to licensing, Windows will limit itself to a certain amount of sockets, depending on the edition you have, but if you configure to instead give it cores instead, it will use all of them 15:35:52 (as in, one CPU socket, 8 cores) 15:36:51 Dooshki: sample.config says "# specify the number of cpu cores to give to the guest" about this parameter 15:37:57 also let me look at the activation status, i think that might actually be it. 15:57:43 Workstation versions of Windows have only ever supported a max of two sockets. 15:58:14 And four for server versions, without custom HALs. 16:34:30 git add -i must be the least intuitive command line interface ever created 17:34:02 i don't know if drm-kmod, sway, or the kernel scheduler is at fault here but i'm a really annoying issue where sometimes if i'm building something (e.g. make -j12 buildworld) my cursor starts moving really slowly and the desktop becomes unusable 17:47:04 I have a box where 'pkg update' says it's updating the repo catalog and that everything is up to date. . . but there's no way it can be. 17:47:17 There some forced check or setting I can poke at? 17:47:59 CrtxReavr: if pkg says it's up to date it's up to date, it doesn't randomly hold back updates - are you sure you're using the right repository? 17:48:20 lw, No. . . I'm not. 17:49:37 https://termbin.com/q1cy 17:51:30 i will look at your url in a sec but i can't move my mouse due above issue... 17:51:39 https://termbin.com/xs95 17:52:03 CrtxReavr: why do you think there should be updates? 17:52:24 'cause it hasn't been updated in a "coon's age." 17:52:30 CrtxReavr: one thing you can try is replace pkg+http:// with http:// in /etc/pkg/FreeBSD.conf -- you might have landed on an out of date mirror 17:52:50 wait, no 17:53:00 use http://pkg0.nyi.freebsd.org 17:53:01 Title: pkg0.nyi.FreeBSD.org 17:53:04 that's the master mirror 17:53:33 And that gets set wher? 17:53:35 where 17:53:38 /etc/pkg/FreeBSD.conf 17:53:52 you're meant to copy that to a new file in /usr/local/share/pkg/repos to edit but you can just edit in-place for testing 17:54:48 url: "pkg+http://pkg0.nyi.freebsd.org/${ABI}/quarterly", 17:54:51 Like that/ 17:54:53 ? 17:55:17 use http:// not pkg+http:// 17:55:30 pkg+http:// is for automatic mirror selection using SRV records, but you want to force it to use that mirror 17:55:59 Okay, now it's doing something. . . 17:56:35 Hmmmm - okay, not quite. 17:57:10 this is giving me flashbacks to when i used to run a cvsup mirror 17:57:37 https://bpa.st/G2KA 17:57:38 Title: View paste G2KA 17:57:52 Remember when the billionth second broke cvsup? 17:58:06 That was such a huge pain in the ass. 17:58:25 Y2K had nothing on the billionth second. 17:58:33 are you really sure there are meant to be updates? like, take a random package and look it up on freshports and see what the latest version for FreeBSD:13:amd64 is 17:58:56 CrtxReavr: what's your config look like rn? 17:58:56 What about that SRV record error? 17:59:13 oh, that's because of mirror_type 17:59:21 i don't think that makes a difference but you can try... (one sec) 17:59:24 https://termbin.com/2dly 17:59:34 CrtxReavr: just comment out mirror_type in FreeBSD.conf 17:59:40 that should fix the SRV thing 17:59:53 what lw said 18:00:30 Okay. . . it's gone. . . still no updates. . . 18:01:06 CrtxReavr: show 'pkg info'? 18:01:39 How about 'pkg version'?: https://termbin.com/01tv 18:02:40 I mean, I can do 'pkg info' but that's prolly less helpful. 18:02:48 that works too 18:04:34 oh qutebrowser crashed 18:05:25 CrtxReavr: just checking a couple of packages (python39, curl) it seems like you might just not have updates 18:05:46 Yeah. . . wierd. . . but yeah. 18:05:52 Thanks though. 18:05:54 although it's odd that FreeBSD:13:amd64 quarterly has curl 8.6.0 while 14 has 8.7.1 18:06:03 maybe the 13 builder is lagging a bit? 18:06:59 ah wait, didn't a new quarterly just come out, it might be busy building that 18:07:26 8.7.1 went into quarterly on april 1 though 18:09:17 i wish pkg-status.freebsd.org was less awful 18:11:41 this is why i would never use pkg.freebsd.org packages, fwiw. the builds take so long you can be weeks out of date on security updates, especially on some architectures 18:14:11 is this a money for servers problem? why does it lag so much? 18:14:53 markmcb: imo it's more of a ports infrastructure problem... or maybe a poudriere problem. there's a fix landing in poudriere soon that will significantly reduce the number of packages to be rebuilt when a dependency changes, which should help a lot with this 18:16:00 ah that's good news 18:16:24 i'm not even sure if pkg.freebsd.org uses incremental builds (as opposed to just rebuilding the entire thing every time) but i assume they do 18:17:56 (i say 'fix' but aiui that patch has been in development about two years, it's pretty complicated to fix) 18:32:38 why can jail.conf have just vnet; and work? man jail says its values are inherit and new so it should be vnet = new; no? 18:40:21 alepzi: because the manpage is wrong, you should submit a patch 19:13:31 when would a jail admin wanna be able to read kernel message buffer? 19:24:45 alepzi: some interesting messages only go to kern msgbuf 19:24:54 like: someone else is using my ip address on 19:25:09 or arp: moved from to 19:25:34 or link state changed to (although that's probably uncommon in jails) 19:25:54 or messages from programs that exit due signals 19:26:12 or various NFS errors (i think NFS can run in jail now, although maybe only the server part) 19:26:51 is that /var/log/messages? 19:27:51 it does end up in /var/log/messages but only because syslogd can read it from kernel msgbuf 19:27:54 i think 19:27:58 actually not 100% sure there 19:36:44 how do i use "depend" in a jail conf? i tried to put depend = "testjail"; in the conf of testjail2 but service jail start says cannot start testjail2 depends on undefined jail "testjail" 19:36:57 are you using /etc/jail.d? 19:37:06 jail.conf.d, whatever it's called 19:37:08 each jail has a file in /etc/jail.conf.d/ 19:37:14 like testjail.conf, testjail2.conf 19:37:16 yeah that doesn't work depend, there's a PR for it 19:37:24 damn 19:37:27 either stop using depend or put them all in jail.conf 19:37:34 fwiw, i don't like depend and don't think it works well 19:37:40 why not? 19:37:49 just because a jail is started doesn't mean its services are available 19:38:02 better to make each jail able to start individually, perhaps with some extra rc sripts if needed 19:38:21 e.g. my KDC jails have an rc.d script to wait for LDAP to become available because otherwise the KDC doesn't start (this is a KDC bug really, but...) 19:38:34 nice 19:42:43 i noticed the handbook has you set up a jail so its console output goes into a file on the jail host. why not have it go into the jail's /var/log like a normal system? 19:44:18 the handbook can't consider every possible configuration someone might want, if you want the console log in the jail, just configure it like that 19:51:10 just read all of man jail 19:51:12 * alepzi flexes 19:56:02 lw, I enabled EXPO, it's building even faster now ^^ 19:56:12 jbo: the fuck's an expo 19:56:18 AMD's version of XMP 19:56:20 ah 19:56:28 is that different from AMP? 19:56:35 dunno, first time doing AMD stuff 19:56:40 everything is different for me atm :p 19:56:53 i think my AM4 board just does XMP but that's pretty old, it's probably changed since then 19:57:11 I am trying to figure out why the CPU has so few clock freqs 19:57:12 dev.cpu.0.freq_levels: 4200/5040 2200/1540 1500/975 19:57:19 jbo: a little birdy (diizzy) told me Zen 4 support is bad and doesn't work properly, how are you finding it? 19:57:20 is that normal in team red land? 19:57:43 not sure about your fancy TR but my Ryzen has only 3 also: dev.cpu.0.freq_levels: 3400/3740 2800/2800 2200/1980 19:58:01 lw, I can't speak for that yet. I setup the box a few days ago and only since today I am actually using it as a desktop/workstation. 19:58:19 interesting yours go down to 1500, i wish the 2700X in my server did that 19:58:25 if you keep using that language I'm gonna ship a TR your way just to make it staph 19:58:50 no stepping between 2.2GHz and 4.2GHz is a bit weird though 19:58:54 I was surprised to see those freqs. form Intel I'm used to seeing more freqs. sometimes the CPU would just clock around 650 MHz or something :D 19:58:57 yeah 19:59:07 maybe this is what diizzy meant? 19:59:20 dunno, diizzy is just jelly 19:59:20 like i wonder if they switched to a new API or something and this is the old API 19:59:36 I hope to find all of this out soon (tm) 19:59:54 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311 19:59:57 Title: 278311 – amdtemp: Does not recognize AMD Threadripper 7960X 20:00:21 i saw that commit in my inbox and though, oh jbo has one of those, oh it was jbo who reported the bug 20:00:30 you are the only freebsd 7960X apparently, congrats 20:01:19 don't thank me, thank $employer 20:01:31 maybe I should start doing something useful with it soon 20:01:42 i can send my ssh public key, let me know 20:01:52 lw, would it help src people if I send experience summary to the ML or something like that? or is that considered noise? 20:02:14 jbo: i don't consider myself 'src people' but i think reporting hardware experiences is useless in general, someone might be searching for it later 20:02:25 i'm not exactly sure what is the best list for that though 20:02:31 uhhh 20:02:36 i mean it's USEFUL, not useless 20:02:40 damned keyboard 20:03:09 maybe amd64@ 20:03:24 lol'd - I am/was genuienly confused now 20:03:30 let me try that again 20:03:31 did you learn how to paste yet? 20:03:46 jbo: yes you should send it to the list because it's useful info for people who will be searching for experiences with this cpu on freebsd 20:04:23 jbo: i keep leaving these glasses of whiskey next to my keyboard and mouse and they start behaving weirdly and not typing/pasting properly, i don't know why it keeps happening 20:05:05 did you know there's an entire mailing list for Enlightenment on FreeBSD? the 3 people still using Enlightenment must be having a great time there 20:06:08 also, freebsd-women@, has not had a post since 2022, that's probably a sad reflection on something 20:06:44 amd64@ seems pretty dead too, i was complaining yesterday there are far too many mailing lists 20:07:32 hardware@, had 21 posts in the whole of 2023 20:07:50 jbo: so in summary, yes you should mail the list, but as to what list, your guess is as good as mine 20:08:06 lw, got some whiskey right now o/ 20:08:31 ack 20:08:35 maybe just mail -current, assuming you're running 15.0 as god intended 20:08:50 (god = kirk mckusick) 20:09:51 lw, is there a way in C++20, to convert a constexpr integer to a hex string_view representation during compile time? 20:10:08 I am _not_ running -current 20:11:14 lw, also, are you running powerdxx on your AMD machines? 20:17:05 no, i use the normal powerd on both amd64 and arm64 20:17:22 and i do not know about constexpr but maybe check if std::to_string is constexpr (i suspect not) 20:17:30 because reasons? 20:17:48 because... it's what's in base and it seemed to work fine 20:17:50 wasn't powerdxx supposed to be "better"? 20:17:52 what does powerdxx do better? 20:17:53 aye 20:18:27 lw, can you explaine those freqs to me? 20:18:39 it seems to be three pairs 20:18:45 what are the two number? 20:18:59 how to report mailing list spammer https://www.le-fay.org/tmp/30d/Screenshot.from.2024-04-16.at.21_18_27.112234313.png 20:19:01 base/boost? but then why is the magnitude/order different? 20:19:20 jbo: first number is cpu speed (MHz), second number is supposed to be power consumption (mW) but i'm extremely dubious about its accuracy in general 20:19:43 also not clear if that's mW per core or total for the package 20:20:22 well doing a stress -c 48 results in 560W power draw (of the entire machine/box). 20:20:28 nvidia-smi says 40W 20:20:35 that is with stock settings, no OC 21:07:15 why did we think it was a good idea to start the build from our phone, now we can't reboot our phone until the build finishes 21:09:53 i'm pretty sure someone suggested using tmux. oh yeah, that was me 21:10:53 yeah well; it's building libclang now 21:11:11 oh right we have our cpu scaling set to powersave 21:26:27 we could probably have been done already but instead we were running it at half the speed 21:54:40 jbo: remember when you told me there are 4,000 src committers? i have reliable information that this is fake news 22:17:15 finally got around to fixing my alc(4) issue https://github.com/llfw/freebsd-src/commit/ec630c555664683dd1475391156ae5359e0ba07a 22:17:16 Title: alc(4): disable MSI-X by default on Killer cards · llfw/freebsd-src@ec630c5 · GitHub 22:17:34 don't even use that card anymore (it's crap) but it annoyed me enough at the time that i thought i should do something about it 23:13:08 ok now what 23:13:17 i did a pkg upgrade and my sway status bar vanished 23:32:40 I have questions 23:32:48 who would like to answer some questions? 23:32:55 jbo: no one 23:32:58 questions are bad 23:32:59 :<<<<<<< 23:33:03 you will accept what we tell you 23:33:18 not sure whether I understand poudriere.conf BASEFS= 23:33:30 https://dontasktoask.com/ 23:33:31 Title: Don't ask to ask, just ask 23:33:32 I set ZROOTFS=/ssd0/poudriere where ssd0/poudriere is a dataset 23:34:11 so I guess I want to set BASEFS=/ssd0/poudriere ? 23:35:55 no 23:36:00 ZPOOL=ssd0 23:36:05 ZROOTFS=/poudriere 23:36:12 BASEFS=/poudriere 23:37:07 that... makes sense 23:37:08 thanks <3 23:37:17 but create the zfs before you run poudriere: zfs create -o mountpoint=/poudriere ssd0/poudriere 23:38:53 wait... why the mountpoint? 23:39:03 is there something wrong with just mounting it under /ssd0/poudriere? 23:39:35 no but then you have to set $ZROOTFS and $BASEFS to /ssd0/poudriere and i think it gets complicated 23:39:47 one of those is reletive to $ZPOOL and i think the other isn't, can't remember which 23:44:27 yeah so I just did what you said but without mountpoint= and it still dropped the jail in /usr/local/poudriere/jails 23:44:32 must be AMD's fault 23:44:46 are you sure it actually did that, it's a bit confusing 23:45:00 it'll create filesystems in /poudriere then mount them in /usr/local/poudriere 23:45:25 wat 23:45:38 zfs list 23:45:39 ssd0/poudriere/jails 1.70G 898G 96K /ssd0/poudriere/jails 23:45:39 ssd0/poudriere/jails/140Ramd64 1.70G 898G 1.70G /poudriere/jails/140Ramd64 23:48:43 lw, it actually seems to set mountpoint= automatically then? 23:49:13 yes exactly, that's what it does 23:49:43 although, wait, maybe not 23:50:07 i think one of those options tells it where to create the filesystems and the other says where to mount them 23:50:11 but i can't remember which is which 23:50:23 now we get back to why I asked 23:50:25 but like, just put them on /poudriere, it works 23:52:37 ugh i need to find a new window manager 23:52:51 * jbo recommends x11-wm/bspwm 23:52:52 what do people use on wayland, hyprland? apparently some freebsd people wrote that? 23:53:00 on wayland I once used hikari 23:53:03 worked nicely 23:53:08 oh, hikari, that's what i was thinking of 23:54:04 lw, how can I confirm under FreeBSD that the TR is actually doing the boost freq thingy? 23:54:10 it's always reporting 4.2 max 23:55:01 i don't think freebsd has any way to monitor that 23:55:19 i'm not even sure it's exposed to the OS at all 23:59:30 trying to build hikari 23:59:32 [main-amd64-main] [2024-04-17_00h54m00s] [balancing_pool] Queued: 231 Built: 0 Failed: 0 Skipped: 0 Ignored: 0 Fetched: 0 Tobuild: 231 Time: 00:00:24 23:59:36 FUCKING PORTS 23:59:47 that's good right? 23:59:55 * jbo throws a CPU at lw