From: "Christopher Nielsen" <cnielsen@pobox.com>
To: alltom@gmail.com,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Easiest way to make a filesystem
Date: Mon, 14 Jan 2008 01:20:38 -0800 [thread overview]
Message-ID: <e0ac85f90801140120q6fa26e25h3c74a5ec05a6c9e8@mail.gmail.com> (raw)
In-Reply-To: <326364c20801140111v1bf9b574p80ea0305edf09c14@mail.gmail.com>
have a look at /sys/lib/lib9p/ramfs.c as a guide for writing one in C.
in the past, i have found it useful and educational.
On Jan 14, 2008 1:11 AM, Tom Lieber <alltom@gmail.com> wrote:
> I'd like to make a few simple filesystems for personal use to do
> things such as combine files or translate between different formats --
> really simple stuff, on par with the filesystems described in the
> "laying namespaces" paper from IWP9.
>
> Is the easiest way to make a filesystem to make one in C in the way
> described in Francisco's book? Are there any wrapping libraries for
> the simplest filesystems? Or filesystems like these to base my work
> on?
>
> shifs (Uriel) seemed encouraging, as did tmfs (Noah Evans), though I
> can't find source, nor determine the viability of either without it. I
> think they are for Inferno.
>
> I just obtained trfs but have not yet given it a thorough look. It's
> intimidating that it is 400 lines for character replacement, since its
> purpose is to pass every request nearly without modification to the
> underlying fs.
>
> --
> Tom Lieber
> http://AllTom.com/
>
--
Christopher Nielsen
"They who can give up essential liberty for temporary
safety, deserve neither liberty nor safety." --Benjamin Franklin
next prev parent reply other threads:[~2008-01-14 9:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 9:11 Tom Lieber
2008-01-14 9:20 ` Christopher Nielsen [this message]
2008-01-14 13:42 ` Eric Van Hensbergen
2008-01-14 20:10 ` roger peppe
2008-01-14 20:30 ` Tom Lieber
2008-01-14 20:40 ` hiro
2008-01-14 21:00 ` Gary Wright
2008-01-14 21:10 ` roger peppe
2008-01-14 21:23 ` Gary Wright
2008-01-14 21:29 ` Roman Shaposhnik
2008-01-15 12:22 ` roger peppe
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e0ac85f90801140120q6fa26e25h3c74a5ec05a6c9e8@mail.gmail.com \
--to=cnielsen@pobox.com \
--cc=9fans@cse.psu.edu \
--cc=alltom@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).