From owner-p4-projects@FreeBSD.ORG Wed Jan 7 19:10:06 2009 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 75C051065670; Wed, 7 Jan 2009 19:10:06 +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 3397B1065678 for ; Wed, 7 Jan 2009 19:10:06 +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 2ABCC8FC19 for ; Wed, 7 Jan 2009 19:10:05 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id n07JA5bk057734 for ; Wed, 7 Jan 2009 19:10:05 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id n07JA5bk057731 for perforce@freebsd.org; Wed, 7 Jan 2009 19:10:05 GMT (envelope-from rene@FreeBSD.org) Date: Wed, 7 Jan 2009 19:10:05 GMT Message-Id: <200901071910.n07JA5bk057731@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 Cc: Subject: PERFORCE change 155769 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2009 19:10:07 -0000 http://perforce.freebsd.org/chv.cgi?CH=155769 Change 155769 by rene@rene_self on 2009/01/07 19:09:32 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#9 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#14 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#9 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/ports/chapter.sgml#7 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#26 integrate .. //depot/projects/docproj_nl/www/en/developers/cvs.sgml#3 integrate .. //depot/projects/docproj_nl/www/en/releases/7.1R/announce.sgml#3 integrate .. //depot/projects/docproj_nl/www/en/releng/index.sgml#12 integrate .. //depot/projects/docproj_nl/www/en/security/security.sgml#5 integrate .. //depot/projects/docproj_nl/www/share/sgml/events.xml#12 integrate .. //depot/projects/docproj_nl/www/share/sgml/navibar.ent#3 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#9 (text+ko) ==== @@ -11,7 +11,7 @@ The &os; Ports Management Team - $FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.35 2008/09/20 18:47:41 linimon Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.36 2009/01/07 09:34:58 pav Exp $ 2003 @@ -491,7 +491,8 @@ build portsupdate arch - branch - Replaces the ports + branch + buildid - Replaces the ports tree with a new ZFS snapshot. Don't forget to use -noports flag to dopackages later! ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#14 (text+ko) ==== @@ -12,7 +12,7 @@ The &os; Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1106 2009/01/05 15:44:57 remko Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1107 2009/01/07 09:49:12 pgj Exp $ 1995 @@ -4590,6 +4590,46 @@ + + Do I need to recompile every port each time I perform a + major version update? + + + + By all means! While a recent system will run with + software compiled under an older release, you will end up with + things randomly crashing and failing to work once you start + installing other ports or updating a portion of what you + already have. + + When the system is upgraded, various shared libraries, + loadable modules, and other parts of the system will be + replaced with newer versions. Applications linked against + the older versions may fail to start or, in other cases, + fail to function properly. + + For more information, see the section on upgrades + in the &os; Handbook. + + + + + + Do I need to recompile every port each time I perform a + minor version update? + + + + In general, no. &os; developers do their utmost to + guarantee binary compatibility across all releases with the + same major version number. Any exceptions will be + documented in the Release Notes, and advice given there + should be followed. + + + + Why is /bin/sh so minimal? Why does &os; not use bash or another ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#9 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -79,6 +79,12 @@ + How to keep your documentation up to date with + CVSup. + + + The difference between the two development branches: &os.stable; and &os.current;. @@ -698,6 +704,327 @@ &prompt.root; portsnap fetch update + + Updating the Documentation Set + + Updating and Upgrading + + + Documentation + Updating and Upgrading + + + Besides the base system and the Ports Collection, + documentation is an integral part of the &os; operating system. + While an up-to-date version of the &os; Documentation Set is + always available on the &os; web site, some + users might have slow or no permanent network connectivity at all. + Fortunately, there are several ways to update the documentation + shipped with each release by maintaining a local copy of the + latest &os; Documentation Set. + + + Using CVSup to Update the Documentation + + The sources and the installed copy of the &os; documentation + can be updated with CVSup, using a + mechanism similar to the one employed for the base system + sources (c.f. ). This section + describes: + + + + How to install the documentation toolchain, the tools + that are required to rebuild the &os; documentation from its + source. + + + + How to download a copy of the documentation source + at /usr/doc, + using CVSup. + + + + How to rebuild the &os; documentation from its source, + and install it + under /usr/share/doc. + + + + Some of the build options that are supported by the + build system of the documentation, i.e. the options that + build only some of the different language translations of + the documentation or the options that select a specific + output format. + + + + + + Installing CVSup and the Documentation Toolchain + + Rebuilding the &os; documentation from source requires a + fairly large collection of tools. These tools are not part of + the &os; base system, because they need a large amount of disk + space and they are not useful to all &os; users; they are only + useful to those users that are actively writing new + documentation for &os; or are frequently updating their + documentation from source. + + All the required tools are available as part of the Ports + Collection. The textproc/docproj port is a master + port that has been developed by the &os; Documentation Project, + to ease the initial installation and future updates of these + tools. + + + When no &postscript; or PDF documentation required, one + might consider installing the textproc/docproj-nojadetex port + instead. This version of the documentation toolchain includes + everything except the teTeX + typesetting engine. teTeX is a + very large collection of tools, so it may be quite sensible to + omit its installation if PDF output is not really + necessary. + + + For more information on installing and using + CVSup, see Using CVSup. + + + + Updating the Documentation Sources + + The CVSup utility can fetch a + clean copy of the documentation sources, using + the /usr/share/examples/cvsup/doc-supfile + file as a configuration template. The default update host is + set to a placeholder value in doc-supfile, + but &man.cvsup.1; accepts a host name through the command line, + so the documentation sources can be fetched from one of the + CVSup servers by typing: + + &prompt.root; cvsup -h cvsup.FreeBSD.org -g -L 2 /usr/share/examples/cvsup/doc-supfile + + Change cvsup.FreeBSD.org to the + nearest CVSup server. See for a complete listing of mirror + sites. + + The initial download of the documentation sources may take a + while. Let it run until it completes. + + Future updates of the documentation sources may be fetched + by running the same command. + The CVSup utility downloads and + copies only the updates since the last time it ran, so every run + of CVSup after the first complete run + should be pretty fast. + + After checking out the sources, an alternative way of + updating the documentation is supported by the + Makefile of the /usr/doc directory. By setting + SUP_UPDATE, SUPHOST and + DOCSUPFILE in the + /etc/make.conf file, it is possible to + run: + + &prompt.root; cd /usr/doc +&prompt.root; make update + + A typical set of these &man.make.1; options + for /etc/make.conf is: + + SUP_UPDATE= yes +SUPHOST?= cvsup.freebsd.org +DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile + + + Setting the SUPHOST + and DOCSUPFILE value + with ?= permits overriding them in the + command-line of make. This is the recommended way of adding + options to make.conf, to avoid having to + edit the file every time a different option value has to be + tested. + + + + + Tunable Options of the Documentation Sources + + The updating and build system of the &os; documentation + supports a few options that ease the process of updating only + parts of the documentation, or the build of specific + translations. These options can be set either as system-wide + options in the /etc/make.conf file, or as + command-line options passed to the &man.make.1; utility. + + The following options are some of these: + + + + DOC_LANG + + + The list of languages and encodings to build and + install, e.g. en_US.ISO8859-1 for the + English documentation only. + + + + + FORMATS + + + A single format or a list of output formats to be + built. Currently, html, + html-split, txt, + ps, pdf, + and rtf are supported. + + + + + SUPHOST + + + The hostname of the CVSup + server to use when updating. + + + + + For more make variables supported as system-wide options in + &os;, see &man.make.conf.5;. + + For more make variables supported by the build system of the + &os; documentation, please refer to + the &os; + Documentation Project Primer for New Contributors. + + + + Installing the &os; Documentation from Source + + When an up-to-date snapshot of the documentation sources has + been fetched in /usr/doc, + everything is ready for an update of the installed + documentation. + + A full update of all the languages defined in + the DOC_LANG makefile option may be done by + typing: + + &prompt.root; cd /usr/doc +&prompt.root; make install clean + + If make.conf has been set up with the + correct DOCSUPFILE, SUPHOST + and SUP_UPDATE options, the install step may + be combined with an update of the documentation sources by + typing: + + &prompt.root; cd /usr/doc +&prompt.root; make update install clean + + If an update of only a specific language is desired, + &man.make.1; can be invoked in a language specific subdirectory + of /usr/doc, i.e.: + + &prompt.root; cd /usr/doc/en_US.ISO8859-1 +&prompt.root; make update install clean + + The output formats that will be installed may be specified + by setting the FORMATS make variable, + i.e.: + + &prompt.root; cd /usr/doc +&prompt.root; make FORMATS='html html-split' install clean + + + + + + + + Pav + Lucistnik + Based on information provided by + + + + + Using Docsnap + + Updating and Upgrading + + + Docsnap + Updating and Upgrading + + + Docsnap is an &man.rsync.1; + repository for updating installed &os; Documentation in a + relatively easy and fast way. A + Docsnap server tracks + the documentation sources, and builds them in HTML format every + hour. The textproc/docproj + is unneeded with Docsnap as only + patches to the built documentation exist. + + The only requirement for using this technique is + the net/rsync port or + package. To add it, use the following command: + + &prompt.root; pkg_add -r rsync + + + Docsnap has been originally + developed for updating documentation installed + to /usr/share/doc, but + the following examples could be adapted for other directories + as well. For user directories, it does not require + root privileges. + + + To update the documentation set, issue the following + command: + + &prompt.root; rsync -rltvz docsnap.sk.FreeBSD.org::docsnap /usr/share/doc + + + There is only one Docsnap + server at the moment; + the docsnap.sk.FreeBSD.org shown + above. + + + Do not use the flag here as there + are some items installed + into /usr/share/doc + during make installworld, which would + accidentally be removed. To clean up, use this command + instead: + + &prompt.root; rsync -rltvz --delete docsnap.sk.FreeBSD.org::docsnap/??_??\.\* /usr/share/doc + + If a subset of documentation needs to be updated, for + example, the English documentation only, the following command + should be used: + + &prompt.root; rsync -rltvz docsnap.sk.FreeBSD.org::docsnap/en_US.ISO8859-1 /usr/share/doc + +]]> + + Tracking a Development Branch -CURRENT ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/ports/chapter.sgml#7 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -714,32 +714,12 @@ Portsnap Method Portsnap is an alternative system for - distributing the Ports Collection. It was first included in - &os; 6.0. On older systems, you can install it from ports-mgmt/portsnap package: - - &prompt.root; pkg_add -r portsnap - - Please refer to Using Portsnap + distributing the Ports Collection. + Please refer to Using Portsnap for a detailed description of all Portsnap features. - Since &os; 6.1-RELEASE and with recent versions - of the Portsnap port or package, you - can safely skip this step. The /usr/ports will be created - automatically at first use of the &man.portsnap.8; command. - With previous versions of - Portsnap, you will have to - create an empty directory /usr/ports if it does not - exists: - - &prompt.root; mkdir /usr/ports - - - Download a compressed snapshot of the Ports Collection into /var/db/portsnap. You can disconnect from the Internet after this step, if you wish. ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#26 (text+ko) ==== @@ -1,7 +1,7 @@ + &header; @@ -210,7 +210,7 @@ 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 relase expires. + older Normal release expires.
Extended
Selected releases (normally every second release plus the last ==== //depot/projects/docproj_nl/www/share/sgml/events.xml#12 (text+ko) ==== @@ -10,10 +10,36 @@ - $FreeBSD: www/share/sgml/events.xml,v 1.64 2008/12/29 11:11:56 murray Exp $ + $FreeBSD: www/share/sgml/events.xml,v 1.66 2009/01/06 13:45:10 danger Exp $ + + FOSDEM '09 + http://fosdem.org/2009/ + + 2009 + 2 + 7 + + + 2009 + 2 + 8 + + + Belgium + Brussels + ULB Campus Solbosh + + + FOSDEM '09 is a free and non-commercial event organized + by the community, for the community. Its goal is to provide Free + and Open Source developers a place to meet. Several &os; + developers will be present, including Kris Kennaway who will be + giving a talk about system performance. + + EuroBSDCon 2009 http://2009.eurobsdcon.org/ @@ -63,6 +89,40 @@ from commercial vendors. + + FreeBSD Kernel Internals: Intensive Evening Course + http://www.mckusick.com/courses/adveveclass.html + + 2009 + 3 + 18 + + + 2009 + 7 + 2 + + + USA + California + Berkeley + + + The + FreeBSD Kernel Internals: An Intensive Code Walkthrough + course provides an in depth study of the source code of the + FreeBSD 8-current kernel as of early March. This course is + aimed at users with a good understanding of the algorithms used + in the FreeBSD kernel that want to learn the details of their + implementation. The class will be held at the historic Hillside Club at 2286 + Cedar Street, Berkeley, CA 94709 just three blocks north of the + Berkeley campus once per week from 6:30PM to 10:00PM starting + Wednesday March 18th and finishing Thursday July 2nd. + + + AsiaBSDCon 2009 http://2009.asiabsdcon.org/ ==== //depot/projects/docproj_nl/www/share/sgml/navibar.ent#3 (text+ko) ==== @@ -1,4 +1,4 @@ - + Developers
  • Developer's Handbook
  • Porter's Handbook
    • -
  • CVS Repository
    • +
  • Source code repositories
  • Release Engineering
  • Platforms
  • Project Ideas