9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] file systems
Date: Mon, 24 Feb 2003 13:28:02 -0800	[thread overview]
Message-ID: <a7b9793b8395552bb3288ebad0378c29@collyer.net> (raw)
In-Reply-To: <Pine.SOL.3.96.1030224142637.17571B-100000@robin.cooper.edu>

`The Plan 9 File Server' (in /sys/doc/fs) describes how the pre-fossil
standalone file server stores data on disks.  kfs is a slight variant
of the non-cached-worm file system.  The main change I noticed when
adapting a private copy of kfs to read standalone file systems was
that struct Superb swaps the order of its members, a Super1 and an
Fbuf, to permit the size of the free list in Fbuf to vary with block
size, which can be chosen at run-time in kfs, but which is fixed at
compile-time in the standalone file server.



  parent reply	other threads:[~2003-02-24 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 19:29 Joel Salomon
2003-02-24 19:33 ` Fco.J.Ballesteros
2003-02-24 21:28 ` Geoff Collyer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-24 16:52 [9fans] (no subject) Steve Simon
2003-02-24 17:38 ` [9fans] file systems Russ Cox

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=a7b9793b8395552bb3288ebad0378c29@collyer.net \
    --to=geoff@collyer.net \
    --cc=9fans@cse.psu.edu \
    /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).