From cperciva at freebsd.org Sat May 2 02:22:50 2009 From: cperciva at freebsd.org (FreeBSD Security Officer) Date: Sat May 2 02:25:13 2009 Subject: [FreeBSD-Announce] FreeBSD supported branches update Message-ID: <49FBAE78.7090608@freebsd.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect the EoL (end-of-life) of FreeBSD 7.0. The new list is below and at . Please note that FreeBSD 7.0 was originally announced with an EoL date of February 28, 2009, but the EoL was delayed by two months in order to allow a 3 month window for systems to be upgraded to FreeBSD 7.1. Users of FreeBSD 7.0 are advised to upgrade promptly to FreeBSD 7.1, either by downloading an updated source tree and building updates manually, or (for i386 and amd64 systems) using the FreeBSD Update utility as described in the FreeBSD 7.1 release announcement. Some users may wish to wait for the upcoming FreeBSD 7.2-RELEASE; however, they should be aware that FreeBSD 7.2-RELEASE will only receive "normal" support (i.e., support for 12 months) and consequently it will not be supported for as long as FreeBSD 7.1. [Excerpt from http://security.freebsd.org/ follows] FreeBSD Security Advisories ~ The FreeBSD Security Officer provides security advisories for ~ several branches of FreeBSD development. These are the -STABLE ~ Branches and the Security Branches. (Advisories are not issued for ~ the -CURRENT Branch.) ~ * The -STABLE branch tags have names like RELENG_7. The ~ corresponding builds have names like FreeBSD 7.0-STABLE. ~ * Each FreeBSD Release has an associated Security Branch. The ~ Security Branch tags have names like RELENG_7_0. The ~ corresponding builds have names like FreeBSD 7.0-RELEASE-p1. ~ Isses affecting the FreeBSD Ports Collection are covered in the ~ FreeBSD VuXML document. ~ Each branch is supported by the Security Officer for a limited ~ time only, and is designated as one of `Early adopter', `Normal', ~ or `Extended'. The designation is used as a guideline for ~ determining the lifetime of the branch as follows. ~ Early adopter ~ Releases which are published from the -CURRENT branch will be ~ supported by the Security Officer for a minimum of 6 months ~ after the release. ~ Normal ~ Releases which are published from a -STABLE branch will be ~ supported by the Security Officer for a minimum of 12 months ~ after the release, and for sufficient additional time (if ~ needed) to ensure that there is a newer release for at least ~ 3 months before the older Normal release expires. ~ Extended ~ Selected releases (normally every second release plus the last ~ release from each -STABLE branch) will be supported by the ~ Security Officer for a minimum of 24 months after the release, ~ and for sufficient additional time (if needed) to ensure that ~ there is a newer Extended release for at least 3 months before ~ the older Extended release expires. ~ The current designation and estimated lifetimes of the currently ~ supported branches are given below. The Estimated EoL (end-of-life) ~ column gives the earliest date on which that branch is likely to be ~ dropped. Please note that these dates may be extended into the ~ future, but only extenuating circumstances would lead to a branch's ~ support being dropped earlier than the date listed. ~ +--------------------------------------------------------------------+ ~ | Branch | Release | Type | Release date | Estimated EoL | ~ |-----------+-----------+--------+-----------------+-----------------| ~ |RELENG_6 |n/a |n/a |n/a |November 30, 2010| ~ |-----------+-----------+--------+-----------------+-----------------| ~ |RELENG_6_3 |6.3-RELEASE|Extended|January 18, 2008 |January 31, 2010 | ~ |-----------+-----------+--------+-----------------+-----------------| ~ |RELENG_6_4 |6.4-RELEASE|Extended|November 28, 2008|November 30, 2010| ~ |-----------+-----------+--------+-----------------+-----------------| ~ |RELENG_7 |n/a |n/a |n/a |last release + 2y| ~ |-----------+-----------+--------+-----------------+-----------------| ~ |RELENG_7_1 |7.1-RELEASE|Extended|January 4, 2009 |January 31, 2011 | ~ +--------------------------------------------------------------------+ [End excerpt] - -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkn7rngACgkQFdaIBMps37IFxACgm/W0s1RMwBtYKHGGa3kk1FSi dwEAn1WIK57UMysjjrj304IySPnxLca9 =veRi -----END PGP SIGNATURE----- From kensmith at FreeBSD.org Mon May 4 00:16:36 2009 From: kensmith at FreeBSD.org (Ken Smith) Date: Mon May 4 00:16:46 2009 Subject: [FreeBSD-Announce] FreeBSD 7.2-RELEASE Available Message-ID: <20090504000613.GA40568@myers.cse.buffalo.edu> The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 7.2-RELEASE. This is the third release from the 7-STABLE branch which improves on the functionality of FreeBSD 7.1 and introduces some new features. Some of the highlights: - support for fully transparent use of superpages for application memory - support for multiple IPv4 and IPv6 addresses for jails - csup(1) now supports CVSMode to fetch a complete CVS repository - Gnome updated to 2.26, KDE updated to 4.2.2 - sparc64 now supports UltraSparc-III processors For a complete list of new features and known problems, please see the online release notes and errata list, available at: http://www.FreeBSD.org/releases/7.2R/relnotes.html http://www.FreeBSD.org/releases/7.2R/errata.html For more information about FreeBSD release engineering activities, please see: http://www.FreeBSD.org/releng/ Availability ------------- FreeBSD 7.2-RELEASE is now available for the amd64, i386, ia64, pc98, powerpc, and sparc64 architectures. FreeBSD 7.2 can be installed from bootable ISO images or over the network; the required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones, such as i386 and amd64. MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message. The purpose of the ISO images provided as part of the release are as follows: dvd1: This contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages, and the documentation. It also supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media. disc1, disc2, disc3, livefs, docs: disc1 contains the base FreeBSD operating system and a few pre-built packages. disc2 and disc3 contain more pre-built packages. Those three can be burned to CDROM sized media and should be all you need to do a normal installation. livefs contains support for booting into a "livefs" based rescue mode but does not support doing an install from the CD itself. You would need to perform a network based install. docs contains the documentation. bootonly: This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself. You would need to perform a network based install (e.g. from an FTP server) after booting from the CD. Note: late in the testing cycle it was discovered some machines do not recognize the i386 disc1 as bootable (they just fall through to booting off the next boot device). All affected machines did see the other discs as bootable. If you have a machine with that problem booting off either bootonly or livefs and then swapping in disc1 once sysinstall starts should work. FreeBSD 7.2-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 7.2-based products is: ~ FreeBSD Mall, Inc. http://www.freebsdmall.com/ BitTorrent ---------- 7.2-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at: http://torrents.freebsd.org:8080/ FTP --- At the time of this announcement the following FTP sites have FreeBSD 7.2-RELEASE available. ftp://ftp.freebsd.org/pub/FreeBSD/ ftp://ftp1.freebsd.org/pub/FreeBSD/ ftp://ftp5.freebsd.org/pub/FreeBSD/ ftp://ftp10.freebsd.org/pub/FreeBSD/ ftp://ftp12.freebsd.org/pub/FreeBSD/ ftp://ftp13.freebsd.org/pub/FreeBSD/ ftp://ftp14.freebsd.org/pub/FreeBSD/ ftp://ftp.dk.freebsd.org/pub/FreeBSD/ ftp://ftp.gr.freebsd.org/pub/FreeBSD/ ftp://ftp.ru.freebsd.org/pub/FreeBSD/ ftp://ftp1.ru.freebsd.org/pub/FreeBSD/ ftp://ftp.tw.freebsd.org/pub/FreeBSD/ ftp://ftp4.tw.freebsd.org/pub/FreeBSD/ ftp://ftp.uk.freebsd.org/pub/FreeBSD/ ftp://ftp3.us.freebsd.org/pub/FreeBSD/ ftp://ftp7.us.freebsd.org/pub/FreeBSD/ ftp://ftp10.us.freebsd.org/pub/FreeBSD/ However before trying these sites please check your regional mirror(s) first by going to: ftp://ftp..FreeBSD.org/pub/FreeBSD Any additional mirror sites will be labeled ftp2, ftp3 and so on. More information about FreeBSD mirror sites can be found at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html Updates from Source ------------------- The procedure for doing a source code based update is described in the FreeBSD Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html The branch tag to use for updating the source is RELENG_7_2. FreeBSD Update -------------- The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.0-RELEASE, 7.1-RELEASE, 7.2-BETA, 7.2-RC1, or 7.2-RC2 can upgrade as follows: # freebsd-update upgrade -r 7.2-RELEASE During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components, and the system needs to be rebooted again: # freebsd-update install # shutdown -r now Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update to upgrade to FreeBSD 7.2, but will be prompted to rebuild all third-party applications (e.g., anything installed from the ports tree) after the second invocation of "freebsd-update install", in order to handle differences in the system libraries between FreeBSD 6.x and FreeBSD 7.x. For more information about upgrading from FreeBSD 6.x using FreeBSD Update, see: http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html Support ------- The FreeBSD Security Team currently plans to support FreeBSD 7.2 until May 31st, 2010. For more information on the Security Team and their support of the various FreeBSD branches see: http://www.freebsd.org/security/ Acknowledgments --------------- Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 7.2 including The FreeBSD Foundation, Hewlett-Packard, Yahoo!, NetApp, Internet Systems Consortium, and Sentex Communications. The release engineering team for 7.2-RELEASE includes: Ken Smith Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination Robert Watson Release Engineering, Security Konstantin Belousov Release Engineering Marc Fonvieille Release Engineering, Documentation George Neville-Neil Release Engineering Hiroki Sato Release Engineering, Documentation Marcel Moolenaar ia64, powerpc Release Building Takahashi Yoshihiro PC98 Release Building Kris Kennaway Package Building Joe Marcus Clarke Package Building Erwin Lansing Package Building Mark Linimon Package Building Pav Lucistnik Package Building Colin Percival Security Officer Trademark --------- FreeBSD is a registered trademark of The FreeBSD Foundation. ISO Image Checksums ------------------- MD5 (7.2-RELEASE-amd64-bootonly.iso) = d77d758684d03815be05f90c12085b2f MD5 (7.2-RELEASE-amd64-disc1.iso) = 3b281f75acef6f6a16d5e405ed003f36 MD5 (7.2-RELEASE-amd64-disc2.iso) = e7d2497054a15906d0e4945d8c91e47f MD5 (7.2-RELEASE-amd64-disc3.iso) = ba4369f5d39fae3bd11ad537f4c52783 MD5 (7.2-RELEASE-amd64-docs.iso) = 97db6efd21c531b2a325224d9897f287 MD5 (7.2-RELEASE-amd64-dvd1.iso) = b3ac4c645aec087480ddefa827c8553c MD5 (7.2-RELEASE-amd64-livefs.iso) = 93c4ad283b66f6cb9d1eb1dcace92ce6 MD5 (7.2-RELEASE-i386-bootonly.iso) = aceb5cdbb14780c97924cb4a645d3258 MD5 (7.2-RELEASE-i386-disc1.iso) = b2415294a55ab3e5c1931f4e0fe67e4e MD5 (7.2-RELEASE-i386-disc2.iso) = b4fd35adea684e6da3a0515b535ece39 MD5 (7.2-RELEASE-i386-disc3.iso) = da2958a3eb6a3ce6237ed7194bdfdd13 MD5 (7.2-RELEASE-i386-docs.iso) = fee5de7fbd8c21e5a7523a1c197c32ae MD5 (7.2-RELEASE-i386-dvd1.iso) = 1d129a999a1db6aefebc57c2f82cacc0 MD5 (7.2-RELEASE-i386-livefs.iso) = decdd91479b8059e70eed6d8e4eb5c06 MD5 (7.2-RELEASE-ia64-bootonly.iso) = d0a84e0014b042f5369e1644a38c380c MD5 (7.2-RELEASE-ia64-disc1.iso) = 58eb2db0a7656a05cb6193aad68e150b MD5 (7.2-RELEASE-ia64-disc2.iso) = bf27c66277e9bea85d9656af154e94ca MD5 (7.2-RELEASE-ia64-disc3.iso) = 1ab4e7e08fa41b7b4e2370a8bde6dcfb MD5 (7.2-RELEASE-ia64-docs.iso) = 01de8413d2829c5b1cb6d495b51cf3a0 MD5 (7.2-RELEASE-ia64-livefs.iso) = 02eadf879e203148610d823e7db515ba MD5 (7.2-RELEASE-pc98-bootonly.iso) = a0eaf2126458fc88ee1ac6d82d1f1c3a MD5 (7.2-RELEASE-pc98-disc1.iso) = 6555c5c4a8606ee043b5a7fbb7759b32 MD5 (7.2-RELEASE-pc98-livefs.iso) = 0a23c3c4fc94d2961be5d148003e9511 MD5 (7.2-RELEASE-powerpc-bootonly.iso) = 17ddd18ad20aa00dd5b4830e536eabad MD5 (7.2-RELEASE-powerpc-disc1.iso) = 015869f4f70124c0204ebd111d876142 MD5 (7.2-RELEASE-powerpc-disc2.iso) = 2f6d5139b57e982039fb90f02cf3f508 MD5 (7.2-RELEASE-powerpc-disc3.iso) = 0a6d3b4a5808374bb44f3f8583df38f7 MD5 (7.2-RELEASE-powerpc-docs.iso) = bb30b266f3c0164b512b3b3317f8ab68 MD5 (7.2-RELEASE-sparc64-bootonly.iso) = e3246598de481f7c1b117c81b46acfaa MD5 (7.2-RELEASE-sparc64-disc1.iso) = 2e767c93f195b69ea83274a1dff4dd5c MD5 (7.2-RELEASE-sparc64-docs.iso) = 1b3d32f0c82c89e18b6f2a3eeca47ae5 SHA256 (7.2-RELEASE-amd64-bootonly.iso) = fb87f4c7ddf8870e8758191181ebf3730dd44534ecc3654069a66d85c56695d3 SHA256 (7.2-RELEASE-amd64-disc1.iso) = 1ea1f6f652d7c5f5eab7ef9f8edbed50cb664b08ed761850f95f48e86cc71ef5 SHA256 (7.2-RELEASE-amd64-disc2.iso) = 0a951c4eea8891b0d2bf3702eb933037dc6db3530b9a37e5b33d765ba9f67154 SHA256 (7.2-RELEASE-amd64-disc3.iso) = 870eeb94b3f21d0ab603986bc6fecb6b3a4a7529f6220ba34aef6458fc43a8b4 SHA256 (7.2-RELEASE-amd64-docs.iso) = 109b9d048b8ff58e392f002ef85f60e75b33ea72ef658edb610f9f50235508d4 SHA256 (7.2-RELEASE-amd64-dvd1.iso) = 1e13d3b6dfa7034e86f17b9ba379fff56761ffad7e029a23a27e92e9dbde2788 SHA256 (7.2-RELEASE-amd64-livefs.iso) = df3cc7f8795b9b260ada2facbd0d77114f0535c35b933a503ac3e56e05947e33 SHA256 (7.2-RELEASE-i386-bootonly.iso) = 6993e73ad5e012d1605c5cf085942b694ec4fa6fb4be114c7e752a012b8c3a5e SHA256 (7.2-RELEASE-i386-disc1.iso) = bf4d00102215b07f5a4c8acac80b9d9bd9bf8bd93ac554fe09b21302f0b41380 SHA256 (7.2-RELEASE-i386-disc2.iso) = 573673db5acebd68dfdbca63f620b923a7e68421f1e946fb26a1381e3d7fd9f8 SHA256 (7.2-RELEASE-i386-disc3.iso) = ec5c98c02849c181f405e63875f193e33e121cb087cec0bd2a3e10f533ffc8e7 SHA256 (7.2-RELEASE-i386-docs.iso) = 77beb6e7a7905a2e9aba4adeb2722be5fbdb699bd44bd0a01e3780b4623d2ce9 SHA256 (7.2-RELEASE-i386-dvd1.iso) = de395cc63cb7fa22a0bf116487c13d56aac71762787fc5581746bfb48e66f750 SHA256 (7.2-RELEASE-i386-livefs.iso) = 4faa7b9d78d125f9b28521247e32e1f0bef3b0b0f21b654ba22c6e79ca3301ce SHA256 (7.2-RELEASE-ia64-bootonly.iso) = 0a2f5fb514f14760b1237059d9ef381e0836fd45579c5264efc2eb49cc57fbb9 SHA256 (7.2-RELEASE-ia64-disc1.iso) = 048850ab672ae6865225b4d3ca324753dd823d526ce93480adf15f602acd96bf SHA256 (7.2-RELEASE-ia64-disc2.iso) = 5fe326d21f2e7646c63a1b6fb5ae913971da99f1c660f0ffd148de19fc47fb11 SHA256 (7.2-RELEASE-ia64-disc3.iso) = 58c0c94d12ca197593ec48cab2fc5ec619a87caa16ae5421958216773665086d SHA256 (7.2-RELEASE-ia64-docs.iso) = 106844d5135e56ed2232ecabe0e4dc8c78e54f7e9d43e92be0ee3f741009a2eb SHA256 (7.2-RELEASE-ia64-livefs.iso) = 70294d2d65e2f483af23d9a4c0d14e1af43da68c086b3e247af31e85050b1247 SHA256 (7.2-RELEASE-pc98-bootonly.iso) = 37f65bb079304353858da6f06936cf12d19cfcdd6f4127aecac91d2a23976db1 SHA256 (7.2-RELEASE-pc98-disc1.iso) = 877845e4dcd3b617f1c23a47b62d27dbe3a5ff6d35075cb20cd038e2b749220f SHA256 (7.2-RELEASE-pc98-livefs.iso) = 3741eb5a178fa0b97a6f50b57dcc750ee7d9d2e1871a244740a4603b22289491 SHA256 (7.2-RELEASE-powerpc-bootonly.iso) = d933276ab67b6de04144ffb3a15e632f6ac6f0a82237654f9349214e0c0acb9b SHA256 (7.2-RELEASE-powerpc-disc1.iso) = b366319ce4cfdbff2ef394cca6f460159dd1e4949927da82904ff5c9baa3f4b8 SHA256 (7.2-RELEASE-powerpc-disc2.iso) = 40e4d5e94c543018fd692efe7150bcca482f1a0a3ddc50330bbbd5a320d90d36 SHA256 (7.2-RELEASE-powerpc-disc3.iso) = fc5ed9a503447c68a9e8392b60c4c35650208c42da982c9c6206e349ad327888 SHA256 (7.2-RELEASE-powerpc-docs.iso) = 58e4f348b057608515bca359a713877964fddf638bca921d09000aada899477b SHA256 (7.2-RELEASE-sparc64-bootonly.iso) = 98aa7492c195df441b4e4699984fd8f38af1db03e7e92cc8d1530089a4d50e11 SHA256 (7.2-RELEASE-sparc64-disc1.iso) = ba7fa45c21d7ca43bacb78fe46c18ef15f73e480e7fe3e6c8ba8c575efe25888 SHA256 (7.2-RELEASE-sparc64-docs.iso) = b67483a4e198e2aeb99bacf9cc826f36a3d9304482fb49c34d05590661d6da76 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-announce/attachments/20090504/d5561081/attachment.pgp From matthias.schuendehuette at siemens.com Mon May 4 07:33:52 2009 From: matthias.schuendehuette at siemens.com (Schuendehuette, Matthias) Date: Mon May 4 11:22:43 2009 Subject: [FreeBSD-Announce] RE: FreeBSD supported branches update In-Reply-To: <49FBAE78.7090608@freebsd.org> References: <49FBAE78.7090608@freebsd.org> Message-ID: Hello, owner-freebsd-security-notifications@freebsd.org wrote on : > The branches supported by the FreeBSD Security Officer have > been updated > to reflect the EoL (end-of-life) of FreeBSD 7.0. The new > list is below > and at . Please note that FreeBSD > 7.0 was originally announced with an EoL date of February 28, 2009, > but the EoL was delayed by two months in order to allow a 3 month > window for systems to be upgraded to FreeBSD 7.1. I have severe problems with this, because NFS-Locking is not working on FreeBSD-7.1 and later with HP-UX clients. See several PRs which are talking about this. FreeBSD-7.0 is the last release that is working and that is therefor still productive at our site. What do you recommend? with best regards Matthias Sch?ndeh?tte SIEMENS AG, Industry Sector, DT LD S IT Tel. +49-30-386 29957 -- Plain text mail please HTML is considered as SPAM From brd at FreeBSD.org Sat May 9 19:40:34 2009 From: brd at FreeBSD.org (Brad Davis) Date: Sat May 9 19:43:11 2009 Subject: [FreeBSD-Announce] FreeBSD Status Reports January - March, 2009 Message-ID: <20090509191339.GE40521@valentine.liquidneon.com> FreeBSD Quarterly Status Report Introduction Since the last Status Reports there has been interesting progress in FreeBSD Development. FreeBSD 7.2 was released just a few days ago. Some of the highlights include: Support for superpages in the FreeBSD Virtual Memory subsystem. The FreeBSD Kernel Virtual Address space has been increased to 6GB on amd64. An updated jail(8) subsystem that supports multi-IPv4/IPv6/noIP and much more. Lots of FreeBSD Developers are in Ottawa, Canada attending the FreeBSD Developer Summit that is before BSDCan. BSDCan officially starts tomorrow and should cover lots of interesting topics, see the BSDCan Website for more information. Thanks to all the reporters for the excellent work! We hope you enjoy reading. __________________________________________________________________ Projects * Clang replacing GCC in the base system * Device mmap() Extensions * OpenBSM * Release Engineering * Sysinfo - a set of scripts which document your system * TrustedBSD MAC Framework in GENERIC * VFS/NFS DTrace Probes * VirtualBox on FreeBSD FreeBSD Team Reports * FreeBSD BugBusting Team Architectures * FreeBSD/powerpc G5 Support * FreeBSD/sparc64 UltraSPARC III support Documentation * Dutch Documentation Project * German Documentation Project * Hungarian Documentation Project Google Summer of Code * BSD-licensed text-processing tools __________________________________________________________________ BSD-licensed text-processing tools URL: http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/ soc2008/gabor_textproc Contact: G?bor K?vesd?n Currently, grep is finished and is only waiting for a portbuild test. It is known to be more or less feature complete, while it is much smaller than the GNU version. As for sort, there has been some progress with the complete rewrite and it is lacking few options. Performance is to be measured, as well. Open tasks: 1. Test grep on pointyhat. 2. Complete sort with the missing features. 3. Do performance measurements for sort and look for possible optimization opportunities. 4. Test sort on pointyhat. __________________________________________________________________ Clang replacing GCC in the base system URL: http://wiki.freebsd.org/BuildingFreeBSDWithClang URL: http://git.hoeg.nl/?p=llvm-bmake URL: http://clang.llvm.org/ Contact: Ed Schouten Contact: Roman Divacky Contact: Brooks Davis Contact: Pawel Worach The last 3-4 months we've been working together with the LLVM developers to discuss any bugs and issues we are experiencing with their Clang compiler frontend. The FreeBSD project is looking at the possibility to replace GCC with Clang as a system compiler. It can compile 99% of the FreeBSD world and can compile booting kernel on i386/amd64 but it still contains bugs and its C++ support is still immature. Ed is maintaining a patchset for the FreeBSD sources to replace cc(1) by a Clang binary and bootstrap almost all sources with the Clang compiler. The LLVM developers are very helpful fixing most of the bugs we've reported (over 100). Unfortunately we are currently blocked on some bug reports that prevent us from building libc, libm, libcrypto and various CDDL libraries with Clang but the FreeBSD kernel itself compiles and boots. Open tasks: 1. Testing Clang with compilation of various applications and reporting bugs. 2. Testing the llvm-bmake branch to find more bugs. 3. Arranging an experimental ports build. __________________________________________________________________ Device mmap() Extensions URL: http://www.FreeBSD.org/~jhb/pat/ Contact: John Baldwin GPU device drivers are increasingly requiring more sophisticated support for mapping objects into both userland and the kernel. For example, memory used for textures often needs to be mapped Write-Combining rather than Write-Back. I have recently created three patches to provide several extensions. The first patch allows device drivers to use a different VM object to back specific mmap() calls instead of always using the device pager. The second patch introduces a new VM object type that can map an arbitrary set of physical address ranges. This can be used to let userland mmap PCI BARs, etc. The third patch allows memory mappings to use different caching modes (e.g. Write-Combining or Uncacheable). Together I believe these patches provide the remaining pieces needed for an Nvidia amd64 driver. They will also be useful for future Xorg DRM support as well. The current set of patches can be safely merged back to 7.x as well. Currently I am waiting for review and feedback from several folks. I am hopeful that these patches will be in HEAD soon, prior to the 8.0 freeze. __________________________________________________________________ Dutch Documentation Project URL: http://wiki.freebsd.org/DutchDocumentationProject URL: http://www.freebsd.org/doc/nl/ URL: http://p4web.freebsd.org/@md=d&cd=//&c=pFl@//depot/projects/docproj_nl/ ?ac=83 Contact: Remko Lodder Contact: Ren? Ladan The FreeBSD Dutch Documentation Project is an ongoing project to translate FreeBSD Documentation into the Dutch language. The translation of the Handbook was completed last January. It is kept up-to-date with the English version. Furthermore five articles and the flyer have been translated. Some initial work has been done to translate the website, but most likely more translators are needed to fully realize it. Open tasks: 1. Recruit more translators. 2. Keep the translations up-to-date with the English versions. 3. Finish the translation of the FAQ. 4. Translate more articles and maybe some books. __________________________________________________________________ FreeBSD BugBusting Team URL: http://www.FreeBSD.org/support.html#gnats URL: http://wiki.FreeBSD.org/BugBusting URL: http://people.FreeBSD.org/~linimon/studies/prs/ URL: http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html Contact: Mark Linimon Contact: Remko Lodder We continue to classify PRs as they arrive, with 'tags' corresponding to the kernel subsystem, or man page references for userland PRs. These tags, in turn, produce lists of PRs sorted both by tag and by manpage Mark Linimon (linimon@) has created special reports for the Release Engineering Team to help focus on regressions and other areas of interest relating to the release of FreeBSD 7.2 in the coming weeks. This is a refinement of the 'customized reports for developers' announced in the last status report. A full list of all the automatically generated reports is also available. Any recommendations for reports which do not currently exist but which would be beneficial are welcomed. Mark Linimon also continues attempting to define the general problem and investigating possible new work flow models, and will be presenting on the subject at BSDCan. The list of PRs recommended for committer evaluation by the BugBusting team continues to receive new additions. This list contains PRs, mostly with patches, that the BugBusting team feel are probably ready to be committed as-is, or are probably trivially resolved in the hands of a committer with knowledge of the particular subsystem. All committers are invited to take a look at this list whenever they have a spare 5 minutes and wish to close a PR. Since the last status report, the number of open bugs continued to hover around the 5600 mark, although has began to rise with the 7.2 ports freeze. As always, more help is appreciated, and committers and non-committers alike are invited to join us on #freebsd-bugbusters on EFnet and help close stale PRs or commit patches from valid PRs. Open tasks: 1. Try to find ways to get more committers helping us with closing PRs that the team has already analyzed. 2. Think of some way for committers to only view PRs that have been in some way 'vetted' or 'confirmed'. 3. Generate more publicity for what we've already got in place, and for what we intend to do next. 4. Define new categories, classifications, and states for PRs, that will better match our work flow (in progress). __________________________________________________________________ FreeBSD/powerpc G5 Support Contact: Nathan Whitehorn FreeBSD 8.0-CURRENT now has support for PowerPC CPUs operating in the 64-bit bridge mode. This includes the PowerPC 970 (G5) as well as the POWER3 and POWER4. Currently only Apple systems are known to work. Open tasks: 1. IBM systems currently are not supported due to missing northbridge support. 2. Software fan control on SMU-based Apple G5 systems (G5 iMac, later Powermac G5) is not available. __________________________________________________________________ FreeBSD/sparc64 UltraSPARC III support Contact: Marius Strobl Like announced in the previous status report, support for sun4u-machines based on UltraSPARC III and beyond has been MFC'ed to stable/7 (the last missing piece was r190297) and thus will be present in the upcoming 7.2-RELEASE and can be already tested with 7.2-RC1. Additionally, as of r191076 machfb(4) has been fixed to work with UltraSPARC III and beyond, that fix unfortunately did not make it into 7.2-RC1 but will be in the final version. The X.Org 7.4 and Firefox ports as well as some other gecko-based ones like Seamonkey once again have been fixed to also work and package on sparc64, including on UltraSPARC III and UltraSPARC IIIi based machines equipped with cards driven by creator(4) or machfb(4). The driver for the Sun Cassini/Cassini+ as well as National Semiconductor DP83065 Saturn Gigabit NICs found on-board for example in Fire V440 and as add-on cards is coming along nicely, the last thing which needs to be implemented before it can hit CURRENT is support for jumbo frames. __________________________________________________________________ German Documentation Project URL: https://doc.bsdgroup.de Contact: Johann Kois Contact: Martin Wilke In February 2009 the German version of the FreeBSD Developer's handbook went online. Additionally we managed to update large areas of the FAQ thanks to the contributions of Benedict Reuschling. The website (at least the areas we see as relevant for a translation) is translated and updated constantly. More volunteers are always welcome of course, as there is still plenty of work to be done. Open tasks: 1. Update the existing documentation set (especially the handbook). 2. Read the translations. Check for problems/mistakes. Send feedback. __________________________________________________________________ Hungarian Documentation Project URL: http://www.FreeBSD.org/hu URL: http://www.FreeBSD.org/doc/hu URL: http://wiki.FreeBSD.org/HungarianDocumentationProject URL: http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@// depot/projects/docproj_hu/?ac=83 Contact: G?bor K?vesd?n Contact: G?bor P?li We are proud to announce that the FreeBSD Hungarian web pages have been extended by the following items: * Project news entries, staring from 2009 (HTML, RSS, RDF) * Press releases, starting from 2008 (HTML, RSS) * Events, starting from 2009 (HTML, RSS) * Security advisories (HTML, RSS) We are still hoping that having the FDP Primer translated will encourage others to help our work. Feel free to contribute, every submitted line of translation or feedback is appreciated and is highly welcome. For more information on how to contribute, please read the project's introduction (in Hungarian). Open tasks: 1. Translate news entries, press releases. 2. Translate Release Notes for -CURRENT and 8.X. 3. Translate articles. 4. Translate web pages. 5. Read the translations, send feedback. __________________________________________________________________ OpenBSM URL: http://www.openbsm.org/ Contact: Robert Watson Contact: TrustedBSD audit mailing list The TrustedBSD Project has now released OpenBSM 1.1, the second production release of the OpenBSM code base. OpenBSM 1.1 has been merged to FreeBSD 8-CURRENT, and will be merged to 7-STABLE before FreeBSD 7.3. Major changes since OpenBSM 1.0 include: * Trail files now include the host where the trail is generated. Crash recovery has been improved. Trail expiration based on size and date is now supported; by default trail files will be expired after 10MB of trails. The default individual trail limit is now 2MB. * Mac OS X Snow Leopard is now a fully supported platform; launchd(8) can now be used to launchd auditd(8). Command line tools and libraries are now supported on Mac OS X Leopard. * Extended header tokens are now supported, allowing audit trails to be tagged with a host identifier. IPv6 addresses are now supported in subject tokens. BSM token and record types have been further synchronized to OpenSolaris; support for many new system calls has been added. Local errors and socket types are mapped to and from BSM values. Since the last test release, OpenBSM 1.1 beta 1, 32/64-bit compatibility has been fixed for the auditon(2) system call. A default "expire-after" of 10MB is now set in audit_control(5). Local fcntl(2) arguments are now mapped to wire BSM versions using new APIs. The audit_submit(3) man page has been fixed. A new audit event class has been added for post-login authentication and access control events. Open tasks: 1. Migrate to sbufs in token-encoding. 2. Support for auditing NFS RPCs. __________________________________________________________________ Release Engineering URL: http://www.FreeBSD.org/releng/ Contact: Release Engineering Team The Release Engineering Team (with lots of help from lots of other people) released FreeBSD 7.2 on May 4th, 2009. During this period we have also begun reminding developers of the upcoming FreeBSD 8.0 release cycle which is scheduled to begin in early June 2009 with release targeted at early September 2009. __________________________________________________________________ Sysinfo - a set of scripts which document your system URL: http://danger.rulez.sk/index.php/2009/04/14/sysinfo-a-set-of-scripts-wh ich-document-your-freebsd-system/ URL: https://forums.freebsd.org/showthread.php?p=19321 Contact: Daniel Gerzo Sysinfo a shell script which purpose is to automatically gather system information and document hardware and software configuration of the given host system. The goal is to provide a system operator with descriptive information about an unknown FreeBSD installation. It consists of several modules (also shell scripts), thus is easily extensible and provides an easy way to inspect overall system configuration. It has been written as part of my Bachelor thesis and its development is a work in progress. Therefore, I would appreciate if you could provide me with some feedback as I will defend my thesis soon. Your feedback is welcome at the forums , or alternatively you can send me a private email. The tool itself can now be installed using the Ports tree from the sysutils/sysinfo port. Open tasks: 1. Receive additional feedback. 2. Perform more testing. 3. Extend and improve the tool. __________________________________________________________________ TrustedBSD MAC Framework in GENERIC URL: http://www.trustedBSD.org/mac.html Contact: Robert Watson Contact: TrustedBSD discussion mailing list There is on-going work to allow "options MAC" to be included in the GENERIC kernel for 8.0. This primarily consists of performance work to reduce overhead when policies are used, and eliminate when none are configured. Work to date includes: * The MAC Framework now detects which object types are labeled by policies, and MAC label storage is not allocated when it won't be used. * Add MAC Framework DTrace probes so allow more easy analysis of MAC Framework and policy interactions. * Eliminate mutex-protected reference count used to prevent module unload during entry point invocation, and replace with an sx lock and an rwlock, respectively for long-sleepable and short-sleepable entry points, significantly lowering the overhead of entering the MAC Framework. If no dynamic policies are loaded, no locking overhead is taken. Open tasks: 1. Move to rmlocks for non-sleepable entry points to reduce cache line thrashing under load. 2. Macroize invocation of MAC Framework entry points from the kernel, and perform caller-side determination of whether MAC is enabled in order to avoid additional function call overhead in the caller path if MAC is disabled. __________________________________________________________________ VFS/NFS DTrace Probes Contact: Robert Watson A new DTrace provider, dtnfsclient, has been added to the FreeBSD 8.x kernel, and will be merged to 7.x before 7.3. The following probes are available: * nfsclient:{nfs2,nfs3}:{procname}:start - NFSv2 and NFSv3 RPC start probes * nfsclient:{nfs2,nfs3}:{procname}:done - NFSv2 and NFSv3 RPC done probes * nfsclient:accesscache:: - NFS access cache flush/hit/miss/load probes * nfsclient:attrcache:: - NFS attribute cache flush/hit/miss/done In addition, a number of VFS probes have been added: * vfs:vop:{vopname}:entry - VOP entry probe * vfs:vop:{vopname}:return - VOP return probe * vfs:namei:lookup:entry - VFS name lookup entry probe * vfs:namei:lookup:return - VFS name lookup return probe * vfs:namecache:*:* - VFS namecache enter/enter_negative/fullpath_enter/fullpath_hit/fullpath_miss/full path_return/lookup_hit/lookup_hit_negative/lookup_miss/purge/purge_ negative/purgevfs/zap/zap_negative probes These probes make it much easier to trace NFS and VFS events. Open tasks: 1. Add VFSOP tracing. 2. Add RPC-layer tracing, such as RPC retransmits. 3. Provide decoded NFS RPCs in order to expose transaction IDs and file handles. __________________________________________________________________ VirtualBox on FreeBSD URL: http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd/ URL: http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd-first-screenshots/ URL: http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001369.html Contact: Beat Gaetzi Contact: Bernhard Froehlich Contact: Dennis Herrmann Contact: Martin Wilke After the first mail from Alexander Eichner on the vbox-dev mailinglist, we started the work on a VirtualBox port. 6 Days was needed to get VirtualBox to start with over 20 patches. We'd like to say thanks to Alexander Eichner, all the VirtualBox Developers, Gustau Perez and Ulf Lilleengen. If you like to play with the current port you can checkout the port here. Please do not ping us about any problems, we know about a lot and are still working to get them all solved before we do an official call for testing. Open tasks: 1. Fix kernel crashes on 7.2-RELEASE. 2. Code cleanup. 3. Fix errors on AMD64. 4. Fix user/permission problems. From deb at freebsdfoundation.org Thu May 28 16:47:49 2009 From: deb at freebsdfoundation.org (Deb Goodkin) Date: Thu May 28 18:50:27 2009 Subject: [FreeBSD-Announce] Foundation Project Announcement Message-ID: <4A1EB85F.1060006@freebsdfoundation.org> Dear FreeBSD Community, The FreeBSD Foundation is pleased to announce another project from our accepted project proposals! Arnar Mar Sig has been awarded a grant to develop AVR32 support for FreeBSD. AVR32 is a 32-bit MIPS architecture targeted for low power high throughput embedded applications. The target platform is the NGW100 reference design board from Atmel. "This work will advance the MIPS support in FreeBSD and our capabilities in building embedded applications," said Sam Leffler, The FreeBSD Foundation, Director. "I'm excited to be able to work on bringing FreeBSD to another architecture and pushing it farther into the embedded market," said Arnar Mar Sig, FreeBSD developer. The project will be completed by August 2009. Sincerely, The FreeBSD Foundation From lgj at usenix.org Thu May 28 17:14:13 2009 From: lgj at usenix.org (Lionel Garth Jones) Date: Thu May 28 18:50:54 2009 Subject: [FreeBSD-Announce] HotCloud '09 Registration Now Open Message-ID: <0B51485E-8E75-47E3-AD0C-CB13E4237A94@usenix.org> We'd like to invite you to the Workshop on Hot Topics in Cloud Computing (HotCloud '09), taking place in San Diego, CA, June 15, 2009. HotCloud '09 will discuss challenges in the Cloud Computing paradigm, including the design, implementation, and deployment of virtualized clouds. Join academics and practitioners in sharing experiences, leveraging each other's perspectives, and identifying new and emerging "hot" trends in this area. The program includes sessions on: * Cloud Platforms and Architectures * Elastic Clouds and Resource Management * Storage Cloud and Appliances * Map Reduce and Cloud Applications * Panel on Cloud Computing The full program can be found at http://www.usenix.org/events/hotcloud09/tech/ Don't miss this opportunity to engage in dynamic discussion on key topics in the cloud computing community. Register today at http://www.usenix.org/hotcloud09/proga HotCloud will be co-located with the 2009 USENIX Annual Technical Conference (USENIX '09), June 14-19: http://www.usenix.org/events/usenix09/ Multiple Conference Savings: Go to both HotCloud '09 and USENIX '09 and save $100 off your USENIX '09 registration. Contact the Conference Department at conference@usenix.org to receive your priority discount code. NOTE: If you're already registered for USENIX '09, contact the Conference Department at the email address above to receive your $100 refund. We look forward to seeing you in San Diego! Sambit Sahu, IBM T.J. Watson Research Center Prashant Shenoy, University of Massachusetts Amherst HotCloud '09 Program Chairs ---------------------------------- Workshop on Hot Topics in Cloud Computing (HotCloud '09) June 15, 2009 San Diego, CA Sponsored by USENIX: The Advanced Computing Systems Association Register online by Monday, June 8, 2009, noon PDT http://www.usenix.org/hotcloud/proga ----------------------------------