Caveat Reader

From owner-p4-projects@FreeBSD.ORG Mon Jan 18 21:13:55 2010 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 3EDE7106568F; Mon, 18 Jan 2010 21:13:55 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 029561065696 for ; Mon, 18 Jan 2010 21:13:55 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id E3BBE8FC1C for ; Mon, 18 Jan 2010 21:13:54 +0000 (UTC) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id o0ILDs9C028128 for ; Mon, 18 Jan 2010 21:13:54 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id o0ILDsKX028126 for perforce@freebsd.org; Mon, 18 Jan 2010 21:13:54 GMT (envelope-from rene@FreeBSD.org) Date: Mon, 18 Jan 2010 21:13:54 GMT Message-Id: <201001182113.o0ILDsKX028126@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 173337 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2010 21:13:55 -0000 http://p4web.freebsd.org/chv.cgi?CH=173337 Change 173337 by rene@rene_self on 2010/01/18 21:13:05 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/building-products/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#45 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/book.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#8 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#42 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml#13 integrate .. //depot/projects/docproj_nl/www/en/news/status/Makefile#8 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2009-10-2009-12.xml#3 integrate .. //depot/projects/docproj_nl/www/en/news/status/status.sgml#9 integrate .. //depot/projects/docproj_nl/www/en/platforms/sparc.sgml#5 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#62 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/building-products/article.sgml#2 (text+ko) ==== @@ -17,7 +17,7 @@ - $FreeBSD: doc/en_US.ISO8859-1/articles/building-products/article.sgml,v 1.7 2006/10/16 11:59:08 keramida Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/building-products/article.sgml,v 1.8 2010/01/15 07:52:25 jkoshy Exp $ &tm-attrib.freebsd; @@ -69,6 +69,17 @@ of collaboration with the project and the pitfalls that need to be avoided while doing so. + + Caveat Reader + The author believes that the characteristics of the FreeBSD + Project listed in this article were substantially true at the + time the article was conceived and written (2005). However, the + reader should keep in mind that the practices and processes used + by open-source communities can change over time, and that the information + in this article should therefore be taken as indicative rather + than normative. + + Target Audience This document would be of interest to the following broad ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#45 (text+ko) ==== @@ -1,4 +1,4 @@ - + 2007 2008 2009 + 2010 The FreeBSD Documentation Project ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#8 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -1567,6 +1567,39 @@ to force the write speed, use the parameter. For more information, read the &man.growisofs.1; manual page. + + + In order to have working files larger than 4.38GB in + your compilation, an UDF/ISO-9660 hybrid filesystem must be + created by passing additional parameter to &man.mkisofs.8; and all related + programs (i.e., &man.growisofs.1;). This is required only + when creating an ISO image file, or writing files directly + to a disk. Disk created this way must be mounted as an UDF + filesystem with &man.mount.udf.8; utility, so it will be + usable only on an UDF aware Operating System,otherwise it + will look as if it contains corrupted files. + + To create a such ISO file: + + &prompt.user; mkisofs -R -J -udf -iso-level 3 -o imagefile.iso /path/to/data + + To burn files directly to a disk: + + &prompt.root; growisofs -dvd-compat -udf -iso-level 3 -Z /dev/cd0 -J -R /path/to/data + + When you have an ISO image containing large files + already inside, no additional options are required for + &man.growisofs.1; to burn that image on a disk. + + Also, be sure that you have an up-to-date version of + sysutils/cdrtools (which + contain &man.mkisofs.8;), as the older ones does not + contain large files support. If you experience troubles + please move to the development package, i.e., sysutils/cdrtools-devel and read + &man.mkisofs.8; manual page. + ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#42 (text+ko) ==== @@ -1,7 +1,7 @@ + October-December @@ -14,16 +14,16 @@ Introduction

This report covers &os; related projects between October and - December 2009. Obviously, this is the last report in the year 2009, - which has shown to be very important for the &os; Project. Besides - other remarkable things, a new major version of &os;, 8.0, has been - released, while the release process for 7.3 is soon to begin.

+ December 2009. This is the last of the four reports covering 2009, + which has shown to be a very important year for the &os; Project. Besides + other notable things, a new major version of &os;, 8.0-RELEASE, has been + released, while the release process for 7.3-RELEASE is soon to begin.

Thanks to all the reporters for the excellent work! We hope you - enjoy the reading. Let us also use this opportunity to wish you all - happy and successfull new year 2010.

+ enjoy reading. Let us also take this opportunity to wish you all a + happy and successful new year for 2010.

Please note that the next deadline for submissions covering the +

Please note that the deadline for submissions covering the period between January and March 2010 is April 15th, 2010.

@@ -109,16 +109,16 @@ - SVN - repository - Official Announcement + + SVN + repository -

A module for DAHDI support for &os; has been created in the +

A DAHDI support module for &os; has been created in the official Asterisk SVN repository.

The following drivers are currently ported:

@@ -166,21 +166,17 @@ - -

The port for dahdi_dynamic_eth and dahdi_dynamic_ethmf is - under way.

- + The port for dahdi_dynamic_eth and dahdi_dynamic_ethmf is + underway. - -

More HW drivers need to be ported.

+ More HW drivers need to be ported. -

Please let me know if you can provide remote access with - serial console to the box with ISDN/T1/E1 HW not currently + Please let me know if you can provide remote access with + serial console to any box with ISDN/T1/E1 HW not currently supported by DAHDI for &os; but supported by DAHDI for Linux. I - am also interested in porting drivers for FXO/FXS cards: please + am also interested in porting drivers for FXO/FXS cards. Please let me know if you can provide a remote access or donate a - card.

- + card. @@ -210,66 +206,55 @@ -

Existing ata(4) infrastructure which has been around many years - has number of problems and limitations, in respect to modern - controllers/devices support. A CAM subsystem (used for SCSI), which - is around for almost the same time, implements many of required - algorithms solving many problems in a better way. To reduce code - duplication and better support border cases such as ATAPI and SAS, - new CAM based ATA implementation has been started in order to use - its benefits.

Existing ata(4) infrastructure, which has been around many years, + has various problems and limitations when compared to modern + controllers/device support. Although the CAM subsystem (used for SCSI) + is almost as old as ata(4), it is more eligible to solve the current + problems. To reduce code duplication and better support border cases + such as ATAPI and SAS, we have started to develop a new CAM based + ATA implementation.

As such, CAM infrastructure was extended to support different - transports. New transport was implemented to support PATA/SATA - buses. To support ATA disks, new CAM driver ada was written. ATAPI +

As such, CAM infrastructure has been extended to support different + transports. New transport has been implemented to support PATA/SATA + buses. To support ATA disks, a new CAM driver (ada) has been written. ATAPI devices are supported by existing SCSI drivers cd, da, sa, etc. To - support SATA port-multipliers new CAM driver pmp was written. To + support SATA port-multipliers another new CAM driver (pmp) has been written. To support most featured and widespread SATA controllers, new drivers - ahci(4) and siis(4) were developed.

+ ahci(4) and siis(4) have been developed.

To support legacy ATA controllers, kernel option ATA_CAM was +

To support legacy ATA controllers, a kernel option ATA_CAM has been added. When used, it makes all ata(4) controllers directly - available to CAM, deprecating ata(4) periperal drivers and external - APIs. To make it possible, ata(4) code was heavily refactored, - making controller driver API more strict.

+ available to CAM, deprecating ata(4) peripheral drivers and external + APIs. To make this possible, ata(4) code has been heavily refactored, + making controller driver API stricter.

Command queuing support gives new ATA implementation up to - double performance benefit on some workloads, whereas 20-30% is + double performance benefit on some workloads, with 20-30% improvement quite usual.

SATA Port Multipliers support makes it easy to build fast and - cheap storages with huge capacities, by using dozens of SATA drives +

SATA Port Multiplier support makes it easy to build fast and + cheap storage with huge capacities, by using dozens of SATA drives in one system or external enclosures,

Some of that code was presented in &os; 8.0-RELEASE, but - 8-STABLE includes much improved version now.

Some of that code has been presented in the recently released &os; 8.0-RELEASE but + 8-STABLE now includes a much improved version.

- -

Improve timeouts and transport errors recovery.

- + Improve timeout and transport error recovery. - -

Improve hot-plug support.

- + Improve hot-plug support. - -

Search and fix any show stoppers for legacy ata(4) - deprecation.

- + Find and fix any show stoppers for legacy ata(4) + deprecation. - -

Write new, more featured driver for Marvell SATA controllers - (specs wanted).

- + Write a new, more featured driver for Marvell SATA controllers + (specifications desired). - -

Write SAS-specific transport and drivers for SAS HBAs (specs - wanted). SAS controllers can support SATA devices and + Write SAS-specific transport and drivers for SAS HBAs (specifications + desired). SAS controllers can support SATA devices and multipliers, so it should fit nicely into the new - infrastructure.

- + infrastructure. @@ -298,25 +283,25 @@

Chromium is a Webkit-based web browser that is largely BSD - licensed. We ported it from linux to &os; in October and have been - posting patches and test builds periodically ever since. Chromium - works well on &os; — it is very fast and stable, but there + licensed. It has been ported from Linux to &os; in October and we have been + posting patches and test builds periodically since then. Chromium + works well on &os; — it is very fast and stable but there are a handful of rough edges that need to be polished up. Two remaining bugs should probably be fixed before releasing a chromium-devel port. We are looking for volunteers to test and - maintain this port, to make this BSD browser a viable option on the - &os; desktop.

+ maintain this port to make this BSD browser a viable option on + &os; desktop systems.

- Fix sporadic rendering freezes + Fix sporadic rendering freezes. - Fix javascript interpreter, v8, on i386 architecture + Fix JavaScript interpreter, v8, on i386 architecture. - SUJ: Journaled Softupdates + SUJ — Journaled SoftUpdates @@ -326,7 +311,7 @@ Roberson - jeff@freebsd.org + jeff@FreeBSD.org @@ -335,24 +320,24 @@ -

I have been adding a small intent log to softupdates to +

I have been adding a small intent log to SoftUpdates to eliminate the requirement for fsck after an unclean shutdown. This work has been funded by Yahoo!, iXsystems, and Juniper. Kirk McKusick has been aiding me with design critiques and helping me - better understand softupdates.

+ better understand SoftUpdates.

Extensive testing by myself and Peter Holm has yielded a stable patch. Current users are encouraged to follow the instructions - posted to current@ to verify stability in your own workloads. - Updates are forthcoming and it is expected to be merged with - current before the end of January. Ports to older versions of &os; + posted to the current@FreeBSD.org mailing list to verify stability in your own workloads. + Updates are forthcoming and it is expected to be merged to + 9.0-CURRENT before the end of January. Ports to older versions of &os; will be available in SVN under alternate branches. Official - backports will be decided by re@ when current is stable.

+ backports will be decided by re@ when 9.0-CURRENT is stable.

The changes are fully backwards and forwards compatible as there are very few metadata changes to the filesystem. The journal may be - enabled or disabled on existing ffs filesystems using tunefs(8). - The log consumes 64 megabytes of space at maximum and fsck time is + enabled or disabled on existing FFS filesystems using tunefs(8). + The log consumes 64 MB of space at maximum and fsck time is bounded by the size of the log rather than the size of the filesystem. Other details are available in my technical journal.

@@ -375,17 +360,17 @@ - The &os; Ports + The &os; Ports Collection + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> Contributing to the &os; Ports Collection &os; ports monitoring system - The &os; + The &os; Ports Management Team marcuscom @@ -393,17 +378,17 @@ -

Most of the recent activity was dealing with the 8.0 release - process. As an experiment, we tried to decouple the ports QA +

Most of the recent activity has been dealing with the 8.0-RELEASE + process. As an experiment, we have tried to decouple the ports QA timeline as much as possible from the src QA timeline. Although this meant that the impact on people actively maintaining and using - ports was much less than in previous releases, it still has not - solved the problem of the release going out with an stale set of + ports has been much less than in previous releases, it still has not + solved the problem of the release going out with a stale set of packages. We are still trying to come up with a better solution for the problem.

The ports count is over 21,000. The PR count jumped to over - 1000, but is now back to around 950.

+ 1,000 but is now back to around 950.

We are currently building packages for amd64-6, amd64-7, amd64-8, i386-6, i386-7, i386-8, i386-9, ia64-8, sparc64-7, and @@ -411,8 +396,8 @@ the last report.

There has been some discussion of when to drop regular package - builds for 6.x, but no decision has been made yet. The cluster, and - the portmgrs, are struggling to keep up with so many branches being + builds for 6.X but no decision has been made yet. The cluster and + the port managers are struggling to keep up with so many branches being active all at the same time.

Mark Linimon continues to make progress on the cluster nodes. @@ -424,20 +409,20 @@ build cluster. The question has been asked of us, "what would it take to speed up package builds?" There is no one simple answer. It is not merely a matter of having a larger number of package - building machines -- before asking for funding we first need to + building machines, so before asking for funding we first need to identify the current bottlenecks. While we are starting to understand the problems on the nodes, the problems on the dispatch machine itself are much harder. Complicating the matter is that there are several periodic processes (ZFS backup, ZFS expiration, and errorlog compression, among others) that can combine to slow - that machine significantly. The interaction of all these - simultaneously is proving difficult to quantify.

+ that machine significantly. The simultaneous interaction of all these + is proving difficult to quantify.

Between pav and miwi, many more experimental ports runs have +

Between Pav Lucistnik and Martin Wilke, many more experimental ports runs have been completed and committed.

We have added 3 new committers since the last report, and 1 - older one has rejoined.

+ older one has rejoined us.

@@ -450,8 +435,8 @@ to get the ports in the shape they really need to be in. Although we have added many maintainers, we still have more - than 4,700 unmaintained ports (see, for instance, the list on - portsmon). (The percentage remains steady at just over 22%.) We are + than 4,700 unmaintained ports. (See, for instance, the list on + portsmon. The percentage remains steady at just over 22%.) We are always looking for dedicated volunteers to adopt at least a few unmaintained ports. As well, the packages on amd64 and especially sparc64 lag behind i386, and we need more testers for those. @@ -477,25 +462,25 @@

The main thing that has taken place since the last Status Report is that I have gotten to the bottom of the remaining PCI problems with Sun Fire V215/V245 and support for these has been completed - and since r202023 now is part of HEAD. With some luck it will also + and since r202023 now is part of 9.0-CURRENT. With some luck it will also be part of the upcoming 7.3-RELEASE.

In other news:

Some other news:

Two bugs in the NFS server causing unaligned accesses and +
Two bugs in the NFS server causing unaligned access and thus panics on sparc64 and all other architectures with strict - alignment requirements (basically all Tier 2 ones) have been + alignment requirements (basically all Tier-2 ones) have been fixed. There likely will be a 8.0-RELEASE Erratum Notice released for these.
&os; has been adopted to the changed firmware of newer Sun - Fire V480 (those equipped with version 7 Schizo bridges) and was + Fire V480 (those equipped with version 7 Schizo bridges) and has been reported to now run fine on these. The necessary change will be part of 7.3-RELEASE. Unfortunately, using the on-board NICs in older models of Sun Fire V480 (at least those equipped with version 4 Schizo bridges) under &os; still leads to the firmware - issuing a FATAL RESET due to what appears to be a CPU bug which + issuing a FATAL RESET due to what appears to be a CPU bug, which needs to be worked around.
Work on supporting Sun Fire V1280 has been started but still @@ -524,18 +509,18 @@ -
Recently a bunch of new device IDs have been added for the - u3g(4) cellular wireless driver, the list should be comparable with +
Recently, a bunch of new device IDs have been added for the + u3g(4) cellular wireless driver; the list should be comparable now with other operating systems around. A lot of these devices have a - feature where the unit first attaches as a disk or cdrom that - contains the Win/Mac drivers, this state should be detected by the + feature where the unit first attaches as a disk or CD-ROM that + contains the Win/Mac drivers. This state should be detected by the u3g driver and the usb device is sent a command to switch to modem - mode. This has been working for quite some time but as its + mode. This has been working for quite some time but as it is implemented differently for each vendor I am looking for feedback on any units where the auto switchover is not working (or the init is not recognized at all). Please ensure you are running an up to - date kernel from head r201681 or later, or stable/8 if r201681 has - been merged by the time of publication.
+ date kernel, like r201681 or later from 9.0-CURRENT, or 8-STABLE + after the future merge of this revision.
@@ -581,17 +566,17 @@
We are happy to announce that Benedict Reuschling is now free - from mentorship and can commit to the doc-tree on his own.
+ from mentorship and can commit to the documentation tree on his own.

Since the last status report, the German Documentation Team has - chased updates to various sections of the &os; handbook, FAQ and - the german website. Many handbook pages were updated to the latest + chased updates to various sections of the &os; Handbook, FAQ and + the German website. Many handbook pages have been updated to the latest version, including chapters about configuration, disks, kernel configuration, printing, multimedia and virtualization.
-
We require help from volunteers who are willing to contribute +
We require help from volunteers that are willing to contribute bug fixes or translations. The following documents need active - maintainership and are a good training-ground for those willing to + maintainership and are a good training ground for those willing to join the translation team:
-
I am sure there are minor items I have forgotten. If so, please - forgive any omission on my part...
- -
he branch had been updated incorrectly several times over the - past year, and the damage was too much to repair. We've retired the - branch and will do further mips development in "head" for the time +
The development branch had been updated incorrectly several times over the + past year, and the damage was too much to repair. We have retired the + branch and will do further mips development in 9.0-CURRENT for the time being. If you have a checked out tree, the suggested way to update the projects/mips tree you have is to do a "svn switch - svn://svn.freebsd.org/base/head" in that tree.
+ svn://svn.FreeBSD.org/base/head" in that tree.

I would like to thank everybody that has contributed time, code - or hardware to make FreeBSD/mips better.
+ or hardware to make &os;/mips better.

As development proceeds, I will keep posting updates. In addition, I hope to have some mini "how-to" wiki pages done for @@ -1092,13 +1070,13 @@ We are still investigating how feasible merging all this work - into stable/8 will be, as it represents a huge leap forward in code + into 8-STABLE will be, as it represents a huge leap forward in code stability and quality. - Flattened Device Tree for embedded FreeBSD + Flattened Device Tree for embedded &os; @@ -1111,51 +1089,51 @@ - Project wiki pages + Project wiki pages - Project P4 branch + Project P4 branch -
The purpose of this project is to provide FreeBSD with support for the +
The purpose of this project is to provide &os; with support for the Flattened Device Tree (FDT) technology, the mechanism for describing computer hardware resources, which cannot be probed or self enumerated, in - a uniform and portable way. The primary consumer of this technology are - embedded FreeBSD platforms (ARM, AVR32, MIPS, PowerPC), where a lot of - designs are based on similar chips, but have different assignment of pins, + a uniform and portable way. The primary consumers of this technology are + embedded &os; platforms (ARM, AVR32, MIPS, PowerPC), where a lot of + designs are based on similar chips but have different assignment of pins, memory layout, addresses bindings, interrupts routing and other resources.

Current state highlights:
- Environment, support tools
- Environment, supported tools