From owner-freebsd-hackers  Sat Jan 13 23:31:24 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA18916
          for hackers-outgoing; Sat, 13 Jan 1996 23:31:24 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA18910
          for <freebsd-hackers@FreeBSD.ORG>; Sat, 13 Jan 1996 23:31:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id XAA20718; Sat, 13 Jan 1996 23:31:07 -0800
To: Ollivier Robert <roberto@keltia.freenix.fr>
cc: freebsd-hackers@FreeBSD.ORG (FreeBSD Hackers' list)
Subject: Re: Building a "custom" release of 2.1.0 
In-reply-to: Your message of "Sun, 14 Jan 1996 00:21:47 +0100."
             <199601132321.AAA24419@keltia.freenix.fr> 
Date: Sat, 13 Jan 1996 23:31:06 -0800
Message-ID: <20716.821604666@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk

> I want to build a release of  2.1 for a friend.  I have 430 MB available on
> /y, is that enough ? 

I don't think so.  You'll probably want close to 650MB to do this,
if memory serves me correctly.

> My  primary problem is  that  I don't want to   build the release  with the
> GENERIC kernel but with a custom one. What do I have to do for that ?

If you don't want to check in your changes into your local repo (I
assume you have a CVS tree there or you wouldn't even be able to do
this) on the RELENG_2_1_0 branch then you've no choice but to simply
watch the process as it goes along and then dash into the checked out
copy of the tree right after the checkout is done and make your
changes to it.


					jordan