OpenBSD Journal

4.3 Pre-release testing needed

Contributed by jason on from the if-you-love-something-test-it dept.

With the 4.3 release impending, Theo de Raadt has asked for testing of recent snapshots and packages on all supported hardware platforms, using the various install methods for each. This is an important step in ensuring the installation media and upgrade process works as expected. Read Theo's message below, download snapshots and packages from your closest mirror, and send in your dmesglogs now!

Date: Tue, 04 Mar 2008 19:38:34 -0700                                           
From: Theo de Raadt                                    
Subject: Pre-release tests                                                      
To: misc@openbsd.org


Right about now is a great time for our user community to jump in and
do some install and upgrade tests.

The 4.3 release cycle is fully in swing, and I hope that I can get it
over with soon so that the developers can start work on the bug fixes
and new work that can't make it into 4.3.

Here's a list of the things that need testing.  I hope that to most
people this list is rather self explanatory; if in doubt just think
for a particular test might mean, grab a snapshot for some
architecture, and take a shot at testing the ones that you can!

Our developers work from a list similar to this, but this time I am
asking that our user community jump in and help as much as they can,
too.  I'm hoping to expose the testing mentality a bit.. so that more
people help.

I must note something of importance in this list.  Some things are
easy to test, because well... everyone has a PC.  Well, the problem is
that the bugs we look for in the last bit of a release cycle are more
likely to be in vax net booting, or sun4c having a problem, or a
particular alpha bug... I mention this hoping that some of you see
that there must be a balance of some sort.  We want all of our
architectures to shine.  When everything is great on the little old
architectures, then the common ones will be great too.

As always, if you find a problem, please file a high quality Problem
Report (if you have the strength, check the PR database first to see
if similar PRs are not yet closed).  You can use the command
sendbug(1) to send a PR...

If you are able to, please submit a dmesglog of the running machine to
dmesg@openbsd.org -- with the Subject: set to the type of your machine
(ie. SunFire V215, or IBM eServer 325 or such) -- and PLEASE avoid the
use of MIME, but instead send your messages without any special
encoding since it lets our developers grep easily through the logs
looking for specific machines when they are fixing bugs.  Recently, I
have had to start deleting the MIME submissions with the SPAM.

Of course, little that you report will be fixed in the release, but if
we run into any show stoppers.. it is a best that we know now.

Please also note something else of importance.  Since we are close to
a release, the snapshots are in a constant state of flux -- as we make
changes new ones are being put onto the FTP mirrors very quickly.
Please make sure that the files you download have correct MD5
checksums, and please include the timestamps of the files in your bug
reports.

Thanks.

i386
	cd43
	cdemu43
	install43
	bsd.rd
	floppyA
	floppyB
	floppyC
	pxeboot
	install
	upgrade
	bsd.mp on MP    
	real CD
	X11R6
	All the packages

amd64
	cd43
	install43
	floppy
	pxeboot
	bsd.rd
	install
	upgrade
	bsd.mp	 
	X11R6
	All the packages

macppc
	cd43
	install43
	bsd.rd hfs
	bsd.rd ffs
	install
	upgrade
	X11R6
	All the packages

sparc64
	cd43
	install43
	netboot
	miniroot
	bsd.rd
	bsd.mp
	floppy
	install
	upgrade
	X11R6
	All the packages

alpha
	cd43
	install43
	netboot
	bsd.rd
	floppy
	floppyB
	install
	upgrade
	X11R6
	All the packages

zaurus
	ipkg
	bsd.rd ffs
	bsd.rd ext2fs
	install
	upgrade
	X11R6
	All the packages

sparc
	floppy
	tape
	cd43
	install43
	netboot
	miniroot
	bsd.rd
	install
	upgrade
	X11R6
	All the packages
	Make sure sun4c and sun4 work

sgi
	cd43
	netboot(tftp)
	bsd.rd
	install
	upgrade
	X11R6
	All the packages

landisk
	bsd.rd
	miniroot
	install
	upgrade
	X11R6
	All the packages

armish
	bsd.rd
	install
	upgrade
	X11R6
	All the packages

mac68k	 
	bsd.rd
	install
	upgrade
	X11R6
	All the packages

hp300
	bsd.rd
	bsd.rd on cd
	netboot
	install
	upgrade
	X11R6
	All the packages

mvme68k
	bsd.rd
	netboot
	s-records
	install
	upgrade
	X11R6 (no srv)
	All the packages

mvme88k
	bsd.rd
	tftpboot
	netboot
	install
	upgrade
	X11R6 (no server)
	All the packages

hppa
	cd43
	install43
	bsd.rd
	lif
	netboot
	tape
	install
	upgrade
	X11R6 (no server)
	All the packages

vax
	cd43
	install43
	floppy/simh
	mop
	tape
	bsd.rd
	install
	upgrade
	X11R6
	All the packages

(Comments are closed)

Comments

  1. By Kevin (24.136.16.163) kkadow@gmail.com on

    So how stable, or unstable, is the MP kernel on Sparc64?

    We've got a whole pile of 280's sitting around collecting dust.

    Literally.

    Comments

    1. By Mark Kettenis (82.92.89.47) on

      > So how stable, or unstable, is the MP kernel on Sparc64?

      Quite stable; the official sparc64 snapshots have been built on a Sun Fire V215 with two CPUs for a couple of months now. There seem to be some stability problems on machines with more than four CPUs, but those don't seem to show up on dual CPU machines at all, so...

      > We've got a whole pile of 280's sitting around collecting dust.

      ...those 280's will happily run bsd.mp.

    2. By Anonymous Coward (72.39.118.252) on

      > So how stable, or unstable, is the MP kernel on Sparc64?
      >
      > We've got a whole pile of 280's sitting around collecting dust.
      >
      > Literally.

      I think the whole point of Theo's post was to have people with all manner of hardware download the appropriate install sets, test them out and provide feedback.

      In all seriousness, _you_ are in the best position to find out how well the hardware you have is supported, and I am sure that everyone who uses OpenBSD will be very thankful for any testing and feedback that you provide. =D

  2. By Peter N. M. Hansteen (pitrh) peter@bsdly.net on http://bsdly.blogspot.com/

    ... and remember, while we're busy testing all manner of 4.3isms, we can start looking forward to hearing the new song :)

  3. By Anonymous Coward (195.42.56.43) on

    What are the new features of this release ?

    Comments

    1. By Anonymous Coward (88.192.76.90) on

      > What are the new features of this release ?

      Check it out from http://www.openbsd.org/plus.html . Everything on that site.

  4. By David Chisnall (137.44.2.39) on

    I see a couple of systrace-related things on plus.html, but no sign of whether systrace is still vulnerable to the argument modification after call vulnerability. Has this been fixed (i.e. by copying or locking arguments for the duration of the system call), or is systrace still vulnerable?


    Comments

    1. By tedu (208.105.14.130) on

      > I see a couple of systrace-related things on plus.html, but no sign of whether systrace is still vulnerable to the argument modification after call vulnerability. Has this been fixed (i.e. by copying or locking arguments for the duration of the system call), or is systrace still vulnerable?


      same as before.

  5. By Anonymous Coward (162.58.82.136) on

    I have an Ultra-80 would this help in any way..?

  6. By Anonymous Coward (71.41.117.107) on


    for testing, you want us to use "snapshots" correct?
    Don't see a 4.3beta on the ftp site... so it must be...:
    ftp://ftp.openbsd.org/pub/OpenBSD/snapshots

    ALSO for warm fuzzies...
    I sure like to know I can do a "make build" on the src
    and make the ports, and make the GENERIC kernel myself on my platform
    I see for the ports:
    ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/ports.tar.gz

    But under snapshots I did not see a src ?

    To use anoncvs to checkout 4.3beta, are we suppose to use "current"
    or is their a branch tag like OPENBSD_4_3_BASE or BETA ?

    TIA.

    Comments

    1. By Anonymous Coward (129.9.163.105) on

      The "-beta" name is just a temporary name for -current. Follow the guidelines in the "following -current" FAQ and if you want to build a system beyond the snapshot, follow FAQ 5. If you want the source tree, yes, you'll need CVS or CVSup etc.

      Comments

      1. By Anonymous Coward (71.41.117.107) on

        > The "-beta" name is just a temporary name for -current.


        Interesting that the snapshot does not carry src.tar.gz
        nor sys.tar.gz like the stables do, but does carry ports.tar.gz


        understandable if snapshot is meant to be only a day or two old...
        and resources are limited... however if so why carry ports.tar.gz in snapshot and not src nor sys?

        Comments

        1. By Anonymous Coward (71.41.117.107) on

          > Interesting that the snapshot does not carry src.tar.gz
          > nor sys.tar.gz like the stables do, but does carry ports.tar.gz


          maybe this is because snapshots for various subfolders (arch) are not from the same date? hmmm.. so if it did carry src and sys, it may not match exactly the snapshots for various arch...

          Comments

          1. By Anonymous Coward (71.41.117.107) on

            > > Interesting that the snapshot does not carry src.tar.gz
            > > nor sys.tar.gz like the stables do, but does carry ports.tar.gz
            >

            duh... my bad.... measure twice, cut once, google twice, ask once....
            googled this as an answer to get matching src for date of snapshot.

            # IF you want stable or say a certain date of current you could
            # check out src from an anoncvs server. For example if you are
            # crazy enough to use a current snapshot, know the target date
            # and need the source for that snapshot date you may could do
            # something like this:
            # cvs checkout -D "2003-07-22 12:00" src

            Comments

            1. By Anonymous Coward (200.51.41.29) on

              > > > Interesting that the snapshot does not carry src.tar.gz
              > > > nor sys.tar.gz like the stables do, but does carry ports.tar.gz
              > >
              >
              > duh... my bad.... measure twice, cut once, google twice, ask once....
              > googled this as an answer to get matching src for date of snapshot.
              >
              > # IF you want stable or say a certain date of current you could
              > # check out src from an anoncvs server. For example if you are
              > # crazy enough to use a current snapshot, know the target date
              > # and need the source for that snapshot date you may could do
              > # something like this:
              > # cvs checkout -D "2003-07-22 12:00" src

              well I personaly can't do that...


              # export CVSROOT=anoncvs@anoncvs.openbsd.org:/cvs
              # cvs -q get -rOPENBSD_4_3 -P ports
              cvs [server aborted]: cannot write /cvs/CVSROOT/val-tags: Permission denied
              # id
              uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest)

              opencvs bug?

              Comments

              1. By Richard Toohey (203.167.190.49) richardtoohey@hotmail.com on

                > well I personaly can't do that...
                >
                >
                > # export CVSROOT=anoncvs@anoncvs.openbsd.org:/cvs
                > # cvs -q get -rOPENBSD_4_3 -P ports
                > cvs [server aborted]: cannot write /cvs/CVSROOT/val-tags: Permission denied
                > # id
                > uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest)
                >
                > opencvs bug?

                Ummm, I might have got the wrong end of the stick, but ... http://www.undeadly.org/cgi?action=article&sid=20080228093414 ...

                "ONE RULE REMAINS. Do NOT even think for a moment
                that you can opencvs against our main repositories in any way"

                Comments

                1. By Anonymous Coward (200.51.41.29) on

                  > > well I personaly can't do that...
                  > >
                  > >
                  > > # export CVSROOT=anoncvs@anoncvs.openbsd.org:/cvs
                  > > # cvs -q get -rOPENBSD_4_3 -P ports
                  > > cvs [server aborted]: cannot write /cvs/CVSROOT/val-tags: Permission denied
                  > > # id
                  > > uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest)
                  > >
                  > > opencvs bug?
                  >
                  > Ummm, I might have got the wrong end of the stick, but ... http://www.undeadly.org/cgi?action=article&sid=20080228093414 ...
                  >
                  > "ONE RULE REMAINS. Do NOT even think for a moment
                  > that you can opencvs against our main repositories in any way"

                  Ok and HOW do I update a 4.3-beta from code then?!
                  Could somebody pls. tell me how to do so I mean if I don't get the src I can't stay u2date without installing each time via binary...

                  That seriously is a BIG issue for me :-/

                  Is the old CVS somewhere inside the beta like cvsold or so?!

                  Comments

                  1. By Anonymous Coward (200.51.41.29) on

                    > > > well I personaly can't do that...
                    > > >
                    > > >
                    > > > # export CVSROOT=anoncvs@anoncvs.openbsd.org:/cvs
                    > > > # cvs -q get -rOPENBSD_4_3 -P ports
                    > > > cvs [server aborted]: cannot write /cvs/CVSROOT/val-tags: Permission denied
                    > > > # id
                    > > > uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest)
                    > > >
                    > > > opencvs bug?
                    > >
                    > > Ummm, I might have got the wrong end of the stick, but ... http://www.undeadly.org/cgi?action=article&sid=20080228093414 ...
                    > >
                    > > "ONE RULE REMAINS. Do NOT even think for a moment
                    > > that you can opencvs against our main repositories in any way"
                    >
                    > Ok and HOW do I update a 4.3-beta from code then?!
                    > Could somebody pls. tell me how to do so I mean if I don't get the src I can't stay u2date without installing each time via binary...
                    >
                    > That seriously is a BIG issue for me :-/
                    >
                    > Is the old CVS somewhere inside the beta like cvsold or so?!

                    I missunderstood the posting!
                    I used a mirror and it worked!

                    I would like to know what "crypto" means for softraid. I read plus.html but can't find a real hint where it deals with crypto? :-(

                    Comments

                    1. By tedu (208.105.14.130) on


                      > I would like to know what "crypto" means for softraid. I read plus.html but can't find a real hint where it deals with crypto? :-(

                      nothing for now.

                  2. By Matthew Dempsky (38.102.129.10) on

                    > Ok and HOW do I update a 4.3-beta from code then?!

                    You don't. You install a newer snapshot.

                  3. By Anonymous Coward (81.83.46.237) on

                    It is a BIG issue for you that you can't upgrade a BETA version that's only meant for testing?

                    (indeed, you just install a newer snap)

                  4. By Xavier Santolaria (xsa) xsa@ on

                    > > > well I personaly can't do that...
                    > > >
                    > > >
                    > > > # export CVSROOT=anoncvs@anoncvs.openbsd.org:/cvs
                    > > > # cvs -q get -rOPENBSD_4_3 -P ports
                    > > > cvs [server aborted]: cannot write /cvs/CVSROOT/val-tags: Permission denied
                    > > > # id
                    > > > uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest)
                    > > >
                    > > > opencvs bug?
                    > >
                    > > Ummm, I might have got the wrong end of the stick, but ... http://www.undeadly.org/cgi?action=article&sid=20080228093414 ...
                    > >
                    > > "ONE RULE REMAINS. Do NOT even think for a moment
                    > > that you can opencvs against our main repositories in any way"
                    >
                    > Ok and HOW do I update a 4.3-beta from code then?!
                    > Could somebody pls. tell me how to do so I mean if I don't get the src I can't stay u2date without installing each time via binary...
                    >
                    > That seriously is a BIG issue for me :-/
                    >
                    > Is the old CVS somewhere inside the beta like cvsold or so?!

                    OpenCVS is installed as /usr/bin/opencvs -- old GNU CVS is still /usr/bin/cvs.

              2. By joris (81.240.97.200) on

                >
                >
                > # export CVSROOT=anoncvs@anoncvs.openbsd.org:/cvs
                > # cvs -q get -rOPENBSD_4_3 -P ports
                > cvs [server aborted]: cannot write /cvs/CVSROOT/val-tags: Permission denied
                > # id
                > uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest)
                >
                > opencvs bug?

                Thats gnu cvs, fyi.

    2. By Anonymous Coward (64.129.81.169) on

      > src for 4.3beta testing?

      that was few days ago... so to checkout src, would have had
      to use a date stamp since no BRANCH tag...
      now,
      don't have to use a date for getting source now, can use tag,
      tags are now available for the BRANCHES of OPENBSD_4_3
      and OPENBSD_4_3_BASE

      http://www.openbsd.org/cgi-bin/cvsweb/src/?only_with_tag=OPENBSD_4_3
      http://www.openbsd.org/cgi-bin/cvsweb/src/?only_with_tag=OPENBSD_4_3_BASE

      Comments

      1. By Otto Moerbeek (otto) on http://www.drijf.net

        > > src for 4.3beta testing?
        >
        > that was few days ago... so to checkout src, would have had
        > to use a date stamp since no BRANCH tag...
        > now,
        > don't have to use a date for getting source now, can use tag,
        > tags are now available for the BRANCHES of OPENBSD_4_3
        > and OPENBSD_4_3_BASE
        >
        > http://www.openbsd.org/cgi-bin/cvsweb/src/?only_with_tag=OPENBSD_4_3
        > http://www.openbsd.org/cgi-bin/cvsweb/src/?only_with_tag=OPENBSD_4_3_BASE

        Testing your own compiled code is NOT what is asked for.

        We request to test snapshots, since we want to exercise what is going to be on the CDs and the ftp site.

        Testing something else won't help the release to be a quality release.

  7. By Dennis van Zuijlekom (tmib) t m i b AT x s 4 a l l DOT n l on

    Submitted dmesg's for a few SPARC64 systems which I have access to; Sun Ultra 5, Sun Ultra 60, Sun Fire 280R, Sun Fire V210 and Sun Blade 100.

Latest Articles

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]