03:04:03 With the 14.2 Beta in progress, is there a guide online somewhere on "how to help test and give feedback" for a pre-release version? I've used -RELEASE versions for years, but have recently tried out a WiFi chipset driver work in progress on a notbook computer that otherwise wouldn't be supported in 14.1 (it won't be included in 14.2 since it needs more testing, so I would need to figure out how to ensure that the driver can still be used). 03:04:03 For example, I am not sure what I should select for port/package sources when testing a pre-release version. 03:21:53 ah dan, phil left 03:21:56 damn, even 03:23:11 kevans, I didn't have any information. Is there a pointer to documentation that if Phil returns we might point him to? 03:24:00 rwp: not really, but the answer to his specific question is that there's no wrong answer 03:24:35 just using it the way he'd typically use a release and keeping an eye out for abnormal behavior is quite helpful 03:24:50 (and, more importantly, reporting it) 03:25:35 "All OK" reports to a mailing list can also be helpful, to confirm that people are actually testing this stuff, imo. it's easy to think we're just throwing shit out into the void and maybe someone eventually uses it 03:25:35 Phil's specific question was what ports/pkgs sources should he be using when testing a pre-release version. 03:25:44 "the usual" 03:26:40 So for a typical RELEASE user the installer sets things up for quarterly. I'll say quarterly would be the default. And many people do switch pkgs to current. And that either would be useful. 03:26:53 yes, exactly 03:27:02 and if you build your own ports, that's also useful 03:27:41 Awesome! Thanks for getting me in the groove. If I see Phil I will pass it along. And I am sure that the others reading this will now have the same information and can pass it along too. 03:28:03 there's really no wrong answer here. using latest or quarterly prebuilt from the cluster puts ABI commpatibility to the test, building your own ports can surface new build failures that maybe we didn't notice from changes in libs/headers, etc 03:28:07 thanks 03:30:27 worst case scenario, maybe he'll come back for BSDCan '25 and I can harass him there about it 03:32:02 JFTR but I am seriously considering attending BSDCan 2025. It would be fun to meet people. I will have a bag of questions that I will be ambushing people with about FreeBSD. :-) 03:32:16 it's a great experience, I highly recommend it 03:45:17 I want to attend it someday. Maybe next year as I've finally got a sort of mask I trust a ton. 06:03:24 I think I've set recordsize too high for /boot/ because now I have the 'cant read MOS' error when loading bootloader. D'oh. I'm fixing it live but wow I wish I was prevented from doing that or at least warned 06:04:28 -> tried 4M on / 14:14:17 Hi, is there a way to see at what percentage is the file which is being copied / rsynced / ...? 14:14:58 lsof has the file pointer only but will be nicer to see a percentage of where is file is being read 14:15:27 --progress show progress during transfer 14:15:48 nerozero: that's from man rsync 14:16:05 nah 14:16:17 nerozero: Yes, yes, it is. 14:16:27 not possible, it is part of the script which is run by the cron ... 14:16:40 https://man.freebsd.org/cgi/man.cgi?query=rsync&manpath=FreeBSD+8.0-RELEASE+and+Ports 14:16:59 Well, now you're introducing new variables. 14:17:01 dvl, I know that rsync has that option 14:18:42 say a backup process is running for > 10h ( couple of terabytes is synced remotely ), .... 14:19:13 just get the file read offset and divide over filesize ... 14:20:47 ok will write my own script 14:21:24 how about rsync with progress writing a log file? 14:22:40 the look it is already running ... 14:24:18 and also it is useful to find position at any file being read on the fly regardless of program .. I wonder there is no dedicated program available 14:26:42 SIGINFO like with any well behaved program ^T from terminal 14:27:04 nah, I will make it better :D 14:27:19 lsof + awk + stat + grep ... 14:27:26 gimme couple of minutes... 14:29:41 maybe you can use dtrace for cases where you can't read stderr of the program you are interessted in 14:32:02 bsd.to is dead ? 14:34:16 WTF dpaste is broken, bsd.to is dead ... 14:34:27 0x0.st 14:35:10 AI has eliminated all the freedom already ... 14:35:13 sad... 14:36:53 https://dpaste.org/3E1ou 14:37:13 publishing script was harder than making it ... we all doomed .... :( 14:37:43 regardless, thanks for sharing 14:38:09 pass a greping arg and see file read progress in percent 14:38:26 fire with gnu-watch and see it in real time 14:38:34 multiple matches possible 14:39:58 HAHA WORKING ! 22:12:47 Curious, anyone else running FreeBSD on a Framework laptop? 22:17:58 Anybody else running FreeBSD on a Framework Laptop? (Sorry if this is a repeat, I had some connection issues) 22:26:21 what is Framework Laptop? 22:28:51 mzar: https://frame.work/ 22:28:54 It's a laptop from a relatively new company that is made to be easy to repair and upgrade. 22:28:59 Modular. 22:31:50 OK, thanks 22:55:52 there are like 8 different laptops from that manufacturer 23:33:55 I think this port is also broken on 13: 484533 -rw-r--r-- 3 root wheel 4.9G Nov 2 19:32 /mnt/data/logs/bulk/133amd64/2024-10-30_18h23m55s/logs/pspp-2.0.1.log 23:34:53 Repeats forever: "doc/pspp-figures/chisquare.png-67522086: error while writing to output stream" 23:52:08 pineheap: just got a 13 amd 7840U working with 15