9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dave Eckhardt <davide+p9@cs.cmu.edu>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] mounting a 9660 file system - writeable
Date: Sat, 08 Jul 2023 12:41:16 -0400	[thread overview]
Message-ID: <16924.1688834476@lunacy.ugrad.cs.cmu.edu> (raw)
In-Reply-To: <CAL6pNZ9afpigBThr3aec+N5kAZcRq2d+B=-NWrLnaOUsivpfzQ@mail.gmail.com>

9660srv's job is to serve the files stored on a CD-ROM.  CD-ROMs
are more or less read-only, so 9660srv serves the files as read-only
as well.

In most setups, the /tmp file system is "stored" in RAM.  It's faster
than sending the data to some storage device, and when you turn the
machine off the files vanish, which matches the mental model people
sometimes use when putting things in /tmp.

If you want to write files that persist across reboots, you'll need
to use some other kind of file system (and give it a storage
partition).  Assuming you're using 9front, you might start looking
somewhere around here:


You might give your VM two storage devices, one blank and one holding
the ISO image; running the installer on the ISO image would guide
you through installing a regular read/write file system on the other
storage device.

If you wanted to layer your changes on top of an underlying CD-ROM
image, that could be done with an overlay file system.  One of my
students wrote one many years ago:


Later other students used it to build kernels without write access
to /sys/src -- their overlay contained their source changes and
also their object files.  The overlay file system will still need
somewhere to store files, though.

Dave Eckhardt

9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T49170188f63f430d-M225108264fd4c3ddf4a231f0
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2023-07-08 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08  8:05 Conor Williams
2023-07-08 16:41 ` Dave Eckhardt [this message]
2023-07-08 23:43   ` Conor Williams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16924.1688834476@lunacy.ugrad.cs.cmu.edu \
    --to=davide+p9@cs.cmu.edu \
    --cc=9fans@9fans.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).