- Kernel -- software that manages the system by providing access to hardware and other resources (memory, network stack, scheduling cpu, etc). Runs in priveleged CPU mode -- kernel mode. It uses kernel-space stack.
- Process -- an OS abstraction for running programs. Runs in user mode with access to kernel mode via system calls. It consists of: memory address space, file descriptors, thread stacks, registers. Process uses user-space stacks. For example, syscalls use a s kernel exception stack associated with each thread.
Discover gists
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.
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.
| services: | |
| bonsai: | |
| image: rocm/dev-ubuntu-24.04@sha256:86e11093b4a7ec2a79b1b6701d10e840a6994f21c7e05929b51eb9be361c683a | |
| container_name: bonsai-2-27b | |
| restart: unless-stopped | |
| devices: | |
| - /dev/kfd:/dev/kfd | |
| - /dev/dri:/dev/dri | |
| environment: | |
| HSA_OVERRIDE_GFX_VERSION: 10.3.0 |
| <div align="center"> | |
| <h1>Interstellar V5</h1> | |
| <h3>Interstellar is one of the most modern and popular unblocking sites.</h3> | |
| ### [Join our Discord!](https://discord.gg/interstellar) | |
| </div> | |
| > **If you do fork this repo, please give the original repo a star! It helps out alot and only 30% of people who fork give us a star... besides, you know you want to...** | |
| <h2 align="center">Features</h2> |
How to add custom fonts to a webpage:
-
Generate web fonts for every browser eg, use https://www.fontsquirrel.com/tools/webfont-generator or https://transfonter.org/
-
Add fonts to
css/fontsfolder or equivalent -
Look inside downloaded font files for a
stylesheet.cssor equivalent and copy the@font-face, while adjusting the file paths to match the location of the font folder@font-face { font-family: "Some font"; src: url("css/fonts/some-font.eot");
src: url("css/fonts/some-font.woff") format("woff"),
A 2005 booklet with mission statement from Scott McNealy.
| // ==UserScript== | |
| // @name IVAC PAYMENT ASSISTANT 8.0 | |
| // @namespace http://tampermonkey.net/ | |
| // @version 8.0 | |
| // @description Optimized payment flow with available slot notification, Cloudflare CAPTCHA support, Auto Cap-Solver integrated with App-Info and Pay Now, draggable panel with minimize/maximize, last button click timer, and rate limit display | |
| // @match https://payment.ivacbd.com/* | |
| // @match https://www.ivacbd.com/* | |
| // @grant GM_xmlhttpRequest | |
| // @grant GM_addStyle | |
| // @grant GM_setValue |
What this is: a single-file CLI and a matching agent skill that give any coding agent
(Claude Code, Codex, OpenCode) a fast, cheap, calibrated second opinion. The agent stays the
reasoning model; jev answers the narrow, repeated judgments (is this relevant? which
bucket? how severe? does the source support this claim?) so the agent never has to read a
thousand items into its context window or trust its own uncalibrated confidence.
Why it exists: LLM agents are expensive and inconsistent at high-volume judgment calls, and they cannot tell you how sure they are. A decision model that returns a real
| #include <stdio.h> | |
| #include <stdlib.h> | |
| void mergesort(int *v, int n); | |
| void sort(int *v, int *c, int i, int f); | |
| void merge(int *v, int *c, int i, int m, int f); | |
| int main (void) { | |
| int i; | |
| int v[8] = { -1, 7, -3, 11, 4, -2, 4, 8 }; |
- Push back on genuinely bad ideas, with reasoning. Point out bugs, misleading names, and better approaches when you see them. Direct but collaborative.
- If requirements are ambiguous or a design decision could reasonably go multiple ways, ask rather than guess. A quick question is cheaper than reworking a wrong assumption.
- If a prompt looks damaged or wrong, STOP and say so — truncated mid-sentence, duplicated blocks, garbled copy/paste, references to context that doesn't exist, or