00:03:50 Delemas: your PATH will dictate which one gets used when you invoke 'openssl', using the full path will give you a specific version 00:05:32 Delemas: the information from pkg-audit comes from vuxml, you can find a fully-rendered version at https://vuxml.freebsd.org/freebsd/index.html which will do a better job of describing what packages are vulnerable 00:05:34 Title: FreeBSD VuXML - entry date index 00:06:15 parv: i usually start with shallow clones, and then give days later i have the full checkout, and three forks… 00:10:16 interesting, so a 12.2 ko does seems to load on 12.3. I guess all major version's are binary compatable? 00:10:41 That would be minor version difference 00:11:07 Or, did you mean major minor versions? ;-J 00:11:30 yeah, 12.x for example 00:12:12 I do not count on the being compatible 00:12:13 KBI and ABI isn't meant to change with minor versions, but without details it's hard to say if that's the case here. 00:12:36 I probably should play it safe and downgrade back to 12.2 00:12:42 s/the/the minor versions/ 00:12:49 at least until I can get a stable driver for 12.3 00:13:36 It's for this peice of hardware https://www.areca.com.tw/products/nonraid-1320.html 00:14:23 What's the driver called? 00:14:35 arcsas 00:15:06 Doesn't look like it's in base or ports? 00:15:12 it's not 00:15:27 I have to grab it from the manufacture, they provide binaries 00:16:21 Depending on how much the server is used, or if you have another machine and another HBA to test with, it'd be great if you could find out which commit broke the compatibility. 00:16:41 That can done by starting with a 12-STABLE snapshot and then using git-bisect. 00:18:38 Yeah, I have a few of those HBA laying around, they are my favorite, perform really well, etc.. I got to see why their latest versions (2.x series) don't work for me. 00:19:07 I mean.. they load, but the system just goes bonkers and just hangs up 00:23:01 It should be relatively simple to isolate the commit; using an older 12-STABLE snapshot where it works, then using git to grab the source (I'd recommend turning on meta-mode, as this speeds things up rather a lot on subsequent builds). Then you use git-bisect(1) and just build and install the kernel - if it loads once you've booted it, you can build a new version, and once you encounter a bad version you 00:23:08 simply boot the older kernel that the installkernel target saves. 00:23:34 Isolating the commit will allow us to try and determine what happened, and if there should be a fix for it. 01:10:45 <_xor> Hmm, strange. Network interface appears to randomly be going down, "Jan 1 08:55:37 router0 dhclient[49327]: send_packet: Host is down" 01:11:07 <_xor> `service netif restart em0` brings it back up fine. I wonder what's causing it to drop out. 01:19:56 Does the difference between "used" & "lused" (used > lused) -- https://termbin.com/yxll -- mean that compression should be disabled? 01:24:30 parv, Disabled? Because it isn't very much difference? 01:25:42 What does this say for you? zfs list -o compression,compressratio,used,usedds,usedsnap,refer,name 01:27:13 rwp, There are no snapshots; "used" & "refer" are the same number: https://termbin.com/yzxh 01:28:03 So it looks like you are getting 21% compression. That seems useful enough for me that I would keep it. 01:28:14 rwp, I would not have minded if there were small difference iff "lused" were larger than "used" instead of vice versa 01:29:20 Hmm... I admit I missed that ratio direction. 01:31:31 Space usage for source, https://termbin.com/u5zp2 # the usual case of compression 01:31:56 I don't normally look at lused. I have one case of it being that direction. lz4 2.19x 1003M 968M 1003M 0B 1003M zroot/usr/ports 01:32:35 With lused=968M used=1003M refer=1003M 01:32:56 Same here re checking "lused" value; got curious after a run of "git-repack; git-gc" 01:43:57 Ok, had set the compression to "lz4" for datatsets with used > lused. 02:19:44 zfs-find-useless-compression.sh : https://termbin.com/crx1 11:39:48 Hi all, happy newyear 11:40:20 Does anyone know why zfs only releases space of deleted files after a reboot? 11:40:36 like, I had 200GB free on a pool, I deleted 800GB of data but only got back like 20GB 11:40:47 I rebooted, bam, over 1TB of free space on the pool 11:42:03 this is pretty meh as I'm in the process of replacing a big part of my linux iso collection with updated versions, and I keep running out of space while a reboot gives me back TB's of space 11:42:17 no snapshots used as linux isos are easy to get 11:43:01 using a zpool of 2 raidz1 vdevs. each raidz1 vdev has 4 spinning rust HDDs 12:11:11 wow that sux 12:13:59 yeah. I know I should add more disks, but that's for another time 12:32:49 mvanbaak: which FreeBSD / ZFS version? 12:35:09 freebsd 13.1 12:35:38 13.1-RELEASE-p5 amd64 12:35:51 zfs-2.1.4-FreeBSD_g52bad4f23 12:35:53 zfs-kmod-2.1.4-FreeBSD_g52bad4f23 12:38:10 I confirmed there's 0 snapshots with `zfs list -r -t all storage/multimedia` 12:40:05 https://forums.freebsd.org/threads/reclaim-lost-zfs-space.39294/ people having similar issues, but i don't see a clear solution. zfs scrub didn't help 12:40:06 Title: Reclaim lost ZFS space | The FreeBSD Forums 12:46:04 NAME AVAIL USED USEDSNAP USEDDS USEDREFRESERV USEDCHILD 12:46:06 storage/multimedia 550G 35.4T 0B 35.4T 0B 0B 12:46:32 this cant be true as my linux-iso automation just deleted roughly 800GB of data in 30 to 50GB files 12:51:40 this kinda thing keeps popping up in my search for an answer to mvanbaak's issue, https://askubuntu.com/questions/1402578/how-to-restore-the-disk-space-after-deleting-syslog-file-with-18-gb and it's just deeply fascinating to me 12:51:41 Title: 20.04 - How to restore the disk space after deleting syslog file with 18 Gb? - Ask Ubuntu 12:56:17 whehe 12:56:23 I've been googling for days 12:56:32 but haven't found anything that helps 13:08:48 ok, it looks like the files are in use or something 13:09:05 I 'fixed' it without a reboot but with: `for a in bazarr bazarr4k pmm pms qbit radarr radarr4k sab; do iocage restart $a; done` 13:09:55 which is strange as none of these services had any mention of the old files anymore 13:12:05 mvanbaak: what does lsof give you? Well, uhm, you'd have to do that before deleting them, i guess 13:12:33 yeah, the delete is automated 13:13:39 I have linux iso X-version.1 and the tool gets X-version.2, when download is succesful X-version.1 is removed using 'unlink' and X-version.2 is moved into the directory X-version.1 was in 13:14:00 mvanbaak: BTW, iocage has fallen out of support, https://github.com/iocage/iocage/pull/1292#issuecomment-1368531213 13:14:01 Title: Pull `freebsd-update` from active branch of freebsd/freebsd-src by aWZHY0yQH81uOYvH · Pull Request #1292 · iocage/iocage · GitHub 13:15:48 you could truncate before the unlink, given that something is holding onto the files. a server maybe? 13:15:52 ugh 13:15:54 how are you downloading them? 13:16:45 most are usenet, some are torrent 13:17:00 so it's either the sab or qbit jail that grabs the data 13:17:19 torrent would hold on to the files for seeding, unless you explicitly say not to 13:17:31 yeah, I know. they are deleted 13:17:44 (not sure how Usenet works any more…) 13:17:48 if a file in qbit download directory has no hardlinks to it, qbit removes them after 30 days 13:18:06 usenet is just grabbing the files and moving them into the right location 13:18:15 it's like fetching emails 13:19:48 hum, I suspect something in plex 13:20:43 lsof is going to be the tool of choice to track this down 13:20:51 the moment I restarted the pms jail, I gained 450GB of free space 13:23:09 ok, I'll look into that 13:23:13 thanks a lot meena 13:23:14 yeah, Filesystems queue up operations. If something is still holding on to a file it's not really deleted, until that process releases the handle 13:24:20 the file was not used for active playback of the content 13:24:27 so it makes sense that a reboot would fix it. and the fact that rebooting the jails fixes it, too, narrows it down to one of the jails 13:24:32 there were 0 active sessions in plex 13:26:44 https://github.com/freebsd/freebsd-quarterly/blob/main/2022q3/lsof.adoc i wonder if this work has been released yet 13:26:46 Title: freebsd-quarterly/lsof.adoc at main · freebsd/freebsd-quarterly · GitHub 13:26:47 ah, lsof is a port 13:27:25 yeah, could well be it's released then already 13:28:53 it segfaults 13:28:55 lol 13:29:05 cool cool cool 13:29:18 `lsof -v` works 13:29:26 `lsof /path/to/file` segfaults 13:29:27 anything useful in the core? 13:29:56 (time to rebuild with debug symbols!) 13:30:11 I'll need to rebuild it indeed 13:30:47 https://github.com/lsof-org/lsof/issues/263 this one? 13:30:49 Title: lsof segfaults in FreeBSD jails · Issue #263 · lsof-org/lsof · GitHub 13:30:49 263 – There is absolutely no documentation for the dialog library https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263 13:32:33 yups 13:32:39 I have it on the host as well 13:33:09 https://github.com/lsof-org/lsof/issues/264 wonder if this is skladu relevant to your use case 13:33:10 Title: [BUG] lsof +L1 produces no output on FreeBSD after file becomes unlinked. · Issue #264 · lsof-org/lsof · GitHub 13:33:49 i'd stick with the host, given that lsof, in theory, should know about jails and other containers 14:04:12 ok, I'll use fstat 14:04:16 which comes with base 14:04:47 I just realised, the person who's work I'm very excited about, https://github.com/dfr/ocijail has been emailing me about my work https://alpha.pkgbase.live/ 14:04:48 Title: GitHub - dfr/ocijail: An OCI runtime using FreeBSD jail 14:06:43 yeah, I guess I'll have to go hunt for an iocage replacement 14:18:49 mvanbaak: how many jails on how many hosts do you manage? and what iocage features do you use? 14:19:50 pot, bastille, cbsd, are all viable alternatives that are maintained. 14:20:19 https://www.freshports.org/sysutils/mkjail/ might be an option, if you have few jails, and really just need a tool to bootstrap and upgrade them 14:20:20 Title: FreshPorts -- sysutils/mkjail: Fat jail creation script 14:21:04 35 jails on one machine, bootstrap, upgrade, snapshot/rollback, snapshot+zfs send to backup server 14:21:52 I create 'thick' jails as iocage calls them, so I can easily send them to my backup server (and I also used it twice to upgrade my homelab server) 15:07:13 is a gaol where only /usr/local, /etc and /var are writable a thin gaol? 15:07:34 (that's a wrong question, ignore) 15:08:35 mvanbaak: I also prefer thick jails. 15:15:57 anybody with some bectl knowledge around at this time of the year? 15:16:17 tct: some. try me 15:17:22 meena, when I first started using BEs I used them incorrectly. Back then, what I did is creating a new BE, activating it and booting into it. essentially leaving the 'default' BE dangling. Now I want to "fix that" (eg. getting back to always staying on the default BE and instead just creating a new BE when needed and only booting into it when I have to) 15:17:31 for this, I want to delete the current 'default' BE and re-create it from the current state. 15:18:27 here's my bectl: https://pastebin.com/nVACKCYd 15:18:28 Title: jbo@knox:~ % bectl listBE Active Mountpoint Space - Pastebin.com 15:18:50 tct: I don't follow. why? why don't you delete the other things you don't need? 15:18:55 when I try to do: bectl destroy -o default I get this: 15:18:57 cannot destroy 'zroot/ROOT/default/git': dataset is busy 15:18:57 unknown error 15:19:20 meena, I'd like to "always" be on the BE named 'default' 15:20:15 bectl activate ...; bectl delete ...; bectl rename ...; 15:20:59 s/delete/destroy/ 15:21:02 V_PauAmma_V, the problem is that bectl delete doesn't work. apparently there is a busy dataset but that shouldn't be the case as the 'default' BE is not the currently active one 15:21:07 bectl destroy* indeed 15:21:24 Even after a bectl activate? 15:22:10 V_PauAmma_V, yes. as you can see from my linked paste the BE named '20230102' is marked both 'N' and 'R' 15:22:18 why is it busy? 15:22:31 Mounted somewhere maybe? 15:23:14 not with `bectl mount` 15:24:47 Maybe with zfs mount? (Or do you need to reboot after the bectl activate? I'm not very familiar with BEs.) 15:25:31 already rebooted. the 'Active' column of 'bectl list' also indicates that it's the currently active BE 15:25:42 I'll check for other mounts 15:27:43 mount, zfs list, lsof, fstat, etc 15:28:02 on it 15:35:24 my jails are all mounting datasets from zroot/ROOT/default although the 'default' BE is not the currently active one 15:35:28 should I be worried? :s 15:35:46 or does bectl somehow alias whatever BE is currently active to zroot/ROOT/default? 16:09:33 tct: how did you create your jails? 16:09:46 meena, using sysutils/cbsd 16:10:29 * meena puts cbsd on her shitlist 16:10:36 :D 16:10:48 evaluated it like 5 or 10 years ago - haven't looked back 16:11:08 mainly using that because it also allows to manage VMs (bhyve, xen, qemu...) all in one tool 16:11:12 and it's just shell scripts, ofc. 16:11:42 https://cbsd.io/cbsd/Installing-cbsd/ 16:11:43 Title: Installing CBSD - CBSD 16:13:33 tct: basically, you told cbsd to use your ROOT as a base for creating jails, and now that's a problem 16:14:09 meena, that is my current theory too - and I don't know yet how to test this theory and how to recover from it (if it is the case) 16:14:12 might have hosed this one 16:14:31 meena, however, I have four different hosts all running a similar setup (FreeBSD 13.1 with BEs and sysutils/cbsd) 16:14:49 the only difference on this host is that I am not on the 'default' BE 16:16:16 tct: what's the "root" of your cbsd installation on this host vs others? what method do you use (clones vs snapshots) on this host vs others? 16:16:45 maybe all you need to do is a targeted "promote"… 16:16:47 meena, cbsd working dir is set to "/usr/jails" that is the same on all other hosts too 16:17:03 meena, I have some jail snapshots which are created using `cbsd jsnapshot mode=create` 16:17:28 meena, but I can't delete those jail snapshots either :D 16:18:18 but you might be able to promote them, and then you'll be able to delete the old "default" BE 16:18:34 meena, promote in which context? 16:18:45 zfs dataset? 16:19:05 meena, I don't have any ZFS clones, only snapshots 16:20:17 clones are created from snapshot 16:20:46 how can I verify that my jails are indeed using datasets from the "incorrect BE" ? 16:20:50 terminology might fail me on this one. 16:20:55 still don't fully understand the situation 16:31:02 tct: the core issues is that something (probably one of your jails) is still holding onto zroot/ROOT/default/git. it might be mounted, or a snapshot relationship, or something is directly accessing it 16:31:37 tct: `zfs list -o mounted,jailed,canmount,name,mountpoint -r zroot/ROOT` 16:31:37 meena, indeed. an excerpt of `zfs list` is shown here: https://forums.freebsd.org/threads/unable-to-delete-be.87616/#post-593576 16:31:38 Title: Unable to delete BE | The FreeBSD Forums 16:32:45 tct: looking at what you posted in forum, here's what I would do 16:33:06 tct: how did you create your BEs? 16:33:13 meena, bectl create 16:33:18 zfs unmount zroot/ROOT/default/{blog.,cppproperties,emby,git,irc,nextcloud} 16:33:30 that won't shell expand, but my meaning should be clear 16:34:29 then, work out where /usr/jails is mounted (I guess its a subdir of / i.e. zroot/ROOT/$ACTIVE_BE ) 16:35:05 zfs create -o mountpoint=/usr/jails -o canmount=off zroot/usr/jails 16:35:16 zfs create -o mountpoint=/usr/jails-data -o canmount=off zroot/usr/jails-data 16:35:38 this makes 2 container datasets (non-mountable, just for keeping your layout simple) 16:35:46 then you can move these 3 datasets under that dir 16:36:06 zfs rename zroot/ROOT/default/blog zroot/usr/jails/jails-data/blog 16:36:14 etc 16:36:44 dch, is this with the goal of getting the jail zfs datasets "outside" of the BEs? 16:36:46 I personally would skip all the -data suffixes, life is *much* simpler if each dataset maps cleanly to each path 16:37:42 after this, you can run `zfs snapshot -r zroot/usr/jails/jails-data@`date -u +%Y%m%d-%H%M` just before doing upgrades 16:37:44 I might have some knowledge gap here: Wouldn't the idea be that creating a BE also "includes" my jails? And when I boot into a different BE the datasets are "re-mapped" and the jails will also be as of the state of the BE? 16:37:58 tct: you can do either 16:38:21 but as somebody who runs a lot of jails, I tend to separate out the base OS and jails completely 16:38:41 so I typically do upgrade/update FreeBSD in base OS (all of zroot/ROOT/default ) 16:38:44 check all things work 16:38:55 and then upgrade/re-deploy all jails one by one 16:39:01 dch, thank you for outlining your idea above. Before attempting any of that I'd really want to understand this situation better. I have no idea how this situation came to be. My idea/intention is that creating a BE also includes jails. cbsd puts everything under /usr/jails which would be part of what the BEs cover, no? 16:39:35 tct: you may find https://freeside.skunkwerks.at/~dch/FreeBSD/diy-jails/tutorial.html useful, its the jails presentation from EuroBSDcon 2022 btw. AMA. 16:39:37 Title: Jails from Scratch 2022 16:40:03 the /usr/jails is just a mountpoint. 16:40:22 dch, thanks, I'll check that out! 16:40:27 you can provide this mountpoint by a dataset under zroot/ROOT/default/messy 16:40:48 which gets you in the situation you are in, upgrading base OS also requires fiddling with all the jails 16:41:04 I highly recommend having separate dataset(s) for each jail 16:41:10 and keeping them outside the base OS tree 16:41:14 dch, that is what cbsd is doing 16:41:16 both jails, and the data inside it 16:41:25 tct: not the way you have it set up 16:41:44 dch, zfs list shows one dataset per jail? 16:41:46 dir /usr/jails is clearly "inside" zroot/ROOT/default 16:41:56 right 16:42:04 or is (in cbsd) /usr/jails completely empty 16:42:26 nah, /usr/jails contains all the stuff 16:42:33 technical term 16:43:57 dch, so we agree that as per my current situation, jail datasets are "inside" of zroot/ROOT/default (which is what I want (or wanted, at least)). This means that creating a BE also snapshots/clones the jails. so how could I end up in a situation where cbsd/jails use the 'default' BE but the system is on the '20230102' BE? 16:44:21 you can't 16:44:34 then why is it this way? :D 16:44:41 as most of CBSD docs are in Russian, I'm not familiar with it 16:44:57 tct, I don't want to give bad CBSD advice as I really am not familiar with it 16:45:30 but what I see here is that you have an awkward mess 16:46:00 when you create a new BE, the subsidiary datasets aren't recursively copied, I guess 16:46:07 dch, that is indeed what I see as well. and I don't have that awkward mess on any of my other hosts. This is my playground host but still... 16:46:59 dch, so basically from here the idea would be to move the jail datasets outside of zroot/ROOT, then delete the `default` BE, re-create a new `default` BE and moving the jail datasets back? 16:54:56 tct I think you're best off finding a place where the CBSD people hang out and ask them for more advice 16:55:17 dch, I'll do that. Thank you for your help - it's much appreciated! 16:55:25 I can give zfs tips easily enough, but I can't know if any of this would break your setup 16:55:39 dch, I fully understand that :) 16:55:47 oh https://cbsd.io/cbsd/What-you-need-to-know-about/ is now all in English (how times change) but a quick skim I'm none the wiser 16:55:48 Title: What you need to know about CBSD - CBSD 16:56:32 https://www.bsdstore.ru/en/about.html#contactus is probably a good start 16:56:32 yeah, cbsd documentation has improved notably over the past few years. 16:56:37 Title: CBSD — FreeBSD Jail and Bhyve Management Tools 16:56:54 already on it: https://github.com/cbsd/cbsd/issues/722 16:56:56 Title: Cannot delete jail snapshots · Issue #722 · cbsd/cbsd · GitHub 16:56:56 722 – Off-by-one error in wbkgd() in ncurses https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=722 16:58:17 i, myself, somehow overwhelme by numerous jail managers 16:58:58 same here. after testing many I eventually settled with cbsd for the fast that it also does VM management and migration stuff. haven't had a single issue with it that wouldn't have been caused by myself so far (+8 years of using it) 16:59:21 ditto. thats why I stopped using them and just have a bare single script now 16:59:32 cbsd has lots of cool features 16:59:43 I think I should have done that too. at least that's what I usually do. as little clutter as possible. 17:05:24 dch: thx for the link 17:06:08 dch, is that tutorial you linked on an IPv6 only network by any chance? 17:06:39 I get a timeout on my end 17:06:55 no, but it is on my computer here 17:07:22 I'm afk for dinner, I'll fix it later. the source is https://git.sr.ht/~dch/diy-jails-tutorial/ 17:07:23 Title: ~dch/diy-jails-tutorial - sourcehut git 17:08:02 thanks & enjoy dinner! 17:25:26 is there an automated way to update leap-seconds.list? 17:31:28 Yes. /etc/periodic/daily/480.leapfile-ntpd, done daily, activated by "sysrc daily_ntpd_leapfile_enable=YES" 17:40:32 That is, if you mean /var/db/ntpd.leap-seconds.list. 17:44:31 tct, link works fine here from outside. I see that VimDiesel also fetched it ok, so its not just a Works On My Machine thing. 17:49:16 V_PauAmma_V: that's it! 18:15:16 hi, my computer keeps crashing, I can't figure it out. dmesg outputs drmn0: [drm] GPU HANG: ecode 6:1:85fffffc, in WebKitWebProcess [100957] 18:15:16 drmn0: [drm] WebKitWebProcess[100957] context reset due to GPU hang 18:15:32 anyone have any ideas? 18:17:18 i seeing similar for intel card on laptop. i reported similar problem. i have disabled intel card on laptop 18:17:52 how do you disable the card? 18:18:17 in BIOS 18:18:43 this laptop has intel an nvidia and it's possible to run either one ( or both ) 18:19:01 oh i see. i think mine just has an intel 18:19:10 this annoyance not fixed in drm-kmod ( for me, at least ) 18:19:35 i periodically check drm-kmod ( from git ) but problem persist 18:19:49 no idea what is the reason. 18:22:55 upstream ( freedesktop.org, intel ) has numerous bug reports with "GPU hang" pattern and it is all unclear what was the fixes. i suspect, that drm-kmod missing certain things in linuxKPI ( or just lagging behind the source code ) 18:54:14 hi folks! Anybody knows what ACLs are for in ZFS? FreeBSD defaults to acltype=nfsv4 when creating ZFS datasets, while the default on Linux is acltype=off. https://www.freebsd.org/cgi/man.cgi?query=zfsprops&apropos=0&sektion=0&manpath=FreeBSD+13.1-RELEASE+and+Ports&arch=default&format=html 18:54:15 Title: zfsprops 18:55:06 NFS ACLs cause issues with ansible, so I am considering disabling them. But I have a hard time understanding the impact of that. 20:13:47 michelem: Linux doesn't support NFSv4 ACLs on ZFS, whereas it's what Illumos and FreeBSD default to. 20:14:44 If ansible has problems with NFSv4 ACLs, that seems like a problem with ansible? At least in so far as they're made to be compatile with lots of things including Windows ACLs. 20:15:01 debdrup, did not know that - thanks 20:15:40 BarnabasDK: it also doesn't look like anyone involved in Linux has any interest in implementing them, despite NFSv4 being nominally supported. 20:16:32 no it seems if you want support for that then you need to run behind samba 20:20:06 nonsense - I am thinking of my smb drives 20:20:27 nfs - yes I understand 20:23:51 Is it important on a high level to tell apart acls on zfs as opposed to for example ext 20:24:07 provided the infrastructure supports it 20:40:28 debdrup: thanks. I've seen from the manual that Linux lacks support for them. I was just wondering why they are enabled by default in FreeBSD. UFS does not seem to have ACLs enabled by default. 20:42:42 michelem: sure UFS has ACL support. 20:43:02 Specifically, it's also NFSv4. 20:43:27 See getfacl(1) et al. 20:44:33 ok. I did not know it's enabled by default. Thanks. 20:45:27 kern.features.ufs_acl should be set to 1 too. 20:45:48 Hrm. If "sysctl net.wlan.devices" is empty, is that all she wrote for FreeBSD wifi on a laptop, aside from things like virtualization with some other OS providing wifi? 20:46:20 To get POSIX 1e ACLs, you'll neet to set the acl flag via mount -o I think, but it's been too long since I've used them. 20:46:57 mason: there may be drivers in ports 20:47:01 they are actually not set by default, indeed. 20:47:33 https://dpaste.org/9WGvj 20:48:19 Huh. Wonder when that changed. 20:49:04 the problem is surely with ansible. It's just a corner case which they'll never fix. So I was wondering if the cause of the problem is worth it. Because UFS-based systems go without ACLs by default, I was wondering why it was chosen to have ACLs in ZFS instead. 20:51:05 I suspect, but can't be arsed to go look, that it might be because Sun had NFS ACLs. 20:51:23 yeah, I guess you're right 20:51:56 anyway, thanks much for the help debdrup 20:52:02 no worries 21:45:05 Nice, I have a freebsd instance in Oracle cloud :D 22:11:07 rogersm: same 22:33:32 dang. i'm so close to getting hdhomerun_record running on aarch64. with 14.0-current it'll run in linux compatibility mode, but for some reason it's detecting its ip as the broadcast ip instead of the interface address