From 21a41cb1a4a8b8ef58f490dff30f1df4f7d11266 Mon Sep 17 00:00:00 2001 From: "Joshua M. Boniface" Date: Sun, 13 Nov 2022 01:39:37 -0500 Subject: [PATCH] Add disclaimer to RPI BMC post --- content/a-raspberry-pi-bmc.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/a-raspberry-pi-bmc.md b/content/a-raspberry-pi-bmc.md index c00a3de..e28fbf7 100644 --- a/content/a-raspberry-pi-bmc.md +++ b/content/a-raspberry-pi-bmc.md @@ -9,6 +9,8 @@ draft = false +++ +**NOTICE:** This project is long-since obsoleted. I never did complete it, and ended up just buying some IPMI-capable motherboards. I would receommend the various Pi-KVM solutions now available as much better, more robust replacements to this project. + IPMI BMCs are pretty ubiquitous in the datacenter and enterprise computing, because in a warehouse full of computers, finding and walking up to one just to reset it or check its console is quite daunting. The same goes for a home server: it may just be in my basement, but in a closed-up rack it becomes a huge hassle to manage a machine without IPMI. I try to get it on every motherboard I buy, but currently my Ceph nodes are running with motherboards that lack built-in IPMI. After an incident with one machine while I was on vacation, I finally decided that they needed remote management, and I decided to make my own BMC for them rather than waste money on replacement (IPMI-capable) motherboards. ## Enter the Raspberry Pi