00:01:57 i got freebsd running on a server and it's way hotter than when i had linux on it. my powerd_flags are -a hiadaptive. is that right or should i change it? 00:01:57 it's a dell r430 fwiw 00:29:22 checked with coretemp and it's all in normal ranges so nvm i guess 06:34:03 phryk: sorry I didn't see your message, hm, I didn't make the port but doesn't gstat_exporter_flags="-l 127.0.0.1" or whatever do something? 06:47:19 phryk: otherwise let me know and I will add a patch to the port rc script because that should of course be possible :) 09:11:18 I have a question about grep, not sure if anyone here will be able to help but I may as well ask. a file which I have been given to grep has special character for bold (^H) how do I get grep to ignore these and match against the word only? 09:14:54 can those appeare inside the substring you are searching for? how about removing them with tr -d? 09:30:08 tykling: thanks, will test later today and tell you whether it worked via query. 09:49:55 polarian: (maybe try #bash or #zsh etc. for that question?) 09:50:46 la_mettrie: I am not using bash though :P 09:51:16 nimaje: not meant to, #linux has helped 09:51:24 I am sufficiently convinced this is the lecturers mistake and not mine 09:52:00 how did you solve it? 10:04:27 I haven't asked 10:04:42 I just realised that one of my modules had been voided... 12 weeks of work has been thrown out and I have failed the module 10:04:47 without reason 10:05:37 I got a feeling its an accusation of cheating, I aced the first coursework (only 100%) but then submitted a half arsed attempt for the second one due to mental health issues, but anyways thats OT. 10:06:48 ah, then I misunderstood your '#linux has helped' as being '[…] and with that help I have solved it' 10:07:43 oh right sorry I missed the messages from p hryk 10:07:53 sorrry 10:08:21 wait I am so confused 10:08:33 oh wait this is likely a panic attack 10:09:55 Hello. I have dumped the hard drive of a physical OpenBSD machine using ddrescue. Now i want to use this image as a bhyve drive so I can create a VM from this disk image. i tried using vm-bhyve but it stucks in the uefi shell. But if i pass it the ahci-hd parameter itwillsimply not boot. Here I attatch the vm-bhyve configuration file and the output log: https://meth.cat/file/173823161586.txt 10:09:57 https://meth.cat/file/173823164492.txt 10:42:25 whats the difference OPTIONS_RADIO vs OPTIONS_SINGLE? 10:42:32 they look the same 10:46:43 With SINGLE you have to choose one, with radio you have the option of not choosing any. I think. 10:47:27 single does the same too 10:48:12 radio archivers/libarchive, single lang/go-devel 10:48:22 space/space 10:48:28 turns both off 10:49:26 ah i see now, Config is invalid. Re-edit? [Y/n], my bad 10:55:58 BdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x3,0x0): Not Found says now 11:11:33 I'd like to see the discussions that ended with this being classified as an errata and not a security advisory: https://www.freebsd.org/security/advisories/FreeBSD-EN-25:02.audit.asc 11:12:57 I sort of assume a "root can do anything anyway" line of reasoning, but when it comes to auditing that is only partially true.. 11:47:41 hi there! i was wondering if somebody could help me to create a fat32 partition on a 1G device? i created a gpt partition table: no problem. i added a partition for fat with: gpart add -t ms-basic-data /dev/da1 ... however: as soon as i try to format that partition i get an error that i need at least 65525 clusters. 11:49:03 gpart show -p da1 givess me "40 2097072 da1p1 ms-basic-data (1.0G)" 11:49:39 unfortunately i dont get the problem here: 1gb should be big enough for a fat32 filesystem, right? 12:07:30 I think newfs_msdosfs needs some options there, to force sectors per cluster to be smaller 12:10:47 Try passing -c ? 12:15:17 So EDK2 can only boot GPT tables? This is garbage 12:15:25 Anyways, how can i convert a disk image from MBR to GPT? 13:14:34 <[tj]> Ltning: does something being an EN rather than an SA make it harder for you to update machines? 13:15:10 It's more about whether we'd be aware of it. We subscribe to announcements on -security; erratas are more randomly picked up. 13:15:48 I could invent something about if it's not an SA we don't get approval for touching prod, but that would - for the time being - be bs. :) 13:16:02 (but it may apply in the future, and very possibly to others) 13:16:42 <[tj]> you could subscribe to errata-notices⊙fo 13:17:41 <[tj]> Ltning: I think it is worth asking secteam directly about this one 13:18:23 Yeah, some of us do. But not feeding into our ticketing system. But that's a "us"-problem, obviously. 13:19:05 But yeah, I'll ask the secteam after I've looked around a bit to see if I find some guidelines they follow on how to classify. 14:01:43 hello, is there a way to change the BootCurrent from /EFI/freebsd/loader.efi to /EFI/BOOT/BOOTX64.EFI ? 14:02:31 I updated /EFI/BOOT/BOOTX64.EFI on each ESP partition, did a zpool upgrade ... but I forgot to update /EFI/freebsd/loader.efi .. is there any way to fix this? 14:02:51 (my system is now unbootable) 14:03:08 hmm, any chance you have a UEFI shell baked into the firmware? 14:03:41 mmh this is a remote Hetzner box .. I just asked for a KVM but didn't have it yet 14:03:46 or is there a non-FreeBSD option if you drop into a firmware boot menu? 14:03:48 oh 14:03:58 that makes it a lot more awkward 14:04:04 :( 14:04:06 oh, wait. it's broken after loader 14:04:27 but I guess you don't have a serial console to interact with loader? loader could chainload bootx64.efi if you can access it 14:04:34 Using portmaster, if I am correctly building openssh-portable with libressl should I expect the output of /usr/local/bin/ssh -V to say something other than OpenSSH_9.9p1, OpenSSL 3.0.15 3 Sep 2024? 14:04:44 kevans: I'm waiting for the KVM .. 14:05:02 kevans: I thought only /EFI/BOOT/BOOTX64.EFI was used 14:05:23 no, bootx64.efi is the removable media fallback; we try to only use the one in our namespace 14:05:46 grrrmrmmlb 14:05:46 :) 14:06:03 once you get into loader, it's the `chain` command 14:06:19 thanks, I'll check 14:06:28 should just be a matter of `lsdev` to identify the name of the ESP, then `chain diskwhatever:/efi/boot/bootx64.efi` or something to that effect 14:06:35 thanks a lot 14:35:30 No SAR on FreeBSD 14 huh? 14:35:42 whats the best way to do this: sar -n DEV 1 1 | grep eth0 | tail -n 1 | gawk '{print "Down: "$5,"Up: "$6}' 14:35:46 works fine in linux 14:39:26 kevans: I have the EFI shell.. no loader 14:40:23 any idea ..? 14:42:52 psionic: netstat -ibn shows in/out pkts/bytes (assuming, that is what gets printed there) 14:44:33 You mean netstat -I 1 14:47:15 I see it's printing it in bytes/sec any way it can do mbit/sec ? 14:53:53 with the -ibn what you said it is printing the overall incoming outgoing packets on the interface since it was rebooted with the -I int 1 it goes into interactive and printing the bytes/sec this is still better for me 14:54:05 just need it to be non-interactive so i can do something with the output 15:01:18 psionic: -q1 would stop after one line 15:01:34 mage: EFI shell should be able to directly execute \efi\boot\bootx64.efi with the right incantation 15:01:49 fs0:\efi\boot\bootx64.efi maybe, depending on the fs# of the ESP 15:02:25 psionic: and -w1 would wait a second for your /sec window 15:05:08 kevans: ok it works! I have to fs0: and cp the loader.efi 15:05:14 thanks :) 15:07:40 Thanks perfect, just what I needed 15:37:35 any recommended link to master the EFI shell? 18:16:40 mage: no but let me know if you find one :-D 18:17:22 the extent of my knowledge is that I threw out a wild ass guess of just typing a path and it worked, and I've only had to do that ever since