In article <1993Apr11.011356.18088@kf8nh.wariat.org> bsa@kf8nh.wariat.org (Brandon S. Allbery) writes:
quoted text
>In article <92214@hydra.gatech.EDU> gt1610c@prism.gatech.EDU (Michael Kenneth McGaugh) writes:
>>In article <2000@dsbc.icl.co.uk> mat@dsbc.icl.co.uk (KID01) writes:
>>>In article <1q2970INN7b1@spiff.seattleu.edu> aehall@calvin.seattleu.edu (root-bound) writes:
>>>>it's workings and I want to contribute to the cause.
>>>>I can't think of anything to write...
>>>
>>>What about new filesystem drivers for things like SYSV ufs/vxfs/sfs/s5
>>
>>How about adding HPFS to that list of filesystems.  I think that many
>
>HPFS is proprietary --- some information is available on it, but I don't think
I'm currently working on implementing the sysv 386 filesystem, just
thought I'd mention it before we get duplication of effort going here.

HPFS could be implemented READ only fairly easily from what I've read.
Allocation of blocks may get hairy...it's odd enough when it's well 
documented, as I've encountered...HPFS is NOT well documented.

I should be testing sysv at the end of this month and have a ROUGH draft
of a document on filesystems (focus on Linux and how it implements systems),
at the same time.  My prof is heading out for the summer and this is my
MS proj so that's a fairly set date.

I would be more than willing to pass on info about the Linux fs which I've
received from various sources (linus and stacks of various unix filesystems)

At this point it would be uneditted.  My doc is currently  a bunch of 
\section and \subsection (and \subsubsection).

(of course, i would take what i have to say with a grain of salt until data
 actually comes from a sysv diskette and lands on my Linux formatted hard drive)

good luck finding a proj
pmonday@eecs.wsu.edu

ps Oh yeah...you may have to hack a little to implement HPFS... (cringe ;-)
not that I don't have my share of misstarts on a bunch of sysv stuff strewn
about my system.