00:03:28 yeah, that's a bit of a corner case because we basically never expect someone to have freshly installed a -p* build 00:04:07 why would it be so odd for someone to install an actually up to date build? 00:04:34 because we, for better or worse (no, definitely worse), can't re-roll install media for a release 00:05:11 so even if there's something critical enough that it really should be rolled in to the release media, that just won't happen right now (though re@ could probably figure it out given a bit of time) 00:05:50 people rolling their own release media in the wild basically never happens if you look at the nonexistent pile of reports that come from that scenario 00:06:37 so really the only supported way of deploying freebsd is install a potentially insecure version of the OS then rush to perform network updates before getting rooted 00:06:47 embellishing a bit but still, the model is broken imo 00:07:15 yup pretty much 00:07:50 doesn't feel great on the user side fwiw 00:08:38 * kevans shrugs 00:08:47 ootb there's not a whole lot of options for remote accessibility in the first place 00:09:06 huh? 00:10:35 polyex i think ootb is out of the box 00:10:52 this is another one of those overly-abstract problems, out of the box there's very few vectors one has to exploit remotely and ideally you're not silly enough to start deploying services before you've updated it 00:10:54 i don't even know what remote accessibility means 00:11:08 if you take off the 'ibility' maybe 00:11:20 eh still tho, to require network connections to freebsd servers to bring a server from installed to up to date sucks 00:11:34 I'm done with laptops for today (possibly) lol later all! 00:11:52 later jb1277976 00:11:53 it doesn't require network connections to freebsd servers necessarily 00:12:03 if you're that paranoid you're probably running your own freebsd-update server in the first place 00:12:49 no the whole idea of installing an out of date OS is what doesn't make sense. the network update after install step should be totally optional 00:13:47 feel free to file a bug report 00:14:33 your point isn't unreasonable, but almost every mainstream OS works like this, unless it has a way to include patches in the install media (like Windows does), but even then hardly anyone actually does that 00:16:23 re is under new management so it's a great time to revisit things like this and try to understand why the current model exists and what can be done to improve the situation 00:16:32 but none of that will happen in #freebsd unfortunately 00:19:26 how can i debug why sudo pkg upgrade outputs pkg: an error occured while fetching package? 00:19:50 it doesn't say which host it's trying to connect to lol 00:21:05 you know, it's odd that a chip called "Killer E2500 Gigabit Ethernet Controller" doesn't actually support 2.5Gbps Ethernet. could they have chosen a more confusing model name? 00:21:16 lol 00:25:51 logically it should support 2.5 terabit ethernet 00:29:15 unixwitch: every time i see that, my dyslexic brain makes this out of it https://im.eena.me/uploads/1a53e1b4f920d7f4/ethernetkiller-4112566390.jpg 00:32:12 There is no brace expansion in sh as there is in bash... how do i replicate this behaviour in sh 'file{1..100}'? 00:51:46 for i in `jot 100`; do echo file${i}; done 01:12:58 Anyone ever received this error? : jemalloc_rtree.c:205: Failed assertion: "!dependent || leaf != NULL" 01:13:11 I don't quote know what it means or have remalloc_rtree.c in /usr/src 01:15:34 rtprio thank you! 01:23:45 fikran: src/contrib/jemalloc/src/rtree.c 01:24:13 no idea where the jemalloc_ prefix comes from in the assertion output 02:01:56 success! 64 bytes from 10.1.4.1: icmp_seq=0 ttl=64 time=0.222 ms 02:02:21 except i'm not sure how i fixed it, i just set the interrupt mask to ~(uint32_t)0 ... probably need to work out which particular bit it wants 02:10:52 kevans: thank you! Curious why its mislabeled... 02:12:26 kevans: what does this error meaning? I don't quite get it from looking at the code. 02:26:14 fikran: no idea, sorry 02:27:27 jemalloc and i haven't been friends since they ripped out the redzone support that was really useful 02:59:50 weird, I'm not even using jemalloc 03:07:12 i think it's the default allocator, i.e. if you do man malloc, you get the jemalloc man page 03:07:32 yeah...not sure how to proceed heh. 03:07:38 This error makes no sense to me. 03:16:09 yeah, jemalloc is the only libc malloc in freebsd today 03:25:27 do you think FreeBSD devs would accept restructuring sys/dev/usb/wlan/STUFF to sys/dev/usb/STUFF ? 03:31:45 I can't really imagine a good reason to do that, no 03:33:10 usb tries to be reasonably organized by function, why would you want to merge all of this? 03:34:13 can anyone see if there is anything wrong with this zfs output? https://bsd.to/fLxN 03:34:14 Title: dpaste/fLxN (Plain Text) 03:34:39 when i try to connect a client to the server.. it keeps giving me this tcp] 192.168.0.120:/storage/blinksystem: RPCPROG_NFS: RPC: Program not registered 03:34:51 when i try to mount the drive.. which DID work at one time 03:35:05 kevans: to be consistent with other USB drivers 03:48:13 fikran: which other drivers? i feel like you're missing that the vast majority of usb drivers are in functional subdirectories (net, serial, video, storage) 03:48:46 everything left directly in sys/dev/usb are mostly infrastructural bits 03:58:31 voy4g3r2: i fought with something like that for a while. try rebooting. the issue is sometimes that the rpc crap gets all registered at once, so if you restarted rpcbind, it drops those registrations. sometimes you will get lucky (it was inconsistent for me), but at some point i realized that i had the configs correct and just restarting allowed all the things to start in the correct order that the nfs shares registered 04:02:48 hrm.. at this point might as well give it a try 04:02:59 scoobybejesus: i know that nfs option works.. i have used it before 04:03:16 well looks like i will be right back 04:11:26 you should see it with showmount 04:18:11 hrm.. still happening 04:25:50 showmount on the server gives the expected output? 04:26:15 -m? -u? I forget 04:27:06 and then showmount from the client 04:28:36 i get that RPG message again 04:28:49 showmount: can't do mountdump rpc 04:30:10 from the server, you get that error? 04:31:01 yeah 04:31:24 you don't have this folder in /etc/exports, right? zfs sharing over nfs is supposed to be easy (I think) 04:33:31 I double checked my notes. you don't need anything in etc/exports, and you don't need to reload mountd or restart nfsd service 04:35:58 nope.. i have no /etc/exports 04:35:59 https://bsd.to/BaqS 04:36:01 Title: dpaste/BaqS (Plain Text) 04:36:03 this is my /etc/rc.conf 04:36:08 messy but i think i got what i need 04:37:00 i know services are working from zfs.. because netatalk is now running.. through time machine on my laptop 04:39:33 you just zfs set sharenfs='network 192.168.0.0/24' storage/blinksystem. you don't need to set it 'on'. try without the maproot part 04:41:26 same result 04:41:29 you have nfs_client_enable instead of nfs_server_enable 04:41:35 son of a gun 04:42:42 i don't know if you need nfsuserd_enable, and i don't think you need (but it couldn't hurt, i don't think) nfsv4_server_enable 04:43:13 was just going to ask that v4 is NOT loaded 04:43:22 add the v4 to the /etc/rc.conf line? 04:43:42 again, you may want to reboot because of how these services register themselves with rpcbind. but service nfsd start might do it.. not sure 04:43:49 it loaded :) 04:43:52 that v4 line is a separate line. you'd keep both 04:43:59 nice! 04:45:18 now to see why this /etc/fstab is garbage 04:45:25 thank you 04:46:49 happy to help. just realized my nfs server is not working now. i thought it survived the jump to 14.0-release. maybe not. i will look into that later 04:47:33 funny you should say that.. last time i fiddled with this was on 13.2 04:47:38 and was like.. why is this not working anymore 04:50:29 thank you scoobybejesus , time to get this git server moved to the zfs 04:50:32 voy4g3r2, In your previous paste https://bsd.to/fLxN/raw there is a line "on,-maproot=chrisdavidson:blinksystem,192.168.0.0/24". What syntax are you using for the 192.168.0.0/24 part? It's just hanging there in space. I have never seen that syntax before. I expect it to be something like a traditional "-network 192.168.230.0/24" or "-network 192.168.230.0 -mask 255.255.255.0" or something and not just an IP address there. 04:50:33 Title: fLxN 04:51:05 rwp: in an article i read it said take what you have in /etc/exports and mold to blah 04:51:12 and make sure on is there.. 04:51:48 but i like the new way better :) 04:52:10 it looks prettier 04:52:41 That is true enough. It should be the line from /etc/exports. In which case what will the "on" do? 04:53:59 if I install ports at install time, will freebsd-update update my ports tree? 04:54:16 mmlj4, No. Ports and base are individual and separate. 04:54:27 Upgrade binary pkg ports with "pkg upgrade" 04:54:34 rwp: the one was suppose to invoke zfs sharenfs=on 04:54:35 so use the git pull method? or...? 04:54:58 rwp: I'm asking about ports, not packages 04:55:17 If you have ports compiled locally then you would follow the make install command for them, which I don't recall off the top of my head. 04:55:28 never mind, thanks 04:56:07 The main issue to be aware of for ports is that they compile and link against shared libs in base. When base updates some of those shared libs are obsoleted and removed. So ports need to be compiled against the new set of base shared libraries. 04:56:28 you're still talking about apples, I'm asking about oranges 04:56:34 Otherwise they try to run, find a shared library that previously existed in base is now missing, and the port can't run. 04:56:58 You said compiled ports. But regardless what I said applies to both. 04:57:04 I did not. 04:57:11 I asked about the ports tree 04:57:20 apples, please 04:58:43 can anyone answer my actual question? thanks. 04:58:47 Sorry but I think we are talking past each other. 05:02:00 4.5.1. Installing the Ports Collection 05:02:02 Before an application can be compiled using a port, the Ports Collection must first be installed. If it was not installed during the installation of FreeBSD, use one of the following methods to install it: 05:02:17 Procedure: Git Method 05:02:28 mmlj4: the answer is no, freebsd-update won't touch a ports tree 05:02:30 ports tree, not compiled ports. 05:02:51 kevans: then the tree is orphaned? 05:03:11 effectively; historically you'd manage it with portsnap, these days you'd manage it with git instead 05:03:34 fair enough. Thanks. 05:04:03 is portsnap a dead project? 05:05:20 kind of... ports folks were insistent on deprecating it because it didn't handle some things very well (quarterly vs. latest, maybe? my memory is foggy) but the servers are alive and well probably for the foreseeable future 05:05:56 the maintainer was somewhat against deprecation because there are many valid uses 05:06:02 it seems to be working, for now anyway 05:06:20 the git method kept crashing for me with different errors each time :-/ 05:06:34 with git you probably have to specifically do ssh cloning with anongit@ 05:06:38 or clone it through github 05:07:09 the ports tree repo is massive and has historically had some issues trying to do HTTP(S?) cloning 05:07:26 if portsnap keeps working I won't need the git method, regardless 05:11:15 I'm down the road, thanks, kevans 05:16:33 dang I need a sound card, but my pci-e slot is taken up by bluetooth wifi card :/ I think 05:29:49 there's only one? 05:31:45 hmm let me double check 05:33:26 yeah it could have two but I think one is obscured by the width of the graphics card 05:33:36 it has been a while since I took it apart 06:02:35 I'm having an issue running a freebsd router with openbgpd using pf as my firewall. I want to be able to restrict traffic to my bgp port from only my peers, and otherwise unrestrict traffic in/out. Is this something anyone can help with? 06:16:38 ok so freebsd gets buggy if i try to build releng/13.2 and latest patchlevel. but is base what's buggy or is it just freebsd-update, and i can just ignore for now? 06:27:29 Can't say, for the latest patch-level may be buggy for you but it has not been in my case🤷🏽‍♂️ 06:29:18 parv so you git pull a branch like releng/13.2 with latest patch, build, build installer, install with installer? 06:32:20 polyex, I think "releng/13.2" would be a Git "tag" not a "branch". Further, I have not notice (do update me if there are) any tags for each patch level. In any case, I follow the "stable/1[34 06:32:41 ]" branch & pick a point in the commit history to install 06:33:11 you pick a point based on what, stable code? 06:34:06 based on guess, past mailing list messages, & specifically when "__FreeBSD_version" changes 06:34:33 k then you run that and don't use freebsd-update? 06:35:09 Right (on some hosts I use "freebsd-update" & others update from the source) 06:36:44 Just updated from source in branch "stable/14" due to "__FreeBSD_version" change as that would become significant in near future for package updates 06:37:08 ok ya. today ppl were acting like i had 3 heads because i was building locally instead of using release plus freebsd-update 06:37:16 was doubting myself for a sec lol 06:40:18 tbh i thought MOST ppl with large fleets deployed up to date code instead of installing old shit + needing a bunch of update downloads 06:40:23 obv not 06:42:28 Whatever works. When I started with FreeBSD 14, it was still -CURRENT thus would not have "freebsd-update" support. Any newer installations, of 14, would be updated via "freebsd-update". A clear advantage, & only one AFAIAC, of updating from source is that I do not have accept all the changes since last patch-level update. 06:43:35 ya 06:43:46 i'm looking at unbound's pkg https://cgit.freebsd.org/ports/tree/dns/unbound but where's the default unbound.conf that we get in /usr/local/etc/unbound after installing? 06:43:47 Title: unbound « dns - ports - FreeBSD ports tree 06:45:05 In one case, really need 14-CURRENT for GPU driver support. In another, I happened to have only 14 installation image, did not bother to download+copy 13 one; so. 06:45:15 s/need/&ed/ 06:48:56 Re unbound, see the "pkg-plist" file; in there at the very top is the sample configuration file location 06:50:36 @sample %%ETCDIR%%/unbound.conf.sample 06:50:41 but how does it get into etc? 06:50:53 it would have to come from the unbound pkg itself no? 06:51:00 Yes 06:51:40 Could be in the directory wherever "unbound" is built 06:54:57 so current is 14.0.RELEASE-p4 - is there a URL or something where this string of latest can be found? 06:57:22 kolla, Outside of errata or security announcements, I do not know; there is https://www.freebsd.org/releases/14.0R/errata/ but does not have exactly that you are seeking 06:57:23 Title: FreeBSD 14.0-RELEASE Errata | The FreeBSD Project 06:58:08 right, I only found it there as well 07:15:45 i can't believe it's so hard to find the unbound.conf that gets installed with the pkg. how is that good for learning? 07:19:05 What? Did you not find a configuration file after fetching+extracting the source (given use of Ports)? 07:19:33 no web 07:22:20 polyex, Do you "unbound" installed? If so, try "pkg info -l -x unbound | grep "[.].conf" 07:23:48 s/you/& have/ 07:31:12 * parv throws a " in past 07:33:34 ya i do 07:36:49 parv: releng/x.y are branches 07:37:19 kevans, Ah. Thanks much for the correction 07:38:05 kevans, While you are here, are patch levels tagged in some way too? 07:39:50 unfortunately not 07:39:58 * parv 🤦🏽‍♂️ 07:40:37 polyex, Correction for "pkg | grep": pkg info -l -x unbound | grep '[.]conf' 07:40:43 kevans, Thanks 07:40:58 I vaguely recall asking someone about this recently, but searching my inbox for "tag patch levels" is a disaster 07:41:25 parv ya ty. i can do that but what i wanted was a way to browse online the package as a unit of what it'll be putting on my OS 07:41:35 so i could see what its default unbound.conf looks like 07:41:47 maybe that's not useful to anyone else 07:41:53 we don't really maintain a set of ports distfiles all extracted anywhere 07:42:04 lots of storage needed 07:42:22 ah 07:42:25 we've had requests from time to time to have such a thing for searching, though 07:43:16 sometimes what you want can be found in files/, but in this case and many others we're just installing something from the software's release archive as a sample 07:43:19 polyex, In that case seek out the project web site|page & hope that it has put up the information of interest 07:48:30 okie 07:58:17 Is anyone using FreeBSD in dual-boot with Windows 11, each on its own partition on a single disk, scenario? (There will be space+connection for only one SSD in the future laptop) 07:58:55 ... yeah I could continue to use FreeBSD VM as currently I am ... 07:59:48 ... but the reports of people getting ads in Windows 11 make running the VM not as appealing. 08:10:58 ugh, what ads 08:18:34 yuripv, See the results of https://duckduckgo.com/?t=ftsa&q=windows+11+ads&ia=web -- one from there: https://www.elevenforum.com/t/disable-ads-in-windows-11.8004/ 08:18:35 Title: windows 11 ads at DuckDuckGo 08:20:29 looks like fud 08:20:55 ok🤷🏽‍♂️ 08:37:15 https://alpha.polymaths.social/@rl_dane/statuses/01HEVP2KV9ZX6WKX0SVFJD7PNX reminded about running Windows in a VM instead! 08:37:16 Title: Post by rl_dane (@rl_dane⊙aps) 08:45:18 ... but the laptop (HP EliteBook 640 G10+|Lenovo ThinkPad T14 Gen 4+) hardware would have to be properly supported by FreeBSD for me to that even consider🤦🏽‍♂️ 08:46:12 i can type resolvconf -a vtnet0 < /path/to/file to pass the file contents in, but what if i wanna pass 'a string of text' in instead of file contents, how should the syntax be? 08:51:34 Use "cat" with "heredoc": https://termbin.com/57b6 08:52:08 8 lines to pass 1 string into resolvconf? 08:52:59 That was just an example. Do not know|care what or how "resolvconf" needs 08:53:36 Last 2 lines are the output of "cat | awk" 08:54:59 There is also "echo" or "printf": printf "%s" "whatever" | resolveconf ... 08:55:33 ... "echo" has different usage than "printf" 10:25:31 hmm after an update to 14.0-RELEASE sudo and pkg where both defunct - needing libcrypto.so.111 and libsso.so.111 - fortunately it turns out they where elsewhere on the disk and I had user elevation though su 10:26:08 now I have a nagging feeling I have a halfway upgraded system 10:30:22 any way to rerun the installation for 14.0-RELEASE again ? 10:39:11 not libsso but libssl 10:59:40 BarnabasDK: openssl was upgraded to version 3 in base; you should rebuild all dependent ports (or force-upgrade packages) 11:00:03 i think freebsd-update tells you to do just that (if you used that) 11:01:29 yes - I saw that in the release notes. I just think it is strange that the upgrade of the OS deletes the needed old shared objects before you get to this step 11:02:01 so - I copied in the old libs - did the upgrade of pkg and a reinstall of sudo - and deleted them again 11:02:21 you had pkg-static for that 11:02:28 ah .. 11:02:49 there is a statically linked version - did not know that 11:28:52 BarnabasDK: did you upgrade with freebsd-update or from source? 11:32:51 freebsd-update 11:35:02 BarnabasDK: so when you do a release upgrade with freebsd-update, you run install three times. the first time installs the new kernel, the second time installs the new userland, and the third time removes obsolete files, including shared libraries. you need to update packages/ports to the new release between the second and third freebsd-update install runs to avoid this. 12:22:28 anyone familiar withj nis? 13:05:06 there a command to append some text to a file? echo "foo" > file.txt doesn't append it overwrites 13:05:17 polyex: echo "foo" >>file.txt 13:06:00 yes!!! 13:08:02 wanna be fancy, you use tee 13:08:11 added bonus, it works with sudo 13:08:14 so this github pull system seems to work quite well, and i imagine it's good for attracting contributors, but it's kind of a shame it depends on github 13:09:19 could set up an official freebsd gitlab instance? 13:09:40 from what I searched, there already is 13:10:19 any clueas why ypbind wont bind on my freebsd client but on linux it's not a problem? 13:10:29 https://gitlab.com/FreeBSD 13:10:31 Title: FreeBSD · GitLab 13:11:08 woo, ypbind, now there's a relic from the past :D 13:12:26 mane: I can think of a few possibilities... lke ipv4 vs ipv6 13:12:32 *like 13:12:59 cxan you be more specific? 13:14:38 are server and client speaking same protocols? 13:14:52 they run both on 13.2 13:15:18 ah, ypserv is also on freebsd? 13:15:22 yes 13:15:45 all systems on same lan? 13:15:53 of course 13:16:29 what's the error message? "server not responding"? 13:16:46 ypcat: no such map hosts.byaddr. Reason: Can't bind to server which serves this domain 13:23:04 is there a reason crypto/heimdal hasn't been updated from upstream for ~10 years? (not a complaint, i'm just curious, especially if there's something i can do help with it) 13:27:06 unixwitch: do you mean the port or the base libraries? 13:27:13 meena: the base libraries 13:28:02 oh that's weird 13:28:25 wow 13:28:58 it's missing some useful newer encryption types, like the SHA-2 based ones (we're stuck with aes256-cts-hmac-sha1-96, upstream has hmac-sha256-128-aes128) 13:29:53 https://cgit.freebsd.org/src/log/?h=vendor/heimdal 13:32:58 meena: the vendor branch has been updated but it doesn't seem to have been merged in... 13:34:19 https://cgit.freebsd.org/src/log/crypto/heimdal the last merge was 1.5.2 in 2012 13:34:27 Title: src - FreeBSD source tree 13:36:58 So then the question is, what's the difference between that, and https://cgit.freebsd.org/src/tree/kerberos5 ? 13:37:00 Title: kerberos5 - src - FreeBSD source tree 13:38:56 is that the freebsd-specific Makefiles etc. for heimdal? 13:40:29 yeah, like kerberos5/lib/libkrb5/Makefile pulls from ${KRB5DIR} which is crypto/heimdal 13:40:58 ah, sorry._. I'm still just on the phone 13:54:18 so i install a default disc1 with basically nothing but defaultrouter and ifconfig_ in /etc/rc.conf.local. so obviously dns fails because i don't have a resolver setup yet but why can't i ping my router? lol 13:54:39 ifconfig shows the expected ip for the if 13:55:01 netstat -rn shows default with the gateway ip of my router 13:55:07 so wtf 13:56:15 My current task: find out why snmpd on jail foo reports Memory Usage, but snmpd on the host itself does not. It must be configuration. snmpd config is not just a single text file. :/ 13:57:22 polyex: is the interface up? what error do you get from ping? what does tcpdump say? 13:58:05 ifconfig says the if status is active. ping says ping: sendto: Host is down 13:58:59 'active' isn't enough, it needs to have UP in the interface flags, like this: ix1: flags=1008943 metric 0 mtu 1500 13:59:44 ah ya it's UP 14:00:11 does tcpdump show packets going out on that interface when you run ping? 14:00:30 how do i use tcpdump for this? 14:00:52 in one window run 'tcpdump -ni ' then in another window run ping (or whatever) and look at what tcpdump prints 14:04:11 k gotta enable ssh gimme a sec 14:05:41 it's gonna take me a bit i gotta rework some stuff. weird that i couldn't just get a network connection to my router lol 14:09:59 hey everyone, i started receiving some i/o errors on my zpool and the only way i was ble to clear them was with a reboot... 14:10:19 the zpool is now operational again but i have a strong feeling, this is NOW dying too.. is there a way to perform a health check of sorts? 14:10:57 voy4g3r2: Does zpool status tell you anything? 14:11:19 vkarlsen: it says everything is good now.. after the reboot of the machine 14:11:34 voy4g3r2: Have you scrubbed recently? 14:11:59 voy4g3r2: what was the `zpool status` before you rebooted? 14:12:01 no i have not 14:12:17 good morning everyone 14:12:39 morn 14:13:04 https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-HC/ 14:13:05 Title: Message ID: ZFS-8000-HC — OpenZFS documentation 14:13:16 it pointed me to that.. for some reason dmesg is now blank... trying to pull up the logs 14:14:05 smartctl is the tool to ask the drive how it's doing; sysutils/smartmontools 14:16:14 i am having a really weird zfs issue, which only started since i upgraded to 14.0 (which makes me wonder if it's a bug) where a pool gets random data errors, but only on snapshots (never on files) and which vanish on reboot 14:16:26 i thought it was a memory issue, but i've run memtest86 twice and it didn't find an problems 14:18:10 https://bsd.to/mAD6 14:18:12 Title: dpaste/mAD6 (Plain Text) 14:18:16 that is one drive.. nothing looks out of wak 14:18:18 whack 14:21:02 oh, a WD green 14:21:22 yeah... 14:21:31 i know i know.. 14:22:02 if i can keep these stable enough.. i want the data OFF the dang things to i can properly evaluate this stuf 14:22:17 i was hoping to wake up, my time machine backup would be done.. and i can start "moving" the data off 14:23:05 you could do a long test, but i wouldn't trust a green further than i could throw it 14:23:29 https://bsd.to/OQi5 14:23:31 Title: dpaste/OQi5 (Plain Text) 14:23:32 it is a lot of information 14:23:42 haha.. yes i have read that and i have had people tell me that 14:25:02 Will ipfw in-kernel NAT support syntax like?: https://bpa.st/QCVQ 14:25:04 Title: View paste QCVQ 14:25:16 I'm specifically referring to the port ranges. 14:25:30 It's supposed to be a (mostly) drop-in replacement for natd, which supported them - but I haven't found any examples with the in-kernel NAT. 14:31:02 just type it in and see if it accepts the syntax 14:35:24 well ltest see what these 235 patches do for the release 14.0 updates 14:35:30 did not expect this many updates since release.. oh well 14:43:21 unixwitch: what's next on the list? 14:43:55 meena: maybe fix this zfs issue :-) i've given up on alc(4) for now, i mailed the Linux driver maintainer to see if they have an actual documentation for the thing... 14:48:28 i don't follow how it only errors on snapshots 14:49:52 it seems like only metadata is affected, when the problem occurs "zfs list -t snapshot" will fail to list some of the snapshots and says "cannot iterate filesystems: I/O error" ... but there's no i/o errors, no checksum errors, and all the data is perfectly fine 14:50:47 unixwitch: alc or acl? 14:50:59 voy4g3r2: alc 14:51:13 the driver for AR81xx Ethernet cards 14:51:25 ah okay.. i am going through documentation "bugs" 14:51:32 and i remember seeing acl issues 14:51:45 in this case the issue isn't freebsd documentation, but documentation for the chip itself :-) 14:51:46 https://bughuntingfreebsd.wordpress.com 14:51:47 Title: FreeBSD Bug Hunting – An inquisitive person finding their way in a FreeBSD world. 14:51:53 haha 14:52:05 https://bughuntingfreebsd.wordpress.com/2023/12/24/boss-we-got-a-list/ <-- specifically this mess 14:52:07 Title: boss!! we got a list!!! – FreeBSD Bug Hunting 14:53:07 that does sound weird 14:53:39 it is very weird, to the point it really feels like an issue with the hardware, but then i'd expect at least cksum errors 14:53:40 rtprio: would you recommend a scrub for this zfs.. before i try to get this data off as you just "love" the wd greens 14:54:19 what's a nice desktop font? i don't like Deja Vu, the spacing seems weird 14:54:57 https://www.programmingfonts.org/#bitstream-vera 14:54:58 Title: Programming Fonts - Test Drive 14:55:04 i have been enjoying this font 14:55:15 https://www.nerdfonts.com/font-downloads 14:55:17 Title: Nerd Fonts - Iconic font aggregator, glyphs/icons collection, & fonts patcher 14:55:20 you can download there 14:58:36 but my days are usually in man pages, nvim and other console tools.. not much of a gui person on the desktop 15:00:49 i use a gui mail client (claws) since i haven't found a terminal client that handles multiple imap accounts and folders very well... maybe i should look at that mutt sidebar patch 15:01:16 that i just use my phone.. mailing list recovering addict here 15:01:29 i remember penn state telling me, i was overloading my email account.. i have been recording every since 15:01:57 like 20 years ago 15:31:04 rtprio: i know not many fans of the wd green.. what about the barracuda line of drives? 15:54:59 ypwhich: can't yp_bind: reason: RPC failure 15:55:40 any ideas what's wrong? 15:57:50 mane: are your rpcbind services running? 15:57:58 yes 16:00:35 rpcbind is running 16:00:51 does dmesg or /var/log/messages say anything more? 16:01:04 i was having similar rpc pains, last night, and it was a tango that i was stepping on feet 16:03:27 god i hate roff syntax 16:03:35 can we convert all the manpages to latex? 16:04:33 voy4g3r2 maybe you'll think something out, really need this project to work 16:05:58 unixwitch: you just have to breathe thru it, and at some point you don't even see the syntax any more 16:06:39 I don't know how long it takes to reach that point, probably writing and rewriting some thirty odd man pages, but, yeah 16:06:49 unixwitch: Can, yes. Although 'can' and 'should' are different words. First step would be to add tex support to man and related commands. 16:07:03 meena: it's giving me flashbacks to highschool when i set my homework in troff 16:07:32 unixwitch maybe you'll know what's wrong? 16:07:49 * tmp_ used a wordprocessor back in the day that used something roff-like for formatting. 16:07:50 Also, picture what the base system would look like, if man supported LaTeX 16:08:00 probably… different 16:08:05 mane: with your YP? sorry, i haven't used that for ages. i use LDAP nowadays. 16:08:07 Very different. 16:08:46 maybe we'd stop pretending that our computer is a teletype, and start treating it as a computer?! 16:17:05 unixwitch maybe you got a good ldap tutorial for me|? 16:18:23 i want to know how to configure the ldap freebsd servers and clients 16:20:11 not sure about a tutorial. for client i use net/nss-pam-ldapd, for server, openldap, it's bit of a hassle to configure but the documentation is good 16:27:38 what are the criteria for marking a commit as "MFC after"? or is it just use reasonable judgement? 16:33:26 unixwitch: kind of a reasonable judgement thing; if it fixes something and can be backported without breaking KBI/ABI somewhere important, that's a good candidate 16:39:34 unixwitch: it would be nice to just be able to have al the man pages in one semantic syntax.. regardless of roff or latex.. i am trying to "find" broken links.. and there are multiple ways to make a link.. .Xr is not the only way.. 16:39:50 mane: you are trying to get bind operational? i apologize not 100% sure what you are trying to get operaitonal. 16:40:17 voy4g3r2: what are the other 'commonly' used ones? 16:40:19 i'm trying to make ypind work 16:40:23 ypbind 16:40:37 it works on linux clients but can't bin on fbsd clients 16:41:18 meena: https://bughuntingfreebsd.wordpress.com/2023/12/24/boss-we-got-a-list/ in the observations section 16:41:19 Title: boss!! we got a list!!! – FreeBSD Bug Hunting 16:41:23 Pagename(section) 16:41:33 \flpagename\fR(section) 16:41:39 \fBpagename\fR(section) 16:41:50 also .Xr all produce links in man pages.. 16:42:00 aaah, i've used Pagename(section) myself before, actually… 16:42:29 yeah, i have been documenting the "fixes" and what i am learning in the process.. there 16:42:39 it all started when i was trying to read up on zfs(8) stuff and a link did not work 16:42:55 https://man.freebsd.org/cgi/man.cgi?domain ← struct protosw { 16:42:56 Title: domain 16:43:05 has a bunch of that, and I didn't realize it's "official" 16:43:17 but i still went out of my way to correct them 16:43:45 then you got weird ones like zzz(8) does not exist in base install 16:43:57 the focus is just what is in FreeBSD 14.0. and NOT including ports 16:44:08 which all circles back to the zfs stuff being a pain as all my work is there 16:46:31 voy4g3r2: i would generally focus on what's in CURRENT, since that's where you gonna contribute fixes to 16:46:54 can you briefly explain why the ZFS stuff is a pain? 16:50:38 > RESOLUTION: Removed this reference as it is not in the base OS but in the ports 16:50:47 I don't think that's necessarily how we want to handle those 16:51:06 kevans: possible, it is why i am documenting what i was doing for the world to see 16:51:24 my focus is NOT ports but base os..and leave it up for debate outside of my efforts 16:51:38 meena: i have thought abou the CURRENT thing, then the zfs stuff was acting up 16:52:09 meena: i think the hard drives in the zfs pool are starting to die and i am having weird status issues, drives sometimes connecting.. all because i am using usb.. i have not figured out root cause 16:52:14 kevans: which one in particular are you referring too? 16:52:28 it would be nice to annotate SEE ALSOs with, these are in ports, installable via $package-name 16:53:27 that one was blk(8) reference in zfs(4) if I'm reading this right, but it's more about the general problem 16:53:38 I don't think we want to axe a link just because the software is in ports 16:53:48 blkid(8) 16:55:05 we have blkid in ports? i could've just depended on it, rather than writing a parser for geom? 16:55:12 i thought of this $package-name route then was getting lost in ports 16:55:19 that one's probably a bad example because I think it went away entirely in a later zfs 16:55:42 oh, util-linux… brrrrr 16:56:22 oh that's neat, I didn't realize freshports lists man pages provided separately (e.g. https://www.freshports.org/devel/util-linux/) 16:56:24 it is interesting when you get down to things like speaker(4) if you do not have a speaker on your computer.. it does not get installed but appears to be part of base install 16:56:24 the new ZFS manpages are full of Linuxisms... 16:56:34 kevans: it's a new development 16:56:41 kevans: it's new. 16:56:54 that's incredibly useful, thanks 16:57:28 then a fascinating one is the whole atof_l() vs atof() 16:57:41 the difference is precision of holding data in a variable.. but one has a man page and another does not 16:57:49 atof_l() no man page.. but references in the stdlib.h 16:58:05 kevans: Thank Graham Perrin too. Blame him. https://github.com/FreshPorts/freshports/issues/492 16:58:07 Title: manual pages: if a page can be inferred from the pkg-plist, then link to the page · Issue #492 · FreshPorts/freshports · GitHub 16:58:07 492 – sysinstall shows "success" after "no space" failure. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=492 16:58:16 voy4g3r2: it should probably just be documented in the same man page as atof() 16:58:36 meena: yup, the "fix" i just pointed atof_l() to the atof() manpage.. dragonflybsd did that 16:58:54 so we can just import it from them? 16:59:17 i did not do that... i just looked at what they did and replicated it manually 16:59:26 this is my first bug i am working through 16:59:30 so learning as i go :) 17:01:14 voy4g3r2: it's simple, you just add the dragonfly git repo as another remote, and git cherry-pick -x the commit where they make the change, then clean up the mess that creates because we've drifted too far apart. 17:01:18 it is why i baselined 14 instead of CURRENT.. i know for a fact CURRENT will change everyday. and that chaos just adds a variable i am not prepared for yet 17:02:03 * meena swims in the chaos (but she cannot properly swim in actual water) 17:02:59 the good thing about using CURRENT is that it's a lot easier to work on this incrementally if you can get finding problems down to a science of some sort 17:03:14 some of these will have disappeared in the interim, and it's hard to say how many that might be 17:03:18 well that output is generated through an awk script :) 17:03:43 it looks through /usr/share/man hierarchy and does it magic. 17:03:44 do people run current on desktops nowadays or just use a VM? 17:04:38 i used it on a laptop, until i bricked it 17:05:03 voy4g3r2: sweet, so that's pretty solid 17:05:12 now I'm too chicken to install it on *this* laptop, which is running some Ubuntu derivate, so I'm running it in VMs 17:05:26 i think i mentioned the other day that the last time i tried it was during the removal of giant locking which kind of put me off running current forever 17:05:45 imo the optimal approach here is to roll with -CURRENT and just re-scope it; e.g., today I'm only dealing with section 1 manpages. your patches will need to be against -CURRENT anyways, so whittling away at the problem there is ideal 17:05:45 i should *maybe* upgrade this Ubuntu derivate some time, that might solve some issues I'm having with it… 17:06:14 unixwitch: removal of giant lock? when is that gonna be? 17:06:32 unixwitch: i've rolled with -current on my laptop for somewhere around 6 years now 17:06:32 unixwitch: that sounds like a good idea for a post on this blog 17:06:40 a VM of current on this mac 17:06:53 meena: hah, well not removal, i mean during 5-CURRENT when fine-grained locking first appeared 17:06:59 kevans: yeah thanks, a person on X has been trying for years and was able to help with building one.. tim chase 17:07:02 (although... isn't giant going away in 15 or 16?) 17:07:13 unixwitch: it's going away any year now. 17:07:25 * meena hasn't been on FreeBSD that long 17:07:36 I think I've started using it full-time when VIMAGE was merged into GENERIC 17:07:45 giant had its tentacles in the kbd/console area, which all gets a bit sticky 17:07:48 in a RELEASE, so, 10.1? 17:07:48 kevans: good to know. maybe i'll try it (with a backup be...) 17:08:01 (had, probably still has) 17:08:18 i think atkbd and psm still use it, which surely can't be removed yet. maybe when i386 is removed... 17:08:20 last time I tried re-locking kbd it got hairy 17:09:03 yeah, you can fix atkbd to not use giant with kbd not using giant, which also requires some work in vt(4) and sc(4) 17:09:10 unixwitch: two words: Boot Environments 17:09:22 to be fair they did say 'backup be' 17:09:33 (i should've used them, it's the reason my old laptop is now a brick) 17:09:40 kevans: don't you know I can't read 17:09:50 meena: that's what i meant by 'backup be' :-) 17:10:03 unixwitch: don't you know I can't read? 17:10:24 (i'm so glad freebsd has caught up Solaris's Live Upgrade from the 1990s :-D) 17:12:02 my first job was solaris, so I thought that was *normal*, and was shocked to find out that it's not 17:14:20 solaris is far from normal 17:14:51 kevans: I've also briefly touched AIX, and 17:14:54 Solaris is the reference implementation of UNIX System V Release 4, so by definition, it is the most normal OS. :-) 17:15:17 what unixwitch said. 17:15:32 bah 17:15:58 and, like, who here hasn't built SVR4 packages? 17:16:23 i used to have a whole custom ports-like toolchain for building those 17:16:37 same… 17:16:47 in retrospect i probably should've used pkgsrc but i don't remember if it worked on solaris at the time 17:16:50 well, mine was inspired by Archlinux 17:17:11 unixwitch: I should've used OpenCSW, but one of the senior admins vetoed it. 17:17:47 "it won't be as optmized as it can be if we don't compile it ourselves" 17:18:02 i have wasted life-times on compiling PHP… 17:18:03 did they know you can't compile solaris 17:18:09 (well okay, you can, but like) 17:18:58 i felt like a bit of an arch user when i put CPUTYPE?=znver3 in my make.conf the other day. maybe that's more gentoo than arch. 17:20:18 unixwitch: try CPUTYPE=native and see what breaks 17:22:38 meena: i have not built SVR4 packages.. i did get to play with a HP-UX box in the late 90s early 2000s 17:22:43 btw, if you remember my setuid ping_exporter complaint from the other day, someone (not me) submitted an update to it: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275628 ... hope this gets committed soon 17:22:45 Title: 275628 – net-mgmt/ping_exporter: Update to 1.1.0 17:22:48 i even got to dabble with carroll.psu.edu back in the day.. 17:23:28 my personal web server used to be an HP-UX box... i quite liked it, even if it was weird in places. (less weird than AIX though) 17:23:59 the packaging system was quite nice, you could bundle a bunch of subpackages (like bin, man, doc) into a single file and select which to install 17:24:22 unixwitch: it's already committed, https://cgit.freebsd.org/ports/commit/?id=b534a3d03a7dfab1f70b755b668d0feab4b40bb5 17:24:23 Title: ports - FreeBSD ports tree 17:24:51 oh, that was 14 minutes, i didn't reload the tab :-D 17:25:29 it's too bad they didn't structure it to fix the setuid issue then update it, but I guess it doesn't matter that much with the end of the quarter days away 17:27:02 kevans: imagine if we could do more than one commit in ports, you know, like in git… 17:28:08 'magic' 17:28:30 meena: you could, i suppose, attach the output of a git format-patch with multiple commits to a bug? or is that not allowed? 17:28:53 unixwitch: i don't know how ports committers do anything 17:29:53 speaking of commits, somebody review and merge my extremely good pull requests, while i go find something to eat 17:30:00 (and reboot the freezer) 17:30:18 well that is just werid.. i thougth when i would do a zpool scrub, it would just run in foreground.. nope it runs in background.. 33% complete :) 17:30:26 a film 20 years from now will open the a voiceover, "In a world... where people had to reboot their freezers..." 17:30:43 silicon valley? didn't they do that whole thing with the fridges 17:30:58 voy4g3r2: you *can* run it in the foreground (zpool scrub -w) but it just runs it in the background and waits for it to complete 17:31:20 i sort of like in background.. it will be done in 3 hours.. and hopefully i will know more about what is goign on 17:31:39 looking at replacement drives now.. no idea what to even get.. i just know not WD green drives.. as rtprio just loves those :) 17:31:45 it's really just a sensor that's broken, not a real computer issue… but I'll need to find someone who knows how to fix big electronics, knows how to use a soldering iron, and knows where to buy the sensor in question, in rural ireland. 17:31:53 until then, "rebooting" it is. 17:32:27 my partner and i both work in the tech industry, and thus, none of our heavy duty equiment has computers inside 17:32:50 voy4g3r2: i like the Seagate Exos drives, which are available in both SAS and SATA flavours, but they're quite expensive. you can find them on eBay easily though, often without too much wear 17:34:27 HGST are also good but i don't know if they make/made SATA disks 17:36:19 oh wow.. for a 128meg catch 4tb is it is 75 bucks on amazon 17:36:32 got to 8tb and 256 jumps to 175 17:37:17 two 16TB 445 17:37:21 wow that jumped quickly 17:38:29 unixwitch: thoughts on the barracuda ones? 17:39:05 i haven't used one of those for a while... from what i remember they were fine but they're designed as desktop disks so they might not like running 24/7, i had a couple die 17:40:23 well gives me something to think about when i gym it up and listening to some podcasts.. https://www.bsdnow.tv 17:40:24 Title: BSD Now 17:40:48 buying consumer hard disks or SSDs nowadays seems like a nightmare because everyone lies about what the device actually is 17:43:55 voy4g3r2: ah yes, the soothing tones of benedict and tom (and i don't think i've actually listened to an episode with jason tubnor just yet) 17:47:33 what kernel options do i want for CURRENT on a desktop? i'm assuming turning off INVARIANTS and WITNESS is probably okay (unless i run into a panic or something)? 17:52:04 What do those options do ? I've not built a kernel in ages, not just for FreeBSD, for any other OS 17:52:45 mns: WITNESS is for debugging mutex-related issues, INVARIANTS is code to check a bunch of things that should always be true (like asserts) 17:55:58 unixwitch: ok that makes sense. Yeah I doubt you'd want those for a desktop system you were using regulary 18:01:28 * unixwitch wonders how hard it is to find a job working on freebsd (if you don't live in the US...) 18:01:53 kinda depends on what exactly you're wanting to work on, I think 18:02:28 yeah, i guess no one is going to pay me to write sctp manpages 18:05:34 klara's often got at least one or two contractor freebsd roles open, they've got folks in and out of north america: https://klarasystems.com/careers/ 18:05:36 Title: Careers | Klara Inc 18:13:53 unixwitch: I would just compile both, GENERIC and GENERIC-NODEBUG, and run GENERIC-NODEBUG and boot GENERIC when you're in trouble 18:14:11 me, use generic? like some sort of pleb? 18:14:12 (personally, I always just ran GENERIC) 18:14:18 (this is a joke don't @ me) 18:14:59 (well, GENERIC-MMCCAM, which, as it turns out, it's actually MINIMAL) 18:15:26 i noticed your PR for that earlier, is this about CAM for mmcsd(4)? or something else 18:16:19 yes, just equalising it across platforms 18:17:06 Also, adding VIMAGE to MINIMAL, because that's pretty useful 18:18:00 re: this heimdal thing, i'm wondering if it makes sense to backport the new algorithms from current heimdal if we can't update it in base. does everyone just use the heimdal port? but that doesn't help with base sshd/nfs/... 18:20:01 why can't we update heimdal? 18:21:27 last full update was just in january, but I vaguely recall that cy was maybe talking about kicking substantial parts of it out of base and maybe switching the rest to mit 18:21:53 kevans: are you sure? the version in main is 1.5.2 which is >10 years old 18:22:12 the vendor branch was updated but it wasn't merged in, as far as i can see 18:22:16 ah 18:22:23 that's unusual 18:23:04 meena: i can't find it now but there was a post somewhere (maybe on the mailing list) that basically said "it's really, really hard to update heimdal because "... but i can't remember what the reason was... 18:23:54 i wonder if therer was som echange to admin-y bits in the interim and we can't update without losing some compatibility with older but supported freebsd releases 18:24:53 it wouldn't seen unreasonable to keep libkrb5 in base and shove the rest into ports (kadmin, kdc, etc) 18:25:43 yeah, the idea was that if you need a server implementation just get the whole thing from ports, but we'd keep just enough client-side bits in base to authenticate against / use kerberos 18:25:58 since those tend to be more compatible with either implementation iiuc 18:26:23 is there a list for discussing this sort of thing? freebsd-ecurity? 18:26:29 -arch probably 18:26:30 -security 18:26:31 ah 18:27:16 the s is ecurity stands for security 18:27:49 kolla, Release patch levels from unofficial source: https://bokut.in/freebsd-patch-level-table/ via https://mastodon.bsd.cafe/@grahamperrin/111658459330472909 18:27:55 Title: FreeBSD Patch Level Table 18:29:01 since we just branched 14 off this would probably be a great time to try and spur movement there 18:29:34 unixwitch: go go go! 18:29:39 i would be happy to push on this since the current situation seems terrible, but i don't want to annoy people 18:29:52 maybe i'll start by asking a question on -arch :-) 18:29:58 annoying people is the only way to get things done 18:30:28 yeah, ask there and cc cy@ specifically just in case 18:30:59 (until you get a commit bit, and then you're seen as the blocker and people start to annoy you) 18:31:06 if you're interested in doing it, getting consensus and making sure you're not stepping on cy's toes are basically the start 18:32:27 meena: i spend far too much time drunkenly computing to get a commit bit anyway 18:32:31 i bet the src part of this is relatively easy and straightening out ports USES=gssapi is the annoying part 18:34:29 kevans: it is not bad with him.. but i ahve been only really listening to them since episode 500 18:39:02 hot new idea for C34 or C45: make __result_use_check the default 18:42:54 voy4g3r2: oh yeah, I'm sure he's good... just kind of ran out of time for podcasts myself 18:44:14 kevans: get rid of your dishwasher, if you want more time for podcasts 18:45:18 i think I'd have better luck getting rid of my eyedoctor / dentist 18:45:43 but she's too cute to evict, and the surprise dental inspections have really calmed down in the last 12 months 18:50:33 kevans: yeah i only get time when i head down to the gym.. it is part of my get out of the 2019-2023 mess.. i use to gym it up 5 days a week.. my body is like what are you doing to me man 18:50:45 hrm.. this current install through virtualbox is not as bad as i remember 18:51:17 current is not as unstable as many people make it out to be 18:51:36 yeah i even went the route of bootonly image amd64 and letting it install on the mac 18:51:51 this will help isolate the manpages work.. because i "guess" i should do this work with current over release 14.0 18:52:04 heck even using an image ont eh zfs.. might as well use the dang thing 18:53:06 loader(8) seems *really* slow on a 4K display, and i'm pretty sure it's because the method it uses to clear the screen via EFIRT is really slow, and it does this like 3 times 18:53:13 i wonder if it could be fixed to just not do that 18:55:18 * kevans runs away 18:56:26 well if you want to send me over that 4k monitor.. i could take a look 18:56:28 no promises though :) 18:56:40 voy4g3r2: you wouldn't want it, it's either broken or about to break... 18:57:01 although weirdly since i switched from macOS to FreeBSD on my desktop is it working a bit better 18:57:09 this VG2732m-LED from viewsonic is showing its age 18:57:39 yeah well going from a retina to a non-retina display "whatever the heck retina means" is hard 18:58:03 i couldn't go back to 1080p now, i use one sometimes in our home "office" and it's so ugly 18:59:14 i had an apple display.. back in teh day a 23" cinema display dvi version.. that was nice 18:59:41 i sold it as i had no room, at the time, for 300 bucks 18:59:58 which was not bad at all.. now this 2012 15" retina is holding on for dear life 19:02:16 well that is just fun.. installer finishes with a checksum error 19:02:30 recently made the horrific discovery that with three displays in my house, the only 1080p display was our old 55"-ish TV 19:03:15 horrific because the gear I was working on wouldn't boot with a 4K efifb, and neither of the 4K displays let you fake EDID to get 1080p where I need it 19:04:14 no wifi on it either, so had to relocate it across the house to debug its boot failure then move it back 19:09:05 oh no, graphics/drm-kmod is broken on main 19:09:57 oh... or it's trying to use src from /usr/src for some reason... 19:12:15 iirc you have to set SRC_BASE for the port build if you're using a different location for your tree 19:13:03 admittedly haven't built a kmod port in ages, I just cloned the drm-kmod rwpo locally and LOCAL_MODULES it in so that it gets built as a tied kmod w/ buildkernel 19:15:31 actually i think was confused about /usr/src, this is in poudriere so it should get the /usr/src from main 19:17:31 voy4g3r2: i had both the 23" and 30" cinema 19:17:40 they were great 19:18:17 yeah they were 19:18:21 pricey but worth it 19:18:59 hopefully this install of current works.. the latest 20231216 bootonly is giving checksum errors 19:19:29 could be that i am using netatalk to transmit the iso images.. we shall see.. because kenny loggins danger zone 19:23:25 netatalk? what the shit 19:24:05 yeah, why would anyone choose AppleTalk when you could use DECnet Phase V? 19:30:54 rtprio: because it was arleady setup for the time machine .. maybe samba? this is all happening on a mac book.. wanted to make it easy :) 19:31:11 i did setup samba for my music library streaming :) 19:32:22 okay, well maybe i should move this image.. that is 2 images from a file server that were not aligning checksum 19:36:26 ah, fixed it, just needed to update to latest ports tree 19:54:36 well okay.. bootonly does not work on a virtualbox.. time to just try disk1 instead 20:03:34 is the llvm FORTRAN compiler really called 'flang'? this just looks like an obscure swear word to me 20:03:44 god flang it 20:08:04 okay thi sis just odd.. how can 3 different iso files from current all have checksum errors 20:08:36 how are you downloading/copying them? don't say netatalk... 20:08:59 haha 20:09:01 well wget 20:09:05 to get them 20:09:14 i even tried installing directly from machine, same result 20:09:19 i am going to try a virtualbox image now 20:09:31 yes.. i have intertwined netatalk in there :) 20:09:32 if you run the checksum multiple times on the same machine, do you get the same result? 20:14:18 voy4g3r2: because iso newer or older than latest snapshot 20:14:51 they don't get updated at the same time? 20:14:57 if all three are from the same build that probably makes sense if we're fetching one or more set 20:15:39 what checksum, i just downloaded the iso images and went from there.. am i suppose to also download the checksum file? 20:16:14 oh, i thought you were downloading the ISO and then checking the checksum of the ISO you downloaded... but you mean the checksum error is during install 20:16:33 yes, it is during install.. my bad 20:18:23 but now my timemachine backups are acting up also 20:18:30 let me reboot this laptop and give this another try 20:19:06 voy4g3r2: not all dist sets are on the release media, some have to be fetched remotely 20:19:18 iirc the checksums for all are stashed on the media 20:20:01 if you have an older snapshot and have to download a dist set, boom, blows up because dist sets are replaced with each buils 20:20:05 build 20:20:13 (along a branch) 20:21:42 unixwitch: do you use New Flang, or Classic Flang? 20:23:56 I'm getting this error for a non bootable SSD. "GEOM: da2: using the secondary instead -- recovery strongly advised." should I ignore it? 20:25:24 s2r: does it contain a ZFS filesystem? i've had that when using zpool create if the disk already has a GPT label... (seems like a bug) 20:25:44 The device has zfs. pool: zssd - ONLINE --errors: No known data errors 20:26:15 in that case i would just ignore it. *don't* use gpart recover because it will wipe the ZFS label and replace it with whatever was there before 20:26:29 I haven't noticed this error in previous reboots. This time is running 13.2p8 20:39:56 nice how the Dovecot docs for setting up Kerberos tell you to do everything via samba-tool, like no one uses Kerberos except on Windows anymore 20:41:17 <_xor> kevans: Do you know if there's active work going on for the Bluetooth stack? 21:08:52 _xor: pretty sure there's not at all 21:09:20 <_xor> :/ I was wondering if I was missing something other than blued. 22:47:58 unixwitch: I don't do windows. 22:48:25 tmp_: neither do i, i was being a bit sarcastic there 22:48:48 Indeed. I felt it called for an obvious followup. 22:49:27 although i did run into an actual problem, which is that dovecot seems to have no obvious way to map kerberos principals to userdb users... 22:49:36 i guess you need to do that in ldap 22:50:10 Windows is a fun little game launcher. 22:50:59 Not something I've dug into. I work with systems with ldap, kerberos, nss and dovecot. 23:01:27 I don't play games, I wonder if that's why windows and I don't get along 23:02:39 i spent so much time playing /usr/games/larn many years ago. apparently that's been removed from base at some point :-( 23:03:37 oh all of /usr/games was removed? 23:04:09 darn those fun-hating freebsd developers 23:04:18 s/darn/flang 23:07:27 is it bad practice to put comments in manpage sources? i feel like this would make them a lot easier to navigate when editing 23:10:46 Some things from /usr/games moved into /usr/bin 23:12:07 factor, rot13, primes, morse.... But hunt is gone. I ran that one a bit. 23:13:21 unixwitch: if comments are useful, then comments should be put in the man page