ReiserFS future

[Tom Buskey]

On 10/12/06, Fred <puissante at lrc.puissante.com> wrote:

> So whomever inherits the code had better spend a LOT of time getting to
> know
> it.
>
> Device drivers in general tend to be tricky, black art stuff. Doesn't have
> to
> be that way, but from what I've seen they usually are. And if you are
> talking about something as complex as today's file system drivers, how the
> code is structured becomes *everything*. I suspect -- I've not seen the
> Reiser code -- that the code is structured very closely to how Hans thinks
> and solves problems (no DUH please! :-)), in that the code is *intimately*
> his and probably does not follow much of the usual methodologies, as if
> they
> could be applied to writing drivers anyway. To know the code is to know
> Reiser. Eek, this is sounding metaphysical.



Having Hans out of the coding for a bit may be a boon for ReiserFS 4 and 3.
Before this incident, there was controversy about including it in the kernel
due to Hans' approach(?) and how ReiserFS 3 is not being well supported.
SuSE is no longer going to be using ReiserFS as the default filesystem.

Personally, I'd love to see ZFS fully ported.  There's an effort in FUSE but
there are limitations there.  I think FreeBSD has a port going and there's
talk of MacOSX getting ZFS (they included Dtrace already).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/mailman/private/gnhlug-discuss/attachments/20061012/a5d86ef2/attachment.html