01:15:03 upgrade to current == build from source, no/ 01:15:14 is there another way? 01:53:44 ngortheone: you could install one of the snapshots 01:54:18 but ... from an existing system. uh, that would be rough 02:01:37 rtprio: you are right, downloading snaphot iso and installing from scratch or tarball and using it as boot env... 02:03:11 i should really read a little more scrollback before replying 02:09:05 my name is technical, last name debt 02:50:25 Reinhilde: you must be a welcome friend in tech startups and huge IT enterprises 02:50:56 surprisingly, no 02:51:04 but I find my way in >:3 02:59:39 lol 03:00:46 ah yes, discord linux bros calling BSDers hipsters who only complain 03:00:56 happens every day, it's not news 03:01:07 solve the problem by not using discord 03:02:39 disregard GNU/Linux users the same way you disregard Windows and Mac users 05:36:08 Reinhilde: i had "technical debt broker" on my internal title at one of my previous jobs 06:41:55 Hello folks, Happy upgrade day :-) 06:53:16 Reinhilde: discard users are hipsters who don't knoe how Internet or conputer xorks. For them it's magical. I did know anything about discord, even I have a old account). 06:53:41 somewhat 06:55:13 sorry, I mean discord 07:01:13 Lovis_IX: they're not hipsters, they're mainstream, however. 07:01:20 as unfortunate as that is 07:02:47 excited to upgrade my freebsd desktop and openbsd server this week 07:05:37 xtile: I am so excited to upgrade my work laptop, but it's yet available in european mirror :-( (and I have noting else importent to do0 07:05:53 * xtile nods 07:06:09 i'm patient, i can wait a couple days. you can be patient too, I hope. :3 07:06:33 it only became april 11 a few minutes ago where i am 07:06:37 which is the listed release date 07:07:33 xtile: I MUST be patient and it's april 11 for 9 hours now in France. 07:08:58 * xtile nods 07:14:48 Must be tiring being ahead of the time (with respect to some other places) ... 07:25:14 I got my hands on an Azure HPC instance, but the infiniband devices aren't showing up. 07:27:03 there should be one or two mellanox (mlx5en(4)) nics, but there's just one hn(4) device 07:29:42 pciconv -lv doesn't show them either 07:32:51 what's funny is that dmesg doesn't show anything any more about mlx since i upgraded to 13.2 07:33:16 that is the opposite of what i expected 07:33:47 No mellons for you, meena! 07:35:45 * parv is aghast for missing on "mellans". For the love of puns! 07:44:57 meena, To ask the obvious is "mkx5en" module already loaded? 07:45:30 s/k/l/ 07:55:17 not according to kldstat 07:55:29 Load that sucker! 07:56:44 The manual page list the syntax to stuff in "loader.conf" 07:56:52 sudo kldload -v mlx5en 07:56:52 kldload: can't load mlx5en: module already loaded or in kernel 07:57:18 phhbttt :-| 07:57:55 "kldstat -v" might have noted that 07:58:39 kldstat -hv | grep -i mlx 174 pci/mlx 07:58:39 173 mlx/mlxd 07:58:39 411 pci/lkpi_mlx5_core_pci_table 11:21:38 https://bsd.to/yy3c 11:21:39 Title: dpaste/yy3c (Plain Text) 11:22:34 I connect the same ssid use Linux iwctl very fast,but in my pc freebsd wpa_supplicant alway error 11:23:20 do they have the same configuration? 11:23:38 same ssid and password 11:23:48 sorry, i should've clarified 11:24:00 does wpa_supplicant.conf have the same configuration on both systems 11:24:39 In linux,I use iwd,not wpa_supplicant.I think the two is diff. 11:25:06 Well, there you go. 11:25:27 they're different software, so you can't assume they should behave the same 11:25:53 yeah,but wpa_supplicant so slow? 11:26:18 is there any way to use iwd on freebsd? 11:26:41 wpa_supplicant is part of the freebsd base system, but it's contributed from https://launchpad.net/wpasupplicant so the person to ask is reinhard tartler 11:26:42 Title: wpa_supplicant in Launchpad 11:27:15 i don't know what iwd is, so i assume it's something linux-specific 11:27:31 I use maybe 1 min to connect to net in bsd,I can't stand it. 11:28:22 it's a virus 11:28:25 I guess in your pc,maybe not too long,right? 11:29:02 it isn't slow at all for me 11:30:15 I can't unstand why sometimes it works not so long,just 10s maybe,but sometimes,too too long.It make me crazy. 11:31:12 and i see that iwd is licensed as gplv2, so it can't be imported into the base system - and even if it could be in ports, it seems to have a heck of a lot of dependencies like dbus and netlink (both of which could in theory be used, since both are available in some form, depending on what version of freebsd you're using), but also something called "main event loop", "Timers" (capitalized, so i assume 11:31:18 it's something special) plus a bunch of primitives which i'd be surprised if freebsd implements 11:31:43 what you _can_ try is enabling fast_reauth in wpa_supplicant.conf(5), though i don't know if it's going to fix your exact issue 11:32:09 i didn't know iwd depends on dbus 11:32:32 well, it depends on a library which needs dbus 11:32:48 at least according to the documentation i can find 11:32:48 i give it a try. 11:33:45 i can't tell you what could be the source of the delay, i can only speculate 11:35:51 it could be anything from differening txpower values, improperly configured base station, or even a bug in wpa_supplicant (though i wouldn't necessarily assume that as the first option, since wpa_supplicant has had pretty wide usage over the years, including on linux) 11:35:57 wouldn't the logs have something to speculate about? 11:36:13 that's entirely possible, but i've seen no longs 11:36:23 s/longs$/logs/ 11:37:28 my log is here https://bsd.to/yy3c 11:37:29 Title: dpaste/yy3c (Plain Text) 11:37:56 CTRL-EVENT-SCAN-FAILED many times 11:38:09 what cause it? 11:39:16 the scan is failing because the access point temporarily disables authentication when the 4-way handshake is failing 11:39:56 you're not providing it the right key, according to the CTRL-EVENT-SSID-TEMP-DISABLED 11:40:07 so you probably mistyped your password or the syntax for the configuration file 11:41:03 and I give another success try https://bsd.to/rjpk 11:41:05 Title: dpaste/rjpk (Plain Text) 11:41:52 do you live close to other people? 11:42:48 yeah,if you mean some people around me. 11:43:39 even if there isn't anyone actively trying to do a wifi deauthentication attack, if you've got regular people around you who've got a bunch of hardware, it's not out of the question that one of them have misconfigured it (or it's been misconfigured from the manufacturer) so that what essentially ends up happening is the same as a wifi deauthentication attack 11:43:57 that'd produce the behaviour you're seeing, where sometimes you can auth quickly and other times you can't 11:45:35 none of this precludes what is aid before either, by the way 11:45:50 s/aid/said/ 11:46:29 you mean someone use something like airmon-ng to attack me, it cause I can't connect quickly,Maybe I guess. 11:46:43 no, it doesn't have to be someone trying to attack you 11:47:27 if you live near a hotel, wifi deauthentication attacks are a well-known thing they do to prevent their guests from using the guests own access points (because they want the guest to pay) 11:48:03 and similarly, it can also be someone near you who has a badly configured piece of hardware (i believe this is how wifi deauthentication attacks were discovered, initially?) 11:48:12 ok,then,if i use my phone hotspot,I should connect quickly 11:48:41 a misconfigured device or hotel chain trying to gouge money out of people would also affect your phone hotspot 11:49:32 I understand,maybe the school surely do this. 11:49:37 you'd have to travel somewhere without ANY people within range of any of your devices (ie. +300 meters from anyone) 11:51:51 school ask us to pay money for month network.gouge money,as you say,so it's the conclusion,thx debdrup 11:51:52 there's a proposal for 802.11w, which is supposed to fix part of the issue with wifi deauthentication, but it doesn't fix the wifi deauthentication attack on the 4-way handshake (which is what it looks like you're struggling with) 11:52:25 it's unfortunately just a result of 802.11 being a shared medium 11:52:39 (and greed) 11:54:34 DOCSIS has a similar deauthentication attack, but at least there the ISP can spot who's doing it on the CMTS - and there's much less benefit to doing it on DOCSIS 11:56:30 the curse of having worked as a network administrator is that you also have to work with wireless 11:57:55 it occur to me,why Linux stable,anyway? 11:58:03 haven't got a clue 11:58:16 how can i update if im running FreeBSD donut 13.2-RELEASE FreeBSD 13.2-RELEASE releng/13.2-n254617-525ecfdad597 GENERIC amd64 11:58:21 or is that the latest? 11:58:22 i never said all of the above was t he reason why, just that it can happen 11:58:36 yep 11:58:36 11:59:21 kezdryx: freebsd-update fetch will tell you 11:59:26 ok 11:59:27 err, sorry 11:59:32 freebsd-update updatesready 12:00:02 or maybe i'm misremembering what they're for, it's been too long since i used -RELASE 12:00:15 s/LASE$/LEASE/ 12:00:37 no updates to install 12:00:50 on either 12:00:58 should i rollback? 12:01:05 why would you do that? 12:01:07 then reinstall? 12:01:15 what are you trying to accomplish? 12:01:35 13.2 has been out for less than 24 hours, expecting updates that soon is a bit much 12:01:42 because IDS says some of the sha255 numbers are off 12:01:59 i updated on april 7th 12:02:01 then say that to begin with 12:02:12 if you updated on april 7th, you updated before -RELEASE was out 12:02:20 oops 12:02:23 =( 12:02:39 whoever told you to go update seems to be the one to ask how to fix this, because they got you into this mess 12:02:50 that was me 12:03:00 how did you know to update? 12:03:05 the announcement hadn't gone out 12:03:19 figured id just do it 12:03:27 welp. 12:04:15 what files are the checksums failing on? 12:05:07 hold on gotta rerun ids 12:05:43 you might wanna set the PAGER environment variable to cat or something else, so you can pipe it to a file 12:05:53 check the freebsd-update(8) manual page 12:07:01 but for reference, whenever you're updating FreeBSD to major or minor releases, -RELEASE isn't out until a mail from the release engineering team has been sent to the announce@ mailing list 12:07:35 even if someone else tells you it's fine to update, they probably don't know what they're talking about 12:07:48 group master.passwd passwd pwd.db shells spwd.db and sysctl.conf 12:08:12 will do next time 12:08:23 kezdryx: are these the files that are different between your box & what IDS shows? 12:08:29 yers 12:08:34 yes 12:08:40 ok those are all fine 12:08:45 yeah, those should be files 12:08:49 s/files/fine/ 12:09:10 group contains user<->group membership mappings 12:09:21 those are all files that're changed by a bunch of things like installing/updating packages or modifying the system intentionally 12:09:28 the passwd/pwd/spwd ones are all related to adding users 12:09:47 shell is a list of what shells can be used by users (e.g. if you add bash/zsh from ports) 12:09:53 and sysctl is always a local thing 12:10:40 I need a tip on how to have Makefile that does A on amd64 and B on aarch64 12:11:01 so, do different things based on architecture 12:12:18 mmm could I put $(sysctl -n hw.machine_arch) in as a Makefile target perhaps 12:12:32 dch: is it make or BSD make? 12:12:38 BSD make has a LOT more conditionals 12:12:46 its our make debdrup 12:12:59 that's BSD make then 12:13:19 check the Conditionals part of the manual page 12:14:48 so im stuck? 12:16:42 debdrup: ok, there's a built in var `MACHINE_ARCH` 12:16:56 so `build: ${MACHINE_ARCH}` DWIM 12:17:04 dch: I don't think that works for what you want, it only checks the present machine's arch 12:17:11 via uname -p 12:17:17 ..unless that's what you want 12:17:26 debdrup: in this case its exactly what I want, this build script will be run on the native h/w each time 12:17:32 ah, fair 12:17:39 yeah then MACHINE_ARCH will do it 12:17:56 I would like to figure out how to make it truly cross-platform but for the moment a simple dirty hack is sufficient 12:19:00 kezdryx: it's not clear what you're stuck on, AFAICT you're on a perfectly normal FreeBSD release there 12:19:27 for example, here's an arm64 13.2-RELEASE I upgraded this morning: 12:19:29 FreeBSD fmrl71 13.2-RELEASE FreeBSD 13.2-RELEASE releng/13.2-n254617-525ecfdad597 GENERIC arm64 12:19:52 did you updage today or earlier? 12:20:04 this is from today 12:20:04 update 12:20:09 oh 12:20:18 but over the last week I have done repeated migrations on other boxes 12:20:48 debdrup: now theres two 12:20:55 and if you updated before the official announcement, `freebsd-update IDS` will tell you whats wrong 12:21:03 and several of his boxen 12:21:08 i don't care. 12:21:08 which as we discussed above, looks like nothing is out of date 12:21:12 heh 12:21:15 it's a dumb idea to update before -RELEASE is out. 12:21:39 dch see, you updated to soon too 12:21:56 even when I ran -RELEASE, I waited at least until the security officer took over the releng branch, but usually longer 12:22:07 kezdryx: the one from this morning, is definitely post official announcement 12:22:18 unless i'm updating because of a security announcement, i'm _NEVER_ ever going to update as soon as i can 12:22:45 so i made a mistake, geeze crucify me 12:22:57 ok 12:23:31 kezdryx: debdrup is just sharing his experience, no worries. I tend to upgrade late in general, but I have some infra where I try to apply the BETA & RC for test purposes 12:24:09 I recompile all the time from source on systems with the capacity. 12:24:28 that's usually 1-2 systems per fleet 12:24:57 for personal deployments, you don't have to do that 12:27:36 also no need to be that conservative unless jumping releases 12:28:10 how conservative, depends how well you track the changelog 13:57:26 That's puzzling actually. Why is there the 1-2 week gap in handing new releases over to the sec team? 14:33:09 morning 14:33:59 Does anyone know how often packages with known vulnerabilities get updated? 14:35:05 Finally getting everything up to 13.1-p7 and pkg audit is showing curl as having multiple vulnerabilities. 14:46:43 hmm 13.2 has the wg driver? I don't see it in the conf 14:47:00 is there a proper way to remove the lib32 system components? 15:42:47 release notes mention nproc(1) but theres no manpage when you click 16:40:13 13.2 here I come 16:43:39 tobias: ! 16:44:44 hi! :) 16:45:08 i'm trying the new 13.2 release in a QEMU VM 16:45:50 first of all, is there a way to boot the amd64 version with just serial console enabled? ("-nographic -vga none" in QEMU) 16:47:06 it appears to get stuck on "Starting the BTX loader" 16:55:48 i can boot with "-display curses -vga std" though. also, i can select "Cons: Serial" in the bootloader then. would be nicer completely without the need for a virtual GPU of course. 16:58:55 https://download.freebsd.org/releases/amd64/amd64/ISO-IMAGES/13.2/FreeBSD-13.2-RELEASE-amd64-dvd1.iso <- that is the iso i'm trying right now 17:51:33 Under: https://cgit.freebsd.org/ You have 3 branches, where is the packages branch? (pkg) 17:51:34 Title: FreeBSD Git repositories 17:53:01 I want to figure out whats the current Quarterly release yet I cant find "pkg.FreeBSD.org/${ABI}/quarterly" in GIT form 17:53:43 I assume it to be 2023Q2 (but that would mean that a 2023Q3 branch would already be created, which it isnt, not in the ports tree atleast) 17:56:22 ElectricJozin, I don't know (I am not a contributor) but AFAIK it's here https://cgit.freebsd.org/ports/ 17:56:23 Title: ports - FreeBSD ports tree 17:57:08 rwp, and so some of those packages are compiled into binaries and shipped right? 17:57:38 If thats the case what determines what packages are shipped 17:58:16 I have this article queued up in my reading list for when I get some time: https://freebsdfoundation.org/wp-content/uploads/2022/03/mingrone.pdf 18:00:33 Also let's not leave out: https://docs.freebsd.org/en/books/porters-handbook/ 18:00:34 Title: FreeBSD Porter's Handbook | FreeBSD Documentation Portal 18:01:27 AFAIK *all* of those packages are compiled into binary packages available from the binary package repository. 18:01:42 Except obsolete packages do get removed when appropriate. 19:46:21 and license reasons (hm, well, I think they even get build, but then not put in the pkg repo when the license doesn't allow official packages) (hm, and obsolete stuff still gets build as long as the port exists and isn't marked broken or ignored) 20:40:35 three cheers for 13.2 ! \o/ 20:40:37 * prg_ celebrates 20:41:07 :P 20:41:15 I finally figured out sway! 20:41:17 https://imgur.com/a/tGxoQCn 20:41:18 Title: Imgur: The magic of the Internet 20:42:42 wayland? that's not very oldfashioned :P 20:42:50 * prg jokes 20:43:20 prg: :D 22:11:20 Is there a reason why pkg-config is not available inside jails? 22:11:35 my base system has it but not my jails 22:13:41 adonis: pkg-config is a package that you can install with pkg 22:13:47 oh 22:14:02 pkg which (which pkg-config) 22:14:03 /usr/local/bin/pkg-config was installed by package pkgconf-1.8.1,1 22:14:39 it is not part of pkg the package manager, it is a different tool with overlapping name 22:16:52 ngortheone: Yea I see that, for some reason I thought it was part of base FreeBSD.. 22:17:02 Thankfully the solution was simple :) 22:54:05 can I set KERNCONF in src.conf or src-env.conf? 22:55:16 Well, it's in make.conf(5).. 22:55:42 src-env.conf is for the source environment, not for the source itself - if that makes sense 22:56:52 So for example, it controls object directory creation, meta-mode, and dir-deps - all things that have to do with control of how the environment the source is built in. 22:57:55 aye 22:58:05 why is KERNCONF in make.conf and not in src.conf? 22:58:34 Because things outside of the source tree can make use of it. 22:58:53 I can't remember if there's anything that does anymore, but I think at one point the ports framework did. 22:59:41 Maybe something third-party does/did too? 23:10:12 Before the masses see it: https://www.bsdcan.org/events/bsdcan_2023/schedule/ 23:10:13 Title: Conference Schedule - BSDCan 2023 23:22:04 yiss