Re: [PATCH 0/7] OMFS filesystem version 3
From: Adrian Bunk
Date: Tue Apr 15 2008 - 11:18:15 EST
On Sun, Apr 13, 2008 at 04:10:14PM -0700, Andrew Morton wrote:
> On Sun, 13 Apr 2008 23:49:20 +0100 Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:
>
> > > I guess I can keep making this point in various ways until someone
> > > actually notices it:
> > >
> > > This filesystem has only 20 users.
> >
> > At the moment. And that probably exceeds Amiga users, 386 users, some of
> > the serial port users, several network card users ...
> >
> > In the past we've merged drivers for network cards where only two
> > existed in the world. Linus has repeatedly stated he wants to see stuff
> > people are using getting in.
>
> None of that means that merging this filesystem is the best decision.
>
> > Good clean code that doesn't affect the core
> > is good reference material.
>
> The reference block filesystem is ext2 (used to be minixfs) - there is no
> need for another.
>
> > I think you are (unusually) the one out of step here ?
>
> I appear to be the only one who is looking at the whole picture.
>
> Merging a new filesystem has costs - I don't need to enumerate them. Do
> the benefits of OMFS exceed them?
We do not have a stable API for external modules, and part of the deal
is that external modules have the chance of entering the kernel where
they will get API changes automatically.
We are talking about a filesystem even Christoph considers OK.
And who asked about the costs of merging crap like
drivers/infiniband/hw/nes/ ?
Speaking about the latter, with Linus' logic one might argue that OMFS
must not be rejected since it adds support for some hardware...
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/