Messages in this thread | | | Date | Thu, 26 Aug 2004 01:45:42 -0700 | From | Andrew Morton <> | Subject | Re: silent semantic changes with reiser4 |
| |
Hans Reiser <reiser@namesys.com> wrote: > > >To get us started on this route it would really help me (and, probably, > >others) if you could describe what these API extensions are in a very > >simple way, without referring to incomprehehsible web pages, > > > what is not comprehensible....?
Pretty much anything at www.namesys.com. The amount of time which is needed to extract the technical info which one is looking for vastly exceeds a gnat-like attention span.
As a starting point, please prepare a bullet-point list of userspace-visible changes which the filesystem introduces, or is planned to introduce.
And describe the "plugin" system. Why does the filesystem need such a thing (other filesystems get their features via `patch -p1')?
And what are the licensing implications of plugins? Are they derived works? Must they be GPL'ed?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |