<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Saurav Sachidanand</title>
    <link>https://saurvs.github.io/</link>
    <description>Recent content on Saurav Sachidanand</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>sauravsachidanand@gmail.com (Saurav Sachidanand)</managingEditor>
    <webMaster>sauravsachidanand@gmail.com (Saurav Sachidanand)</webMaster>
    <lastBuildDate>Thu, 02 Feb 2017 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://saurvs.github.io/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Writing a NetBSD kernel module</title>
      <link>https://saurvs.github.io/post/writing-netbsd-kern-mod/</link>
      <pubDate>Thu, 02 Feb 2017 00:00:00 +0000</pubDate>
      <author>sauravsachidanand@gmail.com (Saurav Sachidanand)</author>
      <guid>https://saurvs.github.io/post/writing-netbsd-kern-mod/</guid>
      <description>Kernel modules are object files used to extend an operating system&amp;rsquo;s kernel functionality at run time.
In this post, we’ll look at implementing a simple character device driver as a kernel module in NetBSD. Once it is loaded, userspace processes will be able to write an arbitrary byte string to the device, and on every successive read expect a cryptographically-secure pseudorandom permutation of the original byte string.
Before we begin, compiling a kernel module requires the NetBSD source code to live in /usr/src.</description>
    </item>
    
  </channel>
</rss>