On Monday 07 January 2002 15:25, Christoph Hellwig wrote:
> In article <3C39E6A0.34A88990@alsa-project.org> you wrote:
> > If you want to keep top level cleaner and avoid proliferation of entries
> > we might have:
> >
> > subsys/sound
> > subsys/sound/drivers
> > subsys/net
> > subsys/net/drivers
>
> And what part of the kernel is no subsystem?
> Your subsystem directory is superflous.
Umm, the subsys part makes a lot of sense in terms of
logically separating the core of the kernel from the
architecture part and the subsystem part. While we
need a MM to complete a kernel, we certainly don't need
"subsys/sound/alsa/driver/es1371.c".
.
./arch
./fs
./init
./kernel
./lib
./mm
./include
./ipc
./subsys
./scripts
./Documentation
If this helps make the kernel source more like the modules
and devfs trees, then it makes even it more logically consistant.
Please remember that everyone who compiles a kernel is not
a uber kernel hacker. Average folks will appreciate some more
structure which helps to explain how things work.
>
> If, for some reason, we want to move all code in the kernel around
> we should do it once and in a planned mannor.
>
> Randomly introducing new and shiny naming schemes sucks. badly.
It's NOT random and it doesn't suck.
>
> Christoph
-- timothy.covell@ashavan.org. - 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/
This archive was generated by hypermail 2b29 : Mon Jan 07 2002 - 21:00:37 EST