Post B76rCkOML3MCD3rbEW by brettm@swarm.coiloptic.org
(DIR) More posts by brettm@swarm.coiloptic.org
(DIR) Post #B73LA4mCJTboYSoftQ by grahamperrin@mastodon.bsd.cafe
2026-06-06T09:45:14Z
0 likes, 1 repeats
FreeBSD / src / 56e5998 / loader.efi: Fix when staging moves late - FreshBSDhttps://freshbsd.org/freebsd/src/commit/56e59980b673affb82c8c5da9d4338e10d946acd– an instant cherry-pick from the main branch, before builds began for 15.1-RC3 (the third release candidate).From the commit log message: "… This bug hunt was greatly assisted by Claude who looked at the crash from the EFI boot loader and surmised that we weren't jumping to the code we thought we were jumping to. After inspecting the code, I asked claude how corruption could happen (I thought overwriting the page table), but claude notice the possibility that staging might change after we computed the page table, and this fix is the result. Claude didn't suggest a diff, but did provide many helpful clues that lead me to this fix."Additional context (RC3): <https://www.reddit.com/r/freebsd/comments/1ty1z0n/comment/oq21krm/>#AI #Anthropic #Claude #FreeBSD
(DIR) Post #B73LzCyBbsl0jco0ga by jae@mastodon.bsd.cafe
2026-06-06T10:08:13Z
0 likes, 0 repeats
@grahamperrin there's a lot of people who hate it and can't articulate why. ive found it to be a useful tool primarily for research and disparate tasking, but its not something id rely solely on. i share a similar sentiment in that im not a proponent of ai but im a proponent of approaching a problemset with rationality and focused tooling. its interesting to see kernel#2 leveraging models for bug hunting. while it may not be widely adopted, it sends a signal that it may be worth exploring.
(DIR) Post #B73NpsUwYO0GXro3Dk by grahamperrin@mastodon.bsd.cafe
2026-06-06T10:28:55Z
0 likes, 0 repeats
RE: https://mastodon.bsd.cafe/@grahamperrin/116515611978395782@jae thanks. For haters, I have a standard response.It was surprisingly difficult to find a good mix of subreddits, because at least one of them has rules that are ignored by the makers of the rules. That's the members' problem, not mine 🙂
(DIR) Post #B746xZOhwt85Ylvorw by jae@mastodon.bsd.cafe
2026-06-06T18:54:34Z
0 likes, 0 repeats
@grahamperrin the cantrill bit feels like sop with the slight backwalk and forcing others into a box. i will say when i see things like "empathy" mixed with tech, it doesn't sit well. usually a sign that there's a laundry-list coc that requires a team to interpret. usually a signal that it's going to be a rough ride in a project from my own experience (can't speak for others)luckily we don't have much of that in bsd-*
(DIR) Post #B756ewhLHv57Ttj8HQ by grahamperrin@mastodon.bsd.cafe
2026-06-07T06:25:48Z
0 likes, 0 repeats
@jae I refrain from discussing codes of conduct at this time.
(DIR) Post #B75BCD8vZCV9rCkOHI by brettm@swarm.coiloptic.org
2026-06-07T07:16:12Z
0 likes, 0 repeats
@grahamperrin@bsd.cafe i thought freebsd brought in a no-ai policy?
(DIR) Post #B75Jj3KzqKDAdUZ0Cm by jae@mastodon.bsd.cafe
2026-06-07T08:52:16Z
0 likes, 0 repeats
@grahamperrin we'll get along fine.
(DIR) Post #B76jmBCJrrqRqfcHXU by grahamperrin@mastodon.bsd.cafe
2026-06-08T00:12:57Z
0 likes, 0 repeats
@brettm I can think of one person who might have that agenda, however I'm not aware of a policy. <https://www.reddit.com/r/freebsd/comments/1tohoxo/comment/ookk03w/> at the end of May 2026 included a link to discussion in April, and a plea: "Let's await an official statement from the Project. Please be patient."Someone doesn't like the plea 🤷 FreeBSD's position on the use of AI-generated code? : r/freebsdhttps://www.reddit.com/r/freebsd/comments/1sbzf3q/freebsds_position_on_the_use_of_aigenerated_code/
(DIR) Post #B76jmCDm3wbR1TIxRg by brettm@swarm.coiloptic.org
2026-06-08T01:18:20Z
0 likes, 0 repeats
Hi Graham,Thanks for the reply, your links sent me down the rabbit hole. It is certainly not easy to find a straightforward answer! Whatever the policy is (or will eventually be) it seems AI-generated code is already in FreeBSD source 😞(see examples in "AI code reviews" https://codeberg.org/small-hack/open-slopware#operating-systems)I'm getting a new laptop and was going to install freebsd or dragonflybsd on it but will stick to openbsd after reading Theo's email: https://marc.info/?l=openbsd-tech&m=177411863202734&w=2(the two commits listed as showing "permissive AI policy" for openbsd are actually "AI found the bug and a human wrote the code" which is as good as it gets now apparently)CC: @grahamperrin@bsd.cafe
(DIR) Post #B76oFnaYbsIn89KfwW by grahamperrin@mastodon.bsd.cafe
2026-06-08T01:35:58Z
0 likes, 0 repeats
@brettm if you can (please) provide a direct link to a commit in the FreeBSD src tree, I'll happily take a look. A firm "no" to any small-hack/open-slopware link.
(DIR) Post #B76oFoPbY58RgTDRVg by brettm@swarm.coiloptic.org
2026-06-08T02:08:25Z
0 likes, 0 repeats
@grahamperrin@bsd.cafethese are the github mirror links of the freebsd source tree:Assisted-By:Claude Opus 4.6 (1M context)https://github.com/freebsd/freebsd-src/commit/e1cff854997884ed9b7251d409d9c9c7a025606dAssisted-by: Gemini:gemini-3.1-prohttps://github.com/freebsd/freebsd-src/commit/1644e2ffd2640fa3e2c191ceaf048a5fc8399493clefru and claude authoredhttps://github.com/freebsd/freebsd-src/commit/6495dafd58b94a44fc9bc966ef47d6bc6916f5b9
(DIR) Post #B76oTYHwIDFNjQBLqi by grahamperrin@mastodon.bsd.cafe
2026-06-08T01:22:22Z
0 likes, 0 repeats
RE: https://mastodon.bsd.cafe/@grahamperrin/116662900525252138@brettm I have an extremely low opinion of that so-called 'Open Slopware' repo. Beware of misinformation and so on – check out the mastodon.social link in the discussion in The Register.
(DIR) Post #B76oTZWrgCmRa0Amki by brettm@swarm.coiloptic.org
2026-06-08T02:11:01Z
0 likes, 0 repeats
@grahamperrin@bsd.cafe openslopware links to commits are pretty useful in my experience, not always correct but generally are, eg can misinterpret 'found by' as 'written by' sometimes. but that is often due to the 'human author' being vague and/or misleading in commit messages
(DIR) Post #B76qL6bTXZb7SaQ6ue by grahamperrin@mastodon.bsd.cafe
2026-06-08T02:29:10Z
0 likes, 0 repeats
@brettm a firm "no" to discussing the Open Slopware repo. In addition to my earlier comment: their tactics towards me were despicable.
(DIR) Post #B76qL7vMd76JYYjVYG by brettm@swarm.coiloptic.org
2026-06-08T02:31:10Z
0 likes, 0 repeats
good to knowCC: @grahamperrin@bsd.cafe
(DIR) Post #B76rCjEkdI4qcyMPcO by grahamperrin@mastodon.bsd.cafe
2026-06-08T02:33:42Z
0 likes, 0 repeats
@brettm thanks. Maybe you can prominently edit <https://swarm.coiloptic.org/brettm/p/1780882372.699734> to make clear that it's more OpenZFS than FreeBSD.
(DIR) Post #B76rCkOML3MCD3rbEW by brettm@swarm.coiloptic.org
2026-06-08T02:41:10Z
0 likes, 0 repeats
Snac edits do not probagate unfortunately.My view is if its in the FreBSD kernel then its in the FreeBSD kernel. No free pass just because it got imported. Someone still chose to let it in. It still has the same extremely dubious provenance now matter how many 'hops' got made along the way.(Probably OpenBSD will have the same problem down the track with Clang/LLVM, and NetBSD with GCC or whatever they use to compile)CC: @grahamperrin@bsd.cafe
(DIR) Post #B76sRAumciWuTfTOZU by grahamperrin@mastodon.bsd.cafe
2026-06-08T02:43:51Z
0 likes, 0 repeats
@brettm I'm not asking for a pass. I'm asking for balance. The post points the finger at FreeBSD without mentioning OpenZFS.
(DIR) Post #B76sRBzQcvq7oMecS0 by brettm@swarm.coiloptic.org
2026-06-08T02:54:48Z
0 likes, 0 repeats
@grahamperrin@bsd.cafe you are starting to sound a bit blinded.the code is in the freebsd kernel and somebody with commit access put it there on purpose that is the issue, not 'was it a freebsd coder or openzfs coder who did the vibe coding?'
(DIR) Post #B76uroVCGFjAh1KqPI by grahamperrin@mastodon.bsd.cafe
2026-06-08T02:57:00Z
0 likes, 0 repeats
@brettm I'm not blinded, just disappointed that your post pointed the finger at FreeBSD without offering any OpenZFS context. I know from experience that too many people do not take the time to join the dots. They'll read your post but have no idea about the OpenZFS context. <https://not.an.evilcyberhacker.net/notes/an86br1ouyyz00tu> might be a good example.
(DIR) Post #B76urpZqGT2O1iW4Ho by brettm@swarm.coiloptic.org
2026-06-08T03:22:28Z
0 likes, 0 repeats
@grahamperrin@bsd.cafe omg is chatgpt writing your responses? Because you started out reasonable and now are not making any sense at all. i will put the important points in allcaps in the hope that they penetrate.The issue is:VIBE CODED COMMITS IN THE FREEBSD SOURCE TREEThe issue is NOT:whether somebody at openzfs or at freebsd did the vibe codingThere is not 'dots' there is no 'context' there is only VIBE CODED COMMITS IN THE FREEBSD SOURCE TREEI am pointing the finger AT FREEBSD for committing VIBE CODED COMMITS IN THE FREEBSD SOURCE TREE.Please tell me that this now clear.