03:34:25 so based on the very small number of examples i could find, i've configured dummynet like this (and it work with with wg): https://www.le-fay.org/tmp/7d/dnctl.txt - but i'm not entirely sure this is correct. what are q65537/q65538? 03:34:36 s/work/does work 08:43:49 pkg(8) can't really count, right? https://x0.at/lFe9.txt we'll be done anytime now, after our 25th 38/38 step... anytime now... 08:59:22 moviuro: there was extensive mail list thread on that 08:59:28 i recall 09:00:13 might as well take it out eh 09:00:34 if you can't predict it 09:02:56 i thought it was fixed, or at least it seemed to stop happening for me at some point 09:08:42 i just had that problem with fetch(1) on certain FTP servers... 09:09:40 limited debugging revealed that it was waiting for the completion of an "on download finished" callback 09:09:58 can't imagine pkg is too different 09:11:16 try running again with -d 09:47:06 I'll do that (add -d) 09:47:14 but nothing left to do now 10:34:34 hello folks! Any idea why "pkg" would claim a package doesn't exist when called with "-r" but succeed for the same package without? https://dpaste.org/sgsCW 11:01:06 ok, found I need to "pkg -r /path/ update -f" there too – the index is also taken from that path, even though the man page only talks about writing into it 13:26:24 Why do people praise FreeBSD for 'stability'? What makes it so much more stable? Genuine non-troll question here, I'm a linux user tinkering with FreeBSD because I enjoy trying new things (how I came to linux years ago). Anyway, I keep reading about how stable and 'rock solid' FreeBSD is, but I don't think I've ever had issues with my linux servers 13:26:24 due to software stability. I am a hobbyist, and to be entirely honest my home power grid (in the US) is flakier than any installation of linux I've ever had. 13:28:18 xgpt: i wouldn't pay any attention to those stereotypes, a lot of them are just 'received wisdom' from 30 years ago that people keep repeating because it's what other people say 13:31:07 there's truth to that actually 13:31:10 Truth. I was reading the handbook and it even had many tropes. To include "it's all open source which makes it so much more tinkerable than 'major commercial operating systems' " (not exact quote) which is true of *all* non-Win non-Mac OS in the home user space at this point. I don't think FreeBSD is more free for a hobbyist than Ubuntu. It's more 13:31:10 free for a company wanting to redistribute without opening it up and sharing because BSDvGPL. (I release stuff under MIT sometimes because that's what's preferred in that community) 13:31:56 ketas: ymmv, i don't personally find freebsd any more (or less) stable than say, RHEL. maybe it depends on your use case, but then it's even more ymmv 13:32:14 I'm just curious what keeps home users using BSD or if I'm just wasting my time. I 10000% see the appeal for commercial entities that may not want to contribute back the things that make their own products stand out, or risk infecting/tainting their own stuff with GPL licensing 13:32:34 (actually i find it a bit less stable but that's because i run 15.0 everywhere :-) so that's not a fair comparison) 13:32:56 I guess my home use case has been running various docker containers on an intel NUC and doing some storage stuff. I'm thinking about home-building a NAS and might want to do ZFS 13:33:26 ivy , that's a deeply unfair comparison. That's like saying debian is unstable because you run Sid. they're both by definition beta 13:33:37 that's literally what i just said? 13:33:48 I was just agreeing with you ivy 13:34:07 personally i prefer freebsd because it's smaller and simpler, both software-wise and when it comes to community 13:34:12 sorry I see my tone might have been confrontational, it was not. was restating to agree not disagree 13:34:34 i've used alpine linux for the same reason, but am thinking about transitioning those alpine servers to freebsd 13:34:34 (also because i've always used BSD of some sort, so there's a bit of inertia there too) 13:34:55 Some of it comes from principle of least astonishment (POLA), stuff shouldn't change for no reason and even if stuff internally changes the interfaces should only change if it is nessesary, not just because some implementation detail changed 13:34:56 the just getting things done approach is much higher in linux 13:35:02 I saw a video of freebsd being updated to the then-current from some ancient version on purpose for the sake of it 13:35:16 like, if i find a bug in freebsd or something i want to improve, i know where the source code is (because it's all in the same repository) and it's easy to edit and submit fixes, and to get help from developers if it's something i can't fix myself 13:35:19 that affects things 13:35:38 agreed. I chose alpine for some cloud hosted VMs and think I want to transition to either openbsd or freebsd for the same reason I'm running Arch linux at home 13:36:03 Arch is a POLA type distro I think, they really value not randomly breaking stuff without announcing it I think. Or maybe I've just been lucky? 13:36:28 But I'd like to transition to an even-more-stable rolling-ish distro? Something I can just install once, and know I can always upgrade? 13:36:41 xgpt: with freebsd you get a stable base and a "rolling release" for everything you get from ports. that's what I like about it and it makes sure my system is always stable 13:36:43 like if I'm running 13.x I can doing point releases all the way up to 14.2 right? 13:37:05 sorry, point release upgrades 13:37:21 getz: wait until base starts rolling as well? 13:37:22 :p 13:37:24 yeah you can skip releases, openbsd requires you to go 7.2->7.3->7.4 and so on 13:37:34 ketas: no did i say that? :o 13:37:36 in theory you can upgrade from any supported release to the current release, but there's a catch with 13.x specifically which is that you have to be on the latest patch first to get a freebsd-update bug fix 13:37:45 but aside from that there's no need to upgrade one minor release at a time 13:39:22 i'm afraid eventually fbsd could be as bad as linux distros maybe 13:39:32 but who knows 13:39:46 that wouldnt make much sense 13:39:56 Why do you think it would be getting worse ketas ? Also which BSD is most likely to remain stable through releases? 13:40:11 why? 13:40:17 I'm wondering if I'd be better served switching to rocky linux or freebsd at this point 13:40:28 like if you have to implement things faster 13:40:30 I'm just sick of the idea of having to re-install stuff on servers 13:40:38 we already have a rolling release base, that's basically what -stable is :-) 13:40:41 xgpt: freebsd obviously you're in #freebsd :D 13:40:49 lol, yeah yeah getz lol 13:40:52 who knows what that'll bring 13:41:28 yeah. Guess I'll just have to do more research 13:42:17 stable, old, not much hw support 13:42:40 How long does it take for someone to notice a documentation 'bug' around here? is there a way to champion a cause and just submit a patch for website stuff? 13:42:48 ketas , stable old? 13:42:58 wait, what doesn't have much HW support? 13:43:10 as arch doesn't develop their own base tools, it is hard to have a pola policy, like they switched from net-tools to iproute2 at some point so there wasn't an ifconfig command anymore 13:43:16 i didn't meant that stable 13:43:28 more like stability stable 13:43:40 nimaje , isn't that them just moving to a more systemd based system? 13:44:18 linux is damn confusing i recall 13:44:20 (systemd isn't actually something I personally hate lol) 13:44:42 do you know how to check if nic has link? 13:44:45 :p 13:44:47 ketas , https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285517 << I just submitted this bug because FreeBSD makes a lot of assumed knowledge 13:45:08 I still don't really have an answer to it 13:46:30 hmm 13:46:53 i don't know 13:46:57 what ci is 13:47:09 i wondered myself i recall 16:43:13 kevans: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282605 might be relevant to your interests 16:43:47 * kevans dreads 16:44:05 oh, in response to a problem I'm having, not one that I can fix. phew =D 16:44:07 <[tj]> ivy: it is being worked on 16:44:14 kevans: yeah, for once :-d 16:44:25 [tj]: i know, i was just sending kevans the link since he was asking about it on net@ 16:44:30 <[tj]> ah 16:44:37 <[tj]> too many places to have conversations 16:44:49 I will 100% apply this ASAP 16:45:05 I'm hitting this maybe twice a day, and between this and iwlwifi my laptop is incredibly unpredictable 16:45:32 yesterday I hit this, then iwlwifi decided it'd panic on boot for the next 10 minutes right as I was starting a meeting 16:45:43 <[tj]> iwlwifi might be the trigger 16:46:04 <[tj]> kevans: you can try: https://shop.pimoroni.com/products/adafruit-micro-lipo-usb-liion-lipoly-charger-v1?variant=351777251 16:46:12 <[tj]> you can try: D49259 16:46:48 <[tj]> you might need to assembly a correctly named firmware file though, there is a fw port update in review 16:48:11 mmm 16:49:34 https://reviews.freebsd.org/D49403 perhaps? which seems to have been committed now, good enough for me 16:49:52 <[tj]> yeah that'll do it 16:49:57 <[tj]> bz is quick 16:54:23 I was going to complain about the port not being NO_ARCH, but I guess if there's an actual kmod somewhere in there 16:56:14 <[tj]> it is because of linuxkpi 16:56:33 <[tj]> but there isn't a kmod in this port so we can change that once someone complains 16:56:57 * kevans inhales dramatically as if he's about to complain 16:57:15 <[tj]> please find me a riscv board with working pcie 16:57:45 <[tj]> the deep computing board next to me doesn't have a slot for a wifi 17:24:02 i should learn how this svcj stuff works 17:25:09 tj: I have a JH7110 running main + Phab https://reviews.freebsd.org/D47919 17:25:25 xhci controller @ pcie on this board works 17:25:47 though, I have never plugged in anything into pcie port on my VisionFive 2 19:02:56 Hi, I have a freebsd libvirt vm which I intend to use only as a console (no X or wayland), I have enabled moused, but the mouse cursor is stuck in the middle of the screen, the vm have both a ps/2 mouse and tablet component, any help would be really appreciated 23:19:06 I have a Sapphire Rapids workstation but the bootloader crashes on 14.2, but 15.0-CURRENT snapshots seem to work fine. I guess it's too new hardware. To what extent is the upcoming 14.3 related to the work in that branch? 23:20:04 (14.2-STABLE also exhibits the same problem, however) 23:35:36 why not use 15 23:46:48 that would be a big rabbit hole in terms of binary updates to base and then migrating to RELEASE