00:03:38 no, fiber 00:03:55 mtu is at 9000 00:05:21 ibv_devinfo doesnot exist 00:08:10 ps, fiber sfp+ 00:09:52 otakon: firstburstlength and maxburstlength seem much lower than their defaults, and I'm not sure I understand why. 00:10:59 meena: I can try asking around if someone has an infiniband card they're no longer using 00:14:22 Hrm, I'll need two and/or a switch that has infiniband, so it might take a longer time :/ 00:20:02 I tried bigger values, still the same cap 00:20:24 debdrup: i wish i was in a hurry, but i have no capacity to be in a hurry 00:20:25 you dont need switch, 2 cards, point to point 00:21:48 a switch does make things more interesting… 00:21:53 otakon: right, but it'd be nice to have IB to play with :3 00:22:21 of course it will be! 00:22:41 1gbe is so 20yrs obsolete 00:24:34 (side question, if I log out now (goto sleep), I 'll lost your posts, right?/) 00:24:50 *loose 00:25:39 Yes, unless you have a client like irssi that you can background using tmux, and the machine stays online. 00:26:10 There's all manner of other ways to achieve persistence logging too, of course. 00:29:56 * meena uses a "WebApp" for IRC, called TheLounge 00:30:21 otakon: but: We'll be back tomorrow, fresh from "sleep", and with better ideas 00:30:37 "fresh" "ideas" 00:30:56 "good" "night" 00:31:09 thank you for your time guys 00:31:21 I'm not quite sure I like the notion of some service that indexes all of IRC; it's fine to have individuals log channels (heck, I've been doing that since 1994), but it's another thing entirely if it's some corporation that's behind it. 00:31:24 i really appreciate your effort 00:32:01 I ll talk tommorow here 08:03:00 hello folks. How can I set build options for a port non-interactively? 08:03:28 I tried to add lines like "www_nginx_UNSET+= HTTP_FLV" to /etc/make.conf but saw that has no effect. 08:39:54 unset… hm 08:41:15 I tried with _SET too, e.g. "www_nginx_SET=WITH_MODSECURITY3" and "www_nginx_SET+=WITHOUT_MAIL", to no avail 08:41:28 michelem: i don't see any UNSET here: https://docs.freebsd.org/en/books/porters-handbook/book/ 08:41:30 Title: FreeBSD Porter's Handbook | FreeBSD Documentation Portal 08:42:13 yes, indeed. 08:42:41 on second thought, that might not be in *that* handbook 08:43:12 How can I possibly set those options programmatically? I can rmconfig and pass them at runtime to "make package" , but then I can't have preparation & compilation separate, and I don't have a trace of the options used. 08:43:41 I tried "BATCH=yes make -DWITH_IPV6 config" and it still prompts me with the configuration curses screen. 08:46:05 sec 08:47:23 https://docs.freebsd.org/en/books/handbook/ports/#ports-using here we go, that's the users' handbook 08:47:24 Title: Chapter 4. Installing Applications: Packages and Ports | FreeBSD Documentation Portal 08:47:35 also doesn't document UNSET 08:47:48 OR SET WTH 08:48:26 * meena has only had one coffee and no breakfast and only opened the laptop because NOBODY IS AWAKE AND SHE COULD FIX UP A PR 08:50:50 https://man.freebsd.org/cgi/man.cgi?query=ports&sektion=7&apropos=0&manpath=FreeBSD+13.1-RELEASE+and+Ports this still talks about SVN 08:50:51 Title: ports(7) 08:54:08 that's a good pointer. https://man.freebsd.org/cgi/man.cgi?query=ports&sektion=7&apropos=0&manpath=FreeBSD+13.1-RELEASE+and+Ports does talk about _SET and _UNSET in "Example 4" 08:54:09 Title: ports(7) 08:56:44 yeah, that's supported. /usr/ports/bsd.options.mk explicitly shows that. I now have to figure out why those options are not applied by make 08:57:18 michelem: when you look at the www/nginx/Makefile 08:57:36 the MAIL_GROUP is implied if any option is still set 09:00:14 that's no problem, the examples above were random. I'm actually testing with MODSECURITY3 , which is independent of all other options 09:00:24 you've been great meena, thank you. 09:00:39 I wonder if you could www_nginx_UNSET=MAILGRP 09:00:44 especially given the low-coffee mode 09:03:58 the fact that BATCH=yes still gets you prompts sounds like something is b0rked 09:04:15 to me, anyway, maybe the people in #bsdports on EFNet know better. 09:04:31 I found the issue 09:05:59 BATCH=y still requiring interaction is still there. I also see it as a bug, but the "config" target might be considered as interactive-only. I see it as a bug because "config" is actually 2 steps: 1) selection 2) generation of options file. BATCH=y should apply to the second step. 09:06:40 the issue with make.conf options not being honored: if there's an existing options file, that overrides any options from make.conf. You need to rmconfig it in order to have make.conf options apply. 09:07:38 That's a bit of a bitch, because if ansible scripts generate make.conf options, and a year later the user manually plays with the port and leaves the options behind, future builds will invisibly ignore the make.conf options. 09:08:00 acceptable though. I'll simply change "make package" to "make rmconfig package" 09:25:20 michelem: so all is well? it builds the way you need it to? 09:25:37 also, have you considered poudriere instead of ansible for building stuff? 09:27:20 ansible is for general deployment of the larger system. Installing application is only a step. Ports are an unfortunate necessity because packages don't include the desired options. 09:28:17 For compiling ports I considered poudriere for a second, but it didn't seem to me to bring enough value for the cost of an extra dependency. You might be able to persuade me otherwise 09:28:29 * meena points at Apache httpd which has a mod_security module you can install, and also mod_md… 09:29:14 michelem: you'd be producing your own repo, so building and configuring ports would be decoupled from installing them 09:33:36 maybe people who actually use poudriere for ports have better arguments 09:34:05 Would I be able to remove complexity? The current process is: 1) add a bunch of _SET and _UNSET options to /etc/make.conf ; 2) run "BATCH=y make rmconfig package" 09:34:08 I just bully porters into making my options default, and use poudriere only for: https://alpha.pkgbase.live/ 09:34:09 Title: Unofficial FreeBSD pkgbase repository 09:34:44 poudriere seems great for port testing. It compiles into own jails so you can easily fake different environments, OS versions etc 09:34:52 https://man.freebsd.org/poudriere(8)#CUSTOMIZATION 09:34:53 Title: poudriere(8) 09:35:11 ah ah ah ah 09:41:50 it is heartbreaking that FreeBSD does not support NVIDIA Cuda 09:42:02 (or the other way around) 13:21:40 which is? 13:22:08 ah, gpu hw accel library 13:22:44 sounds proprietary to me. no open standard, why would they? 13:36:34 it is rather nvidia does not provide CUDA in their driver for FreeBSD ( an opposite ) 13:36:59 i know there are some workarounds, using linux compat 13:37:55 https://forums.freebsd.org/threads/can-cuda-be-installed-on-freebsd-now.85879/ 13:37:56 Title: Can CUDA be installed on FreeBSD now ? | The FreeBSD Forums 13:38:07 rather, messy thread 13:40:40 meena: looks like you've had some responses to the infiniband thing? 14:32:18 debdrup: yes, unfortunately the second response invalidated my hypothesis that all i need is ifconfig -a 14:33:39 hmm 14:34:05 my graphics module is causing a panic... 14:34:53 amdgpu, latest git pull from kernel sources 14:35:24 i upgraded my system, amdgpu broke, tried pulling in latest kernel sources... still broken 14:35:49 am i misunderstanding something? 14:36:00 i did `make kernel 14:36:38 then ran `make reinstall' on /usr/ports/graphics/gpu-drm-amdgpu... or such 14:38:16 i dont think its a bug, i think it's some mismatch that i'm not understanding 15:23:08 nekobit: did you run 'make distclean && make clean' before running 'make' in graphics/gpu-drm-amdgpu ? 15:23:39 also did you refresh your ports tree ? 15:23:41 f451: i did not, ill try that later 15:23:42 i did 15:26:12 after running make i normally run make deinstall reinstall in that kind of situation 15:47:03 What's the new name of the IRC social channel? I see #Not-##FreeBSD isn't really in use anymore. 15:47:43 Dereckson: You're in it. 15:53:00 Interesting pkg behavior: https://bsd.to/CvFV 15:53:01 Title: dpaste/CvFV (Bash) 16:10:19 vkarlsen: sich part seems unusual? 17:40:06 why is Y the default option for you? (or is it the default option when pkg upgrades pkg and I just never noticed?) 17:52:25 Hey, so for years I've been getting email updates from the FreeBSD bugzilla. Footer always says I'm getting the email because "I'm the owner" which simply isn't true. Is there anyone I can contact to help fix this? 17:57:04 Maybe I can just use this: https://lists.freebsd.org/ 17:57:06 Title: FreeBSD Mailing lists 17:58:37 Wouldn't you just edit the bugs in Bugzilla? (Maybe I don't know) 18:21:41 ganthore: #gitcvt on EFnet 18:22:02 xtile: I'm not manually editing hundreds of bugs. :-) 18:22:06 ganthore: but you can also open an issue in bugzilla 18:22:54 aha 18:23:39 It feels like I get an update for every single thing 18:23:59 how many bugs did you submit? 18:24:00 My gmail inbox got flooded so bad I finally ran out of storage space =D 18:24:12 None 18:24:16 yeah, i would goto #gitcvt and ask for help 18:25:11 I thought gmail gives you infinite storage 18:25:27 no, just 15 GB 18:25:33 https://imgur.com/a/dVi4AgN 18:25:34 Title: Imgur: The magic of the Internet 18:25:47 But yeah, it's kinda insane. :-) 18:25:55 unlimited is long past 18:26:13 time for a gmail filter 18:26:31 rtprio: that's my "to trash" filter. 18:26:44 * meena deleted her Gmail account fifteen? years ago 18:27:30 Anyway, it's mostly my fault for not really addressing this way back whenever it first started happening. 18:28:00 I was active in the community back around 2011. 18:29:35 meena: thanks for the suggestion, I'll give that a shot. 18:39:38 "Confirm unsubscribe from freebsd-ports-bugs⊙Fo" 18:39:43 Maybe that fixed it. 18:41:27 ganthore: sounds much more plausible than you being accidentally maintainer of hundreds of ports and these ports not being marked as abandoned by their maintainer 18:42:27 I know right? 19:03:12 ganthore: check the headers of the mail addresses 19:03:49 s/\ addresse// 19:05:31 All of the FreeBSD mailing lists contains the List- headers that define both the ID as well as the subscription and unsubscription emails. 19:06:04 Meanwhile, Bugzilla emails contains the X-Bugzilla- items 19:07:12 They're there not just because it helps get legitimate automated mail (as in, something the user subscribed to) past spam filters, but also because it makes it super easy to sort into folders. 19:07:19 s/folders/directories/ 19:54:01 grreetings 20:33:00 welcome otakon 20:40:24 hrm 22:54:21 Hello. Please tell me, when installing the program through the pkg package manager, after the installation is completed, various information is displayed, such as recommendations and mandatory actions for configuration. How can you see all the information after installing the package, if it does not interfere with one screen? 23:00:49 pkg info -D packagename 23:10:31 V_PauAmma_V: Thanks for your reply. I just looked at the output of this command. I have situations where when installing one package, many other packages are installed along with this package as dependencies that may have their own message after installing these packages. I'll think about how I can view these messages. 23:19:23 i just realized, i could totally deduce this from reading the source code: https://lists.freebsd.org/archives/freebsd-infiniband/2023-February/000010.html 23:19:24 Title: RE: Soliciting infiniband ifconfig output 23:19:45 but sometimes it's easier to look at real output… 23:20:58 (rather than try to use brain to imagine output) 23:20:59 can I make buildworld on a Linux + GNU system? 23:21:43 first line of attack was procuring bmake, but then I run into "awk: cmd. line:1: warning: regexp escape sequence `\#' is not a known regexp operator" 23:22:11 don't know how deep that compatibility rabbit hole goes, so wanted to check first 23:22:12 aportnoy: you need another awk then… 23:22:24 aportnoy: have you looked at our .github/actions tho? 23:22:30 they build on linux and mac 23:22:41 ah thank you for the pointer! will check that out 23:23:27 https://github.com/freebsd/freebsd-src/blob/main/.github/workflows/cross-bootstrap-tools.yml#L45 23:23:28 Title: freebsd-src/cross-bootstrap-tools.yml at main · freebsd/freebsd-src · GitHub 23:24:37 one of the best things of having CI is that you can see how the sausage is made 23:24:44 (it's usually not pretty) 23:25:27 hrm… I'm not actually seeing a buildworld 23:25:31 how are these template parameters filled out? like "${{ matrix.pkgs }}" 23:26:30 aportnoy: there's a parameter that's called matrix: further up, it defines several target platforms and their dependency packages 23:26:55 gotcha I see it's right there 23:27:25 but, again, I'm not sure you'll be able to build world. 23:27:34 I thought the CHERI people do, but I don't know! 23:28:09 either way, tools/build/make.py will get you further than bare (b)make 23:29:36 I see, thank you. Will give that a try. 23:31:24 https://github.com/freebsd/freebsd-src/blob/main/tools/build/make.py ← reads like it should buildworld on Linux and MacOS 23:31:25 Title: freebsd-src/make.py at main · freebsd/freebsd-src · GitHub 23:31:49 https://wiki.freebsd.org/BuildingOnNonFreeBSD this should be fairly up-to-date, as CheriBSD is built on non-FreeBSD (it may have changed) 23:31:50 Title: BuildingOnNonFreeBSD - FreeBSD Wiki 23:37:19 if i could get poudriere running on Linux, I could totally build pkgbase.live on Linux! 23:37:28 (but then I'd have to run linux, and run things on Linux…) 23:37:42 Yeah, that seems like the opposite of what one might want.