From owner-freebsd-hackers  Tue Apr 29 21:15:47 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA02187
          for hackers-outgoing; Tue, 29 Apr 1997 21:15:47 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA02180
          for <freebsd-hackers@FreeBSD.org>; Tue, 29 Apr 1997 21:15:44 -0700 (PDT)
Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id VAA23511; Tue, 29 Apr 1997 21:15:59 -0700 (PDT)
To: Simon Shapiro <Shimon@i-Connect.Net>
cc: freebsd-hackers@FreeBSD.org, Julian Elischer <julian@whistle.com>
Subject: Re: A Desparate Plea for Help... 
In-reply-to: Your message of "Tue, 29 Apr 1997 09:00:19 PDT."
             <XFMail.970429174652.Shimon@i-Connect.Net> 
Date: Tue, 29 Apr 1997 21:15:58 -0700
Message-ID: <23509.862373758@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> How does one then maintain several kernel versions without going mad?
> In Linux (sorry), one has /lib/modules/X.y.z.... and a current symlink that
> actualy gets created at boot time by some clever awking of /proc/version.

In practice, the LKMs don't go out of sync that often, so you
basically just watch the cvs-all mailing list and whenever you see a
kernel or LKM change go by which looks like a resync might be
necessary again soon, you just make a mental note to update both next
time you install a kernel.

> many years ago.  I already pay 10% of my income in contributions.  I
> promise,
> instead to donate 100 hours of community service to the FreeBSD project.
> My activity?  Create noise about threads.  My server engineer tells me they 
> are broken.  how is that?

Sold! :-)

						Jordan