00:02:57 Some theory: https://forum.netgate.com/topic/2322/calculating-the-required-bandwidth-for-ack-queues-for-asymetric-link/7 00:02:58 Title: Calculating the required bandwidth for ACK queues for asymetric link | Netgate Forum 00:33:14 mason: altq, yeah 00:33:42 mason: the firewall improves the more letters you remove from 'ipfw' 00:38:44 heh 00:46:44 I dunno. w doesn't look like much of one to me. 00:47:30 yeah, but f is off the chain 00:47:49 Anyone out here running unbound on opnsense ? 01:00:37 kevans: yes, f or p would be the next one 01:06:03 Hm, I'm reading about ack filtering, distinct from prioritizing them. Does altq do that too? 01:06:09 c.f. https://lwn.net/Articles/758353/ 01:06:10 Title: Let them run CAKE [LWN.net] 01:24:29 Looks like I can do ack filtering via Linux or ack prioritizing with altq. That's unfortunate, having to choose. 02:43:49 ugh 02:43:59 I was upgrading a box from 12.1 to 13.2 and ran the first freebsd-update install 02:44:10 due to inattention ran it a second time without rebooting 02:44:21 and all hell broke loose 02:44:33 I hard rebooted but now it says all kinds of libraries are broken 02:44:56 stuff like /usr/lib/lib/libmd.so.6 invalid format, etc 02:45:01 am I hosed hosed ? 02:46:18 last1: does 13.2 have /rescue/fetch? 02:46:49 if you can get to a rescue shell, you can always /rescue/fetch base.txz and /rescue/tar it 02:47:53 I booted to single user mode 02:48:00 tried running freebsd-update install here 02:48:22 it says: ld-elf.so.1 /lib/libmd.so.6 invalid file format 02:52:09 last1: Try what kevans is suggestion. It'll work. 02:52:16 suggesting* 02:52:27 is the single user mode the rescue shell ? 02:52:30 can I do it from there ? 02:52:46 last1: From anywhere you have a shell, /rescue has statically-linked binaries 02:52:58 you could do it from single user, but you do need to manually put your NIC up if you're going into single-user 02:53:05 yeah that's fine 02:53:52 ah no it's not 02:53:53 lol 02:53:58 ? 02:53:58 ifconfig reports invalid elf file 02:54:02 /rescue/ifconfig 02:54:49 in general, /rescue should have everything to help get out of scenarios precisely like this 02:55:55 hmm, wpa_supplicant is notably missing from /rescue; that would be cool 02:56:53 darn, 13.2 has no /rescue/fetch 02:57:11 sh /rescue/fetch file not found 02:57:15 bah 02:58:16 i'd bet a -CURRENT /rescue/fetch wouldn't rely on any kernel behavior you don't have 02:58:32 but getting it on there is the tricky part, going to need some bootable media at this point 02:59:09 oh wow, pretty silly for freebsd-update install to allow itself to run twice and thrash the whole system 03:03:22 ok, so I got the bootable media 03:03:35 I boot with that, drop to shell, mount my / and drop base.txt in there ? 03:03:42 base.txz ? 03:03:58 yeah, pretty much; extracting base.txz over your / should generally be safe 03:04:15 wait 03:04:17 is this zfs or ufs? 03:04:41 ufs 03:04:48 ah, ok 03:05:30 that's unfortunate; with zfs this would've been just a "*sigh* /rescue/bectl activate blah; /rescue/reboot; profit" 03:08:46 Only wild-eyes fanatics use ZFS. 03:09:00 eyed - really kills the trolling when I typo 03:11:48 in the usb boot 03:11:51 do I choose shell or live cd 03:12:47 last1: live cd ought to be fairly full-featured 03:13:55 last1: you'll want to fetch https://download.freebsd.org/releases/amd64/13.2-RELEASE/base.txz 03:14:00 presuming amd64 03:15:34 yep 03:18:43 ijm fetching 03:18:48 I'm fetching, yay 03:19:17 so simply xz -d base.txz 03:19:20 then tar -xf base.tar ? 03:19:42 tar will decompress for you generally 03:20:04 k, fingers crossed 03:20:05 mount up root and any other filesystems that matter - probably just root, cd into it, untar 03:20:17 yeah yeah, I got it under /mnt 03:20:21 or untar with -C or similar 03:21:05 it says: can't unlink already existing object 03:22:03 https://imgur.com/a/fMhwVxN 03:22:04 Title: Imgur: The magic of the Internet 03:22:49 Well. tar has an --unlink option that unlinks before unpacking, which could be useful 03:23:01 I'm always hesitant to recommend anything that deletes stuff of course. 03:24:30 https://imgur.com/a/G0Rb6jB 03:24:31 Title: Imgur: The magic of the Internet 03:24:35 now am I hosed ? :) 03:25:25 Hrm. Hopefully someone will chime in with better ideas, but I'd be tempted to unmount and give fsck a look at it. 03:26:00 "This post may contain erotic or adult imagery" 03:26:04 Also, note that you'll probably want to save some things in /etc, as I just remembered that unlike, say, NetBSD, FreeBSD doesn't ship etc.tgz separately. 03:26:11 kevans: Hot terminal action. 03:26:33 base.txz shouldn't wipe out anything pertinent in /etc 03:26:40 I'm thinking at this point I may just reinstall everything 03:26:59 kevans: It doesn't include an empty password, by way of example? 03:27:09 i have a quick question im running kali linux in freebsd bhyve is there a way to access the kali linux gui or is this not supported yet in bhyve ? 03:27:12 I don't believe so, passwd is considered a config file 03:27:27 last1: you're not completely hosed, just some weird stuff going on here 03:28:08 what does ls say about some of these? ld-elf*so and libc are probably noschg, but the error doesn't match what I would expect from noschg I don't think 03:28:21 those files are special 03:28:24 I tried removing them 03:28:25 didn't work 03:28:30 oh, right, flags 03:29:00 er, schg 03:29:12 hm, chflags doesn't have a recursive option 03:29:14 try `chflags noschg ` 03:30:00 find . -flags schg -print might be interesting 03:31:12 rather, find . -flags schg -print 03:31:16 I did chflags noschg on thsoe files 03:31:18 removed them 03:31:22 ran tar again 03:31:36 argh, sorry, meant +schg - tired 03:31:43 Ill reboot see if the old system fancies a run now 03:33:44 yep, came up lol 03:33:46 but users are gone 03:33:50 let me see what else is gone 03:34:30 last1: That'd be the passwd file I was mentioning. =cough= 03:36:11 and vi depends on libncursesw.so.8 which I no longer have lol 03:36:16 I just have libncursesw.so.9 now 03:36:34 last1: That's odd. The tarball ought to have been internally consistent. 03:36:35 is there another edit that lets me modify the /etc/group file ? 03:36:50 there should be a copy in /var/backups for some of these 03:37:14 kevans: You should push for a separate etc.tgz like what NetBSD does. Useful for these situations. 03:37:25 There's a lot of dancing around upgrades that can be avoided. 03:37:36 is there a way to redo the upgrade process in a more controlled environment ? 03:37:47 cuz now I feel some files haven't been updated and whatnot 03:37:58 last1: ZFS is the most common answer because you can snapshot. Unsure what the best way is with UFS. 03:39:18 so there's nothing like freebsd-update -r 13.2-RELEASE reinstall ? 03:39:47 Not as such, no. But the tarballs really ought to be internally consistent. That's worth exploring. 03:39:57 tar exits after a few errors 03:40:07 so it doesn't complet extracting everything 03:40:08 last1: More of the same sort? 03:40:11 yeah 03:40:15 can't unlink, etc, etc 03:40:21 schg errors 03:40:33 last1: As noted, find . -flags +schg -print 03:40:42 so now /bin/vi is the old version 03:40:51 while /lib has the new libs 03:40:53 hence that error 03:40:57 then if you're very confident with the list, you can swap -delete for the -print 03:41:03 but note that it's quite dangerous to do this 03:41:41 last1: And remember the statically-linked bits in /rescue, which should include vi 03:41:55 but you want to get that tarball unpacked fully before trying to use the system 03:42:13 mason: yeah, I tend to agree now. up until, oh, 5 minutes ago, I would've sworn up and down that base.txz didn't contain anything pertinent in /etc :-) 03:42:51 I guess etc.txz would contain both etc/ and the etcupdate metadata that goes with it 03:43:05 It's been a while so I don't remember precisely what they included. 03:44:55 I really care just about the /var partition on this machien 03:45:01 can I reinstall and somehow keep /var in there ? 03:45:42 or rather, can I fool the system that it's 12.1 again and run freebsd-update on it ? 03:45:53 last1: You can rename it - careful with targeting the find -delete if you end up doing that so that you don't reap through it, in case there's anything schg in there 03:46:03 Don't think that'll work, unfortunately. 03:46:53 you already updated base to 13.2, is kernel 13.2? if so, you don't really have much else to do besides maybe some config files that need merged and pkgs 03:47:08 oh, this was 12.x to 13.x 03:47:23 yeah, nvm, I got it somehow 03:47:32 I re-extracted base.txz in multi-user 03:47:34 it worked here lol 03:47:56 last1: It's usually not as painful as what you just went through, FWIW. 03:48:33 for sure, but it seems silly to go through this after running freebsd-install twice you know 03:48:46 I just did arrow-up enter out of habit, and voila 03:49:08 basepkgs will arrive at some point 03:50:11 rebooting now for good measure 03:51:01 yep, came back up. huzzah 03:51:54 \o/ 03:51:57 thank you for your help fellas 03:52:01 much appreciated 03:52:23 happy to help 04:16:05 If I am running 13.2-release is there a way to just update if I download 14.0-current image? 04:21:08 prob shouldn't be using current if you have to ask that 04:23:38 Appreciate the input 07:42:17 llua: and yet, i have made it very easy for people to do: https://alpha.pkgbase.live 07:42:18 Title: Unofficial FreeBSD pkgbase repository 07:49:03 FIRECRACKER fails to link 08:40:18 meena: it should be just 'base hash' 08:40:40 (the help widget needs to be updated, yes) 08:41:07 yuripv: i tried several things, but the preview doesn't do shit 08:41:23 try base hash, preview will show it 08:42:01 oh, it probably does not work when *creating* PR, i remember some reports about it 08:42:12 works when updating PR though (the preview) 08:44:18 btw, the issue you reported is discussed here: https://lists.freebsd.org/archives/dev-commits-src-main/2023-July/016995.html 08:44:19 Title: git: 60381fd1ee86 - main - memdesc: Retire MEMDESC_CCB. 08:46:06 I'm surprised FIRECRACKER doesn't include CAM 08:46:44 grumble. why is the dev-commits-src-main list sending me malformed MIME messages 08:47:21 CAM has a lot of delay stuff at startup. 08:50:13 that's a good reason to not include it in FIRECRACKER. or speed it up 08:51:54 I think whatever's generating dev-commits mail has a bug; it seems to sometimes generate multipart/* messages with quoted-printable transfer encoding 08:59:10 you mean the replies to commit messages? 09:03:24 no 09:03:38 looking at the one I bounced, it's an actual commit 09:04:45 anyone by any chance have a copy of message 17037 on dev-commits-src-main including full headers? 09:06:15 https://lists.freebsd.org/archives/dev-commits-src-main/2023-July/017037.txt :) 09:06:18 the copy in the archives doesn't have the offending headers 09:06:24 ah sorry 09:06:37 i.e. whatever mangled it happened after the copy was archived 09:29:58 RhodiumToad: i reckon that our archiver sanitizes headers 09:30:46 I think it's the opposite, that the mailing list manager is sometimes adding headers 09:30:56 but I can't tell until I see the headers :-) 11:57:59 hey, ive been trying to set up a windows wirtual machine through bhyve, but it never seems to actually start even though i have the iso for windows and bhyve-firmware 12:03:26 what options are you using? 12:04:09 and are you using a vnc client for display? does anything show up? 12:17:14 options, i think i just copied an uefi config from a website 12:17:26 as dor vnc, im using tigervnc. doas vm list says the vm is stopped 13:27:36 Hi Is it possible to mount a subpart of my fs into a jail ? I have confusing info on the net. (As a possible security issue with jail-mount) 13:28:35 use nullfs 13:29:29 the security impact will be up to you to deduce in how you are using it. some automated jail systems already do this using the mounts from / 13:29:29 from outside the jail, you can nullmount basically anything into it as you please 13:30:42 (I have a vm running poudriere at the moment, and it has like 40 nullmounts just because of that) 13:30:48 personally i like to have a jail that mimics the rootfs / exactly and then remount with nullfs from there 13:39:41 if you have a good handle on zfs ... then this becomes very easy 13:43:19 thank you. Documentation about that is a little bit old. thanks again 13:43:52 np brother BSD'r 14:17:18 hi, any way to run old 32 bit stuff in a 64 bits FreeBSD modern installation? 14:17:26 applixware # ./install 14:17:29 ld-elf32.so.1: Shared object "libX11.so.6" not found, required by "install" 14:17:42 https://archive.org/details/Applixware_Office_for_FreeBSD_Walnut_Creek_November_1999 14:17:43 Title: Applixware Office for FreeBSD (Walnut Creek) (November 1999) : Free Download, Borrow, and Streaming : Internet Archive 14:18:54 uskerine: you'll need 32-bit versions of any libraries that the old software needs 14:19:10 Is it doable or is it going to be a hell on earth? 14:19:24 probably easier in a jail 14:20:13 are jails like containers for FreeBSD? 14:20:16 but I don't know where you'd find the necessary old packages 14:20:19 yes 14:20:28 ports have archives, but I feel like x11 hasn't changed much in the past 24 years 14:20:38 uskerine: yes, more closely related to Linux's OpenVZ than containers, but the same similar idea 14:21:04 interesting, libX11 is indeed still version .6 14:21:23 so maybe just installing 32-bit X11 packages in the jail would do 14:22:48 Well I think I will save the task for one of those days where you feel like learning something. Does not sounds like something to do in half an hour. I just found that CD and I was curious to see applixware in action (in all its Motif/X11 shine) 14:39:03 I didn't see anything inside jail. I am using mount parameter https://bpa.st/2XTQ. What I am doing wrong ? /usr/home/mik is empty 14:54:02 it seems mount option mount nullfs inside the host. Is nto what I want . I want to share existing directory on my host with the jail. Is it possible ? 14:56:56 ah ok got it 14:57:59 the mount line should be /path/to/jail/some/dir /home/whatever nullfs ... 14:58:24 er sorry 14:58:36 /home/whatever /path/to/jail/some/dir nullfs ... 15:02:08 and why is there no manpage for ucl 15:12:16 lol 15:21:09 dch: hey! do you have knot-resolver setup guide anywhere? 15:22:29 Yes RhodiumToad Did that indeed 15:22:37 I did* 15:22:47 angry_vincent, just made me lookup knot ... thanks man 15:31:06 Midjak: you can also do /home/whatever $path/home/whatever nullfs ... 15:31:12 I would like to use this jail for building stuff from amd64 to armv7. As I understand I juste need to buildwolrd into this arch. Right ? 15:31:50 do you want to build ports, or software of your own? 15:31:54 Well I gave the path from the jail which is an actual path in my system 15:32:09 a go program 15:32:19 I need sdl2 15:33:36 there's more to it than just having a jail 15:34:17 the best way to cross-build packages is to use poudriere, which knows how to mix native and qemu-static 15:34:32 well with go as soon we don't need an external lib no 15:34:52 I don't want package it's my own program 15:35:13 I have no idea if it's even possible to set up a go cross-compiler5 15:36:04 * RhodiumToad does not use go 15:36:23 https://github.com/veandco/go-sdl2 15:36:25 Title: GitHub - veandco/go-sdl2: SDL2 binding for Go 15:36:45 cross-building freebsd itself is amazingly simple, but that won't help you much 15:36:57 https://github.com/veandco/go-sdl2#static-compilation 15:36:59 Title: GitHub - veandco/go-sdl2: SDL2 binding for Go 15:37:08 too bad... 15:37:35 I thought with an armv7 world it would be ok 15:38:32 there is something called binmisc 15:38:38 maybe it could help? 15:39:16 if go will let you cross-compile, do you even need an armv7 world? 15:41:01 ultimate goal is ? 15:41:12 binmisc combined with qemu-user-static is how poudriere can do cross-builds for ports 15:42:10 this is what I get into the amd64 env https://bpa.st/V55A 15:42:11 Title: View paste V55A 15:42:43 ah good. i did not know poudriere does it but maybe was on right track about it 15:42:53 /usr/include/sys 15:43:04 (best way to set up binmisc is to install qemu-user-static and do sysrc qemu_user_static_enable="YES", then service qemu_user_static start) 15:44:02 I found nothing about binmisc 15:45:07 Midjak: ah. ok. in that case, do make TARGET_ARCH=armv7 buildworld and then make DESTDIR=/your/jail TARGET_ARCH=armv7 installworld distribution 15:45:16 (in /usr/src) 15:45:18 I am using this https://wiki.freebsd.org/arm/crossbuild 15:45:20 Title: arm/crossbuild - FreeBSD Wiki 15:45:49 ah cool 15:46:16 what id distribution meaning ? 15:46:19 but the resulting jail won't run unless you install and enable qemu-user-static 15:46:37 I am doing buildworld right now 15:46:47 make DESTDIR=... distribution is responsible for installing most of the config files and some other directory setup 15:47:02 Thanks a lot. 15:47:11 do NOT run it without DESTDIR=, it can wipe out your whole /etc if misused 15:47:31 * RhodiumToad has made that mistake 15:47:41 Where is these is documented ? I have a real hardtime to find information abotu that? 15:47:55 see the start of /usr/src/Makefile 15:48:09 ok that's was the reason I will do that inside a jail 15:48:23 though mention of the distribution target seems to have vanished 15:48:25 But I will get the semae result indeed 15:49:17 So I need to do that touside the jail right ? 15:49:42 do what? 15:49:52 the buildworld 15:49:59 no ? 15:50:09 your source tree is outside the jail? 15:50:10 because I cannot run the jail 15:50:16 no 15:50:43 where is it then? 15:50:44 but If I install world jail will continue working ? 15:51:07 in /usrc/src inside the jail 15:51:25 you use DESTDIR= to tell it where to install to. the place where you install the armv7 binaries will NOT work as a jail, unless you use qemu-user-static 15:51:48 well I don't need jail 15:51:54 (because you can't execute armv7 code on an amd64) 15:52:29 I have to find a way to give this DISTDIR to go build 15:52:36 DESTDIR 15:53:28 > because you can't execute armv7 code on an amd64 15:53:28 yes 15:53:44 you'll have to tell it to get all include files from there rather than from /usr/include 15:53:59 I don't know what else it might need 15:53:59 I think I need to look that for bo build I think 15:54:09 go is your problem, not mine 15:55:32 fair enough. But I am not sure it will be easier with another language :-) 15:57:50 if I needed to do it with something written in C or C++, I'd make a port for it, test it on amd64, then use poudriere to cross-build it 15:58:10 * RhodiumToad has, in fact, done this 16:02:30 to be fair, the arm people are working on arm32 support for aarch64 16:04:49 yes, but that only helps if you have an aarch64 :-) 16:04:51 cool in order to have only one image running on various arm arch right ? 16:05:09 emulate it 16:05:15 ok 16:05:30 why emulate an aarch64 rather than an armv7? 16:07:14 I have read that corssbuilding freebsd for ARM v7 needs qemu. (this is what i try to avoid in fact) 16:08:26 no. crossbuilding freebsd _itself_ requires nothing. 16:08:46 crossbuilding _ports_ for armv7 on amd64 requires qemu. 16:13:00 hi 16:13:26 unless you're crossbuilding FreeBSD, in which case it does require qemu-user-static, but I'm not sure it actually uses it :D 16:14:11 I use this code in my installation script -> chroot $BSD_ROOTFS /bin/sh < and I wonder why it doesn't work while installing freebsd 16:14:38 $BSD_ROOTFS is correct for sure 16:15:04 humm ok 16:15:59 Iget this error with buildworld disctriution https://bpa.st/5MBQ 16:16:00 Title: View paste 5MBQ 16:16:11 may i share my script with you? 16:16:30 Maybe something to allow into the jail 16:16:33 meena: why would crossbuilding freebsd require qemu? 16:16:45 meena: (I do this a _lot_) 16:17:06 wikan: "does not work" -- in what way? 16:17:43 RhodiumToad: qemu-user-static, not qemu. and it probably needs it because ports requires it, and whoever built the (Pkg)Base build feature didn't look any further. 16:17:57 Midjak: you'd need allow.chflags, or tell installworld not to do chflags 16:18:28 meena: yes, you need qemu-user-static to build ports, and NO, you do not need it to build freebsd itself 16:18:45 RhodiumToad: i know that. poudriere doesn't. 16:18:59 meena: if pkgbase is requiring it, I assume it's to run the target build of pkg 16:19:08 https://github.com/freebsd/poudriere/issues/1048 16:19:10 Title: PkgBase: why does poudriere require qemu to cross build FreeBSD? · Issue #1048 · freebsd/poudriere · GitHub 16:19:11 1048 – ep driver fails to detect card when told specific values https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=1048 16:19:13 thank you I was looking this 16:19:18 https://pastebin.mozilla.org/TBhyajHz 16:19:19 Title: Mozilla Community Pastebin/TBhyajHz (Bash) 16:19:51 my installation script breaks around 217 line 16:19:55 RhodiumToad: ah, i didn't consider pkg… but, doesn't base come with pkg and pkg-static? 16:19:59 wikan: breaks with what error? 16:20:05 meena: nope 16:20:25 right, it doesn't. it comes with pkg-bootstrap… 16:20:27 ha, i am really sorry but I can't tell you what error because I don't remember now. 16:20:28 meena: there's a 'pkg' command in base, but it does nothing except try to fetch and install the real pkg 16:20:39 but it was shell error 16:20:51 wikan: then go away and reproduce it 16:20:54 and that might be fraught if we don't build ports for that arch 16:20:58 maybe I would try to install freebsd on virtual machine 16:21:06 you can't expect people to help you if you can't tell them the error you got 16:22:04 wikan: and… if you install in a virtual machine and it works, then maybe the error was specific to the hardware… 16:22:41 will try 16:24:13 wikan: btw, you don't need chroot to do that 16:25:01 pw -R "$BSD_ROOTFS" ... 16:26:04 right. i wanted to fix pw to work without root… 16:26:12 i should put that on a real todo list 16:26:36 hmmm RhodiumToad 16:28:30 echo "$BSD_CFG_ROOT_PASS" | pw -R "$BSD_ROOTFS" usermod -n root -h 0 16:28:35 is it correct? 16:29:13 should work, though I use -h 3 3<&0 16:29:52 (actually i use -H, but that's similar) 16:30:11 secure_data | awk -F':' -v user="root" '$1==user { print $2 }' | pwcmd usermod root -s /bin/sh -H 3 3<&0 16:30:20 so, what is wrong with chroot? 16:30:27 where pwcmd is a function that does pw -R "$rootdir" "$@" 16:30:56 wikan: how on earth can we know that unless you tell us the error? 16:31:25 wait, will install soon 16:32:23 downloaded 16:36:39 will back, must restart my X session 16:36:50 i don't have privileges to run VM :) 17:36:05 i haven't checked in on raidz expansion. how has that come along? is it in openzfs yet? 17:47:13 hm. I may have found another autofs bug 17:53:10 RhodiumToad: cool! 17:53:52 with a -media map I keep getting a subdir showing up named "-fstype=ufs,nosuid" 17:54:09 which, um, shouldn't happen 19:20:42 o_O 19:20:56 nosuid is an fstype? 19:22:48 nope 19:22:59 ufs is, though 19:34:32 That's kind of my point though. . . seems like there's more going on than misplaced syntax. 19:35:25 special_media outputs lines of the form "-fstype=ufs,nosuid :/dev/whatever" when run with a specific device param 19:35:48 automountd is supposed to parse that 19:38:11 Looks like auto_master(5) syntax. 20:18:43 yuripv: not sure I understand your latest commits, zpool iostat -w (first run, specifically) displays trims done since the system was booted, and all the pools I have on SSDs report millions of trim commands executed at around 8-16ms latency. 20:20:32 debdrup: it's only about the default value of autotrim 20:20:41 not related to trim itself 20:21:52 yuripv: but what would responsible for TRIM stuff, other than autotrim? 20:22:29 what exactly are you asking? 20:25:40 my change is not related to how/when/why trim runs, it's related only to default value of autotrim used when creating a pool (if not specified explicitly); it was supposed to be 'on' (same as before switching to openzfs), but due to mess with defines it became 'off' 20:26:17 yuripv: BIO_DELETE doesn't automatically send ATA_TRIM or SCSI/SAS UNMAP without autotrim, does it? 20:26:46 that's completely unrelated? 20:27:04 we are talking about default property value 20:27:32 I guess I don't understand what that means. 20:27:48 the one used when creating pool 20:28:35 you can set autotrim to on explicitly, and autotrim will work 20:29:46 Oh, I _did_ enable explicitly. 20:30:27 right, so it does something for yo 20:30:31 you :) 20:31:10 my change was removing the FreeBSD specific defines that were supposed to have autotrim default to 'on', but didn't work 20:31:27 Right, and it was probably appearing as off before then, due to IFDEFs - but then wouldn't it be better to ensure it gets enabled, to restore the functionality that we had before OpenZFS? 20:32:59 well, may be, but it's been quite some time, *and* the man page says default is 'off' 21:27:29 is anyone around ? 21:27:54 Don't see anyone. 21:28:33 is this the official irc for freebsd ? 21:28:38 Yes. 21:28:44 One of them anyway. 21:28:54 how can I get an official affiliation with FreeBSD for my software projects ? 21:28:55 https://wiki.freebsd.org/IRC 21:28:56