From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <41e2cd58fce6cb1b2869ae5dae63bef0@collyer.net>
From: Geoff Collyer <geoff@collyer.net>
Date: Fri, 14 May 2004 15:31:44 -0700
To: 9fans@cse.psu.edu
Subject: Re: [9fans] disk/^(mbr format fdisk prep)
In-Reply-To: <d5611683a8b70c9b9a6cc2c5a8c8f3f9@9srv.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 7be245ae-eacd-11e9-9e20-41e7f4b1d025

When I asked 1127 folks what the "k" in "kfs"
stood for (and suggested "kludge"), they said
it stood for "Ken".  The on-disk formats of kfs
and /sys/src/fs are clearly related, with kfs's
intended to permit easily parameterising the
block size.  I have used a modified kfs to
recover data from a damaged Ken fs.  kfs is
roughly a subset of Ken fs; perhaps distinguishing
user vs. kernel or standalone vs. non-standalone
would clarify which "kfs" or "ken fs" we mean.