{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreies7vdfgoc5kg6ebbt7xlkffdh3a3hrytawba42hln6jpdc6qdt34",
    "uri": "at://did:plc:b3tz6srl4ochk2wxn6dv6xpy/app.bsky.feed.post/3mgv62uuwymg2"
  },
  "path": "/Articles/1062163/",
  "publishedAt": "2026-03-12T14:58:09.000Z",
  "site": "https://lwn.net",
  "tags": [
    "nullfs"
  ],
  "textContent": "One of the first changes merged for the upcoming 7.0 release was nullfs, an empty filesystem that cannot actually contain any files. One might logically wonder why the kernel would need such a thing. It turns out, though, that there are places where a null filesystem can come in handy. For 7.0, nullfs will be used to make life a bit easier for `init` programs; future releases will likely use nullfs to increase the isolation of kernel threads from the init process.",
  "title": "[$] Practical uses for a null filesystem"
}