I prefer to work in flat ASCII. Perhaps the doc project can HTMLize
the final product.
Currently, I'm hatching a plan to free up an AMD386/40 running
FreeBSD 2.1.5 for use as a 4.x sandbox. The little thing has been
faithfully and unerringly natd-ing my whole Solaris/NetBSD/Linux/
UNIXWare LAN onto the big cloud for more than 2 years. It really is
emotionally difficult to pull the little box out of production. It
has a personality and everything.
Anyway, Mr. Dillon, once I have a development box to smack around, I
intend to start with your suggestion of implementing a filesystem
of my own concoction by returning an error for all VOP calls and
issuing a kernel printf. How visible will the new VOP code be to
me at this level? The Penguins are rewriting the bejesus out of their
VFS system to the point where all the existing FS code must be redone
to conform. Please debifurcate:
1) Any attempt from-scratch FS development should definitely wait for
the new VFS code. Start now and you'll only end up rewiting in the
Fall.
2) Hack away. All changes will be completely transparent to the FS
coder. Your code, as well as everything in 2.x and 3.x will drag
and drop right into the new model and build like the very wind.
Thanks
-----Original Message-----
From: Nik Clayton [mailto:n...@nothing-going-on.demon.co.uk]
Sent: Friday, July 30, 1999 05:09
To: Alton, Matthew
Cc: 'Matthew Dillon'; David E. Cross; freebsd-hackers@FreeBSD.ORG
Subject: Re: DOC volunteer WAS:RE: userfs help needed.
On Thu, Jul 29, 1999 at 10:45:51AM -0500, Alton, Matthew wrote:
> I ran screaming into the woods last year from trying to grok VOP_foo. The
> prospect of a rewrite fills me with warmth and fuzziness. I hereby volunteer
> to maintain the VOP(9) man pages and to flesh out my notes into a big, beefy
> FS-implementer's Guide to the new VOP_foo. All the coders have to do is
> answer my (at least marginally clueful) questions along the way and keep
> posted as to what's going on in new VM-land. I won't even pester anyone
> with design suggestions... very much. Solid offer, kids. Everybody wins.
> Give it some thought.
Sounds good. Yell for any assistance you need from the Doc. Proj.
In particular, the FS Implementer's Guide sounds good. What (markup)
language were you planning on using?
N
PS: Reply-to: should probably be set to doc, but I've left that at your
discretion.
--
[intentional self-reference] can be easily accommodated using a blessed,
non-self-referential dummy head-node whose own object destructor severs
the links.
-- Tom Christiansen in <37514...@cs.colorado.edu>
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
