OpenBSD Journal

OpenBSD turns 4.4-beta

Contributed by jason on from the CSRG-would-be-proud dept.

Theo de Raadt has tagged 4.4-beta. Snapshots should be available soon for testing, check the mirrors for availability. Read below for the full commit message.

CVSROOT:	/cvs
Module name:	src
Changes by:	deraadt@cvs.openbsd.org	2008/07/01 18:13:32

Modified files:
	sys/sys        : param.h 
	share/tmac/mdoc: doc-common 
	share/mk       : sys.mk 
	distrib/miniroot: install.sub 
	etc/root       : root.mail 
	sys/arch/macppc/stand/tbxidata: bsd.tbxi 
	sys/conf       : newvers.sh 

Log message:
move to 4.4-beta

We need users to help test all parts of OpenBSD and report any critical bugs and problems you can find so we can release a fully functional and stable OpenBSD 4.4.

Editor's Note: There has been a lot of new functionality added over the last two hackathons. In this editor's opinion, this should be one of OpenBSD's greatest releases, coinciding with a very historic version number. Let's all pitch in and do our part to squash any outstanding bugs.

(Comments are closed)


Comments
  1. By Anonymous Coward (74.12.26.243) on

    Out of curiosity, what is note worthy of a 4.4 release number?

    Comments
    1. By jason (jason) on http://www.dixongroup.net/

      > Out of curiosity, what is note worthy of a 4.4 release number?

      There's a hint in the department. Learn your UNIX history! :)

    2. By Anonymous Coward (85.222.21.198) on

      > Out of curiosity, what is note worthy of a 4.4 release number?

      http://en.wikipedia.org/wiki/BSD#4.4BSD_and_descendants

      Have a nice reading! :-)

  2. By Anonymous Coward (70.173.232.231) on

    a pity no new perl or groff this release, but still lots of sweet candy to make up for it

  3. By Sacha Ligthert (83.160.140.70) on http://sacha.ligthert.net

    $ wc -l changes
    603 changes

    Devs: Thank you and congrats! :D

  4. By Anonymous Coward (88.90.37.194) on

    I'm running -current myself, but at work I use -stable. I'm really looking forward to buying the new CD-set to see the new art, listen to the new song, and to read the usually hilarious, though serious, story (yes, yes, the code-changes is what really matters, but I already have that ;-) )

    I think this will be an excellent release (or, rather, "more excellent" than usual).

    Good work, guys. I'll keep supporting you for as long as I can.

  5. By Anonymous Coward (82.116.241.176) on

    So the ports-tree will get locked soon too?
    If so: There some updates (wich where posted on ports@) wich are not yet integrated (or did I missed f.e. FF 3.x?).

    I just mention this because f.e. FF 2.x runs out of support kinda "soon". :)

    Comments
    1. By Matthias Kilian (91.3.36.128) on

      > So the ports-tree will get locked soon too?
      > If so: There some updates (wich where posted on ports@) wich are not yet integrated (or did I missed f.e. FF 3.x?).

      Help testing and debugging it, especially on platforms beyond i386 and amd64.

      Comments
      1. By Anonymous Coward (213.221.123.174) on

        > > So the ports-tree will get locked soon too?
        > > If so: There some updates (wich where posted on ports@) wich are not yet integrated (or did I missed f.e. FF 3.x?).
        >
        > Help testing and debugging it, especially on platforms beyond i386 and amd64.

        And that's the problem... I just own i386(+64bit) not no PPC or Sparc.. :/

        Comments
        1. By sthen@ (2a01:348:108:155:216:41ff:fe53:6a45) on

          > > > So the ports-tree will get locked soon too?
          > > > If so: There some updates (wich where posted on ports@) wich are not yet integrated (or did I missed f.e. FF 3.x?).
          > >
          > > Help testing and debugging it, especially on platforms beyond i386 and amd64.
          >
          > And that's the problem... I just own i386(+64bit) not no PPC or Sparc.. :/

          If you have 64-bit capable machines running i386, moving them to amd64 -current, testing things and reporting software which has unusual crashes that you're not used to would certainly be useful.

          If you can dual-boot and compare i386/amd64 for the same OS and software versions, that would be ideal. You may well find bugs on amd64 that are not currently seen on our other 64-bit capable arch.

          If you run into problems, please give concise summaries (on ports@ not here), and if it involves doing more than just starting the software please tell us how to make it crash :-)

      2. By Sacha Ligthert (ligthert) on http://sacha.ligthert.net/

        > Help testing and debugging it, especially on platforms beyond i386 and amd64.

        By any chance, do you have a series of scripts or tests I can run on my hardware?

        Comments
        1. By Marc Espie (163.5.254.20) espie@openbsd.org on

          > > Help testing and debugging it, especially on platforms beyond i386 and amd64.
          >
          > By any chance, do you have a series of scripts or tests I can run on my hardware?
          >

          Just run stuff, figure out what breaks that used to work.

          If we had scripts to do everything, we would do all the testing ourselves. External users input is invaluable...

  6. By Shane J Pearson (203.20.79.196) on

    * In pfctl(8), add a counter to record how many states have been created by a rule.

    * Added a kernel implementation of the 4-way handshake and group-key handshake protocols of 802.11i, and a software implementation of TKIP and CCMP, making WPA/WPA2-PSK usable in both station and hostap modes for bwi(4), malo(4), ral(4), iwn(4), wpi(4), ural(4), rum(4), upgt(4), and zyd(4).

    * Implemented an AES XTS mode in the crypto(9) framework.

    * Initial version of softraid(4) crypto support. Disabled for now.


    Wow, this is all very exciting! Now we wait for the pre-orders!

    Thank you to all the devs!

    Comments
    1. By Anonymous Coward (203.169.184.37) on

      > * In pfctl(8), add a counter to record how many states have been created by a rule.
      >
      > * Added a kernel implementation of the 4-way handshake and group-key handshake protocols of 802.11i, and a software implementation of TKIP and CCMP, making WPA/WPA2-PSK usable in both station and hostap modes for bwi(4), malo(4), ral(4), iwn(4), wpi(4), ural(4), rum(4), upgt(4), and zyd(4).
      >
      > * Implemented an AES XTS mode in the crypto(9) framework.
      >
      > * Initial version of softraid(4) crypto support. Disabled for now.
      >
      >
      > Wow, this is all very exciting! Now we wait for the pre-orders!
      >
      > Thank you to all the devs!

      Of course this is impressiv but some questions remain:

      -> Will the algorithm used for svnd change as well?
      Or will there even be a option or a config file to choose an algorithm?
      -> I am sure AES XTS gets HW accelerated some day (I think about the VIA
      CPUs) am i correct?

      The WPA thing is realy realy awesome! Thank you very much! (just a note: my manpages do not mention it and I run current. Maybe it was forgotten (or don't mangaes get rebuild from CVS as well?? :( ).

      But I kindly would like to mention that there are networks wich do use WEP but WEP with up to 256Bit (so called "WEP+" sometimes). I am not sure if it is hard to support this but I would be happy about supporting this kind of WEP as well even it is not that common and WPA is more secure.

      Also I like to forward a little "Please do test"-Request from tech@ because I think not everybody reads tech@ or cvs@ and I do not see so many testing requests on misc@ (maybe somebody founds test@ where such requests get sended to? It may would be handy).

      It deals with ACPI and speedstep so if you own a laptop and do run current:
      http://marc.info/?l=openbsd-tech&m=121493180205892&w=2

      Thank you very much Developers!

      Comments
      1. By George Koehler (kernigh) on http://kernigh.pbwiki.com/OpenBSD

        > The WPA thing is realy realy awesome! Thank you very much! (just a note: my manpages do not mention it and I run current. Maybe it was forgotten (or don't mangaes get rebuild from CVS as well?? :( ).

        The current ifconfig(1) manual page mentions WPA. Look in the "IEEE 802.11 (WIRELESS DEVICES)" section, for the "wpa" options.

        Comments
        1. By Anonymous Coward (206.57.47.49) on

          > > The WPA thing is realy realy awesome! Thank you very much! (just a note: my manpages do not mention it and I run current. Maybe it was forgotten (or don't mangaes get rebuild from CVS as well?? :( ).
          >
          > The current
          > http://www.openbsd.org/cgi-bin/man.cgi?query=ifconfigIEEE 802.11 (WIRELESS DEVICES)" section, for the "wpa" options.

          That is correct just there is no information wich drivers do support it.
          And in f.e. the ral-manpage there is nothing mentioned.

          THat was the thing I wanted to point out. :)

    2. By Anonymous Coward (84.192.197.63) on

      > * Initial version of softraid(4) crypto support. Disabled for now.
      is it possible to stack up disciplines with softraid? for example, have two disks in a raid1 setup, then layer crypto on top of that? or should i treat the two disks as two raw partitions, svnd 'em and then raid1 the svnd's?

  7. By Richard Toohey (121.72.16.128) knightofthecode@gmail.com on

    Looks like the current install44.iso snapshot is corrupt? Should I be trying to use it to test, or some other method?

    Got the install44.iso from ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/i386/

    When I boot I get this ...

    >> OpenBSD/i386 CDBOOT 2.02
    cd0a: /etc/boot.conf: line too long

    This from install44.iso snapshot of 2nd July, around 105Mb - 4.3 snaps are around 215Mb?

    I can boot off it, but when trying to install I get error messages. (Answering my own question, really, aren't I?)

    Mirrors seem to have the same size file:

    ftp://ftp3.usa.openbsd.org/pub/OpenBSD/snapshots/i386/
    ftp://ftp5.usa.openbsd.org/pub/OpenBSD/ (cannot connect)
    ftp://rt.fm/pub/OpenBSD/snapshots/i386/

    Thanks.

    Comments
    1. By Loki (218.214.194.113) on

      > Looks like the current install44.iso snapshot is corrupt? Should I be trying to use it to test, or some other method?
      >
      > Got the install44.iso from ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/i386/
      >
      > When I boot I get this ...
      >
      > >> OpenBSD/i386 CDBOOT 2.02
      > cd0a: /etc/boot.conf: line too long
      >
      > This from install44.iso snapshot of 2nd July, around 105Mb - 4.3 snaps are around 215Mb?

      I downloaded that one today (GMT+1000):
      214 MB (225,062,912 bytes) 4 July 2008, 11:00:41 AM

      Works just fine, so far. Only tried booting to help you, no install yet.
      4.4-beta (RAMDISK_CD) #803: Tue Jul 1 21:06:16 MDT 2008

      Any more help needed?
      Loki/
      ---

    2. Comments
      1. By Richard Toohey (121.72.16.128) knightofthecode@gmail.com on

        > Check those MD5... ;)

        Thanks, guys.

        Looks like I looked at the wrong time - but I did check a couple of mirrors.

        Next time - look at the MD5s as well, and wait a few hours!

        I'll download again tonight and get testing.

  8. By RISC (risc) km.cyberpirate@gmail.com on none

    Good News!
    Thanks all :D

  9. By Anonymous Coward (88.191.80.227) on

    How's about NFS? Any speed improvements?
    plus.html does not clarify this for me.

    Comments
    1. By Anonymous Coward (122.49.167.130) on

      It clarifies it for me...
      "Improves write performance due to less syncing"

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.]