00:11:01 Twenty-twenty-three is on. 00:29:04 its not fully on the air yet 00:59:37 Did you all watch Dinner For One as you should on New Years Eve? 01:00:29 I watched it for the first time, today. It was alright in a good way! Not the greatest, but still funny. 01:01:01 By the time it is on you should be half drunk already :-) 02:32:26 anyone know what the general steps one should take to run a linux (arm64) binary on freebsd (aarch64)? i added linux_enable="YES" to rc.conf, and done service linux start, and if i try to start the program it just sits at 100% cpu in state 'futex' 02:43:21 wcarson: FWIW, take something simple like "cat" so you've got a nice base test case. 02:43:49 wcarson: Next, https://wiki.freebsd.org/LinuxJails is very recent. 02:43:50 Title: LinuxJails - FreeBSD Wiki 02:44:34 hmm, thank you for that wiki article. it's always a challenge for me to find the most accurate/recent information. looks like i need 14-current and i'm on 13.1-release 02:45:27 i also can't kill the process and have to force power off :/ 02:46:05 i wish silicondust would just release hdhomerun_record for freebsd/aarch64. they release amd64, and for linux x86_64/arm64.. oh well. 02:56:46 oh interesting 02:56:49 it's failing with this linux: jid 0 pid 1103 (hdhomerun_record_ar): unsupported socket(AF_NETLINK, 3, NETLINK_ROUTE) 02:57:04 it's repeating that as fas as it possibly can 02:58:03 https://reviews.freebsd.org/rG7e5bf68495cc0a8c9793a338a8a02009a7f6dbb6 02:58:04 Title: rG7e5bf68495cc 02:58:07 nice, landed with 14.0! 02:58:16 dare i update.. 02:59:02 Do ya feel lucky, wcarson? Do ya? 02:59:18 i may as well : ) 03:00:21 because if it works, it means i don't need to spin up another system :) 03:42:54 Happy New Year to all who are in right time zone. (Yeah, still 2022 here, not that I am in any hurry) 05:16:40 /wc 06:11:22 w0rd! 08:45:12 how can I tell if I need to reboot my system after doing a 'freebsd-update fetch install' ? 08:51:34 if `freebsd-version -k` and `uname -r` give different outputs, then you need to reboot 08:51:58 thank la_mettrie 10:04:56 I would like to dual-boot freebsd with linux. I have made a separate root partition, but would like to share the boot partition (efi). Will the freebsd installer stomp on the existing boot files? If so, how can I tell it to not do that? 10:25:47 moon-child: IIRC the installer can use manually created partitions 10:26:00 but for safe keeping, make a copy of your EFI partition to be sure. 10:26:14 but will it stomp on the data in the partition? 10:27:14 it will write what it needs, no idea if that conflicts with what your linux needs 10:43:54 moon-child: There's a shortish article on the FreeBSD wiki about this that might possibly be somewhat helpful: https://wiki.freebsd.org/Laptops/Lenovo_Yoga_3_14/DualBoot 10:43:55 Title: Laptops/Lenovo_Yoga_3_14/DualBoot - FreeBSD Wiki 10:44:31 I wonder though, why it involves resizing an ext4-formatted partition. 10:45:05 One could leave space for the FreeBSD installation when installing Linux. 10:45:58 that seems to recommend using a separate boot partition for each os. Something I would like to avoid 10:46:20 Oh, I see. 10:46:59 The FreeBSD Handbook doesn't seem to cover this either. I just had a look. 10:54:30 at a guess, it will overwrite bootx64.efi. So if I rename refind bootx64.efi to something else and then play efitoobmgr dance, it should work fine? 10:56:04 There's probably hundreds of ways you could dual-boot FreeBSD with some other OS, and none are "the right way" - so it's not e xactly something that the handbook can cover. 10:59:04 Just using FreeBSDs standard boot loader, there's something like 10 variations. 10:59:53 moon-child: its going to be quicker to test this than guess... FreeBSD has had a /boot/efi/EFI/FreeBSD/.... section but you are probably correct that it will over-write it 11:00:15 the default bootx64.efi file 11:00:40 I highly recommend adding refind into the mix for dual booting, it makes life much simpler 11:01:08 I am using refind 11:01:11 nice 11:03:33 here's whats in my efi partition, filtered for readability https://www.irccloud.com/pastebin/cObkFV7X/efi.partition 11:03:34 Title: Snippet | IRCCloud 11:04:20 with a bunch of obvious stanzas for refind.conf 11:04:33 menuentry "FreeBSD current" { \n loader /EFI/FreeBSD/loader.efi \n } 11:04:51 > debdrup: 11:04:51 > 2023-01-01 10:59 (GMT) 11:04:51 > Just using FreeBSDs standard boot loader, there's something like 10 variations. 11:04:51 it can boot linux? 11:05:08 oh no, that formatted horribly, i'm so sorry 11:06:07 If it's new enough, yes: https://cgit.freebsd.org/src/log/?qt=grep&q=kboot 11:06:11 Title: src - FreeBSD source tree 11:08:27 very cool 11:12:50 dch: thanks 11:13:59 is this mounted anywhere, or do I have to tell the installer about it some other way? 11:14:09 (esp doesn't seem to be mounted by default on my laptop) 11:16:01 moon-child: I have this `/dev/gpt/efiboot0 /boot/efi msdosfs rw,late 0 0` 11:16:06 in fstab 11:16:52 my system is so far off standard I assume its added in installer but I can't be sure anymore 11:17:14 and this is a 14.x too 11:20:32 Under normal circumstances you shouldn't need to mount the ESP. 11:21:00 /boot/efi isn't a standard mountpoint by the installer as far as I know. 11:21:54 it is now 11:22:28 hm, I have a line like that too and I'm sure I didn't add it, but why would you mount it writeable by default? 11:24:37 https://github.com/freebsd/freebsd-src/commit/0b7472b3d8d2f1e90fade5236b44fd98d8e396c2 11:24:39 Title: Mount the EFI system partition (ESP) on newly-installed systems. · freebsd/freebsd-src@0b7472b · GitHub 11:26:54 nimaje: so the efi loader can be updated during freebsd-update I assume? 11:28:16 yuripv: huh. 11:30:56 oop, how does manual/shell partitioning work? Instructions said to mount the new root fs in /mnt, and put an fstab in /tmp/bsdinstall_etc/fstab; I did that, resumed install, and got: 'eError while extracting base.txz: Failed to open 'Error: Expected no more than 3 tokens for --msgbox, have 9. Use --help to list options./base.txz' 11:31:02 ' 11:35:03 seems to go away when I don't ask it for debug syms. Guess I can install those after the fact 11:35:04 shouldn't it remount it then to have it only writeable when needed? 16:42:30 is there an automated way to update leap-seconds.list? 17:19:31 moon-child: odd. that sounds like a bug 19:03:24 Hi, can it be that FreeBSD mpr driver supports Broadcom 9341-8i HBA despite the manpage not mention it? 19:03:35 (at last its also a broadcom card) 19:28:05 megaTherion: if a man page lies about driver support, that's either a bug, or, no, there's no either/or, it's just a bug 19:29:55 meena: sometimes manpages aren't all up to date, I'd not consider this a lie 19:30:48 You can also make certain new hardware work by accident by coding support for a similar (older) one. 20:24:45 On Freebsd 13, running /usr/bin/openssl and typing version returns 1.1.1o. pkg info | grep openssl is listing 1.1.1s. What is the correct way to indentify the version in use? 20:26:20 Ah nevermind... Currently one is installed in /usr/local.... 20:29:06 the /usr/bin/openssl one comes from the base system, as that needs openssl sometimes (e.g. fetch, ...), so openssl comes bundled with freebsd, but you can install some version via pkg too (same with llvm/clang) 20:30:03 I see you answered your own question, so I'll just mention that "pkg info openssl" would work as well. 20:32:31 if you use PkgBase, you'll get two OpenSSL packages in that pkg info | grep statement 20:33:17 megaTherion: a docs bug is still a bug 20:35:26 bug and outdated yes, but I too wouldn't call it a lie 20:52:09 I found "pkg audit openssl-1.1.1s" but the output doesn't make much sense to me. I ran an pkg audit -F first but it is still reporting vulnerabilies that are already patched in 1.1.1s ex. CVE-2022-0778. 20:52:54 perhaps having two different versions installed gets audit confused? 21:02:55 i don't think that's what it goes on 21:28:34 Hmm it appears you cannot ask unpatched vulnerabilities in a particular package only the whole system with an pkg audit -F. 23:31:35 Even if one does not make own changes (or barely any), running "git repack -d && git gc --prune --aggressive" in /usr/{src,ports}, once in a blue moon reclaims (significant enough in my case) disk space. Note that "git-gc" in /usr/src could take some noticeable time. 23:50:08 Is it possible to load a 12.2 kernel module on 12.3? 23:53:56 If all the other related dependencies are fulfilled, perhaps could specify the file to load; see the examples in "kldload(8)" manual page