<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Netconsole on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/netconsole/</link>
    <description>Recent content in Netconsole on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/netconsole/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux Kernel Remote Logging: netconsole vs Remote Syslog vs pstore/Ramoops</title>
      <link>https://www.pistack.xyz/posts/2026-06-01-linux-kernel-remote-logging-netconsole-rsyslog-pstore-guide/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-01-linux-kernel-remote-logging-netconsole-rsyslog-pstore-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;When a Linux server crashes, panics, or hangs, the kernel log messages (&lt;code&gt;dmesg&lt;/code&gt;) are often the only clue to what went wrong. But accessing those logs is impossible if the system is unresponsive or the disk is corrupted. Remote kernel logging solves this problem by transmitting kernel messages off-machine in real time — before a crash can destroy the evidence. This guide compares three approaches: the built-in &lt;code&gt;netconsole&lt;/code&gt; module, remote syslog forwarding, and the persistent &lt;code&gt;pstore&lt;/code&gt;/&lt;code&gt;ramoops&lt;/code&gt; mechanism.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
