Adding RELEASEDIR/iso to release(7)

The new iso-image code recently committed by Manuel Bouyer
builds small
CD-ROM images in RELEASEDIR/MACHINE/install/cdrom/*, and
large CD-ROM
images in RELEASEDIR/iso/*.  The small images tend to be for
exactly
one platform, and contain a kernel, sysinst, some
crunchgenned tools,
but not *.tgz sets.  The large images contain *.tgz sets,
and could in
principle be multi-platform.

releases(7) doesn't talk about RELEASEDIR/iso at all.  I'd
like to
update it, but first I'd like to understand the difference
between the
two locations.  Given a CD-ROM image, how would you
determine which
directory it belongs in, and how would you choose the file
name?

--apb (Alan Barrett)

On Tue, Apr 03, 2007 at 12:17:11PM +0200, Alan Barrett
wrote:
> The new iso-image code recently committed by Manuel
Bouyer builds small
> CD-ROM images in RELEASEDIR/MACHINE/install/cdrom/*,
and large CD-ROM
> images in RELEASEDIR/iso/*.  The small images tend to
be for exactly
> one platform, and contain a kernel, sysinst, some
crunchgenned tools,
> but not *.tgz sets.  The large images contain *.tgz
sets, and could in
> principle be multi-platform.
> 
> releases(7) doesn't talk about RELEASEDIR/iso at all. 
I'd like to
> update it, but first I'd like to understand the
difference between the
> two locations.  Given a CD-ROM image, how would you
determine which
> directory it belongs in, and how would you choose the
file name?

Well, the isos in RELEASEDIR/MACHINE/install/cdrom/* only
contains
INSTALL kernels, but not the binary sets. This is for
someone
who wants to boot from CD but install with some other way
(e.g. network),
or which needs different boot options (e.g. console on
com0).

-- 
Manuel Bouyer <bouyerantioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la
difference
--

On Thu, 05 Apr 2007, Manuel Bouyer wrote:
> > releases(7) doesn't talk about RELEASEDIR/iso at
all.  I'd like to
> > update it, but first I'd like to understand the
difference between the
> > two locations.  Given a CD-ROM image, how would
you determine which
> > directory it belongs in, and how would you choose
the file name?
> 
> Well, the isos in RELEASEDIR/MACHINE/install/cdrom/*
only contains
> INSTALL kernels, but not the binary sets.

Is that true for all architectures, including those that
still use
mkisofs to generate images?

Is "does not contain binary sets" the important
factor that should me
mentioned in release(7) as a differentiator between
RELEASEDIR/iso and
RELEASEDIR/MACHINE/install/cdrom?

If the answers to the above questions are both
"yes", then does
the following patch look OK?

--apb (Alan Barrett)

Index: src/share/man/man7/release.7
============================================================
=======
--- release.7	1 Apr 2007 14:13:55 -0000	1.22
+++ release.7	6 Apr 2007 12:54:36 -0000
 -34,7
+34,7 
 ." ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE
 ." POSSIBILITY OF SUCH DAMAGE.
 ."
-.Dd April 1, 2007
+.Dd April 6, 2007
 .Dt RELEASE 7
 .Os
 .Sh NAME
 -155,6
+155,42 
 command:
 .Sy date -u .
 .
+.It Sy iso/
+CDROM images in ISO 9660 format, usually created with
+.Dq ./build.sh ... iso-image ...
+after a
+.Dq ./build.sh -x ... release sourcesets ...
+in
+.Pa src .
+.Pp
+Images in this directory, unlike images in the
+.Sm off
+.Xo
+.Sy .../NetBSD-
+.Em *[Lt]rel*[Gt]
+.Sy /
+.Em *[Lt]machine*[Gt]
+.Sy /installation/cdrom/
+.Xc
+.Sm on
+directory, should contain file systems that
+have an internal layout that corresponds to
+a complete release for one or more machine types.
+These images are usually bootable.
+.Bl -tag -width "netbsd-ARCH.iso"
+.It Sy BSDSUM
+.It Sy CKSUM
+.It Sy MD5
+.It Sy README
+.It Sy SYSVSUM
+.Sm off
+.It Xo
+.Em *[Lt]machine_arch*[Gt]
+.Sy cd.iso
+.Xc
+.Sm on
+.El
+.
 .It Sy shared/
 Files shared by one or more platforms.
 .Bl -tag -width "*[Lt]machine_arch*[Gt]"
 -353,14
+389,16 
 installation helper items
 .Bl -tag -width "diskimage/"
 .It Sy cdrom/
-CDROM images in ISO 9660 format, usually created with
-.Dq make iso-image
-in
-.Pa src/etc
-after a
-.Dq ./build.sh -x ... release sourcesets ...
+CDROM images in ISO 9660 format, usually created as part
of
+.Dq build.sh ... release ...
 in
 .Pa src .
+.Pp
+Images in this directory will typically be bootable,
+and will contain one or more of a kernel, installation
tools,
+and rescue tools.
+They will not contain installation sets, source sets, or
+other components of a complete release.
 .Bl -tag -width "netbsd-ARCH.iso"
 .It Sy BSDSUM
 .It Sy CKSUM

On Fri, Apr 06, 2007 at 02:58:50PM +0200, Alan Barrett
wrote:
> On Thu, 05 Apr 2007, Manuel Bouyer wrote:
> > > releases(7) doesn't talk about RELEASEDIR/iso
at all.  I'd like to
> > > update it, but first I'd like to understand
the difference between the
> > > two locations.  Given a CD-ROM image, how
would you determine which
> > > directory it belongs in, and how would you
choose the file name?
> > 
> > Well, the isos in
RELEASEDIR/MACHINE/install/cdrom/* only contains
> > INSTALL kernels, but not the binary sets.
> 
> Is that true for all architectures, including those
that still use
> mkisofs to generate images?

Not yet; the attached patch should make it that way.

> 
> Is "does not contain binary sets" the
important factor that should me
> mentioned in release(7) as a differentiator between
RELEASEDIR/iso and
> RELEASEDIR/MACHINE/install/cdrom?

I think so.

> 
> If the answers to the above questions are both
"yes", then does
> the following patch look OK?

The images in RELEASEDIR/iso are named 'ARCH'cd.iso, to
match what we
currently have in pub/NetBSD/iso/. Otherwise, looks good !

-- 
Manuel Bouyer <bouyerantioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la
difference
--

On Sun, Apr 08, 2007 at 01:30:26PM +0200, Manuel Bouyer
wrote:
> On Fri, Apr 06, 2007 at 02:58:50PM +0200, Alan Barrett
wrote:
> > On Thu, 05 Apr 2007, Manuel Bouyer wrote:
> > > > releases(7) doesn't talk about
RELEASEDIR/iso at all.  I'd like to
> > > > update it, but first I'd like to
understand the difference between the
> > > > two locations.  Given a CD-ROM image,
how would you determine which
> > > > directory it belongs in, and how would
you choose the file name?
> > > 
> > > Well, the isos in
RELEASEDIR/MACHINE/install/cdrom/* only contains
> > > INSTALL kernels, but not the binary sets.
> > 
> > Is that true for all architectures, including
those that still use
> > mkisofs to generate images?
> 
> Not yet; the attached patch should make it that way.

With the patch, this time

-- 
Manuel Bouyer <bouyerantioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la
difference
--

On Sun, 08 Apr 2007, Manuel Bouyer wrote:
> > > Well, the isos in
RELEASEDIR/MACHINE/install/cdrom/* only contains
> > > INSTALL kernels, but not the binary sets.
> 
> Not yet; the attached patch should make it that way.

Thatnks for reviewing the patch to release(7).  I have
committed it with
minor changes.

Could you commit your patch to make the build actually do
what's now
documented?  It would be nice if you could also generate
checksums in
the RELEASEDITR/iso directory.

--apb (Alan Barrett)

On Mon, Apr 09, 2007 at 10:23:32AM +0200, Alan Barrett
wrote:
> On Sun, 08 Apr 2007, Manuel Bouyer wrote:
> > > > Well, the isos in
RELEASEDIR/MACHINE/install/cdrom/* only contains
> > > > INSTALL kernels, but not the binary
sets.
> > 
> > Not yet; the attached patch should make it that
way.
> 
> Thatnks for reviewing the patch to release(7).  I have
committed it with
> minor changes.
> 
> Could you commit your patch to make the build actually
do what's now
> documented? 

Done

> It would be nice if you could also generate checksums
in
> the RELEASEDITR/iso directory.

Well, it means each build would have to generate its
checksums without
overwriting the ones for previous builds. I don't know if
it's
easy with the current framework.

-- 
Manuel Bouyer <bouyerantioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la
difference
--