Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Jun 1999 19:51:00 -0400
From:      "Christopher J. Michaels" <cjm2@earthling.net>
To:        "FreeBSD Mailing List" <questions@FreeBSD.org>, <FAQ@FreeBSD.org>
Subject:   FAQ Revision: 13.2. How do I make my own custom release?
Message-ID:  <000101bebd0a$1445e480$0200000a@shithead.weeble.dyndns.org>

Next in thread | Raw E-Mail | Index | Archive | Help
Hello,
I tried following the faq section 13.2. How do I make my own custom release?
http://www.freebsd.org/FAQ/FAQ243.html#246

I am using version 3.2-STABLE.  I wanted to make a release because I was
talking my friend into installing 3.2 instead of redhat (or dual boot).
Anyway.. neither of us wanted to wait for a download, and I don't have the
cd's.  Since I already keep up with the source tree via cvsup, why not 'make
release'.

So, I followed the instructions in that FAQ.  1st if failed because my
/usr/obj was unpopulated.  Nothing in this faq states or implies that you
need to have a buildworld done previous to running a 'make release'.

Ok, fine, I can figure that out on my own.  Since the error message said
very plainly something was missing (/usr/obj/usr/src/tmp/usr/bin/make if
memory serves me [man is that a long path]) so I did a 'make buildworld'.

Now I figure, ok, this is going to work.  So I run 'make release' again,
following the FAQ to the letter (paths changed to protect the innocent).
Low-and-behold, it fails this time trying to make compat3x?!?!?!?!  I'M
RUNNING 3.2-STABLE, and that's what I want to make.  SHEESH.

Ok, so then a kind soul sends me the attached e-mail, with very nice
instructions, and it works.  I'm happy, my friend's happy, even 'make' is
happy.  :)

What really bugs me the most.. as I look at that FAQ page today.  It was
updated YESTERDAY!  Yesterday?  In whomever's defense, the FAQ is either
geared toward someone running -CURRENT or is just written by someone
running -CURRENT.

I know the FAQ is a work in progress, and it's 100% volunteer effort, and
I'm not bagging on the person (people) who work on it.  All I ask, is that
the instructions in the attached letter be considered for incorporation into
that FAQ page (sans instructions on burning a cdrom).

I don't know who maintains that page, and was hoping that either someone
here knows where to forward this information, or is the person who maintains
the page and can consider this request.

I've added a few comments to the message below, reflecting what experiences
I had.  I hope this e-mail isn't taken in the wrong light, I'd just like to
see things fixed for the next guy who has the same question.  I'm willing to
do some typing myself, if need be.

Thank you,
-Chris

"f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng."

> -----Original Message-----
> From:	Thierry Herbelot [SMTP:Thierry.Herbelot@alcatel.fr]
> Sent:	Monday, June 21, 1999 8:42 AM
> To:	Christopher J. Michaels
> Cc:	Christian Weisgerber; FreeBSD Mailing List
> Subject:	Re: CVS repository for 'make world'?
>
> "Christopher J. Michaels" wrote:
> >
> [SNIP]
>
> Here's what I found on the list (I used it for my first "make release"
> one week ago)
>
>
> Subject: Re: Problem with "make release" - Solved
>    Date: Fri, 2 Apr 1999 22:16:03 +0200 (CEST)
>    From: N <niels@bakker.net>
>      To: freebsd-stable@FreeBSD.ORG
>
>
>
>
> The final guide on how to do a `make release' and convert it into
> something suitable for burning onto a CD-R for 3.1-STABLE.
>
> First of all, please consider buying your CD's at Walnut Creek, or any
> vendor that supports the FreeBSD project.  They are the companies that
> help make FreeBSD possible.  If you won't (or can't), *please* make a
> donation directly.  Thanks!
>
> On with the show:-
>
>    (1)  Find a place with around 1.7 GB of space, and be sure you don't
>         mount it with the `nodev' option.
>
>    (2)  Make sure you have the results of a `make buildworld' from the
>         sources you wish to release in /usr/obj.
>
>    (3)  Read the Handbook and FAQ, especially
>         http://www.freebsd.org/FAQ/FAQ237.html#239.  Note that you will
>         need to add 'src-crypto' to the supfile shown there.

I believe this link should be to http://www.freebsd.org/FAQ/FAQ243.html#246.
I looked at the above link and it was to the FAQ page about "Scratching in
my memory banks".

>
>    (4)  Run cvsup.  A complete copy of the CVS tree currently is 615 MB.
>         cvsup itself needs another 5 to store data for itself.  If you
>         place this data somewhere else than the partition from step 1 you
>         can subtract the appropriate amount from the figure mentioned
>         there.  Putting the CVS tree someplace else than where the build
>         will end up is a nice performance boost as well.
>
>    (5)  cd /usr/src/release; DATE=`date +%Y%m%d` CVSROOT=/home/ncvs \
>         time make release BUILDNAME=3.1-${DATE}-SNAP \
>         CHROOTDIR=/lots/of/space/rel RELEASETAG=RELENG_3

I believe the RELEASETAG was the stumbling block that I ran into when I
tried my 2nd attempt at a make release.

>
>    (7)  After several long hours you'll have about 1 GB worth of files in
>         /lots/of/space/rel, including a directory R/cdrom/.

STOP!  We don't really NEED to add, how to burn your own copy.  This is a
judgement call, since this would detract from cdrom sales at Walnut Creek.
On the other hand, if someone went to this level of trouble already, they'll
probably find a way to burn a cdrom.

>
>    (8)  Copy some stuff to R/cdrom/disc1/ from ftp.freebsd.org (or any
>         mirror) - I add compat22, CVSup, tools, CERT and XFree86, and a
>         .tar.gz of the CVS tree, to fill things up a bit.  You can also
>         populate a packages directory, for example.

compat22 appears to be build with 'make release' now.  At least, I have a
compat22 directory that is populated with files.

And, on a similar note, what is disc2/ for?  Is that the "live file system"
cdrom?

>
>    (9)  Run /usr/share/examples/worm/makecdfs.sh with suitable arguments:
>         makecdfs.sh -b FreeBSD-${DATE}-SNAP
/lots/of/space/rel/R/cdrom/disc1 \
>         /var/run/freebsd.iso "FreeBSD, Inc."
>
>   (10)  Burn the resulting image (some 400 MB) onto a CD-R, with cdrecord.
>         You can change the makecdfs.sh script to pipe its output directly
>         to cdrecord, saving you space and probably costing you a CD-R:
>         mkisofs -a -l -L -R -r <filesys> | \
>         (sleep 300; cdrecord -v speed=4 -data -dev=XXX -)
>
> Hopefully, you now have a bootable CD-R.  I don't think I forgot to
> mention any steps I took in the process of building one myself (that did
> work fine in the end). I hope this will save someone somewhere some
> time, it certainly made me respect JKH even more. :-)

Saved me a hell of a lot of time.  And I greatly appreciate it.

>
> Any comments appreciated.  I still don't know how to include the tools
> directory automatically, why compat22 isn't built, or what to change to
> make some ports a default part of the system (like ssh, of course a
> unique host key should be generated during the install).
>
> Cheers,
>
>
>         -- Niels.
>
>
> -
> Thierry Herbelot <thierry.herbelot@alcatel.fr>
> (+33) 1 46 52 47 23
> http://perso.cybercable.fr/herbelot



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




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?000101bebd0a$1445e480$0200000a>