From owner-freebsd-hackers  Thu Sep 18 08:19:48 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id IAA12318
          for hackers-outgoing; Thu, 18 Sep 1997 08:19:48 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA12309
          for <hackers@FreeBSD.ORG>; Thu, 18 Sep 1997 08:19:45 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id IAA06273; Thu, 18 Sep 1997 08:17:22 -0700 (PDT)
To: nik@iii.co.uk
cc: Mike Smith <mike@smith.net.au>, hackers@FreeBSD.ORG
Subject: Re: Different kernels for the bindist and boot.flp? 
In-reply-to: Your message of "Thu, 18 Sep 1997 12:45:22 BST."
             <19970918124522.57711@strand.iii.co.uk> 
Date: Thu, 18 Sep 1997 08:17:21 -0700
Message-ID: <6269.874595841@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> This is why I was thinking about seperating the bin dist into a bin dist and
> a kernel dist. The new bin dist contains everything non-kernel specific,
> the kernel dists each contain one kernel with support for a specific set of
> features, and the kernel config file used to create them.

You can do this already with the "synthetic dist" support.  See
/usr/src/release/scripts/*-make.sh for how the existing synthetic
dists are made (a "synthetic" dist defined as one which was not
actually created directly by doing a "make distribute").  There's
nothing which says you couldn't pull the kernel out of bin, add a
couple more kernels, and call it a kdist or something.

					Jordan