<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Read-Only-root on Pjotrs.nl</title>
    <link>https://pjotrs.nl/tags/read-only-root/</link>
    <description>Recent content in Read-Only-root on Pjotrs.nl</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 02 Jan 2023 16:29:55 +0100</lastBuildDate><atom:link href="https://pjotrs.nl/tags/read-only-root/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Running (php)Virtualbox on a Readonly Root System</title>
      <link>https://pjotrs.nl/posts/running-phpvirtualbox-on-a-readonly-root-system/</link>
      <pubDate>Mon, 02 Jan 2023 16:29:55 +0100</pubDate>
      
      <guid>https://pjotrs.nl/posts/running-phpvirtualbox-on-a-readonly-root-system/</guid>
      <description>Since I like to run servers from USB sticks and store the server data on harddisks. It is wise to make the root-file system read-only, to extend the life of a USB-stick. However, some programs require extra configuration to do this, since I could not find a post to do this with VirtualBox I&amp;rsquo;m making this one.
Figuring out which files need to be writeable for Virtualbox We can use strace, to find the calls an application makes to the OS, (If you&amp;rsquo;re using Windows, process monitor can do similar, but still different things (including registry access) ).</description>
    </item>
    
  </channel>
</rss>
