00:01:23 a topological sort would be nice but I'm not really sure how best to do that with elasticsearch 00:22:04 satanist: i thought you could only expand raidz, not mirrors 00:23:23 damnit satrapes stay in th channel bit longer 00:39:04 Freaky: I guess there's no way to order them maintaining the parent relationship / ordering by `git rev-list --count --first-parent ` ? 00:39:36 this'll likely come up a lot with third party contributions in particular 01:12:19 kevans: there's surely something that can be done that'll be reasonably efficient, I just need to set aside the time to try stuff 01:14:13 if I leave it long enough maybe someone will make a nice search engine with graph database capabilities ;) 01:42:36 Freaky: you seen Hillel Wayne's lasted newsletters? 01:44:14 https://buttondown.email/hillelwayne/archive/unusual-basis-types-in-programming-languages/ (things missing) and https://buttondown.email/hillelwayne/archive/if-you-work-on-a-big-language-id-like-to-talk/ 01:44:15 Title: Unusual basis types in programming languages • Buttondown 01:44:48 oh no, more trees 01:45:18 I can't wait for civilization to collapse so we have to go back to basic linked lists 01:47:35 meena: thanks, these were fun and not too overwhelming 01:48:31 oh, wait, this one has Raku, I take it back 01:49:38 Raku is weird 01:50:10 it looks like Perl from another dimension 01:50:12 it's like, what are we spending our language's weirdness budget on? everything 01:50:51 Raku was a push towards larrys goal but it got complicated :) 01:53:26 that wasn't the goal? 02:12:36 When Perl 7? :P 02:14:03 higher version number = better 02:14:34 With Rust and C++, yes, yes it is :P 02:14:50 and browsers 02:14:57 Getting ready to put FreeBSD in a virtual machine to get a feel for it 02:15:20 Most of you also daily drive FreeBSD for your Desktop type computing? 02:15:29 Yep 02:16:18 Cool, I plan to do it with KDE Plasma. And will be debating replacing my Linux Host OS with it (Fedora) 02:19:48 perl is excelent. every time i install git, it depends on a bunch of perl modules 02:20:00 same with many oses 02:20:26 but i can understand many people prefer not to understand what is perl 02:21:06 I can say the same with python 02:22:04 and not trying to start a language war either 02:22:38 pretty similar.. except perl is independent.. no BIG company promoting it.. python has google behind 02:23:15 let the language wars begin 02:24:00 I often wonder why Rust gets so much attention and Golang isn't even in the conversation 02:25:05 Because there is a whole lot of zealotry behind it along with an intense motivation to blindly rewrite everything in it 02:25:12 thats a good sign... independent for the win 02:25:33 big players dont need my blessing 02:25:59 i use firefox :) 07:23:07 so does Firefox on FreeBSD use pulseaudio? this guide I was looking at regarding bluetooth audio makes it seem like getting audio from pulse to the bluetooth audio virtual_oss device involves a janky hack that introduces noticeable latency 07:23:27 but I dunno if I really want to use chromium 08:35:06 It can, but it can also use FreeBSDs own audio stack, which can do things no Linux audio stack can do. 08:41:56 I'm not sure I understand why you need to introduce pulseaudio, when bluetooth is handled by netgraph and the audio device should be present in /dev/sndstat. 08:42:53 Oh wait, no I'm misremembering - you use virtual_oss to create a sink. 08:43:28 For what it's worth, virtual_oss is used by at least one musician (specifically, meka in this channel) for low-latency audio monitoring. 08:44:36 See the -i switch on virtual_oss(8). 09:19:06 debdrup: I'm talking about cases where an application pulls in pulseaudio, regardless of what I'd want to use. apparently pulseaudio won't play through a virtual_oss sink without a hack where you use some pulse command-line utility to record audio and redirect it 09:27:20 nowadays I wouldn't willingly touch pulseaudio proper since pipewire exists, though while I see ports has a port of pipewire, I think I read something about applications still pulling in actual pulse as a dependency 09:32:31 (hell, even on Linux, before switching to pipewire, I slogged through using bare ALSA due to my prior experiences with pulse) 10:14:47 The only use-case I've had for bluetooth audio is using it for WebRTC based conferencing, which works via oss(4) on FreeBSD so doesn't involve pulseaudio - so I've not had to install it. 10:40:32 I was under the impression that some applications, ones that don't natively support OSS, or take the sane route of using some kind of portable abstraction layer such as libao, SDL, OpenAL, could pull in pulseaudio as that "abstraction layer" 10:41:15 like they use pulseaudio as a roundabout way of getting sound through OSS in lieu of native support 10:45:58 what I read made it sound like firefox was one of those applications with a hard dependency on pulse, and that's what I remember from using firefox with ALSA, which forces (or at least forced) firefox to use this library called apulse that basically provides the bare minimum of the pulse API for sound to function 12:43:06 tm512: Firefox uses a library called cubeb which, technically, supports a large number of audio backends including OSS (iirc). the catch is that Mozilla only supports the PulseAudio backend. 13:03:14 are we meant to remove *all* sccsid/rcsid tags now, or just $FreeBSD$ ones? 14:30:43 why does ipsec_set_policy take a char* instead of a char const *? 14:33:15 looks like there is no actual reason for it, should be fixed 14:33:39 lw: it's probably one of those cases where it changed something at some point, but then didn't anymore and the type stayed 14:33:48 wouldn't be the first one 14:33:51 ... or last :) 14:34:20 it eventually gets passed to yacc (yy_scan_string), so perhaps that was changed to be const correct at some point 14:57:54 ipsec_dump_policy(char *buf, char *delim); ... "The buf argument points to an IPsec policy structure, struct sadb_x_policy." what? 14:58:52 this code must be like 20-30 years old if it comes from KAME i guess, but still, that's weird 15:09:12 hello. what is /usr/local/etc/namedb/dynamic? 15:09:17 is that some freebsd innovation? 15:09:27 first, i have never seen *namedb* before 15:09:44 V-T60: the default to write bind's dynamic zones. that specific path might be freebsd-specific but most distributions of bind have something similar. 'namedb' is the traditional name for the named configuration directory 15:10:06 okay 15:12:19 i have never seen such a terminology as *dynamic zone* unfortunately 15:12:30 i only refered to it as just *zone* 15:13:20 no, not frebsd magic 15:13:31 what is that for? 15:13:32 dynamic dns? 15:13:33 well yes, technically a dynamic zone is a type of zone, but dynamic zones need different file permissions so named can write to them, similar to secondary zones 15:13:39 so it's useful to put them in a separate directory 15:13:41 V-T60: it's a zone stored in an opaque database file rather than a text file 15:14:02 V-T60: for nsupdate(1), and also DNSSEC uses it in some configurations, and maybe a couple of other things 15:18:01 rtprio: hmhmhm, i can see how people store there just simple text files 15:19:39 https://bind9.readthedocs.io/en/v9.18.13/chapter6.html 15:19:40 Title: 6. Advanced Configurations — BIND 9 9.18.13 documentation 15:40:52 i wonder how much difference witness+invariants makes to compile times. should be relatively little, since that's all cpu-bound, i would have thought 15:55:02 hi, im trying to install freebsd, i have 2 disks, one failed DST check (i dont wna to u use it) freebsd install fines, i have another that freebsd gives me alot of errors saying "root mount waiting for graid" then it proceeds to install 15:55:30 but i cant install using the guided option because it stays "no disks" 15:56:25 the auto ufs shows the disk, but when i try to do anything it says "operation not permitted geom ada0" 16:18:03 dstolfa: https://github.com/freebsd/freebsd-src/pull/1099 16:18:04 Title: libipsec: make const-correct by llfw · Pull Request #1099 · freebsd/freebsd-src · GitHub 16:22:43 lw, I'm working on mediaelch right now 16:22:55 came to the office on a saturday just for you :* 16:24:19 jbo: i feel bad now because it's really not *that* critical :-P but thanks :-) 16:24:31 nah all good - I wanted to have this done 10 days ago. 16:24:36 but $life 16:27:12 i actually found a weird (minor) bug in mediaelch the other day that i suspect might be a qt6-wayland issue... should probably investigate that 16:28:07 and I found a python software that I want to use on freebsd but I don't feel like maintaining python stuff 16:30:50 hmm, it has a pypi entry, so maybe not that difficult 16:31:09 that's what i thought when i wanted to port sublime-music and became toot maintainer 16:31:13 run, run while you still can 16:31:48 (although tbf the other ~4 python ports i submitted at the same time went fine, so...) 16:31:51 lw, f*cking hell have to build lang/rust again to test the mediaelch changes - and that probably for more than one jail :<<<< 16:32:20 jbo: yeah iirc it somehow depends on gcc, llvm and rust? although that seems to be normal for all ports nowadays 16:32:32 yeah it's stupidly ridiculous 16:32:40 i'm sure a lot of these gcc dependencies could be fixed with a bit of upstream work 16:32:57 AFAIK (but I am really not even remotely sure), rust uses GCC's standard libs under the hood so you can always build that first... 16:32:59 rust not so much... but did you see the rust binary port? i'm not sure if it's in-tree yet 16:33:17 it uses the binaries from the rust people instead of building it 16:33:40 yeah I have, rust-bin but as a committer I don't think I should rely on that. I need to make sure that things will build under a common/reasonable scenario which includes the official pkg builders 16:33:56 * dstolfa shakes his head at how horrible the whole ecosystem is 16:34:10 dstolfa, which one? 16:34:13 jbo: rust's 16:34:19 * jbo nods 16:34:24 nobody seems to agree tho 16:34:29 gotta have your cargo cult 16:34:31 rust would be okay if it didn't seem to update so often, literally every time i build ports it's building rust 16:34:49 that might just be cognitive bias since i find it so annoying though 16:34:51 jbo: most people who had to work with it in the context of distributing software that i've talked to do 16:34:59 AFAIK microsoft is heavily jumping on the rust wagon - looking forward to see what happens to rust in the next 5 to 10 years 16:35:05 (i don't even dislike rust as language, but it's quite silly we have to compile so many compilers for these trivial packages like mediaelch) 16:35:10 rust's issues are almost entirely in the ecosystem 16:35:36 yep. and companies like microsoft do not have a track record of making those better 16:35:54 i'm sure their internal stuff is good, it's just not going to help anyone else 16:35:55 and on top of that I personally (!) still think that a lot of what people see in rust as a language is totally what modern C++ allows for too. 16:36:43 jbo: imo C++ still has the problem of being "accidentally" unsafe, but you can address that by judicious application of clang-tidy and the c++ core guidelines... 16:37:04 (put all your unsafe code in one module, apply a strict clang-tidy ruleset to the rest of the code) 16:37:36 (which is actually how you're meant to use the core guidelines, just no one does this) 16:37:37 a few years ago I had to work with libraries written by google quite often (and with that, their own tooling ofcourse such as gtest, abseil, bazil, ...). A lot of people are "whooo, it's a library written by google, it must be amazing". but what they fail to understand is that google, like any other company or person, makes stuff to solve a problem that they have. the overall problem is that google has problems that nobody else has. therefore, their solutions are 16:37:38 IMHO often not easy to employ in other real world scenarios 16:38:14 and I feel like rust has potentially the same problem, but I don't know enough about it for making a point/argument there. 16:38:14 jbo: but re: -social, you know it's going to be easier to get rust in base than to actually support C++ 16:38:28 lw, yes, but IMHO for non-technical reasons. 16:38:32 oh yes 16:38:39 C++ is there, for free. 16:38:53 lw: i'm not so sure. the technical issues to be addressed with rust are pretty monumental at the moment 16:39:01 someone needs to do the work. until then, it's pretty much a no-go 16:39:04 i'd like to see a proof of concept 16:39:18 dstolfa: yeah, but people are working on them, while certain people will die on the hill of (for example) not correctly supporting C++ in libc 16:39:30 my proof-of-concept is building lang/rust probably three times today just to be able to commit a port of a media player written in python. 16:39:49 lw: people have worked on rust pocs for a while, but none yielded any actually useful results yet 16:39:56 there are prototypes sitting around, but not ones we can use 16:40:26 I should think of getting a PC hardware upgrade/replacement... 16:40:27 dstolfa: as jbo said, this is going to end up being a political issue, not a technical issue. the technical issues can be fixed (with enough work), but C++ will never be politically acceptable while rust is trendy 16:41:09 I suggest we'd have an easier time rewriting parts of freebsd in javascript than accepting the benefits that C++ can bring over C if one is willing to accept that 2024 C++ is not 1998 C++ 16:41:21 i don't really care about what people find trendy, i care more about what the code actually does and how it works. right now, C++ is something i can use in base to solve useful problems. rust is still a long way away from being in an acceptable state to be in base 16:41:23 Windows and Darwin have C++ *in the kernel*, FreeBSD can't even support C++ in libc 16:42:15 lw, can you elaborate on that? most of my work is C++ but always outside of base. are talking about lack of libc++ in base or that libc in base is C++ "incompatible" ? 16:43:26 jbo: my libc patch was reverted here: https://lists.freebsd.org/archives/dev-commits-src-main/2024-February/021484.html - which is fine, it's wrong - but see that the person who requested the revert said they would object strongly to any attempt to fix the problem requiring the revert 16:43:27 Title: Re: git: c27a89971805 - main - stdlib.h: add __noexcept to prototypes 16:43:36 from the point of view of a _USER_, I'd just like to point out that ever since firefox started transitioning to rust I did not get a better firefox experience. Obviously one can argue that this can be due to a lot of web crap but my point stands. 16:43:57 (meaning this problem can never be fixed) 16:45:01 as long as that same person also strongly objects against getting rust into base I'm fine :D 16:45:19 I am mainly upset about how one can rust fanboy but deny anything C++ 16:45:27 but I guess the term "fanboy" explains why. 16:46:01 i haven't really done anything with Rust but people i know in the C++ community seem fairly pragmatic about both languages. the "you can never write secure code if it's not in rust" people are quite annoying though 16:46:13 yeah 16:46:19 any bhyve gurus here? 16:46:21 i'm somewhat conflicted with what kind of C++ should be in base and what we should handle. i don't think we should have any exceptions in base, and i don't think any of our libraries should support them or RTTI (for base, anyway). this isn't so much about C++ as it is about how exceptions work in general, pretty much in any language 16:46:36 although, it's also not untrue, if your only options are C and Rust... which they are in Unix, because see above re: C++ being politically unacceptable 16:46:59 dstolfa, not having exception handling or RTTI in base is a fine thing to do IMHO. 16:47:27 dstolfa: the problem is without libc knowing about exception, it's impossible for a C++ compiler running on FreeBSD to conform to the C++ standard 16:47:31 someone in #c++-social argued earlier that std::basic_view was implemented incorrectly 16:47:48 that doesn't mean strlcpy() should be throwing exceptions or anything, it just needs the basic support to provide conformance 16:48:28 you shouldn't use strlcpy() in C++ anyway 16:48:48 (i personally dislike exceptions and would be strongly opposed to base libraries throwing an exception anywhere - for one thing they are terrible for performance, and once you put them in libc, the user can't elect to avoid that overhead) 16:49:06 If anyone can explain WHY bhyve is stuck, I will be very happy :) https://antranigv.am/misc/bhyve_procstat_kstack.png 16:50:04 lw, quick question on all of this (because I think my understanding might be wrong here): you would use std::memcpy() instaed of C lib memcpy() in C++ code, right? and std::memcpy() would/could be implemented by libc++ so you can leave libc as is? 16:50:52 jbo: i would writes std::memcpy() in the source code but it's just an alias for ::memcpy() so it doesn't really make any difference, neither libc nor libc++ need to know about std::memcpy 16:51:01 (except that libc++ has to provide the alias in ) 16:51:33 lw: did kib elaborate on the reasons why he opposed a patch that would ensure we call std::terminate? 16:51:38 lw, but does the standard require it to alias C's memcpy()? your libc++ could just provide a "C++ implementation" of memcpy()? 16:51:49 dstolfa: no and i didn't ask since this isn't a discussion i want to get into right now 16:52:19 the longer we don't get into these discussions the harder it becomes down the road tho :< 16:52:31 jbo: i don't know the answer to that. the standard says that the contents of should be "the same as" the contents of . does that mean ::memcpy and std::memcpy need to be the same function? i have no idea 16:52:44 but i'm not sure why you'd want to provide a separate implementation of std::memcpy anyway 16:52:56 lw, that was with regards to not modifying libc at all 16:53:04 as in, that was my thinking - but I didn't know - hence I asked 16:53:34 iirc you aren't allowed to take the address of standard library functions so i don't think an application could tell if std::memcpy was a separate function or not 16:54:59 jbo: i'm not suggesting "C++ support in base" means providing std::memcpy() though. libc++ already does that 16:55:11 so, reading the email thread, it reads to me that kib is concerned about adding C++ ABI semantics in general into libc. i'd be interested to know his reasoning and i think this is a discussion worth having because it sounds like he has specific technical reasons for it, but didn't elaborate further on the mailing list 17:00:14 [00:36:28] [06] [00:35:39] Finished lang/rust | rust-1.75.0: Success 17:00:28 [00:27:19] [02] [00:00:00] Building devel/llvm15@default | llvm15-15.0.7_10 17:00:29 q__q 17:00:33 for a media player. 17:00:36 written in python. 17:00:44 seriously? 17:00:54 yes, ask lw 17:01:00 he makes me do this :p 17:01:03 oh yeah, that sublime player 17:01:29 ah wait, that is indeed incorrect. this is not for the sublime player, this is for mediaelch 17:01:32 even worse then :p 17:01:47 i'm pretty sure you actually offered to do this :-P although you might be regetting that now 17:01:57 nah, all good - I'm just teasing 17:02:10 I feel mainly bad that I couldn't do it the last two weeks because real life 17:02:14 I've just updated from 13.2 to 14. I followed the instructions that involved running freebsd-update a number of times and rebuilding all the packages I had installed from ports. Now, after the upgrade, unbound (from ports) refuses to start complaining about missing SSL libraries. I've rebuilt it twice but the problem persists. Does anyone have any suggestions on how to approach the problem? 17:02:38 njdoyle: which ssl library is it looking for? 17:03:29 Sorry, my network is being a pain. I may have missed some messages. 17:03:43 This is what I see when I try to start the service: unbound[32533:0] error: error in SSL_CTX verify crypto error:80000002:system library::No such file or directory 17:04:03 that's when I do: doas service unbound start 17:11:15 ldd says unbound is linked against /usr/lib/lib{ssl,crypto}.so.30 which seems correct to me post upgrade. 17:11:47 or, that is /usr/lib/libssl.so.30 and /lib/libcrypto.so.30 17:12:18 njdoyle: did you run the final freebsd-update step that removes the old libraries? i wonder if it's somehow picking them up during install. never saw this error though (and unbound is working fine for me on 14/15) 17:12:49 lw: I did run the final freebsd-update that removes old libraries. 17:13:14 lw, can I ask you sanoid related stuff? 17:13:37 the only thing i can think of is that openssl 3.0 removed some legacy cyphers and perhaps it's failing because of that? ... but i would expect a different error then, any in any case i don't think TSIG/DNSSEC uses those cyphers 17:13:56 jbo: sure but i promise no answers 17:14:12 Is there a way I might be able to figure out what file unbound thinks is missing? 17:14:34 njdoyle: you could try starting it under 'truss' which will log open() calls 17:14:49 (generates a lot of output, redirect 2> to a file) 17:15:32 lw, assume a dataset hierarchy like A/B/C1, A/B/C2, A/B/C3 ... A/B/C17 In sanoid.conf I have a rule for A/B which uses my production template. however, I want to exclude A/B/C7 because that is a gigantic dataset (poudriere VM image). I came across this: https://github.com/jimsalterjrs/sanoid/issues/627 17:15:34 Title: How to exclude child datasets from snapshots? · Issue #627 · jimsalterjrs/sanoid · GitHub 17:15:35 627 – vidcontrol causes crash when booted with sc0 disabled https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=627 17:15:55 so I created a rule for A/B/C7 using a template with everything set to no/0 but it's still making the snapshot 17:16:30 do you have that "exclusion" mechanism working? 17:16:37 let me see 17:17:12 lw, this is my actual config: https://termbin.com/zwgo 17:17:52 jbo: this is what i use and it works for me (i just checked) https://www.le-fay.org/tmp/30d/i75Eme.txt 17:18:36 jbo: i think recursive = zfs won't work for this because zfs snapshot -r doesn't care about your sanoid config 17:18:40 lw, any idea why mine wouldn't work? looks very similar except that I have more hierarchy in the dataset paths and I use recursive=zfs (not sure what the difference is) 17:18:48 lw, aah 17:18:50 try recursive = yes instead 17:19:07 lw, I couldn't find sanoid docs on the difference between recursive=yes and recursive=zfs. do you know the difference? 17:19:15 Okay, I figurd out my problem. It looks like security/ca_root_nss got uninstalled in package cleanup. It must have been a dependency of something and not a thing I installed specifically. Reinstalling that fixed things. 17:19:33 jbo: recursive = yes manually snapshots every descendent filesystem, recursive = yes uses zfs snapshot -r which is theoretically more consistent but it always snapshots everything 17:19:39 Okay, I figurd out my problem. It looks like security/ca_root_nss got uninstalled in package cleanup. It must have been a dependency of something and not a thing I installed specifically. Reinstalling that fixed things. 17:19:48 er, the second recursive = yes should be = zfs there 17:20:07 lw, but... what 17:20:11 njdoyle: odd that it caused that error, which says nothing about the actual problem 17:20:22 openssl doing openssl things i suppose 17:20:26 so recursive=zfs is proper -r flag in zfs. but recursive=yes means that somebody is doing the recursive handling in perl? 17:20:27 lw: agreed. The message could have been way more helpful. 17:20:41 jbo: yes, with =yes sanoid enumerates the filesystems by itself and snapshots them one at a time 17:20:57 lw, so you use =yes instead of =zfs everywhere? 17:21:01 jbo: yes 17:21:13 lw, so if I were to change that now.... this is a production server :D 17:21:25 i only have 73 filesystems so i very much doubt this causes a performance issue, maybe if you had thousands it would matter 17:21:38 nah I have low tripple digits 17:21:53 jbo: well, i've never tried changing it... but... i think it should create the same snapshot names so it *should* be fine. and you have backups right? :-d 17:22:18 :3 17:22:32 it just means the hourly_whatever timestamp on the child filesystem might be different from its parent, but syncoid doesn't care about that 17:23:35 lw, is there a sane way of deleting all snapshots of a dataset (without modifying the current state of the data on the dataset, similar to doing it manually, just "remove all the snapshots from this dataset but don't screw up"? 17:24:21 jbo: not that i know of, i usually do: zfs list -Honame -rt snapshot data/set/name | xargs -n1 zfs destroy # i STRONGLY suggest using 'echo zfs destroy' to make sure this does what you expect 17:24:38 i really, really wish the command to destroy a snapshot was different from the command to destroy a dataset 17:24:50 hell yes. 100% that 17:25:05 would be even fine to leave zfs destroy as is, but having a separate subcommand just for snapshots 17:25:12 zfs snapdestroy or whatever 17:25:15 zfs destroy-snapshot 17:25:27 you literally mistype an @ and you can be whooped :D 17:25:48 or even zfs destroy -t snapshot or something 17:25:53 yeah 17:26:06 like, say i want to destroy foo/bar@baz, i type "zfs destroy foo/bar" and my cat walks across the keyboard... whoops 17:26:24 lw, so, when I fix my config and sanoid no longer takes snapshots - will syncoid also not push them to the backup destination host? 17:26:45 jbo: if the snapahots exists they will be pushed, i don't believe syncoid cares about your sanoid config at all 17:27:04 yeah 17:27:10 I really want a proper --exclude option :<<<<< 17:28:08 https://github.com/jimsalterjrs/sanoid/pull/189 17:28:10 Title: added ability to skip datasets... simply set syncoid:no-sync=true by attie · Pull Request #189 · jimsalterjrs/sanoid · GitHub 17:28:11 that sounds fuckly 17:28:24 oh i use that all the time, but isn't it called syncoid:sync=false? 17:28:41 so you set custom properties? 17:28:43 attributes 17:28:48 yeah 17:29:01 there's syncoid --exclude 17:29:05 https://www.le-fay.org/tmp/30d/jYMskp.txt 17:29:36 Does Steam Gaming work with FreeBSD? 17:29:47 yes 17:29:51 SponiX: somewhat yes, there is one person (i think) who maintains Steam on FreeBSD 17:30:00 as to how many games actually work, no idea 17:30:15 Okay, thanks for the replies lw and jbo 17:30:18 lw, can you tell me about your reasoning/opinion on the zfs property vs. the syncoid --exclude=REGEX option? 17:30:28 lw, there's an outdated list 17:30:47 https://github.com/shkhln/linuxulator-steam-utils/wiki/Compatibility 17:30:48 Title: Compatibility · shkhln/linuxulator-steam-utils Wiki · GitHub 17:30:51 SponiX, ^ 17:30:56 jbo: to me whether a filesystem is backed up is a property of the filesystem itself and not something that should be centrally configured where i'll forget to update it. this way i can create a new filesystem and tell it not to sync at the same time, for example 17:31:10 jbo: analogous to other operating systems which have a "backup" file flag 17:31:22 and if you use zfs delegated administration, this lets users configure backupiness by themselves 17:31:25 does anyone here get some segfaults with these? https://paste.mozilla.org/preuMHCB https://paste.mozilla.org/MJB1rc32 17:31:27 Title: Mozilla Community Pastebin/preuMHCB (C) 17:31:54 lw, that sounds reasonable. so now to figure out whether it is syncoid:no-sync or syncoid:sync 17:32:09 jbo: syncoid:sync definitely works and i'm sure that's what i found in the documentation 17:32:30 yeah https://github.com/jimsalterjrs/sanoid#syncoid-dataset-properties 17:32:31 Title: GitHub - jimsalterjrs/sanoid: These are policy-driven snapshot management and replication tools which use OpenZFS for underlying next-gen storage. (Btrfs support plans are shelved unless and until btrfs becomes reliable.) 17:32:45 oh interesting, you can set it to a list of hosts, never knew about that 17:33:24 lw, that is very, very nice. 17:33:26 lw, thank you 17:33:46 meanwhile... [01:14:07] [02] [00:46:48] Finished devel/llvm15@default | llvm15-15.0.7_10: Success 17:34:08 do you want to ask more syncoid questions while gcc builds? i'm waiting on make packages (which is surprisingly slow) 17:34:38 also i think it's putting the packages in the wrong place so i should probably stop it and fix that 17:35:38 lw, I'll take a rain check on that :p 17:35:51 * lw wonders where make packages is documented 17:37:38 lw, so it's zfs set syncoid:sync=false A/B/C7 right? 17:37:47 jbo: y 17:38:02 don't do what i always do and set 'sanoid:sync=false' instead because that doesn't work 17:38:23 heh :) 17:38:36 I do stupid things myself every now and then, don't worry 17:40:30 ah it's ${EXTRA_REVISION} which is causing my bad package names, but you can override this with make PKG_VERSION=15 i guess 17:41:02 * lw wonders if this breaks upgrades 17:41:12 * lw wishes pkgbase had more documentation, also 17:43:43 * jbo wishes his understanding of xargs would be better. I am shitting my pants right now regarding destroying those snapshots 17:45:20 jbo: if you're worried, just use 'echo zfs destroy', review the commands and copy+paste them into your shell 17:45:29 that's what i did the first time i wanted to destroy a load of snapshots 17:45:56 that doesn't keep me from soiling my pants as we speak 17:47:03 lw, stupid question, but does something | xargs work when using doas? 17:47:13 something | doas xargs ... 17:47:15 i.e. doas something | xargs cmd 17:47:28 my shell foo is very, very poor. 17:47:31 unless something needs to run as root as well in which case doas something | doas xargs 17:48:32 jbo: i want to mention right now that if you delete all your datasets this was definitely not my fault and you still have to commit mediaelch 17:49:03 aaaaand it's gone 17:49:08 lw, of course, yes :D 17:49:15 :-p 17:49:40 lw, I honestly like that zfs property solution for syncoid:sync 17:49:43 that seems very, very nice. 17:49:56 yeah, i didn't even realise zfs had custom properties but i can see lots of uses for them 17:50:37 ah my packages are fine, it put a latest symlink in the package directory: lrwxr-xr-x 1 root wheel 21 Feb 3 17:46 latest -> 15.snap20240203170857 17:51:31 lw, so are you typically setting up your sanoid.conf to snapshot the entire filesystemn (including /etc, /usr/local/etc and so on) and then use the zfs property to prevent it from syncing or what's your normal operation mode here? 17:52:07 jbo: yes, i sync everything by default because i'd rather waste a bit of bandwidth than forget to back something up. i check on the backup server every couple of weeks to make sure it hasn't synced something it shouldn't 17:52:32 lw, would you mind sharing your typical sanoid config for that? 17:54:11 jbo: it's pretty basic, this is my desktop: https://www.le-fay.org/tmp/30d/WANqRJ.txt and this is our fileserver: https://www.le-fay.org/tmp/30d/4E3eJc.txt and this is what ends up on the backup server: https://www.le-fay.org/tmp/30d/KXHyRt.txt 17:55:44 lw, that brings me to my next question: I once asked you how you prune snapshots on the backup host. AFAIK you told me that you just run the same sanoid.conf of the source host on the backup destination host. However, I have a dataset for each host similar to what you just showed (/backup/${HOSTNAME}) how do you deal with that? 17:55:57 or do you just have a sanoid.conf that only does prune on the entire /backup dataset? 17:57:15 jbo: i just looked and apparently i didn't actually get around to setting this up yet, but my plan is to just make a sanoid.conf with one entry for all of [backups] that just needs a reasonable selection of snapshots (so autoprune = yes, autosnap = no) 17:57:41 lw, and then values for monthly, hourly etc? 17:57:45 did not realize that freebsd can use ubuntu binaries the things you learn when you read documentation :) 17:57:57 lw, but that means that it's indeed corect that you do not need to have THE SAME config as the one running on the source host, right? because that bugged me. 17:58:10 bsdbandit, +1 on always reading docs 17:58:19 jbo: yeah, i don't think the config can be the same in this situation 17:58:31 if only because the paths / dataset names are different 17:58:47 indeed 17:59:00 I have hdd/backups/hosts/${hostname}/zfs as the prefix :D 17:59:09 "prefix" 18:00:51 since you're asking i'm going to set this up now and see how it goes 18:01:22 and I'll wait for a single-core build of qt6-base to complete 18:01:40 lw, that syncoid:sync=false property seems to work :) 18:05:31 lw, what's your reason to bother explicitly disabling backups on zroot/var/crash ? 18:05:44 that would not be more than a few MB anyway, right? 18:05:52 /var/crash contains a memory dump of every kernel panic, it can easily end up being many gigabytes 18:06:04 aye 18:07:10 lw, let me know how that pruning works out 18:07:16 jbo: so i just created a sanoid.conf on the backup host like this: https://www.le-fay.org/tmp/30d/mxtrPM.txt - and it's now destroying all the snapshots as expected. however, syncoid will immediately push them again next time it runs. so i think what i'm going to do is set daily = 90, monthly = 12 and then see if i need to exclude hourly backups from syncoid somehow 18:08:02 hmm, actually, i don't think syncoid will push them again because it should only push snapshots created since the last syncoid snapshot, if i understand zfs send -I correctly. so that might not be a problem 18:08:35 are you sure about that? ._. 18:08:41 no, but i'm going to test it :-) 18:09:08 i might also add some specific config for filesystems like prometheus because i very much doubt i'll ever need to restore a specific prometheus tsdb from 3 weeks ago or whatever 18:09:32 (and if i do, i still have the snapshot on the source system...) 18:11:09 meena: make update-packages doesn't seem to work, it's just creating a new 15.snapwhatever with a new timestamp 18:12:52 lw, why tf do you have zroot/swap 18:14:18 jbo: because i thought 4GB of swap would be enough when i installed and it turns out it really isn't, i had to add another 16GB on a zvol 18:14:34 lol 18:14:41 you would think 32GB would be enough to run poudriere (with tmpfs disabled!) but no 18:14:51 it's not poudriere's fault 18:14:57 electron.... chromium.... 18:15:15 it's not those either, when i asked on -current someone suggested it might be the zfs arc prune bug 18:15:48 basically something ends up wrongly using loads of memory (it's stuck in Inact) and eventually poudriere runs out of memory and the kernel complains about 'out of swap space' 18:16:17 is that -current only? 18:16:31 i've only noticed it on -current but i think the bug exists in older versions 18:16:38 b 18:16:43 c 18:16:44 oh, sorry 18:16:49 otoh i thought the bug was only about cpu usage, not memory use, so i'm not convinced it's actually this 18:17:08 i wanted to do ctrl+b+d 18:17:31 swap usage does seem to have gone down though so maybe it's fixed: Swap: 16G Total, 405M Used, 16G Free, 2% Inuse 18:17:42 in the past i'd end up with several GB of swap used after a (non-tmpfs!) poudriere run 18:18:25 (non-tmpfs! is important because whenever i mention this someone tells me to turn off tmpfs, like you can even use tmpfs on a system with less than 128GB of RAM) 18:28:50 lw, I remember that there were a couple of forum posts/threads from people that suddenly couldn't build stuff like lang/rust and similar on their poudriere sets. I don't recall the details but wondering... 18:40:30 * lw installs pkgbase 18:42:15 Good, Good… 18:43:08 i'm just testing on my build VM for now, so if it breaks everything i can just rebuild and... wait... this may not have been the best idea 18:48:57 wow, pkgbase overwrote all my config files, that's a bit rude 18:49:27 they should still be in foo → foo.pkgsave 18:49:39 yeah but still: 18:49:40 lily# head /etc/master.passwd 18:49:40 root::0:0::0:0:Charlie &:/root:/bin/sh 18:50:10 that's what you get for using stupid hostnames. everybody knows that hostnames should be elements of the periodic table. 18:50:48 jbo: i'll call my next vm 'jbo' 18:50:54 :3 18:52:10 lw, I just wanted to tell you that testport for 14.0 mediaelch is still running when it finally dawned on my why this is taking HOURS 18:52:12 I'm an idiot. 18:52:21 i'm glad you're the idiot this time and not me 18:52:58 I was building on/for the stable jail rather than the release jail 18:55:13 whoo pkgbase FreeBSD lily.eden.le-fay.org 15.0-CURRENT FreeBSD 15.0-CURRENT #0: Sat Feb 3 16:12:37 GMT 2024 root⊙lelo:/builds/obj/data/public/src/freebsd/src/main/amd64.amd64/sys/GENERIC amd64 18:55:31 now to find out how to switch to MINIMAL 18:55:34 Tobuild: 205 18:55:35 fml 19:03:58 ok, i already like that i can 'pkg remove' all the useless crap i don't want and it will never come back 19:07:07 i don't like uname doesn't show the git revision though, is it ignoring my make.conf/src.conf for some reason? i have WITHOUT_REPRODUCIBLE_BUILD=yes set... 19:19:48 it does? FreeBSD tyrone.17es.net 15.0-CURRENT FreeBSD 15.0-CURRENT #4 n266291-2ffd30f7ee15: Mon Nov 6 20:12:25 UTC 2023 ... 19:20:22 rtprio: it does on my non-pkgbase system, it doesn't on my pkgbase system with identical make.conf/src.conf 19:20:37 FreeBSD 15.0-CURRENT #0 main-n268031-49619f73151a-dirty: Sat Feb 3 14:42:48 GMT 2024 lexi⊙ielo:/src/obj/src/freebsd/src/main/amd64.amd64/sys/ILYTHIA 19:20:39 FreeBSD 15.0-CURRENT #0: Sat Feb 3 16:12:37 GMT 2024 root⊙lelo:/builds/obj/data/public/src/freebsd/src/main/amd64.amd64/sys/GENERIC 19:21:08 oh, didn't catch it was pkgbase. 19:22:27 i notice it also built a bunch of pkgbase packages for things i have disabled in src.conf, which is fine, but makes me wonder if it ignores these files for pkgbase build 19:26:38 lw ping 19:26:43 hello the jbo 19:27:01 can you quickly sanity check this (visually): https://termbin.com/q7jo 19:28:40 jbo: looks good at first glance 19:28:56 you don't like pkg-plist? 19:28:59 lw, ack, testports almost done 19:30:09 > If the port installs just a handful of files, list them in PLIST_FILES, within the port’s Makefile. 19:30:18 https://docs.freebsd.org/en/books/porters-handbook/book/#porting-pkg-plist 19:30:19 Title: FreeBSD Porter's Handbook | FreeBSD Documentation Portal 19:30:30 hmm, i saw that also but i thought 'handful' would be <= 3, like 'a few'. it's fine though, i don't care either way 19:30:45 well the example there has 6 so... :D 19:30:49 ah 19:30:51 hence I changed it 19:31:07 handful is a terrible quantifier anyway 19:31:22 a handful of grains of salt vs a hand full of excavators... 19:31:43 this reminds me of the German habit of talking about how 'heavy' a file is 19:31:49 which i always quite liked, tbh 19:31:53 personally, I hate that convention anyway. I'd be all pro always having pkg-plist no matter what. 19:31:59 the handbook even tells you that it's a PITA 19:32:00 like 'this package weighs too much, you must make it smaller' 19:33:17 Im following the jail guide trying to set up vnet. It says for hosts to add this to the rc.conf: 19:33:20 ifconfig_bridge0="inet 192.168.1.150/24 addm em0 up" 19:33:24 Where does that ip address come from? 19:33:44 somebody just typed it as an example 19:33:52 Yeah i know 19:34:00 Where do I find the ip im supposed to use. 19:34:33 matthewp: if you're adding a new bridge containing the vnet interface and your existing public interface, it should be the address of your existing public interface 19:34:41 and remove the address from the public interface at the same time 19:35:03 (so the address of em0 in this case, i assume) 19:35:22 then just set ifconfig_em0="up" with no address 19:35:33 I don't have an em0 19:35:36 I have a vtnet0 19:35:42 ok, replace em0 with vtnet0 then 19:35:58 if this is on a VM, i highly recommend checking your serial console works before rebooting... 19:36:01 That's an external, public facing ip address, this is what i put into the rc.conf? 19:36:14 well, what do you have in rc.conf right now, for ifconfig_vtnet0? 19:36:34 I don't have that in the rc.conf at all 19:36:46 that's curious, do you know how it gets an address then? 19:37:12 even if it's DHCP i would expect it to have ifconfig_vtnet0="DHCP"... 19:37:17 im a novice in networking, i have route_linklocal in the config 19:37:26 can you paste your entire rc.conf somewhere? 19:37:35 yes 19:37:51 * lw images this is going to be some Hetzner-style config 19:38:12 it's possible i've removed that... i don't recall doing so but if i did and haven't rebooted, could that be the reason? 19:38:35 oh wait 19:38:42 i'm so sorry, i do have a ifconfig_vtnet0 19:38:45 possibly yes, that will definitely break if you reboot though 19:38:58 ifconfig_vtnet0="DHCP -rxcsum -tso" 19:39:03 ah ok 19:39:28 hang on, let me check something in the manual 19:43:00 matthewp: ok, i *think* what you want is this: set ifconfig_vtnet0="-rxcsum -tso up", and set ifconfig_bridge0="DHCP addm0 vtnet0" ... however i've never tried a bridge with DHCP before so i can't guarantee this will work, either make sure you have serial console access, or take a snapshot of the VM first or something in case it doesn't come up after you reboot 19:43:33 ok, i will try that, thanks for your help 19:43:56 sorry, that's 'addm vtnet0' not addm0 19:44:24 And i'm removing DHCP from the ifconfig_vtnet0 part? 19:44:43 yes, because you want the address to be added to the bridge interface, which requires running dhcp on the bridge instead 19:46:59 this post seems interesting: https://forums.freebsd.org/threads/trying-to-set-up-a-network-bridge-for-dhcp.20287/ 19:47:00 Title: Solved - trying to set up a network bridge for dhcp | The FreeBSD Forums 19:47:02 lw, how easily could you run a -current testport for me right now (not related to mediaelch)? 19:47:14 jbo: i'd say 87% easily, what do you need 19:47:31 lw, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276228 19:47:33 Title: 276228 – audio/cava: update to 0.10.0 19:47:49 matthewp: yeah their config is wrong in OP because they're setting ifconfig_bridge0 twice, only the last one will be used 19:47:51 lw, but without the .if ${OPSYS} == FreeBSD && ( ${OSVERSION} >= 1400079 || ( ${OSVERSION} >= 1302505 && ${OSVERSION} < 1400000 )) 19:49:55 jbo: this is the makefile you want testported? https://www.le-fay.org/tmp/30d/FgNbP5.txt 19:50:03 i removed the .if and .endif 19:50:14 but left CFLAGS+= 19:50:41 lw, also drop the CFLAGS+= that was incapsulated in that block 19:50:45 ah ok 19:52:57 god pkg.freebsd.org is so slow, or at least my local mirror is 19:53:15 getting 5MB/s download speeds 19:54:23 lw where are you at? 19:54:31 antranigv: UK 19:54:42 deathstar #7 19:54:57 jbo: running now [main-audio_cava] [2024-02-03_19h51m56s] [parallel_build] Queued: 179 Built: 0 Failed: 0 Skipped: 0 Ignored: 0 Fetched: 142 Tobuild: 37 Time: 00:02:53 19:55:02 lw sometimes geoDNS might be configured wrongly, just use a specific one in FreeBSD.conf 19:55:22 lw, thanks 19:55:40 lw for some reason Armenia is set to South African server, should be changed to one in Europe, so I just change it manually. 19:55:52 antranigv: i wonder if the geodns doesn't work properly for ipv6 19:56:04 lw oh, that's also possible! 19:56:10 i'm not even sure if poudriere lets you change it, i should investigate that 19:57:05 jbo: can you PM an email address to send the invoice for electricity usage to? 19:57:18 (this is a joke, don't do that. although before long, who knows.) 19:57:49 lw, it should be a fairly light port. it is truly only if it's no inconvenience to you at all. I can handle it on my end otherwise. 19:58:03 no it's fine, i'm just editing shell scripts anyway 19:58:39 jbo: oh testport finished already, no problems, bulk is running now. do you want me to test the port itself? (i have no idea what it is/does) 19:58:58 lw, no need to runtime test. just whether testport succeeds on 15-CURRENT 19:59:05 jbo: ok all done then, no errors 19:59:19 thanks! 19:59:32 Warning: you might not need LIB_DEPENDS on libEGL.so 19:59:32 Warning: you might not need LIB_DEPENDS on libSDL2.so 19:59:35 fyi 19:59:56 ack 20:00:03 also cava.c:409:36: warning: passing arguments to 'getPulseDefaultSink' without a prototype is deprecated in all versions of C and is not supported in C2x [-Wdeprecated-non-prototype] 20:00:08 but it was not an error 20:00:17 yep 20:07:13 can someone help explain why i can ssh to a host on the lan, but not curl to it? 20:07:17 over nat 20:08:54 ports are open, can test that locally; 20:10:16 rtprio: tcpdump 20:11:00 i can tcpdump but not decipher it 20:11:13 show the tcpdump output while you're curling 20:11:27 on the destination 20:16:33 https://bsd.to/7ugV/raw 20:16:34 Title: 7ugV 20:17:07 which system is the server and which is the client? 20:17:26 24 is the server, the web server is port 3000 20:17:44 18 is the client, which is nat'ing wireguard 20:17:49 that's weird 20:17:54 from 18 directly works fine 20:18:17 also i noticed the sendq for that tcp connection increases until it's reset 20:18:55 it seems like the reply to the syn is getting lost 20:19:13 Proto Recv-Q Send-Q Local Address Foreign Address (state) 20:19:14 tcp4 0 32061 10.0.17.24.3000 10.0.17.18.58686 FIN_WAIT_1 20:19:56 i suppose i could try ipfw but now it's basically a "nat on $ext_if inet from !($ext_if) -> ($ext_if:0)" 20:20:09 how does curl behave, connect timeout? 20:20:46 connection reset 20:21:04 oh that's weird. there is no RST in that tcpdump 20:21:28 it feels mor like it times out 20:21:32 19:22 i notice it also built a bunch of pkgbase packages for things i have disabled in src.conf, which is fine, but makes me wonder if it ignores these files for pkgbase build ⬅️ weird. I would think this is a bug 20:21:38 after sending GET / and all that 20:21:56 rtprio: you're using pf? try adding log to your block rules (if you don't have them already) and tcpdump on pflog0 to see if it's dropping anything 20:22:30 meena: maybe i will ask pkgbase@, although i could do without someone telling me i'm an idiot today :-) 20:22:33 maybe i need just pass all; i didn't have any other rules at first and the same symptoms 20:22:49 rtprio: if you can start with pass all i'd do that and see if it works at least 20:22:57 or even set skip on wg0 20:23:03 (although that will break nat ofc) 20:23:18 lw: given PkgBase@'s response times, you should be safe 20:23:35 lw: do the packages contain anything sensible? 20:23:43 meena: yeah, the packages themselves are working fine 20:24:04 *weird* 20:24:27 lily# pkg info -l FreeBSD-kernel-generic|grep /kernel/kernel 20:24:33 /boot/kernel/kernel 20:24:42 /quit 20:25:12 ok, so new question, i created a git repository by pushing to it then put it on http, but my git client won't find it because info/refs doesn't exist: 2024/02/03 20:16:08 [error] 65926#117500: *43 open() "/data/public/src/freebsd/src.git/info/refs" failed (2: No such file or directory), client: 2001:8b0:aab5:106::20, server: git.eden.le-fay.org, request: "GET /freebsd/src.git/info/refs?service=git-upload-pack HTTP/1.1", host: "git.eden.le-fay.org" 20:25:20 am i missing something obvious here? 20:25:31 src.git/info only has 'exclude' 20:27:21 * meena hasn't exposed git over http in ca 9 years 20:32:29 my local git repositories don't have a info/refs either so i'm not sure why it expects this 20:33:23 ah... i need something called git-http-backend 20:34:37 ah no, i just need to run git update-server-info... wonder why this is so complicated 21:18:03 lw, ping 21:18:10 jbo: YO 21:18:39 lw, I want to port this: https://github.com/gaphor/gaphor 21:18:40 Title: GitHub - gaphor/gaphor: Gaphor is the simple modeling tool 21:18:43 lw, any idea how much pain that will be? 21:19:39 jbo: well it's got a pyproject.toml so you can use PEP-517 which makes it easier. probably depends on how many of the dependencies already exist 21:19:55 lw, what is PEP-517 exactly? 21:20:07 i have never used poetry though so i don't know if that makes it more difficult 21:20:15 jbo: the replacement for setup.cfg/setup.py from distutils 21:20:21 https://wiki.freebsd.org/Python/PEP-517 21:20:22 Title: Python/PEP-517 - FreeBSD Wiki 21:20:53 ah, so it's the typical: "here is the 17th solution to the problem everybody has" type thing 21:20:59 yeah 21:21:19 like the python version of make/bmake/autotools/cmake/xmake/meson/... 21:21:58 you just write this in Makefile and it magically works though: USE_PYTHON= autoplist concurrent pep517 21:22:19 but like i say i don't know anything about poetry (that's the new version of pip/setuptools or something? not really sure) so... 21:22:25 lw, I still need to list RUN_DEPENDS and BUILD_DEPENDS manually by copying from the pyproject.toml? 21:22:30 yes 21:22:47 oh and it needs python 3.11, so have fun testporting it 21:22:54 -__- 21:23:17 jbo: although i'm not sure if you saw the comment on the sublime-music PR but apparently ports is switching to 3.11 as default RSN 21:31:55 not sure why we skipped 3.10 tbh 21:32:08 mumble mumble 21:40:08 apparently style(9) says nothing about where const should go, so i'm going to use 'char const *' as the Gods intended 21:41:27 daring 21:44:40 this might cause almost as much bikeshedding as C++ support in libc 21:44:56 but i am nothing if not a massive a troll, so let's find out 21:48:35 * lw wonders if we're allowed to declare variables anywhere other than the function start nowadays 21:48:39 doesn't C support this now? 21:48:56 "now"? for literal decades. 21:49:28 top of any block, for decades. Anywhere at all, yes just recent 21:49:57 jgh, C99 allows that, no? 21:50:03 I was wondering if it was even c89 21:50:22 i thought it was in C99 but i'm not really sure without checking the standard 21:50:34 don't think so, but I could be wrong... I'm stuck in the 80's 21:50:42 i'm also not sure src/ is allowed to use anything later than C99... isn't the C11 update still in progress? 21:54:48 lw: yes, still not done 21:55:41 but it might also just be style(9) to prefer variables only at function / block start 22:04:47 rtprio: looks like an MTU issue 22:05:30 wheeeee https://github.com/freebsd/freebsd-src/pull/1100 22:05:31 Title: move traceroute from contrib to base by llfw · Pull Request #1100 · freebsd/freebsd-src · GitHub 22:16:31 Question for the pf experts out there. I have a few Asterisk PBXs that I’m looking to secure behind a separate FreeBSD box with pf rules as the firewall. In iptables on the CentOS Asterisk PBX’s today I use a rule of “-A INPUT -p udp -m string -i eth0 --dport 5060 -j ACCEPT --string "REGISTER sip:[FQDN HERE]" --algo bm” to look for if you know the FQDN, you’re allowed. Is there an equivalent way to do this in pf? 23:44:21 hi all, is this article valid with freebsd13 https://calomel.org/freebsd_network_tuning.html 23:44:22 Title: FreeBSD Network Performance Tuning @ Calomel.org 23:56:14 * lw wonders if using zfs (rather than ufs) on a bhyve vm is a bad idea 23:56:55 use zfs on the host 23:56:58 ufs on the client 23:57:37 daemon: do you have any numbers to support that? 23:59:30 no and I do not have a server handy to prove it, but double caching is generally a bad idea in any case 23:59:53 well, UFS also caches, unless you mean to mount it with directio or something? (does UFS support that?)