00:00:55 Jj 00:01:06 Sorry, hit enter by mistake 00:01:28 There is talk about git being replaced by jj, which uses the Apache license (BSD friendly) 00:02:52 Apparently it's git-compatible or it's own alternative...i think. Gits internals really are garbage. 00:07:56 TIL jj - any relation to got? 00:08:11 https://github.com/jj-vcs/jj 00:08:23 farhan: Who's planning this? 00:08:44 Hm, Rust. 00:08:46 Planning? I don't follow? 00:08:58 "< farhan> There is talk about git being replaced by jj," 00:09:03 Who's talking about it? 00:09:10 Not sure I want to encourage the Rust community. 00:09:24 Oh...umm..the most credible source: YouTube!! 00:09:55 I'm on team rust, but know the community is largely against it. 00:10:49 I'm also on team "yes, chase shiny new things" 00:15:46 I remain curious about https://gameoftrees.org/ 00:42:51 usually reinventing the wheel produces more money, specially when you must promote the use of whatever language... 00:43:25 lets do GIT again! we have some funds to expend somehow!@#!! 00:43:39 i've never heard of "jj" but there is definitely talk of git being replaced by got 00:43:53 but aiui, got is binary compatible with git, so this doesn't actually matter 00:43:58 ivy: by who lmao? theo? XD 00:44:07 badkat: by freebsd committers 00:44:12 :O 00:52:41 Seems reasonable to me. 01:37:22 i ran into some logistics issues when i was trying to write a script to clone a repo with got 01:37:48 it really doesn't like the thought of keeping the repo contents as a subdir of a worktree 01:40:09 I don't think that's necessarily a deal-breaker, you could keep the .git dir elsewhere and provide some tooling to checkout a .git tree at /usr/src to bridge the gap, but it's still a bit ugly 01:40:28 but the worktree layout's not necessarily compatible 01:41:50 so if you checkout /usr/src with got, there's no quick and dirty way to conver that to a git worktree; you have to blow it away and setup a new worktree from the repo 01:42:19 (as far as I've found) 02:04:53 I'm having trouble finding where in net80211 a ieee80211_rateset struct is set. Anyone have any insights? 02:05:04 Looking at you kevans (: 02:11:00 farhan: looks like it's setup via ieee80211_setmode -> ieee80211_setbasicrates, typically 02:12:27 * farhan searches, thank you! 02:13:35 ahh, setbasicrates in ieee80211_proto.c 02:29:11 yeah, there- 03:07:12 just remember.. you can just put some yacht rock on.. and try to use the telescope (neovim plugin) to search and then almost want to throw your monitor across the room.. when you can not find something 03:11:58 kevans: Hrm, I thought they were supposed to be interchangeable by design. TIL. 03:19:14 mason: you can at least reuse the same repository, so it's not a total loss if you try to switch between them 03:19:34 you just can't seem to setup a layout wherein both git and got will both Just Work(TM) without a bit of fun 03:20:18 That's the kind of thing I'd want to do. :P I'm glad you've experimented with it. 03:20:27 I posted to freebsd-git about it just a bit ago. I don't know if this is really a problem, as long as we can provide something to do the conversion to a git repo 03:21:46 otherwise we'd probably look at a script that can do your standard checkout and update along a branch, just enough to, e.g., get a copy of the ports tree and move it forward in case the version you pulled was tragically broken in some fashion 03:22:07 just an idea, not really a solid plan that anyone's agreed to 03:22:49 got is that the openbsd "game" 03:22:58 i see it popup a few times on discoverbsd.com and X.com 03:23:20 This uncovers a bit of ignorance on my part. If you git push, does that invoke a git (or got?) binary on the other end? I wonder if migration could be made to happen via pushes or clones. 03:24:47 voy4g3r2: gameoftrees, yes 03:25:20 mason: yes, a push would typically invoke a git on the other side to receive the push 03:25:36 but afaik that wouldn't strictly be necessary, the concern is we don't necessarily want to expose got 03:25:46 kk 03:34:49 ah, thanks kevans .. i am over here just dealing with git branches on small projects.. 03:35:03 and as i learn more about git.. i wish client would STOP using bitbucket.. blargh 03:35:21 i find bitbucket to be less bad than some alternatives, at least 03:36:17 this is true.. the workflow that is "standard" makes managing releases and documentation horrible 03:37:02 i am also the person receiving the output.. i asked for access to it and then people started asking me.. to do code reviews.. 03:37:24 i quicly asked to have my access revoked.. i just wanted to see the "signature" and the release details and someone was on vacation.. 03:38:14 "standard" == customized and configured to some odd committee based metric.. that does not make sense.. 03:38:39 i had one developer.. using a local version of git.. doing all the branches/merges/management of code.. then just throwing up a branch to merge in bitbucket.. 03:39:11 and we were like.. why do you have so many commits.. but we do not see the work in bitbucket.. "oh well i use my own copy of git, on my machine.. because i do not like bitbucket seeing my work..." 03:40:39 oh well, nothing to do with this conversation.. just a baabble 04:17:12 g'evening 08:17:38 what would be the best way to move several ZFS datasets from one machine to another ? 08:23:48 is zfs snapshot -r zroot_jupiler/data/jails@migrate ; zfs send -Rv zroot_jupiler/data/jails@migrate | ssh root@myhost zfs recv -eu zroot_stout/data/jails enough ? 10:19:00 mage: it's been some time since i used zfs commands, so i can't confirm the flags but the structure of the command (send -> ssh pipe -> recv) looks right to me 10:20:53 that should be enough indeed 10:26:01 if the dataset is big, you may want to pipe it to a file instead on the source machine, rsync it to the destination machine and then pipe it to zfs recv 10:32:03 ^ so that rsync could resume the transfer if your connection broke 18:38:42 hi, when installing freebsd 14.2 into qemu guest vm, does it make any sense to use ZFS (which ends up in qemu raw image) or also does it not have any disadvantage vs the UFS system? thanks. 18:39:36 clemens3: i suggest using zfs so you have the benefit of snapshots and boot environments, which makes upgrades easier and less risky. however if you have low memory (< 4GB) you may find UFS works better 18:39:43 clemens3: it's worth learning ZFS, even if it's only a VM to play wiht FreeBSD 18:40:15 (i run ZFS on systems with 2GB RAM and it's fine, but this is definitely not a super recommended configuration) 18:41:00 good, thanks all! 18:41:18 ZFS with low RAM isn't a problem unless you're using de-dup. ZFS will be fine on low-memory systems (for the most part.) 18:41:41 So, just don't use de-duplication. :) 18:42:17 ok, always wondered what they did back in the sparc days with ZFS when 4GB memory where gigantic 18:42:32 if it was ok then, should be ok now 18:43:37 they told people not to use ZFS on small systems :-) 18:43:58 4GB was basically the minimum you'd expect in a server or workstation back then 18:44:19 it didn't work on i386 without proper tuning 18:44:30 (iirc, it was also recommended not to use it on 32-bit systems, but i think that's been improved a bit... not that you should really be using 32-bit systems anymore anymore) 18:45:29 AFIK it doesn't work now on arm (32-bit), but it used to work in the past (2-3 years ago) 18:47:32 freebsd still doesn't have ARC integration with the memory manager 18:48:21 no, but there were some significant improvements to vm reclamation of memory from arc a few months back so that should be less of a problem than it used to be 18:48:41 i still set arc_max in a few places 18:49:11 yes, it's first step when you suffer from memory starvation 18:49:13 and make sure your filesystem doesn't get *too* full, might start losing files... 18:50:59 no worries 18:52:30 so, why is it that the x86 definition of struct trapframe has amd64 registers? 18:52:50 Back in the day, it was designed for Sparc64 systems. It was kinda hacky in the beginning to use it on i384/x86_64 (the latter being more supported, obviously) 18:53:12 putting it all in the same file and then surrounding it with #ifdef __amd64__ defeats the purpose of the machine-specific include directories 18:53:28 ring0_starr: Because hacky? 19:52:44 are recent improvements in 802.11 allowing to utilise 802.11ac now ? 19:55:21 mzar: I believe so? I tested out some changes a while back and I could've sworn *ac was working just fine. 19:56:52 thanks for feedback ek 19:58:38 mzar: Sure thing. Actually, now you have me curious and second guessing. I'm gonna re-install on one of these laptops and check it out. :) 19:58:43 Cure some of my boredom. 20:01:42 let me wish you a fun and fruitful installation then 20:02:18 om' 20:02:57 Haha. Thank you! 20:29:01 the code is subtly wrong for cpu_fetch_syscall_args on x86 and amd64, at least 20:30:04 argp starts at &frame->tf_rdi and then iterates through the struct as though it were an array 20:31:35 the assumption being that the next member of the struct starts at sizeof(syscallarg_t) bytes after, which is perfectly valid for subsequent array elements, but not for struct members due to potential alignment issues 20:32:34 maybe in a parallel universe this code is fine because the rules around struct member alignment have been relaxed by having stronger guarantees in the standard 20:33:11 but here, it is not, because the C standard allows for too many gotchas in using code like this 20:38:03 ring0_starr: I guess we could add some static assertions about the alignment to make you feel better, but generally we won't be doing anything to increase the alignment of the frame 20:39:22 nah it's fine - if there was an architecture encountered where the assumptions made here lead to what is technically UB, you'd notice it immediately by syscalls not working 20:41:06 sure, but otoh it's nice to be able to document these kinds of assumptions in a way that we can detect hijinkery at compile-time instead of runtime 20:41:23 nicer for the human debugger-to-be 20:41:35 you'd need to depend upon _Alignof() which I think is C23 20:42:44 mm no nevermind that's C11, and then changed to alignof() as of C23 20:42:58 hernan604: that command only fetches updates based on the currently installed world but doesn't tell me which upgrades (new releases) are available. 20:43:03 we use _Alignof in some places, which may be shimmed out to __alignof or alignof 20:43:22 our current CSTD in the kernel is gnu17 20:44:07 why is it following a gnu extension when you switched to clang like 12 years ago now? 20:45:46 because gnu added some niceties that were apparently appealing enough for clang to adopt. there is no clang17 that I'm aware of, just gnu17 and c17 20:53:22 ring0_starr: ac wifi depends mostly on the driver implementation btw not in the OS stack itself 21:04:47 what?? 21:05:34 badkat: I'm quite sure ring0_starr and kevans are talking about something else completely. :) 21:07:20 lol i wanted to quote mzar :P 21:07:48 but.. please improve wifi ac in freebsd driver development overlords :(! 21:08:35 i don't even have any 802.11ac hardware to test with 21:18:24 https://cgit.freebsd.org/src/tree/sys/arm64/arm64/trap.c#n166 ????? what is up with this, how do return values work in arm64 21:23:17 err nevermind, i mean why does td_retval get set to anything in this function in any architecture? 21:23:52 the retval is going to just be garbage and overwritten after it actually executes 21:35:00 ring0_starr: might be a good one for -hackers@ if nobody responds 21:35:16 I could speculate, but better to hear from someone with confidence 21:50:40 what is -hackers@? 21:51:31 it seems like void syscalls have their second retval set to the second arg. except for arm64 which just gets 0. 21:51:42 ring0_starr: -hackers@ is a freebsd-hackers@ mailing list 21:52:29 i thought so, just wanted to make sure since there is an irc network by that name too