karpathy

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

noslin005

insmod tga
insmod png
insmod gfxterm
insmod lspci
insmod vbe
insmod ntfs
insmod chain
insmod biosdisk
insmod font
#GRUB_HIDDEN_TIMEOUT=10 #0 par defaut

noslin005

[ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
mkdir /target

# list drives
fdisk -l

# find each partition, i.e, /, /boot, /boot/efi and /home

# mount them

noslin005

Redfish cheat sheet

This document is intended to provide a set of [Redfish][1] client commands for OpenBMC usage. (Using CURL commands)

Query Root

$ export bmc=xx.xx.xx.xx
$ curl -b cjar -k https://${bmc}/redfish/v1

noslin005

1. Install tools and config IPXE

# Install compiler and dependencies
sudo apt-get install -y git gcc make liblzma-dev

# Grab the source code
git clone https://github.com/ipxe/ipxe.git
cd ipxe/src

# Enable NFS support

noslin005

authoritative;
allow bootp;
default-lease-time 600;
max-lease-time 7200;
log-facility local0;
ddns-update-style none;

# Parent class for all test
class "test" {
	match concat(

noslin005

Firewall

# INTERNAL ZONE
firewall-cmd --set-default-zone=internal
firewall-cmd --zone=internal --add-interface=bond0 --permanent
firewall-cmd --zone=internal --add-service={dhcp,tftp,http,https,dns,nfs,mountd,rpc-bind} --permanent

DHCP

noslin005

#!/bin/bash
set -euo pipefail

# --- Settings ---
IMG="rocky_installer.img"
VMDK="rocky_installer.vmdk"
SIZE="20G"
LABEL="ROCKY_INSTALLER"
ISO="/VMs/isos/Rocky-9.5-x86_64-dvd.iso"
MNT_ISO="/mnt/iso"

noslin005

VXLAN+VLAN+BRIDGE+LINUX

• Both Host A and Host B are running Linux with identical VXLAN and VLAN aware bridge configurations.
• They communicate through a VXLAN overlay (ID 100) carried over multicast (239.1.1.1) on UDP port 4789.
• VLANs are extended across the VXLAN tunnel.
• Subinterfaces br0.10 and br0.20 provide access to specific VLAN networks (10 and 20).
• Devices on the same VLAN across hosts can directly communicate as if they are on the same Layer 2 segment.

Use iproute2 tools (testing)

ThomasFrans

A Gentle Introduction to Git Worktree

Git worktree has become a major part of how I use Git over the past year. Anytime I mention it somewhere however, I get reactions from people who have never heard about the feature. Others have heard about it, but don't know how exactly it works or why it's beneficial. That's why I decided to write a short tutorial/introduction on this awesome feature that is baked right into the very git you are already using. I hope this can help people discover worktrees and be a gentle introduction on how to get started using them.

What is Git worktree

Git worktree facilitates working with multiple branches. In a normal Git workflow, you can only ever have one branch checked out at a single time.