From: "Alexander G. M. Smith" <agmsmith@rogers.com>
To: Tom Vier <tmv@comcast.net>
Cc: reiserfs-list@namesys.com
Subject: Re: development
Date: Tue, 06 Jan 2004 21:44:33 -0500 EST [thread overview]
Message-ID: <8567103824-BeMail@cr593174-a> (raw)
In-Reply-To: <20040107022330.GA2930@zero>
Tom Vier wrote on Tue, 6 Jan 2004 21:23:30 -0500:
> On Tue, Jan 06, 2004 at 11:25:18PM +0300, Hans Reiser wrote:
> > We use UML for everything it can be used for.
>
> what about putting the core code in a lib and using a file for storage? once
> it stabilizes, remove the userland stuff and hook it up to the vfs. [...]
I just use lots of dprintf statements to write debugging messages out to
a serial port and a log file, and avoid writing buggy code in the first
place (lots of sanity checks, etc). But that was for a fancy RAM file
system, a one person project, not something as big as ReiserFS. I also
had a user level file system test program which was useful for comparing
how different file systems handled, well, just about everything. Old
screen shot at http://web.ncf.ca/au829/BeOS/AGMSRAMFSMounter.screen.gif
Admittedly I did develop some components in user-land, like the pattern
matching code or the AVL trees. But most debugging (there wasn't much)
just needed print statements. I also know of other people that use a
VFS simulator / test harness for their file system code. But that's on
BeOS so it won't be too useful for Unix style development.
- Alex
next prev parent reply other threads:[~2004-01-07 2:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 20:13 development Grant Miner
2004-01-06 20:25 ` development Hans Reiser
2004-01-07 2:23 ` development Tom Vier
2004-01-07 2:44 ` development Andreas Dilger
2004-01-07 2:44 ` Alexander G. M. Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-06 20:19 development Burnes, James
2001-11-23 14:59 Development lk
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=8567103824-BeMail@cr593174-a \
--to=agmsmith@rogers.com \
--cc=reiserfs-list@namesys.com \
--cc=tmv@comcast.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.