A real working lfs would be cool. Then again, a jfs would also be cool. 
I've seen so many people go up to an RS/6000 and just cut it off. Then 
they wonder why I have this pained look on my face. 

Here's a question: How can I implement an atomic system for CVS that will 
be able to restart an operation even if the system goes down in the 
middle. If the filesystem goes foom, and one of my files goes away in the 
middle of the transaction, what can I do? Just assume that this will not 
happen? What? If an important file goes away, then the ability to back 
out of the halfway transaction will be destroyed. So how can I *ensure* 
the correctness of the filesystem? Can I make sync() calls *extremely* 
often? What?

NFSv3 would also be cool.

XCOMM --------------------------------------------------------
XCOMM Kevin P. Neal, Sophomore CSC/CPE     kpneal@eos.ncsu.edu 
XCOMM North Carolina State University      kevinneal@bix.com
XCOMM --------------------------------------------------------

On Tue, 21 Nov 1995, Jonathan Stone wrote:

> 
> "Perry E. Metzger" <perry@piermont.com> writes:
> 
> >Hubert Feyrer writes:
> >> - What's the status of the Log-File-System (lfs). Is it still broken
> >>   (as it was with 1.0, the last release i've installed before ;-).
> >
> >I have never heard tell of a functioning lfs. If anyone knows of one...
> 
> Margot Seltzer has  a log-based filesystem that supposedly "just works".
> I don't recall off-hand if it's been dropped into FreeBSD; given
> Margot's group's leanings, the code is possibly written for BSDI.
> 
> (I think this may actually be "JFS"; I can find out, if anyone cares.)
> 
> There's also the NFSv3 for 4.4bsd, which Rick Macklem reworked into FreeBSD.
> Having that would be, mm, nice.
>