From: Brandon S. Allbery (bsa@kf8nh.wariat.org)
Date: 04/10/93


From: bsa@kf8nh.wariat.org (Brandon S. Allbery)
Subject: Re: Things to write (was Re: How can I get a piece of the action?!)
Date: Sun, 11 Apr 1993 01:13:56 GMT

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
it's enough to design filesystem code from.

ufs is basically BSD FFS. Since *that* issue comes up every week :-) I expect
that *someone* will port it.

S51K is a bit of a problem, because it can be 1KB (SVR2), 2KB (some SVR2, as
an option), or 4KB blocks. On the other hand, all we probably care about is
the 4K block one, because all 386 System V (R3.x) uses it: any smaller and it
can't demand-page 386 executables from their files, because a 386 page is 4KB.

You also probably want to support AFS and EAFS filesystems for all those SCO
(l)users out there. The former I could probably whack together, but we
*still* haven't gotten the go-ahead to upgrade to 3.2v4 so I have no idea how
to handle EAFS. And I expect that we're pretty much alone in that regard, so
I'd expect EAFS to be a higher priority. (Note that SCO mountable floppies,
at least in 3.2v2, are S51K, so that still may be useful... but tar is better
and works now.)

++Brandon

-- 
Brandon S. Allbery                                       bsa@kf8nh.wariat.org

It's not too late to turn back from the "Gates" of Hell... Linux: the FREE 32-bit operating system, available NOW. Why waaaaaait for NT?