Re: The Kernel

[George Bonser <grep@oriole.sbay.org>]

On Wed, 21 Jan 1998, Rick Jones wrote:

> William T Wilson wrote:
> > 
> > Is not the purpose of the core to have a system which developers and users
> > alike can call a standard?  I would think that would imply some degree of
> > standardization...
> 
> I have to say that I am also a bit dissmayed at the disro leaders idea
> of, seemingly, having a core that enforces no standard.


It absolutely DOES. It requires that adistribution 1) Contain a specific
core set of software and 2) requires that these core components are
withing specific versions

I think there is confusion about the two cores.  There is the distribution
core which WILL define a filesystem layout, a packaging format, etc. and
there is a Linux core which defines only the base software.

> 
> When I conceptionalize a core, I think of the smallest collection of
> Linux binaries, to include a basic GUI layer, that will allow me to run
> *ANY* program made for Linux.  That does not count programs that require
> specialized libraries or toolkits that provide a specific functionality,
> i.e. Motif, although the *ability* to add those specialized items *and*
> have them work properly is paramount.

Correct. THe problem comes in with versions. This package will not compile
with GCC older than ??.?? while that package requires lic5 newer than ?.??
and this other package must have an ld.so newer than ?.??

It is not enough to say that a system must have ld.so, GCC, and libc5, we
must enforce a version range. Then a person can look at their system and
say .. cool, I have SEUL 1.3 and they will know that any software that
says "Requires SEUL 1.3" will work on their system.

THAT specification does NOT enforce a filesystem layout, package manager,
etc.  You can use RPM and put your uucp config files in /usr/lib/uucp and
be compliant or you can use dpkg and put your uucp configs in /etc/uucp
and be compliant. What THAT spec does is gives me confidance that I can
download that software, put it in /usr/local/src and do a make and it will
compile.

A package that complies with the DISTRIBUTION core can be distributed and
a dpkg file that simply installs in the correct location without needing
to be compiled AND will run properly.

I am getting tired of talking about it, lets put something together and
modify it to get what wer want. We can sit here and talk till we are blue
in the face and have the greatist plan in the world with absolutely
nothing on the table.

> purposes, so be it, but the files that aren't specific to their distro
> have to comply with FSH.  i.e. If Debian wants to put /usr/doc/Debian/*
> in /Debian so be it, it only effects Debian specific files/programs. 
> Putting /etc/* under /Debian/etc/ is forbidden to remain compliant.



Lets do this.  Debian 2.0 is adopted as-is for SEUL-0.1 for the
Distribution core. A DESCRIPTION of the core components becomes the Linux
Core document. 

As we modify things and add them, we diverge from Debian (or Debian adopts
them)