900 karma · joined July 27, 2015
ETA: I've got Homebrew 7 building packages from source on an Intel Mac running Monterey; nothing yet required from MacPorts and a pretty minimal patch to the installer. I'd probably want to add legacy-support from MacPorts and update the macOS build environment to add it as an extra library on Intel Macs if I were to continue.
That being said, I'm sure y'all talked about continuing to support Intel Macs as source-based and ultimately decided against it, so it's unlikely that this will be interesting to the team. But let me know if I'm wrong and I'll open a couple PRs for further discussion.
I generally discourage my agents from storing memories locally because they don't travel; I'd much rather have a small in-repo document—whether it's an architectural decision or TODO or session log entry or runbook or environmental quirk or something else—that the prompt/CLAUDE.md/whatever can guide agents to grep and sed. Then I can dispatch work to a local agent, or a local agent running in a sandbox, or an agent running in a provider's cloud environment, or a GitHub agentic workflow running a headless harness, etc. and they all have access to it. Another benefit is that memory updates get PRs and reviews like everything else.
So what am I missing by not using something like engrim or gbrain?
ETA: specifically on older server/workstation boards instead of the stock firwmare
Looks like prices on the E810-XXVDA2 have come up since the last time I looked while prices on the ConnectX-6 Lx have come down, so that'd be a good option!
Yep still are, although fiber transceivers are surprisingly affordable, and of course you can usually re-use jumpers when you upgrade transceivers so TCO over a couple generations might be comparable.
It's truly bananas especially in a homelab environment. Nearly every time I've thought to myself "oh I can just do a copper gbic for this" it's been the wrong thing to do.
I spun up some iSCSI-backed SQL Server a few months ago and 10G couldn't keep up with the workload, so I dropped in a pair of 100G ConnectX-4 cards with iSER (iSCSI Extensions for RDMA) support for that particular use-case.
Just because your uplink is less than 10G doesn't mean the rest of your network can't be a bit more capable. :)
ETA: OK, there are quite a few highly-rated options on Amazon, so I just need to solve the "putting music on there" problem and the "dropping it and immediately destroying it problem".
I ran Slackware on my BP6 while I was in college. Of course CONFIG_SMP wasn't set in the default kernel config at the time so you had to build your own. Great for running bind, apache, sendmail, etc., and of course NetQuake servers. :)
Yes but they got hard to find in a hurry once word spread. I had two 366s in my BP6 overclocked to 550 but IIRC I had to buy a few to find two that were stable at this frequency.
> There was a whole cottage industry of folks modding these CPUs as a small side hustle for people who were not comfortable with soldering onto CPU pins if you wanted to put these into a SMP system.
No modifications necessary with the BP6.
It's got a middling display (the 2-in-1 display is better) and a somewhat dated Hawk Point SoC, but it's fine for running to a client's site for imaging or network troubleshooting or what have you. I still don't think it's going to last very long, but it's a nice complement to the MacBook I use for client dev work and it didn't break the bank.
I've been dealing with this recently. Linux won't hibernate if you have Secure Boot enabled, even if your swap is encrypted. So I either have to leave my laptop plugged in all the time or remember to shut it down before unplugging it so it doesn't completely drain its battery while sleeping.