02:36:27 20 04:04:12 Hello community, I need to know for sure if the following options are enough to remove 32bit support for the entire system: In the custom kernel configuration file: nooption COMPAT_FREEBSD32 In the src.conf file: WITHOUT_LIB32=yes This is enough? And if so, will it bring stability problems to the system? 04:06:01 no, it shouldn't bring any stability changes 04:06:11 that looks good enough to me 04:09:18 Ok, thanks for your feedback 06:11:58 i think that some changes should be made to the freebsd news flash rss feed since all the articles link to the same page, the only thing that differs is the first few lines that would be description of the item i guess, so like take the article "New FreeBSD Core Team Elected" for example i think that instead of linking to https://www.freebsd.org/news/newsflash/#2024-06-12:1 it would be better to link to https://lists.freebsd.org/archives/freebsd-ann 06:11:58 nce/2024-June/000136.html 06:11:58 also btw are there any other rss feeds for freebsd? 06:12:20 F, the link got messed up 06:12:34 https://lists.freebsd.org/archives/freebsd-announce/2024-June/000136.html is the correct link 06:38:32 and the security rss feed is messed up even more(https://www.freebsd.org/security/feed.xml) articles on it just contains the proper title but when the article is opened it just contains a link that just redirects to the main page of the rss feed -_- 06:38:32 i would share a video to explain better but idk how to use dcc :/ 11:23:25 clear 11:53:17 https://lists.freebsd.org/archives/freebsd-hackers/2024-July/003391.html huh, didn't realize this had landed 11:54:46 splash(4) on -CURRENT now has png support on UEFI systems 11:57:48 If I understand right, https://cgit.freebsd.org/src/commit/?id=f6e8b0e850 means that it can be the same splash screen from loader(8) 11:59:32 Yeah, that's outright stated in https://cgit.freebsd.org/src/commit/?id=00460cc8c5a 12:01:01 It's a few hundred lines of code, and now we get to make jokes about year of the freebsd desktop 12:06:15 https://cgit.freebsd.org/src/commit/?id=ef2a572bf6bdc say what?! 14:04:44 Gotta say, I am not fond of accelerated FOSS release cycles, and am unhappy FreeBSD is going there with RELEASE. I use "LTS" Linux and FreeBSD on my @work servers to avoid churn. :( I'll live with it because FreeBSD is my favorite OS and I have no choice if I want to keep using FreeBSD ... and I do want to keep using it. Hopefully there won't be much more churn on our FreeBSD RELEASE installs, we'll see. Fingers crossed. :) 14:06:33 unixman_home You can always use the -STABLE branch btw. it also gets features much earlier 14:06:46 I'm planning on moving to -STABLE soon 14:11:47 but you would need to update more often with -STABLE than with -RELEASE, unixman_home wants to update less often 14:14:15 Correct, less churn for OS upgrades is what I want. Plus we have lots of Linux and Windows folk, but only two FreeBSD savvy folk, me and one other, who manage our thousands of VMs and standalone boxes. Anyway, I'm just whining. It may not end up being as awful as I fear. ;) 14:39:13 unixman_home: same for me. I am not complaining, as FreeBSD is completely free and really awesome :) I use it exclusively in our data center to host all kinds of gnu/linux VMs 14:39:44 I do love that the upgrade process is easy and painless, though I do wonder at times how many security vulnerabilities are never detected/fixed tbh 14:45:42 Hmm, the remark that I am using it to run linux VMs (using bhyve) is not meant sarcastically in any way -- it's just that the specific software we need to run requires a specific linux setup 14:46:04 Having freebsd as the host system is wonderful because bhyve is simple enough to give me a chance to actually understand it + zfs 14:46:46 I even run a windows 11 VM on it, was surprised just how stable that (the VM) was 14:53:22 lets seem if the shorter and more predictable release cycle makes it easier for re@ and if it makes stuff easier for users 15:14:15 The one thing I find a bit unsettling tbh is the ABI changes and need to recompile everything 16:03:44 I bought a new threadripper in preparation of that :p 16:05:52 /25/sb end 16:05:56 (woops) 16:06:51 hc: what's your favourite human interface to bhyve? A web page? Or just pure terminal CLI? 16:07:05 I used to use sysutils/cbsd for 10-ish years 16:07:16 now I am transfering via sysutils/vm-bhyve to just base tools 16:07:29 ah shit, that was directed at hc - never mind 17:04:31 Hecate: I'm using the vm from the ports/pks 17:04:43 Hecate: bascially what jbo suggested 17:07:18 vm-bhyve is the one. Works very well and reliably 17:08:29 I moved from the default config of having image files to using zvols, though. In my experience it is safer and also you can pass trim commands through 17:53:47 that is still on my todo list. still just images here 17:53:55 but at least they are _inside_ of a dataset 18:01:54 heh 18:02:05 Actually, it wasn't difficult to transition, I just dd'd it onto the zvol 18:02:42 With images, I had frequent ext4/xfs corruptions inside the containers when rolling back a snapshot made while the VM was running. With zvols no such problems so far 20:02:42 Hecate: i'm also a fan of vm-bhyve