Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Dec 1998 02:55:31 +0100
From:      Poul-Henning Kamp <phk@FreeBSD.ORG>
To:        current@FreeBSD.ORG
Subject:   LKMs 
Message-ID:  <70843.914810131@critter.freebsd.dk>

next in thread | raw e-mail | index | archive | help

Greg:

I think Soren was surprised by the fact that vinum sources lived
under src/lkm, they shouldn't have, in particular not because klds
were already on the way when vinum came in, but that aside, a
repository copy (as noted in the commit message) will put the
sources back in action the right place in the tree, and vinum will
be with us again.

Everybody:

LKMs can still be loaded, we just don't produce any as part of make
world anymore, klds are the future in that respect.

The flurry of emails we see here now is the very reason why so little
advance notice was given:  It is impossible to delete anything from
the tree based on concensus.  We even had people complaining when
we deleted some X.25 code (because they had >dreamed about< being
able to use it for!!)

If at least people would read their >ENTIRE< mailbox before starting
to send more or less carefully thought out emails, things would be
a lot better around here, and maybe a more democratic process could
work.

After 4 years, I have little or no hope that this will ever happen.

But, let's reiterate the criteria we used today:

   0.  All this code can be found in the Attic.  (Along with NETISO,
	NETCCITT, the old ISDN code, and God knows what we have
	up there with the old 5" irons and the xmas decorations.)

   1.  "It is in the tree" is not sufficient reason for it to stay there.

	Examples: if_eg, DSI_SOFTMODEM

   2.  All code should pass the "We would import it today if it was
       offered to us" test (with a decent margin of hysteresis)

	Example: pcvt, if_eg, DSI_SOFTMODEM

   3.  If it is unmaintained and need maintenance, it will be
       a hindrance to further (possibly independent) development.

	Examples: ft, pcvt, sea, nca0, uha0

   4.  If circumstances change (for instance: somebody hacks the
       code into better shape or makes a better implementation)
       reevaluation will take place.

	Example: isdn4bsd.

And notice number 4:  Can anybody by any chance remember the storm
that was raised when the old junky isdn code was yanked ?  

Well, look at the result:  now we have WORKING isdn & a maintainer.

The dynamics of FreeBSD is not only addition, it is also subtraction.

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?70843.914810131>