00:24:05 how do you update zfs list ? 00:24:22 i tested out poudriere and now deleted it but zfs list still shows it 00:24:25 oxbar: uh, you don't? 00:24:30 oh 00:24:32 zfs list shows the current system configuration 00:24:59 even though the folder dosen't exist anymore ? 00:26:44 https://dpaste.org/jnFpx 00:27:58 can you demonstrate what you mean by 'the folder doesn't exist anymore'? 00:30:50 it fixed itself thanks.. 00:31:10 oxbar: If Poudriere created a jail (using ZFS) it'll remain even as a dataset even if you remove Poudriere. 00:31:21 ok 00:31:27 You need to delete the jail via Poudriere first and then delete Poudriere. 00:31:37 Or, you can simply destroy the dataset. 00:31:48 yea i destroyed it 00:31:54 -r 00:32:02 That'll do it. 00:37:44 ivy: I committed a fix for one of the IPv6-only wireguard issues you found, sent a patch to wireguard-tools upstream for the other 00:39:28 kevans: 7121e9414f294d116caeadd07ebd969136d3a631? 00:39:52 yeah 00:40:01 that fixes the "I accidentally added an IPv4 address" one 00:41:00 DragonflyBSD takes yet a different approach and they don't actually teardown the peer if you misconfigured something like that 00:41:08 thinking about that one a bit, it would simplify things 00:41:20 their theory is that you're probably just going to try again anyways 00:42:56 that's admittedly pretty hard to argue against. in the off-chance that you aren't, having to remove that peer isn't that bad 00:43:50 ah, you committed the 'bad' version of the PR since no one bothered to make a better one? :-) 00:43:58 no I committed the better version 00:44:18 their patch mostly just applied, only had to tweak it slightly 00:44:41 ah ok 00:44:57 they took away a point of improvement from the exercise, too, so that feels like a win 00:46:32 * ivy provides N cookies to kevans 00:46:50 i suppose i should actually test this as you bothered to commit it 00:50:40 yes, yes you should 00:54:58 god you're SO demanding 00:55:14 first i have to demand you fix all these bugs then you demand i test them, mutter mutter 00:55:25 this world is so unfair gahhh 00:55:46 let's see if LINT-NOINET still builds 01:01:23 the song of freebsd committers https://www.youtube.com/watch?v=1sp33WgVWMA. that thumping sound is all the commits going past 01:05:26 hmm, this is confusing, i did build LINT-NOINET and installed it when i reboot uname -a says: FreeBSD freebsd15.eden.le-fay.org 15.0-CURRENT FreeBSD 15.0-CURRENT #0 lf/dev/traceroute-tests-n276342-a1b43b7bf0fa-dirty: Thu Apr 10 16:50:37 BST 2025 ivy⊙felo:/home/ivy/obj/home/ivy/src/bsd/traceroute-tests/amd64.amd64/sys/GENERIC amd64 01:07:22 okay i see, NOTES has a makeoptions DESTDIR=/tmp 01:07:24 tricksy 01:33:02 kevans: somehow this has completely broken my test host's ipv6 connectivity 01:38:39 Are all patch levels of a given supported release supported thru the whole release cycle or does older patch levels go EOL when the new patch is released? 01:39:05 ex: 14.2-p3. p2 and p1 are considered out of support? 01:40:57 skered: the patches *are* the support for their associated revision. if you're running 14.2, you install 14.2-p1, 14.2-p2 etc. to get the support updates for 14.2 01:41:58 it's not that 14.2-p1 is "out of supported", it's that if you're running 14.2-p1, you're running a supported release but you chose not to install the fixes that were provided as part of that support 01:43:50 I guess it's more of ports question and I'd guess it's the same for releases that just end of life. When can you start to use a given pX fix that doesn't work in I think the recommend time frame is a month or so. 01:44:21 this should not affect ports at all, a release patch should never introduce functional changes 01:44:35 except maybe for things like tzdata updates, but even so 01:44:54 should? maybe do? yes. 01:45:13 if you're maintaining a port, you can't rely on anything except the oldest supported 14.x release because that's what the package builders use 01:45:13 For instance the latest daemon update fixes something that would otherwise be broken. 01:45:37 ivy: I understand that but we're talking patch levels now. 01:46:38 ah, so your question is, you have a port and it requires a daemon fix that was only introduced in an errata? 01:46:44 So if I stop hacking around the fix from p3. Do you just just tell p1/p2 users upgrade 01:46:53 Correct. 01:47:20 i would suggest asking ports@ at this because it's a fairly unusual situation and i don't think there is any official guidance 01:47:37 i suspect the answer might be that you still have to support 14.2-RELEASE though 01:48:06 My gut would say it would follow the same rules as a release going EOL. But we'll see. 01:48:07 (i don't agree with that, i just think a lot of people will say that) 01:48:19 ivy: what 01:48:36 kevans: wait, i am building GENERIC to test 01:49:53 okay it's not your patch that broke it, GENERIC works fine, GENERIC-NOINET (i just made this up) does not have ipv6 working at all 01:50:19 funky 01:50:31 ugh i am going to have to debug this aren't i 01:50:47 yeah, who knows when bz will update his systems next :-p 01:51:07 bz bikeshedded my diff so i hope all his networking stops working 01:51:11 (this is a joke don't @ me) 01:51:52 hah 02:27:49 * ek @'s ivy 14:42:41 Other than editing /etc/fstab entries, what else would I need to do to move a drive from ada3 to ada0 (when I installed, I didn't realize that only ada0 was SATA3, and the other 3 are only SATA2. 14:45:10 break19, I suggest using GPT labels if at all possible as that avoids the kernel selected numbering on the ada# driver. 14:45:27 To answer your question there is nothing more needed to be done. 14:47:08 Humorously I have an ASUS motherboard with HUGE marketing letters for the 6.0Gb/s SATA. But only 2 of the 8 ports are 6 and the others are 3Gbps. Things like that catch everyone. I installed an LSI2008 SAS/SATA HBA card. 14:57:31 rwp: Thanks. And this is a 2013-era Optiplex that's been upgraded to 16G ram and had a handful of drives added. My HBA card is enroute, and I have 3 SAS drives ready to replace three of the 4 drives currently in it. :) 14:59:24 For my home use I have been buying datacenter used SAS drives for cheap. Have yet to have one of those fail on me. Have gotten some good deals. Have gotten some just okay deals. But with zfs+raidz2 plus backup I am feeling pretty good about things. 14:59:48 I bought 3 cheap drives, not noticing they were SAS. But its an excuse to upgrade lol 15:00:20 reminds me I bought a SAS by mistake and do not have a adapter XD 15:01:02 You might find those SAS not faster than SATA but with file system buffer cache and RAM that difference is not signficant in the end. And so far the enterprise SAS drives have been rock solid for me. 15:01:08 thedaemon: Either get a cheap lsi, or send me the drive. :) 15:02:16 rwp: Maybe. But it's a media server for a 3 person household, so speed isn't really a huge deal. 15:03:40 Is pkg frozen? I've not seen any repo updates in several days, and I'm on "latest" ... 15:05:52 there were a/some(?) issue(s) which lead to many fallouts and skipped packages, afaik they should be fixed and only waiting for mirrors to sync the last successful build of the pkg repo 15:06:00 I feel the same way. For the house I don't need the performance level as the 300 person design lab needs. Reliability is what I am needing. 15:06:50 nimaje: hm, alrighty then. 15:09:35 nimaje: is there a list of mirrors that are in/out of sync somewhere? 15:41:56 How does one live in the terminal and finally things like word processing watching movies etc… ? Isn’t that kinda hard ? 15:42:32 break19: yeah it's well out of sync. last build it seems there were lots of failures 15:43:11 https://pkg-status.freebsd.org 15:44:01 only real way around this is to either set up a poudriere instance or upgrade the old way with something like portmaster 15:45:28 break19: last quarterly is more recent than 'latest' 16:13:31 cool 17:09:46 oxbar: TeX and why would you watch a movie in a terminal? but you could use mpvs caca, tct, sixel or kitty video output 17:12:08 word processing part is easy 17:18:52 ivy: never try to run a LINT kernel 17:24:07 goodness gracious, what happened? 18:21:28 kevans: the plot thickens: this is an hn(4) bug. if INET isn't defined, it comes up with a random non-default mac address that doesn't work; resetting it to the hardware address fixes it 18:31:27 no, actually it's an ifconfig bug. it seems to auto-detect an iP address as a MAC address if INET isn't enabled 19:50:33 ivy: huh, that's wild 19:51:55 i guess no one noticed because usually you wouldn't try to do this, and also it only works with certain IP addresses and not others 19:52:23 hopefully easy to fix, but i got distracted and will have a proper look later (the basic problem is that ifconfig defaults to "inet", unless INET isn't in the kernel, then it defaults to "link") 19:53:14 big fan of being explicit 19:53:22 interesting story, thanks for sharing ivy 19:53:46 * mzar fires up building machine to build stable/14 without INET 19:53:48 kevans: unfortunately there's a bit comment in the source about why we can't just force people to write "inet" all the time :-d 19:53:55 s/bit/big 19:54:00 big fan of deleting comments I don't agree with =-D 19:54:34 oh that's hilarious 19:54:34 well, part of is you'd now have to say 'ifconfig hn0 link up' which i could see being contentious 20:16:42 * mzar begins building with WITHOUT_INET and nooptions INET set 20:36:21 Can a pr be opened up again ? 20:37:10 woohoo! go based packages have returned to the amd64 repo 20:37:28 oxbar: yes, if there's a reason for it, but i think only triagers and admins can do that. what's the PR? 20:37:53 I'm trying to identify which slot my drive is in. I know it is "da1 at mrsas0 bus 1 scbus1 target 2 lun 0" - I'm going to guess that translates to "Physical Disk 0:1:2" In my Dell R730. I tried sesutil map, but that's useless for this (https://dpaste.org/tkjvd). 20:39:54 is choosing which disk to boot off of, something you set in hardware or in freebsd itself? on macos, it's entirely a software setting 20:40:58 ivy: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283956 20:41:20 The issue wasn't resolved the guy just installed another os and that was it 20:41:37 GoSox: the system firmware (legacy BIOS or UEFI) chooses the disk used to start the boot processes. once it's loaded the boot loader, the boot loader decides what to do next - e.g. for FreeBSD it looks at a hardcoded root path, or for a bootable zfs pool 20:45:48 oxbar: do you also have the same problem? i don't want to reopen it unless someone else is still affected (if so, please put a comment on the bug) 20:46:35 ivy: yes i have the same problem.. so does this dev https://forums.freebsd.org/threads/audio-card-intel-tiger-lake.96345/page-2#post-685550 he said he just didn't try to fix it 20:51:29 GoSox: Is this a general question, or is there a problem you are trying to solve? 20:54:24 no i'm just wondering how it will work when i actually set up my bsd server. on my previous mac servers, i'd just make a primary boot drive, and a backup boot drive. Since its all set in software, i can screen share in, tell it to boot off the backup drive, restart, then reconnect to screen sharing on the backup drive and run repair utilities as needed on the primary drive 20:54:38 i'm wondering how a process like that would work on a non mac 20:55:44 GoSox: what macOS is doing is almost certainly just changing firmware settings. on freebsd you may be able to do this with efibootmgr(8), although PC firmware is of variable quality so it may or may not work 20:55:46 there is efibootmgr if you want to configure the uefi boot manager of your system from within freebsd 20:56:05 (it *should* work on most modern, average quality EFI firmware) 20:57:57 i'm eying an old surplus HP proliant server 20:58:23 but i haven't bought anything yet, i'm still working on setting up the basic server i need on a test machine 20:58:35 and i never have time to work on that so i'm making basically no progress :/ 22:58:17 oxbar: did you want that bug reopened? if you can just put a comment on it like "i am also seeing this" it makes it more obvious what's going on rather than just reopening random bugs :-) 23:22:49 ivy: I will when I get home.. stopped at a red light lol 23:23:06 oh okay :-) no rush just ping me here (unless someone else gets to it first) 23:23:32 i'm not actually entirely certain you can't just reopen it yourself but i don't *think* normal users can do that 23:30:10 Ok 23:32:33 ivy: you'll be able to with cluster login 23:32:56 also killing spammer comments/accounts 23:32:57 kevans: i already could as i have magical bugmeister role, i was just wondering if oxbar could do it themselves 23:33:02 ahh 23:33:07 or triager role, whatever it's called 23:33:20 not that one that makes you a bugzilla admin, i don't have that 23:34:13 *nod* 23:37:10 Hi, I'm sending a zfs dataset to an ssh'd server and apparently is sending more data than the origin. zfs list shows 5.6gb, but the progress of the zfs send | zfs recv shows now 6.4gb and counting. Is there a way, on the destination system to see how much data is received? 23:50:14 ivy: I see you on discord 23:50:45 me? on discord? this is more likely than you think... 23:50:53 Aw 23:50:56 My bad