From owner-freebsd-hackers Fri Jul 30 18:21: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 7B62214E5F for ; Fri, 30 Jul 1999 18:21:06 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA95376; Fri, 30 Jul 1999 18:19:59 -0700 (PDT) (envelope-from dillon) Date: Fri, 30 Jul 1999 18:19:59 -0700 (PDT) From: Matthew Dillon Message-Id: <199907310119.SAA95376@apollo.backplane.com> To: "Alton, Matthew" Cc: "'Nik Clayton'" , "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: RE: DOC volunteer WAS:RE: userfs help needed. References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :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 I would go with option #2. The VFS/BIO changes are several months away at the very least. The framework hasn't even been worked out yet. The new model will not be compatible with the old, but if your stuff is in the source tree whoever winds up doing the major porting work will port it along with everything else. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message