X-Git-Url: https://gitweb.dragonflybsd.org/ikiwiki.git/blobdiff_plain/0703c256270fc19d6ccd04357af11e4f72418a50..HEAD:/release34/index.mdwn diff --git a/release34/index.mdwn b/release34/index.mdwn index 0f2ce1f6..731780d9 100644 --- a/release34/index.mdwn +++ b/release34/index.mdwn @@ -1,6 +1,11 @@ # DragonFly Release 3.4 -Version 3.4.0 released xx April 2013. +Version 3.4.1 released 29 April 2013. + +Version 3.4.2 released 27 May 2013. See the [tagged commit](http://lists.dragonflybsd.org/pipermail/commits/2013-May/130119.html) for details. + +Version 3.4.3 released 26 August 2013. See the [tagged commit](http://lists.dragonflybsd.org/pipermail/commits/2013-August/197955.html) for details. + ## Big-ticket items @@ -8,7 +13,7 @@ Version 3.4.0 released xx April 2013. John Marino has created a system, DPorts, that uses the FreeBSD ports system to build ports for DragonFly, and uses [pkgng](https://github.com/pkgng/pkgng#readme) to manage the binary packages produced from those ports. -The default packaging system on DragonFly is pkgsrc. To use DPorts, you must remove or disable pkgsrc packages. Pkgsrc and DPorts cannot be used at the same time, or have packages mixed together. See the [DPorts Howto page](docs/docs/howtos/HowToDPorts/) for details on installing and using DPorts. Note: this is the first release with DPorts, and this is still experimental. +The default packaging system on DragonFly is pkgsrc. To use DPorts, you must remove or disable pkgsrc packages. Pkgsrc and DPorts cannot be used at the same time, or have packages mixed together. See the [DPorts Howto page](/docs/howtos/HowToDPorts/) for details on installing and using DPorts. Note: this is the first release with DPorts, and this is still experimental. The [DragonFly snapshots](http://avalon.dragonflybsd.org/snapshots/) are built using dports. (and also have XFCE for the desktop) @@ -16,9 +21,11 @@ The [DragonFly snapshots](http://avalon.dragonflybsd.org/snapshots/) are built u The process of testing [poudriere](https://fossil.etoilebsd.net/poudriere/doc/trunk/doc/index.wiki), a tool for mass-producing binary dports packages, exposed stability issues when repeatedly mounting and unmounting many tmpfs systems on large multicore (48) systems. These issues have been fixed. In addition to stability, several changes were made to improve performance in situations with heavy processor and disk usage. +Improvements in [poudriere performance, tmpfs performance](http://lists.dragonflybsd.org/pipermail/kernel/2013-April/031224.html), and [CPU usage](http://lists.dragonflybsd.org/pipermail/kernel/2013-April/031227.html) (graphs are linked in those message) were graphed by Francois Tigeot and posted on the kernel@dragonflybsd.org mailing list. + ### New default compiler -The two base compilers have swapped roles. GCC 4.7, introduced as an alternative compiler with Release 3.2, is now the primary compiler used to build DragonFly. GCC 4.4 remains on the system and still has an important role as the primary DPorts compiler. GCC 4.7 brings [OpenMP](http://http://openmp.org/) (parallel programming) support to DragonFly via libgomp as well as stack smashing protection via libssp, neither of which was supported by GCC 4.4. The newer compiler also offers improved C++ and Objective-C support. +The two base compilers have swapped roles. GCC 4.7, introduced as an alternative compiler with Release 3.2, is now the primary compiler used to build DragonFly. GCC 4.4 remains on the system and still has an important role as the primary DPorts compiler. GCC 4.7 brings [OpenMP](http://openmp.org/) (parallel programming) support to DragonFly via libgomp as well as stack smashing protection via libssp, neither of which was supported by GCC 4.4. The newer compiler also offers improved C++ and Objective-C support, and introduces [Link-Time Optimization](http://en.wikipedia.org/wiki/Link-time_optimization) (LTO) support. ### New USB stack @@ -38,33 +45,55 @@ The release ISO images should be available on most of the [[mirrors|mirrors]]. I MD5 sums for the compressed images: -* MD5 (dfly-i386-3.2.1_REL.img.bz2) = a592... -* (FIXME) +* MD5 (dfly-i386-3.4.1_RELEASE.img.bz2) = 304aac2b5662f11af790c7f0873a1aa3 +* MD5 (dfly-i386-3.4.1_RELEASE.iso.bz2) = 2d5bdbff3b6bd67956519757e346ab26 +* MD5 (dfly-i386-gui-3.4.1_RELEASE.img.bz2) = 5d2b24c3ac661b0a22f588ac81f2e2ad +* MD5 (dfly-i386-gui-3.4.1_RELEASE.iso.bz2) = 4ca4b3511cff0f46b3cf0a4130be95fa +* MD5 (dfly-x86_64-3.4.1_REL.img.bz2) = ea1f86fc95f9cf30b9481a0bf4dff8eb +* MD5 (dfly-x86_64-3.4.1_REL.iso.bz2) = 4e7dad45b484f00290accd14fe030171 +* MD5 (dfly-x86_64-gui-3.4.1_REL.img.bz2) = 3c8897a6f2ae2c2d2b9c000d3a85a720 +* MD5 (dfly-x86_64-gui-3.4.1_REL.iso.bz2) = ca66aa3f58d9e66075480ce10f3249e9 + MD5 sums for the uncompressed images: -* MD5 (dfly-i386-3.2.1_REL.img) = 52c416d... -* (FIXME) +* MD5 (dfly-i386-3.4.1_REL.img) = a233e06f0149e454e973996da9004850 +* MD5 (dfly-i386-3.4.1_REL.iso) = 5cc59952ecfc8fc18b447df8dd2b6086 +* MD5 (dfly-i386-gui-3.4.1_REL.img) = d0338bd1a48533a1fbed346fd43cfc40 +* MD5 (dfly-i386-gui-3.4.1_REL.iso) = bb9b3a6032e56d66b10f448a8ff5ed33 +* MD5 (dfly-x86_64-3.4.1_REL.img) = d430112f7d901fdd10c2f53d345c333d +* MD5 (dfly-x86_64-3.4.1_REL.iso) = 5b1db3c77eeb6a71cf507cd76ddff860 +* MD5 (dfly-x86_64-gui-3.4.1_REL.img) = cd0a0dd126d280b37a864918705b33a1 +* MD5 (dfly-x86_64-gui-3.4.1_REL.iso) = 3b77c0074f141ee37c1cb221ed018bfd + ### pkgsrc packages -Pkgsrc packages have not been pre-built for this release. We suggest building from source for pkgsrc installation. +Prebuilt pkgsrc packages are built using pkgsrc-2013Q1. 'pkg_radd' can be used to automatically install binary pkgsrc packages and dependencies. We supply a Makefile in `/usr` to track the pkgsrc tree and we supply a Git mirror of the NetBSD pkgsrc CVS repo at `git://git.dragonflybsd.org/pkgsrcv2.git`. We recommend that users use it, instead of pulling from NetBSD with CVS. Our Git mirror is updated several times a day. Type 'make' in /usr to see the available commands for performing these actions. ## DragonFly 3.4 Special Installation and Upgrade Notes -**Disk size warning** - Installations using HAMMER should be to disks over 50G in size. HAMMER history will consume disk space quickly. Either use UFS on smaller disks, or prune your file history carefully. +**Disk size warning** - Installations using HAMMER should use disks over 50G in size. HAMMER history will consume disk space quickly. Either use UFS on smaller disks, or prune your file history carefully. **Virtual PC users** - Virtual PC does not supply serial numbers for the virtual disks. The system may need to be manually directed in the boot loader if the disk identifier changes. (Hit ? in the boot loader for a list of available volumes.) **Qemu users** - If you see a large number of error messages on the console when booting, you may need to boot DragonFly with ACPI disabled. This can be done in the menu presented at initial boot. If that doesn't help, try placing hw.ioapic_enable=0 in /boot/loader.conf. +**VMWare Player users** - xorg.conf may require additional configuration to display a desktop on the i386 GUI DragonFly images. + **Installer Crypt Options** - The installer can encrypt the root volume and the swap volume. It will not work properly for other volumes despite any additional check-boxes you might see. Installer and boot-time support works but is still a bit rough around the edges. Performance will be relatively high on multi-core machines. -## DragonFly 3.4.0 Release Notes +## DragonFly 3.4.2 Release Notes + +For a list of per-commit changes between 3.4.1 and 3.4.2, see the [3.4.2 tag commit](http://lists.dragonflybsd.org/pipermail/commits/2013-May/130119.html). + +The major reasons for this point release were fixes for DragonFly [under Xen with more than 2 CPUs specified](http://lists.dragonflybsd.org/pipermail/commits/2013-May/130116.html), and for [booting x86_64 DragonFly in KVM](http://lists.dragonflybsd.org/pipermail/commits/2013-May/130071.html). -For a list of per-commit changes, see the [3.4.0rc tag commit](http://lists.dragonflybsd.org/pipermail/commits/2013-April/129831.html). +## DragonFly 3.4.0/3.4.1 Release Notes + +For a list of per-commit changes, see the [3.4.0rc tag commit](http://lists.dragonflybsd.org/pipermail/commits/2013-April/129831.html) and the [3.4.1 tag commit](http://lists.dragonflybsd.org/pipermail/commits/2013-April/129946.html). > ### Kernel changes @@ -100,7 +129,8 @@ For a list of per-commit changes, see the [3.4.0rc tag commit](http://lists.drag * SMBIOS information is now detected and available. * ifnet/ifaddr statistics are now saved per-CPU. * virtio, virtio-blk drivers added. - +* eaccess support implemented +* SO_NOSIGPIPE support implemented > ### Hardware changes @@ -136,6 +166,11 @@ For a list of per-commit changes, see the [3.4.0rc tag commit](http://lists.drag * System make set to bmake. * Automatic installation of dports via /usr/Makefile added. * Fixed bug in powerd that could lead to only 1 cpu in the cpumask for userland scheduling. +* libfetch synced with FreeBSD +* libutil updated with file group utilities and hexdump +* cp, mv synced with FreeBSD +* getline bug fixed +* Implemented automatic backup of binaries prior to installworld > ### Removals @@ -145,8 +180,9 @@ For a list of per-commit changes, see the [3.4.0rc tag commit](http://lists.drag * Shipping with pkgsrc-2013Q1. * gcc4.1 removed -* gcc4.7 added -* flex updated to 2.5.3.7 +* gcc4.7 promoted to primary compiler +* gcc4.4 demoted to alternate compiler +* flex updated to 2.5.37 * bmake updated to 20121010 * OpenSSH updated to 6.1p1 * m4 updated