Skip to content

Instantly share code, notes, and snippets.

View Fiooodooor's full-sized avatar

Milosz Linkiewicz Fiooodooor

View GitHub Profile
# agentic with "Kimi-K2-Instruct-0905" via "novita logonovita"
Below is a complete, ready-to-execute “AI-Swarm” that incrementally ports any high-performance Linux Ethernet NIC driver to FreeBSD with **zero overhead** and **zero changes to the original Linux source tree**.
The swarm is 100 % modular: every OS dependency is injected through a **shim layer** (seams: `#ifdef` trees, inline wrappers, weak symbols, KPI mapping headers).
Adding a third OS tomorrow means **only extending the shim**, never touching Linux or FreeBSD code again.
The deliverable is:
1. A **team design** (roles, iterations, sub-tasks, chapters).
2. A **transition plan** (what happens in which sprint).

Quick Reference — Bare Metal to Kubernetes

Master Class Handout (1-pager per session)


SESSION 1 CHEAT SHEET: Bare Metal → Virtualization

The Stack

VMs → Hypervisor → Hardware

examples inside the gist

Let me check the current setup script and runtime options to give you the exact commands:

Ran terminal command: cd /opt/llm3/vhelm-ai-swarm-orchestrator && head -25 scripts/setup-full-stack.sh | grep -E "^#" && echo "=== FLAGS ===" && grep -E "^\s+--" scripts/setup-full-stack.sh | head -15

Ran terminal command: cd /opt/llm3/vhelm-ai-swarm-orchestrator && python3 nic_porting_graph_runtime.py --help 2>&1

Von Neumann's Insight: Life is Embodied Computation

Mathematical Foundation Crossbar energy:

$$ (E = V^2 \sum G_{ij} \cdot \text{spikes}) $$

. Scalability via percolation theory: giant component forms when average degree

Multi-OS Ethernet Driver Engineering Manual (07.III.2026)

  • Pre-ambule - Framework-independent, native-API-first NIC dataplane porting foundation
  • Volume I - Framework-independent, native-API-first NIC dataplane porting foundation, Linux extraction, Intel-style descriptor architecture, portable core, major portions of the FreeBSD skeleton
  • Volume IIComplete Native FreeBSD Driver Skeleton
  • Volume IIIWindows NDIS Miniport Driver Architecture and Implementation
  • Volume IVCross-OS NIC Driver Portability Guide and Multi-OS adapters (illumos, NetBSD, RTOS)
  • Volume VSelf-hosted Automated LangGraph Multi-Agent Orchestration
  • Volume VI - Modern High-Performance Networking Stack Architectures (DPDK, AF_XDP, virtio-net, SR-IOV, RDMA Driver Internals)
  • Volume VII - Deep Internal Architecture of Modern Ethernet NICs
@Fiooodooor
Fiooodooor / sunfish-update-log-201023-1242.txt
Created January 4, 2026 04:42 — forked from nooriro/sunfish-update-log-201023-1242.txt
sunfish update log (SUCCEEDED LOG) / from QD4A.200805.003 to RP1A.201005.006 (using FULL OTA IMAGE) / Update URL (Full OTA Image): https://ota.googlezip.net/packages/ota-api/google_sunfish_sunfish/4e536e3e15bfab486e26dbed8170f2e0ad164456.zip
--------- beginning of system
--------- beginning of main
10-23 12:41:58.177 3342 5418 I SystemUpdate: [Installation,ReceiverIntentOperation] Received intent: Intent { act=com.google.android.gms.update.BASE_MODULE_INIT cat=[targeted_intent_op_prefix:.update.control.ReceiverIntentOperation] cmp=com.google.android.gms/.chimera.GmsIntentOperationService }.
10-23 12:41:58.520 3342 5418 I SystemUpdate: [Control,InstallationControl] Update URL changed from "" to "https://ota.googlezip.net/packages/ota-api/google_sunfish_sunfish/4e536e3e15bfab486e26dbed8170f2e0ad164456.zip".
10-23 12:41:58.663 3342 6201 I SystemUpdate: [Execution,InstallationEventIntentOperation] Handling event of type 1.
10-23 12:41:58.683 3342 6201 I SystemUpdate: [Execution,InstallationEventIntentOperation] Handling event of type 102.
10-23 12:41:58.685 3342 6201 I SystemUpdate: [Execution,ExecutionManager] Finishing the current execution.
10-23 12:41:58.728 3342 6201 I SystemUpdate: [Execution,SynchronizedUpdateEngine] reset()
10-23
#!/usr/bin/env bash
# gpuup.sh - NVIDIA driver and CUDA toolkit installer for Ubuntu 22.04/24.04
set -Eeuo pipefail
if [[ "${GPUUP_DEBUG:-0}" == "1" ]]; then
set -x
fi
if [[ "${GPUUP_TRACE:-0}" == "1" ]]; then
https://x.com/i/grok/share/u7qUed0FwgrMDIA7nMJl11iLL
coverity https://x.com/i/grok/share/eZ60X6fI3c7i6ZUutW0eeDAm4
netbox: https://x.com/i/grok/share/kBw2S30rCgA3mZ5VMKtESNdVS
https://x.com/i/grok/share/UZUEebJmIIqhEFdSZDUZYukDe
"Configuring HCI Harvester for VLAN 1076": https://x.com/i/grok/share/motnb7lGG6VLPnop4m9ctsxVi
"Ansible Script for PXE Boot via BMC LAN": https://x.com/i/grok/share/Z4Cxy97XDEjGbWMAnJEptkSln
"Ansible Script for PXE Boot via BMC": https://x.com/i/grok/share/8dU03Skr2MCECoGw7SJsscXsC
"Harvester Cluster Networking and Hugepages Setup": https://x.com/i/grok/share/uWufwtXjrgOg11yc3Q64qk9ke

Migrating a PostgreSQL database from version 15 to version 16 for NetBox v4 involves upgrading the PostgreSQL instance while ensuring the NetBox data remains intact. PostgreSQL 16 introduces improvements like better performance, new monitoring features, and some syntax changes, but it’s a minor version upgrade, so the process is relatively straightforward. Below is a step-by-step guide to migrate your NetBox v4 database from PostgreSQL 15 to PostgreSQL 16. Prerequisites Current Setup: NetBox v4 running with PostgreSQL 15. Target Setup: A system where PostgreSQL 16 will be installed (this can be the same server or a different one). Backup: Always back up your database before starting. Downtime: Plan for downtime, as NetBox will be unavailable during the migration. Compatibility: NetBox v4 supports PostgreSQL 16 (as of March 07, 2025, based on current trends and NetBox’s requirements), but verify this with the latest NetBox documentation if you’re using a newer release. Steps to Migrate PostgreSQL 15 to Postgre