Re: Making a release of stable/12 with multiple kernels

2020-01-11 Thread Trond Endrestøl
On Sat, 11 Jan 2020 12:51+0100, Trond Endrestøl wrote:

> Currently, I'm running:
> 
> /usr/bin/make -C /usr/src -D NO_CLEAN -j 8 buildworld buildkernel
> /usr/bin/make -C /usr/src/release KERNEL="PE1950 DL360G5 GENERIC PER200 
> PER320 XENGUEST ZFS" MAKE_CONF=/etc/make.conf NODOC=1 NOPORTS=1 NOSRC=1 
> SRC_CONF=/etc/src.conf release

It turns out specifying KERNEL, MAKE_CONF, and SRC_CONF belongs to 
release.sh. My bad.

I was missing was -D NO_INSTALLEXTRAKERNELS, just what we also need to 
specify when running make packages.

I.e.:

/usr/bin/make -C /usr/src/release -D NO_INSTALLEXTRAKERNELS NODOC=1 NOPORTS=1 
NOSRC=1 release

Maybe GENERIC should be at the head of KERNCONF when making a release. 
Some .CURDIR magic in /etc/make.conf might help with that.

I'm sorry for the noise.

-- 
Trond.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Making a release of stable/12 with multiple kernels

2020-01-11 Thread Trond Endrestøl
Hi,

I'm trying to make a release of stable/12 and I was hoping to include 
all my custom kernels in the generated disc1.iso and memstick.img.

Currently, I'm running:

/usr/bin/make -C /usr/src -D NO_CLEAN -j 8 buildworld buildkernel
/usr/bin/make -C /usr/src/release KERNEL="PE1950 DL360G5 GENERIC PER200 PER320 
XENGUEST ZFS" MAKE_CONF=/etc/make.conf NODOC=1 NOPORTS=1 NOSRC=1 
SRC_CONF=/etc/src.conf release

The latter command only picks up the first kernel. All kernels are 
present and accounted for.

The list is based on KERNCONF from /etc/make.conf. PE1950 is the 
kernel for my builder and thus listed first.

Should I be using release.sh instead? I prefer using the existing 
source tree, and skip the doc and ports trees.

-- 
Trond.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: making a RELEASE

2000-08-03 Thread Oliver Fromme

In list.freebsd-stable Plamen Petkov [EMAIL PROTECTED] wrote:
  3. hacking /usr/src/release/Makefile, where, instead of 'cvs'-ing srcs, I
  just 'cp' them in $CHROOTDIR/src

Using tar (or star from the ports) is probably better
than cp.

  Well, this is a bit away from the 'standard' release/snap making
  procedure, but as i said in my prev messages - I do this for me only, to
  have MY snapshot on a bootable CD, just in case. The price is reasonable -
  a night of my life :-)

And what is the advantage over simply making a backup
of your disk?

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])
Addresses will change soon!!  If in doubt:  www.fromme.com

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: making a RELEASE

2000-08-03 Thread Nora Etukudo

On Thu, Aug 03, 2000 at 02:21:24PM +0200, Oliver Fromme wrote:

   have MY snapshot on a bootable CD, just in case. The price is
   reasonable - a night of my life :-)
 
 And what is the advantage over simply making a backup
 of your disk?

If I have such a CD, I can it auto install on several machines, without
further investigation. This is much less time consuming than a cloneing
from a backup.

Just my 0.02 euro.

Liebe Grüße, Nora.
-- 
[EMAIL PROTECTED]http://www.sappho-net.de/
 Lesbian Computer Networks, Finland   http://www.sappho.net/
 Web for Women (von Frauen, für Frauen)   http://www.w4w.net/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: making a RELEASE

2000-08-03 Thread Oliver Fromme

In list.freebsd-stable Nora Etukudo [EMAIL PROTECTED] wrote:
  On Thu, Aug 03, 2000 at 02:21:24PM +0200, Oliver Fromme wrote:
 have MY snapshot on a bootable CD, just in case. The price is
 reasonable - a night of my life :-)
   
   And what is the advantage over simply making a backup
   of your disk?
  
  If I have such a CD, I can it auto install on several machines, without
  further investigation. This is much less time consuming than a cloneing
  from a backup.

Yes, I know that.

But Plamen Petkov wrote that he just needed a crash recovery
for a single box.  In that case, making a full release and
putting it on CD-R is a complete waste of time, IMO.
You have to make regular backups anyway, except if you don't
care about your data at all (and then you can just re-install
from your latest release CD-ROM and start over from there).

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])
Addresses will change soon!!  If in doubt:  www.fromme.com

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



making a RELEASE

2000-08-02 Thread plamendp

Hi,

I cvsup-ed all src collections, including ports and doc (i.e. src-all, doc-all and 
ports-all).

I went to /usr/src/release and tried to "make release". It asked me to provide CVSROOT 
variable. And oops.. I am confused ... :-) 

Wich path should I give to CVSROOT dir ?

Any documentation regarding "make release" procedure ?

10x.

p.s. please CC: [EMAIL PROTECTED]

 
---
Plamen D. Petkov, ICQ# 2214327
[EMAIL PROTECTED]
First Bulgarian Internet Store
http://www.bgstore.com



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: making a RELEASE

2000-08-02 Thread Dominic Mitchell

On Wed, Aug 02, 2000 at 01:34:00PM +0100, [EMAIL PROTECTED] wrote:
 Hi,
 
 I cvsup-ed all src collections, including ports and doc (i.e. src-all,
 doc-all and ports-all).

 I went to /usr/src/release and tried to "make release". It asked me to
 provide CVSROOT variable. And oops.. I am confused ... :-)

 Wich path should I give to CVSROOT dir ?

You need to download the the cvs collections, not the "checked-out"
collections for make release to work.

 Any documentation regarding "make release" procedure ?

% less /usr/src/release/Makefile

:-)

-Dom


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: making a RELEASE

2000-08-02 Thread Chris BeHanna

On Wed, 2 Aug 2000, Dominic Mitchell wrote:

 On Wed, Aug 02, 2000 at 01:34:00PM +0100, [EMAIL PROTECTED] wrote:
  Hi,
  
  I cvsup-ed all src collections, including ports and doc (i.e. src-all,
  doc-all and ports-all).
 
  I went to /usr/src/release and tried to "make release". It asked me to
  provide CVSROOT variable. And oops.. I am confused ... :-)
 
  Wich path should I give to CVSROOT dir ?
 
 You need to download the the cvs collections, not the "checked-out"
 collections for make release to work.
 
  Any documentation regarding "make release" procedure ?
 
 % less /usr/src/release/Makefile

SLOW DOWN!

"make release" will make the iso images (right?)

What he wants, I suspect, is to cd to /usr/src and follow the
instructions in /usr/src/UPDATING.

Regards,
Chris BeHanna
[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: making a RELEASE

2000-08-02 Thread Chris D. Faulhaber

On Wed, 2 Aug 2000 [EMAIL PROTECTED] wrote:

 Hi,
 
 I cvsup-ed all src collections, including ports and doc (i.e. src-all, doc-all and 
ports-all).
 
 I went to /usr/src/release and tried to "make release". It asked me to provide 
CVSROOT variable. And oops.. I am confused ... :-) 
 
 Wich path should I give to CVSROOT dir ?
 
 Any documentation regarding "make release" procedure ?
 

http://www.FreeBSD.org/FAQ/hackers.html#CUSTREL

-
Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED]

FreeBSD: The Power To Serve   -   http://www.FreeBSD.org



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: making a RELEASE [should make buildworld made before?]

2000-08-02 Thread Domas Mituzas

Hi,
 I cvsup-ed all src collections, including ports and doc (i.e. src-all, doc-all and 
ports-all).
You should fetch cvs collection.

Btw, I missed to find, that "make buildworld" is mandatory before make
release (It failed in several places, if I didn't build the
world). Therefore, during make release world is recompiled at least two
times. Is it a normal operation?

With respect,
Domas Mituzas
dbit.lt, network systems engineer



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: making a RELEASE

2000-08-02 Thread David O'Brien

On Wed, Aug 02, 2000 at 11:42:50AM +0100, Dominic Mitchell wrote:
  I cvsup-ed all src collections, including ports and doc (i.e. src-all,
  doc-all and ports-all).
...
  Wich path should I give to CVSROOT dir ?
 
 You need to download the the cvs collections, not the "checked-out"
 collections for make release to work.

You could also set CVSROOT to the anoncvs.freebsd.org service.  This
would be slower, but save you disk space.

-- 
-- David  ([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: making a RELEASE [should make buildworld made before?]

2000-08-02 Thread John Baldwin

Makoto MATSUSHITA wrote:
 
 obrien However, today's buildworld is more resilent having better
 obrien build-tools, etc.. targets than when release/Makefile was
 obrien first written.  Maybe this need could be removed.  But this
 obrien hasn't happened yet.
 
 If I understand the facts of src/release/Makefile correctly, 
 
 - First 'make installworld' under /usr/src is for "creating a chroot
   environment for further release engineering." Maybe it can be
   supercedesed by copying existing environment or just extracting
   'bin' distribution. But there is no tool for this.

Yes, and just doing a make installworld is the easiest way to do this.

 - Second 'make buildworld' inside a chroot environment is the actual
   build procedure. Obviously, it cannot remove :-)
 
 - Second 'make installworld' inside a chroot environment is for
   "creating an environment for further _actual_ release procedures."
   Even though we have much much better procedures for build-tools,
   _actual_ release procedures (release.[1-9], doc.?, cdrom.?, and
   ftp.? target in src/release/Makefile) does not consider about
   that. If these procedures requires newer version of toolchain, it
   should be a release-breaker.

Well, it is similar to the reason we have build-tools, etc. in the
world.  We want to make sure that we have tools that match the release
Makefile we are using.  Also, it is a good test, since we need to make
sure that the sources can do an actual installworld before we ship them
out to people. :)

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message