From: Juhana Kouhia (jk87377@cc.tut.fi)
Date: 08/14/92


From: jk87377@cc.tut.fi (Juhana Kouhia)
Subject: Re: Stabilizing Linux
Date: 14 Aug 1992 12:21:04 GMT


Well, I have no much experiences in software system engineering and I
don't know about the heart of Linux, but I suggest:

1. All common sources for the various different Linuxes are checked
to a master version.

2. Those features which are in one Linux only is directly copied to
master version; if this is not possible to do directly, people
rewrite them.

3. Those features which overlaps in Linuxes is added to master version
either by switches or choosing best one or writing a compromise.

About 1: I don't know what different program parts (modules)
there are and how they communicates together.
It could help to organize if those parts (or program modules) are
listen down -- at least if I have to organize Linux again, I would
like to write a list (or program tree) about what is there.
Then it could be easier to check where programs overlaps
and helps to design more modular system.

By these differences I don't mean different versions of GNU emacs or
zoo or such :-)

Actually, does somebody know what features are different in the
different Linux releases (MCC, etc.)?
We could list only those in the first place.

As I said I'm not experienced software developer, so no flames,
instead an educating critisms, which I have allready read from this
group, are welcome.

Juhana Kouhia