Hi Frank, This is great!
> I have a series of articles in the works that talks about how to > implement a filesystem (kernel driver + utilities) for Solaris. I > started this with the idea of making a series of blogs.sun.com articles > from it, but maybe it'd be better to put something like this onto > opensolaris.org ? Maybe we could link it under developer resources? http://www.opensolaris.org/os/community/documentation/doc_index/dev/ > I also wonder if we have a mechanism to solicit editorial review on such > writeups. I'm quite aware that the official "writing device drivers" > guides deliberately omit certain topics such as filessytems or bus nexus > drivers, and I know reasons for that, so my goal here is not to provide > an official guide "this is how to do it". But OpenSolaris needs I believe you are one of the first to inquire about this, so I imagine we'll be making this up as we go along. :) > filesystems (think ntfs, Linux ext[23]/reiser/jfs/xfs, ...), and there > are people in the community who already have started such projects; a > writeup "this is how it _can_ be done" therefore seemed appropriate ... > > In any case, for those on the lists that are Sun-internal, what I have > written to date is on my Sun-internal weblog page, > http://blogs.sfbay.sun.com/roller/page/frankho (use the 'permalink'); > does anyone know a way to make this reviewable by the osol community as > well ? The docs community will be happy to help you get this setup. In the past draft documentation has been made available for review by downloading as a tarball from one of the various doc community pages. We could certainly go that route if you wanted. Or as you have done within Sun you could make this available via blog entries. I guess it really boils down to what format you want to author the material in as well as personal preference of presentation. If you feel brave enough to give the docs toolchain a try, I would happily work with you offline to convert your draft blog entries into DocBook, which can be used to generate PDF as well as hierarchical HTML trees from a single source. We also have a functioning SVN repository now so if you wanted to make the source available we could check it into the repository for easy revising and distributed contributions. This is what is being done with the OpenSource developer reference. Cheers - Eric
