Skip to content

html templates #144

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
devops-stack merged 1 commit into from
Jul 15, 2026
Merged

html templates #144

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
117 changes: 117 additions & 0 deletions templates/kernel-dna.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,117 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Kernel DNA - Live Linux Kernel Anomaly Detection &amp; Syscall Visualization</title>
<link rel="icon" href="/favicon.ico" sizes="any">
<link rel="icon" type="image/png" sizes="32x32" href="/static/images/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/static/images/favicon-16x16.png">
<link rel="apple-touch-icon" sizes="180x180" href="/static/images/apple-touch-icon.png">
<meta name="description" content="Kernel DNA: a live double-helix visualization of Linux kernel and process telemetry with machine-learning anomaly detection — EWMA/z-score baselining, Isolation Forest scoring, concept-drift detection and STIDE syscall n-gram analysis, in real time.">
<meta name="keywords" content="
kernel dna,
linux kernel anomaly detection,
linux syscall monitoring,
machine learning intrusion detection,
ebpf kernel telemetry,
isolation forest anomaly,
concept drift detection,
stide syscall n-gram,
real time kernel visualization,
linux architecture,
kernel architecture
">
<meta name="robots" content="index, follow">
<link rel="canonical" href="/kernel-dna">
<meta property="og:type" content="website">
<meta property="og:url" content="/kernel-dna">
<meta property="og:title" content="Kernel DNA — Live Linux Kernel Anomaly Detection">
<meta property="og:description" content="A double-helix visualization of live Linux kernel telemetry with ML anomaly detection: EWMA/z-score, Isolation Forest, drift detection and STIDE syscall n-grams.">
<meta property="og:image" content="/static/images/009.png">
<meta property="twitter:card" content="summary_large_image">
<meta property="twitter:url" content="/kernel-dna">
<meta property="twitter:title" content="Kernel DNA — Live Linux Kernel Anomaly Detection">
<meta property="twitter:description" content="Live Linux kernel telemetry as a DNA helix, scored by machine learning: EWMA/z-score, Isolation Forest, drift detection and STIDE syscall n-grams.">
<meta property="twitter:image" content="/static/images/009.png">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebPage",
"name": "Kernel DNA — Live Linux Kernel Anomaly Detection",
"url": "https://ring-0.sh/kernel-dna",
"description": "Live double-helix visualization of Linux kernel and process telemetry with machine-learning anomaly detection: EWMA/z-score baselining, Isolation Forest scoring, concept-drift detection and STIDE syscall n-gram analysis.",
"about": [
{"@type": "Thing", "name": "Linux kernel anomaly detection"},
{"@type": "Thing", "name": "Syscall monitoring"},
{"@type": "Thing", "name": "Machine learning intrusion detection"},
{"@type": "Thing", "name": "Linux kernel architecture"}
],
"isPartOf": {"@type": "WebSite", "name": "ring-0.sh", "url": "https://ring-0.sh/"}
}
</script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/three.js/r128/three.min.js"></script>
<link href="https://fonts.googleapis.com/css2?family=Share+Tech+Mono&display=swap" rel="stylesheet">
<link rel="stylesheet" href="/static/css/main.css?v=3">
<style>
body {
margin: 0;
background: #0E1114;
color: #d4dbe8;
font-family: "Share Tech Mono", monospace;
}
.seo-dna {
position: absolute;
left: -10000px;
width: 1px;
height: 1px;
overflow: hidden;
}
</style>
</head>
<body>
<h1 class="seo-dna">Kernel DNA &mdash; Live Linux Kernel Anomaly Detection</h1>
<section class="seo-dna">
<h2>A DNA Helix of Live Kernel Telemetry</h2>
<p>
Kernel DNA renders the running Linux kernel and its processes as a double-helix strand.
Each bead on the strand is a live telemetry sample &mdash; CPU, memory, I/O, context
switches and syscall activity &mdash; and "mutations" appear where behavior deviates
from the learned baseline. It turns the abstract state of the kernel into an organism
you can watch evolve in real time, driven by real counters from /proc and the process
table.
</p>
<h2>The Machine-Learning Anomaly Pipeline</h2>
<ul>
<li><strong>EWMA + z-score baselining</strong> &mdash; an exponentially weighted moving average learns the normal range of each feature; deviations are scored as z-scores.</li>
<li><strong>Isolation Forest</strong> &mdash; an unsupervised model that isolates rare multi-dimensional feature combinations as anomalies.</li>
<li><strong>Concept-drift detection</strong> &mdash; the system watches the feature distribution over time and triggers automatic retraining when the workload shifts.</li>
<li><strong>STIDE syscall n-grams</strong> &mdash; sequences of system calls are modeled as n-grams so that unusual syscall patterns (a classic intrusion signal) light up.</li>
</ul>
<h2>Why Visualize Kernel Behavior</h2>
<p>
Anomaly detection at the kernel boundary (ring 0) is central to Linux security and
observability. Understanding how syscall patterns, process lineage and resource usage
form a behavioral fingerprint helps reason about the wider Linux architecture and kernel
architecture: where intrusions, crypto-miners or misbehaving services first become
visible. Kernel DNA is the front-end of that pipeline &mdash; the same statistics that
power drift detection and retraining, made visible.
</p>
</section>
<script src="/static/js/safe-utils.js?v=2"></script>
<script src="/static/js/frontend-logger.js?v=2"></script>
<script src="/static/js/kernel-dna.js?v=49"></script>
<script>
(function startKernelDnaPage() {
if (typeof window.KernelDNAVisualization !== 'function') {
console.error('KernelDNAVisualization is not available');
return;
}
const viz = new window.KernelDNAVisualization();
const ok = viz.init('kernel-dna-container');
if (ok === false) return;
viz.activate();
})();
</script>
</body>
</html>
119 changes: 119 additions & 0 deletions templates/linux-devices-subsystem.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,119 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Linux Device Subsystem - Device Model, sysfs, udev &amp; Drivers Visualization</title>
<link rel="icon" href="/favicon.ico" sizes="any">
<link rel="icon" type="image/png" sizes="32x32" href="/static/images/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/static/images/favicon-16x16.png">
<link rel="apple-touch-icon" sizes="180x180" href="/static/images/apple-touch-icon.png">
<meta name="description" content="Interactive Linux device subsystem visualization: the kernel device model (kobjects, buses, classes), sysfs, udev and hotplug, driver binding, and block/char/network devices — driven by real device telemetry in real time.">
<meta name="keywords" content="
linux device subsystem,
linux device model,
linux device drivers,
sysfs udev hotplug,
kobject kset bus driver,
block char network devices,
device tree enumeration,
linux kernel driver binding,
linux architecture,
kernel architecture,
linux kernel device visualization
">
<meta name="robots" content="index, follow">
<link rel="canonical" href="/linux-devices-subsystem">
<meta property="og:type" content="website">
<meta property="og:url" content="/linux-devices-subsystem">
<meta property="og:title" content="Linux Device Subsystem Visualization">
<meta property="og:description" content="The Linux device model visualized: kobjects, buses and classes, sysfs and udev, driver binding and hotplug, block/char/network devices — in real time.">
<meta property="og:image" content="/static/images/009.png">
<meta property="twitter:card" content="summary_large_image">
<meta property="twitter:url" content="/linux-devices-subsystem">
<meta property="twitter:title" content="Linux Device Subsystem Visualization">
<meta property="twitter:description" content="How the Linux kernel models devices: kobjects, buses, sysfs, udev, driver binding and hotplug, visualized live.">
<meta property="twitter:image" content="/static/images/009.png">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebPage",
"name": "Linux Device Subsystem Visualization",
"url": "https://ring-0.sh/linux-devices-subsystem",
"description": "Interactive visualization of the Linux kernel device subsystem: the device model (kobjects, buses, classes), sysfs, udev and hotplug, driver binding, and block/char/network devices.",
"about": [
{"@type": "Thing", "name": "Linux device model"},
{"@type": "Thing", "name": "sysfs"},
{"@type": "Thing", "name": "udev"},
{"@type": "Thing", "name": "Linux kernel architecture"}
],
"isPartOf": {"@type": "WebSite", "name": "ring-0.sh", "url": "https://ring-0.sh/"}
}
</script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/three.js/r128/three.min.js"></script>
<link href="https://fonts.googleapis.com/css2?family=Share+Tech+Mono&display=swap" rel="stylesheet">
<link rel="stylesheet" href="/static/css/main.css?v=3">
<style>
body {
margin: 0;
background: #070c10;
color: #d4dbe8;
font-family: "Share Tech Mono", monospace;
}
.seo-dev {
position: absolute;
left: -10000px;
width: 1px;
height: 1px;
overflow: hidden;
}
</style>
</head>
<body>
<h1 class="seo-dev">Linux Device Subsystem &mdash; Device Model, sysfs &amp; Drivers</h1>
<section class="seo-dev">
<h2>The Linux Device Model</h2>
<p>
This page visualizes the Linux device subsystem &mdash; the unified device model that
the kernel uses to represent every piece of hardware. At its core are kobjects and
ksets, organized into buses (PCI, USB, platform), device classes and drivers. The model
is exported to userspace through sysfs (/sys), and udev listens for hotplug uevents to
create device nodes and apply rules. The visualization is driven by real device
telemetry.
</p>
<h2>Device Subsystem Concepts</h2>
<ul>
<li><strong>Device model</strong> &mdash; kobject/kset reference-counted objects that form the /sys hierarchy of devices, buses and classes.</li>
<li><strong>Buses</strong> &mdash; PCI, USB, platform and virtual buses that enumerate devices and match them to drivers.</li>
<li><strong>Driver binding</strong> &mdash; the probe/remove lifecycle that attaches a driver to a matching device.</li>
<li><strong>sysfs</strong> &mdash; the in-memory filesystem at /sys that exposes device attributes and topology to userspace.</li>
<li><strong>udev + hotplug</strong> &mdash; uevents from the kernel drive device-node creation, permissions and naming.</li>
<li><strong>Device classes</strong> &mdash; block, character and network devices, plus input, sound and GPU classes.</li>
</ul>
<h2>Kernel Architecture Context</h2>
<p>
The device subsystem is the bridge between the Linux kernel and physical hardware,
sitting beneath the filesystem and network subsystems that ultimately depend on block
and network devices. Understanding the device model &mdash; kobjects, buses, sysfs and
driver binding &mdash; is a key part of the overall Linux architecture and kernel
architecture: how hardware is discovered, named and made available to the rest of the
system.
</p>
</section>
<script src="/static/js/safe-utils.js?v=2"></script>
<script src="/static/js/frontend-logger.js?v=2"></script>
<script src="/static/js/devices-belt.js?v=24"></script>
<script>
(function startDevicesPage() {
if (typeof window.DevicesBeltVisualization !== 'function') {
console.error('DevicesBeltVisualization is not available');
return;
}
const viz = new window.DevicesBeltVisualization();
const ok = viz.init('devices-belt-container');
if (ok === false) return;
viz.activate();
})();
</script>
</body>
</html>
Loading
Loading