Date: Wed, 7 Jan 2009 19:10:05 GMT From: Rene Ladan <rene@FreeBSD.org> To: Perforce Change Reviews <perforce@FreeBSD.org> Subject: PERFORCE change 155769 for review Message-ID: <200901071910.n07JA5bk057731@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
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 @@ <corpauthor>The &os; Ports Management Team</corpauthor> </authorgroup> - <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.35 2008/09/20 18:47:41 linimon Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.36 2009/01/07 09:34:58 pav Exp $</pubdate> <copyright> <year>2003</year> @@ -491,7 +491,8 @@ <listitem> <para><literal>build portsupdate <replaceable>arch</replaceable> - <replaceable>branch</replaceable></literal> - Replaces the ports + <replaceable>branch</replaceable> + <replaceable>buildid</replaceable></literal> - Replaces the ports tree with a new ZFS snapshot. Don't forget to use <literal>-noports</literal> flag to <command>dopackages</command> later! ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#14 (text+ko) ==== @@ -12,7 +12,7 @@ <corpauthor>The &os; Documentation Project</corpauthor> - <pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1106 2009/01/05 15:44:57 remko Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1107 2009/01/07 09:49:12 pgj Exp $</pubdate> <copyright> <year>1995</year> @@ -4590,6 +4590,46 @@ </qandaentry> <qandaentry> + <question id="ports-major-upgrade"> + <para>Do I need to recompile every port each time I perform a + major version update?</para> + </question> + + <answer> + <para>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.</para> + + <para>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.</para> + + <para>For more information, see <ulink + url="&url.books.handbook;/updating-upgrading-freebsdupdate.html#FREEBSDUPDATE-UPGRADE">the section on upgrades</ulink> + in the &os; Handbook.</para> + </answer> + </qandaentry> + + <qandaentry> + <question id="ports-minor-upgrade"> + <para>Do I need to recompile every port each time I perform a + minor version update?</para> + </question> + + <answer> + <para>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.</para> + </answer> + </qandaentry> + + <qandaentry> <question id="minimal-sh"> <para>Why is <command>/bin/sh</command> so minimal? Why does &os; not use <command>bash</command> or another ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#9 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.235 2009/01/02 16:25:57 manolis Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.236 2009/01/07 09:18:54 pgj Exp $ --> <chapter id="updating-upgrading"> @@ -79,6 +79,12 @@ </listitem> <listitem> + <para>How to keep your documentation up to date with + <application>CVSup</application><!-- and + <application>Docsnap</application>-->.</para> + </listitem> + + <listitem> <para>The difference between the two development branches: &os.stable; and &os.current;.</para> </listitem> @@ -698,6 +704,327 @@ <screen>&prompt.root; <userinput>portsnap fetch update</userinput></screen> </sect1> + <sect1 id="updating-upgrading-documentation"> + <title>Updating the Documentation Set</title> + + <indexterm><primary>Updating and Upgrading</primary></indexterm> + + <indexterm> + <primary>Documentation</primary> + <see>Updating and Upgrading</see> + </indexterm> + + <para>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 <ulink + url="http://www.freebsd.org/doc/">&os; web site</ulink>, 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.</para> + + <sect2 id="csup-doc"> + <title>Using CVSup to Update the Documentation</title> + + <para>The sources and the installed copy of the &os; documentation + can be updated with <application>CVSup</application>, using a + mechanism similar to the one employed for the base system + sources (c.f. <xref linkend="makeworld">). This section + describes:</para> + + <itemizedlist> + <listitem> + <para>How to install the documentation toolchain, the tools + that are required to rebuild the &os; documentation from its + source.</para> + </listitem> + + <listitem> + <para>How to download a copy of the documentation source + at <filename class="directory">/usr/doc</filename>, + using <application>CVSup</application>.</para> + </listitem> + + <listitem> + <para>How to rebuild the &os; documentation from its source, + and install it + under <filename class="directory">/usr/share/doc</filename>.</para> + </listitem> + + <listitem> + <para>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.</para> + </listitem> + </itemizedlist> + </sect2> + + <sect2 id="installing-documentation-toolchain"> + <title>Installing CVSup and the Documentation Toolchain</title> + + <para>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.</para> + + <para>All the required tools are available as part of the Ports + Collection. The <filename + role="package">textproc/docproj</filename> 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.</para> + + <note> + <para>When no &postscript; or PDF documentation required, one + might consider installing the <filename + role="package">textproc/docproj-nojadetex</filename> port + instead. This version of the documentation toolchain includes + everything except the <application>teTeX</application> + typesetting engine. <application>teTeX</application> is a + very large collection of tools, so it may be quite sensible to + omit its installation if PDF output is not really + necessary.</para> + </note> + + <para>For more information on installing and using + <application>CVSup</application>, see <link + linkend="cvsup">Using CVSup</link>.</para> + </sect2> + + <sect2 id="updating-documentation-sources"> + <title>Updating the Documentation Sources</title> + + <para>The <application>CVSup</application> utility can fetch a + clean copy of the documentation sources, using + the <filename>/usr/share/examples/cvsup/doc-supfile</filename> + file as a configuration template. The default update host is + set to a placeholder value in <filename>doc-supfile</filename>, + but &man.cvsup.1; accepts a host name through the command line, + so the documentation sources can be fetched from one of the + <application>CVSup</application> servers by typing:</para> + + <screen>&prompt.root; <userinput>cvsup -h <replaceable>cvsup.FreeBSD.org</replaceable> -g -L 2 <filename>/usr/share/examples/cvsup/doc-supfile</filename></userinput></screen> + + <para>Change <replaceable>cvsup.FreeBSD.org</replaceable> to the + nearest <application>CVSup</application> server. See <xref + linkend="cvsup-mirrors"> for a complete listing of mirror + sites.</para> + + <para>The initial download of the documentation sources may take a + while. Let it run until it completes.</para> + + <para>Future updates of the documentation sources may be fetched + by running the same command. + The <application>CVSup</application> utility downloads and + copies only the updates since the last time it ran, so every run + of <application>CVSup</application> after the first complete run + should be pretty fast.</para> + + <para>After checking out the sources, an alternative way of + updating the documentation is supported by the + <filename>Makefile</filename> of the <filename + class="directory">/usr/doc</filename> directory. By setting + <makevar>SUP_UPDATE</makevar>, <makevar>SUPHOST</makevar> and + <makevar>DOCSUPFILE</makevar> in the + <filename>/etc/make.conf</filename> file, it is possible to + run:</para> + + <screen>&prompt.root; <userinput>cd /usr/doc</userinput> +&prompt.root; <userinput>make update</userinput></screen> + + <para>A typical set of these &man.make.1; options + for <filename>/etc/make.conf</filename> is:</para> + + <programlisting>SUP_UPDATE= yes +SUPHOST?= cvsup.freebsd.org +DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting> + + <note> + <para>Setting the <makevar>SUPHOST</makevar> + and <makevar>DOCSUPFILE</makevar> value + with <literal>?=</literal> permits overriding them in the + command-line of make. This is the recommended way of adding + options to <filename>make.conf</filename>, to avoid having to + edit the file every time a different option value has to be + tested.</para> + </note> + </sect2> + + <sect2 id="updating-documentation-options"> + <title>Tunable Options of the Documentation Sources</title> + + <para>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 <filename>/etc/make.conf</filename> file, or as + command-line options passed to the &man.make.1; utility.</para> + + <para>The following options are some of these:</para> + + <variablelist> + <varlistentry> + <term><makevar>DOC_LANG</makevar></term> + + <listitem> + <para>The list of languages and encodings to build and + install, e.g. <literal>en_US.ISO8859-1</literal> for the + English documentation only.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><makevar>FORMATS</makevar></term> + + <listitem> + <para>A single format or a list of output formats to be + built. Currently, <literal>html</literal>, + <literal>html-split</literal>, <literal>txt</literal>, + <literal>ps</literal>, <literal>pdf</literal>, + and <literal>rtf</literal> are supported.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><makevar>SUPHOST</makevar></term> + + <listitem> + <para>The hostname of the <application>CVSup</application> + server to use when updating.</para> + </listitem> + </varlistentry> + </variablelist> + + <para>For more make variables supported as system-wide options in + &os;, see &man.make.conf.5;.</para> + + <para>For more make variables supported by the build system of the + &os; documentation, please refer to + the <ulink url="&url.doc.langbase;/books/fdp-primer">&os; + Documentation Project Primer for New Contributors</ulink>.</para> + </sect2> + + <sect2 id="updating-installed-documentation"> + <title>Installing the &os; Documentation from Source</title> + + <para>When an up-to-date snapshot of the documentation sources has + been fetched in <filename class="directory">/usr/doc</filename>, + everything is ready for an update of the installed + documentation.</para> + + <para>A full update of all the languages defined in + the <makevar>DOC_LANG</makevar> makefile option may be done by + typing:</para> + + <screen>&prompt.root; <userinput>cd /usr/doc</userinput> +&prompt.root; <userinput>make install clean</userinput></screen> + + <para>If <filename>make.conf</filename> has been set up with the + correct <makevar>DOCSUPFILE</makevar>, <makevar>SUPHOST</makevar> + and <makevar>SUP_UPDATE</makevar> options, the install step may + be combined with an update of the documentation sources by + typing:</para> + + <screen>&prompt.root; <userinput>cd /usr/doc</userinput> +&prompt.root; <userinput>make update install clean</userinput></screen> + + <para>If an update of only a specific language is desired, + &man.make.1; can be invoked in a language specific subdirectory + of <filename class="directory">/usr/doc</filename>, i.e.:</para> + + <screen>&prompt.root; <userinput>cd /usr/doc/en_US.ISO8859-1</userinput> +&prompt.root; <userinput>make update install clean</userinput></screen> + + <para>The output formats that will be installed may be specified + by setting the <makevar>FORMATS</makevar> make variable, + i.e.:</para> + + <screen>&prompt.root; <userinput>cd /usr/doc</userinput> +&prompt.root; <userinput>make FORMATS='html html-split' install clean</userinput></screen> + </sect2> + +<!-- FIXME: Waiting for a working docsnap server... --> +<![ IGNORE [ + <sect2 id="docsnap"> + <sect2info> + <authorgroup> + <author> + <firstname>Pav</firstname> + <surname>Lucistnik</surname> + <contrib>Based on information provided by </contrib> + </author> + </authorgroup> + </sect2info> + + <title>Using Docsnap</title> + + <indexterm><primary>Updating and Upgrading</primary></indexterm> + + <indexterm> + <primary>Docsnap</primary> + <see>Updating and Upgrading</see> + </indexterm> + + <para><application>Docsnap</application> is an &man.rsync.1; + repository for updating installed &os; Documentation in a + relatively easy and fast way. A + <quote><application>Docsnap</application> server</quote> tracks + the documentation sources, and builds them in HTML format every + hour. The <filename role="package">textproc/docproj</filename> + is unneeded with <application>Docsnap</application> as only + patches to the built documentation exist.</para> + + <para>The only requirement for using this technique is + the <filename role="package">net/rsync</filename> port or + package. To add it, use the following command:</para> + + <screen>&prompt.root; <userinput>pkg_add -r rsync</userinput></screen> + + <note> + <para><application>Docsnap</application> has been originally + developed for updating documentation installed + to <filename class="directory">/usr/share/doc</filename>, but + the following examples could be adapted for other directories + as well. For user directories, it does not require + <username>root</username> privileges.</para> + </note> + + <para>To update the documentation set, issue the following + command:</para> + + <screen>&prompt.root; <userinput>rsync -rltvz <replaceable>docsnap.sk.FreeBSD.org</replaceable>::docsnap <replaceable>/usr/share/doc</replaceable></userinput></screen> + + <note> + <para>There is only one <application>Docsnap</application> + server at the moment; + the <hostid>docsnap.sk.FreeBSD.org</hostid> shown + above.</para> + </note> + + <para>Do not use the <option>--delete</option> flag here as there + are some items installed + into <filename class="directory">/usr/share/doc</filename> + during <command>make installworld</command>, which would + accidentally be removed. To clean up, use this command + instead:</para> + + <screen>&prompt.root; <userinput>rsync -rltvz --delete <replaceable>docsnap.sk.FreeBSD.org</replaceable>::docsnap/??_??\.\* <replaceable>/usr/share/doc</replaceable></userinput></screen> + + <para>If a subset of documentation needs to be updated, for + example, the English documentation only, the following command + should be used:</para> + + <screen>&prompt.root; <userinput>rsync -rltvz <replaceable>docsnap.sk.FreeBSD.org</replaceable>::docsnap/en_US.ISO8859-1 <replaceable>/usr/share/doc</replaceable></userinput></screen> + </sect2> +]]> + </sect1> + <sect1 id="current-stable"> <title>Tracking a Development Branch</title> <indexterm><primary>-CURRENT</primary></indexterm> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/ports/chapter.sgml#7 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml,v 1.286 2008/12/23 18:59:03 trhodes Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml,v 1.287 2009/01/07 15:25:46 pav Exp $ --> <chapter id="ports"> @@ -714,32 +714,12 @@ <title>Portsnap Method</title> <para><application>Portsnap</application> 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 <filename - role="package">ports-mgmt/portsnap</filename> package:</para> - - <screen>&prompt.root; <userinput>pkg_add -r portsnap</userinput></screen> - - <para>Please refer to <link linkend="updating-upgrading-portsnap">Using Portsnap</link> + distributing the Ports Collection. + Please refer to <link linkend="updating-upgrading-portsnap">Using Portsnap</link> for a detailed description of all <application>Portsnap</application> features.</para> <step> - <para>Since &os; 6.1-RELEASE and with recent versions - of the <application>Portsnap</application> port or package, you - can safely skip this step. The <filename - class="directory">/usr/ports</filename> will be created - automatically at first use of the &man.portsnap.8; command. - With previous versions of - <application>Portsnap</application>, you will have to - create an empty directory <filename - class="directory">/usr/ports</filename> if it does not - exists:</para> - - <screen>&prompt.root; <userinput>mkdir /usr/ports</userinput></screen> - </step> - - <step> <para>Download a compressed snapshot of the Ports Collection into <filename class="directory">/var/db/portsnap</filename>. You can disconnect from the Internet after this step, if you wish.</para> ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#26 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Dutch Documentation Project - $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.9 2008/12/23 23:07:32 rene Exp $ + $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.10 2009/01/06 22:10:38 rene Exp $ %SOURCE% en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml %SRCID% 1.420 ==== //depot/projects/docproj_nl/www/en/developers/cvs.sgml#3 (text+ko) ==== @@ -1,13 +1,15 @@ <!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ <!ENTITY base CDATA ".."> -<!ENTITY date "$FreeBSD: www/en/developers/cvs.sgml,v 1.9 2008/07/24 07:55:40 pav Exp $"> -<!ENTITY title "CVS Repository"> +<!ENTITY date "$FreeBSD: www/en/developers/cvs.sgml,v 1.10 2009/01/07 14:52:31 pav Exp $"> +<!ENTITY title "Source code repositories"> <!ENTITY % navinclude.developers "INCLUDE"> ]> <html> &header; + <h2>CVS</h2> + <p><a href="http://www.FreeBSD.org/cgi/man.cgi?cvs">CVS</a>; (the Concurrent Version System) is the tool we use for keeping our sources under control. Every change (with accompanying log message explaining @@ -43,6 +45,14 @@ <a href="http://cvsweb.FreeBSD.org/">USA/California</a>; and <a href="http://www.FreeBSD.org.ua/cgi/cvsweb.cgi?cvsroot=freebsd">Ukraine</a>.</p>; + <h2>Subversion</h2> + + <p>In June 2008, development of the base system moved to a different + version control system, <a href="http://subversion.tigris.org/">Subversion</a>; + (SVN for short). The <a href="http://svn.freebsd.org/viewvc/base/">web + interface</a> is available for browsing the repository. All changes are + also exported back to the CVS repository.</p> + &footer; </body> ==== //depot/projects/docproj_nl/www/en/releases/7.1R/announce.sgml#3 (text+ko) ==== @@ -1,6 +1,6 @@ <!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ <!ENTITY base CDATA "../.."> -<!ENTITY date "$FreeBSD: www/en/releases/7.1R/announce.sgml,v 1.2 2009/01/05 04:08:29 hrs Exp $"> +<!ENTITY date "$FreeBSD: www/en/releases/7.1R/announce.sgml,v 1.3 2009/01/07 13:35:09 danger Exp $"> <!ENTITY title "FreeBSD 7.1-RELEASE Announcement"> <!ENTITY % navinclude.download "INCLUDE"> ]> @@ -231,7 +231,7 @@ <h2>Acknowledgments</h2> - <p>Many companiews donated equipment, network access, or man-hours + <p>Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 7.1 including The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!, Network Appliances, and Sentex ==== //depot/projects/docproj_nl/www/en/releng/index.sgml#12 (text+ko) ==== @@ -1,6 +1,6 @@ <!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ <!ENTITY base CDATA ".."> -<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.248 2009/01/05 06:54:04 delphij Exp $"> +<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.249 2009/01/06 07:15:16 blackend Exp $"> <!ENTITY email 're'> <!ENTITY title "Release Engineering Information"> <!ENTITY % navinclude.developers "INCLUDE"> @@ -100,9 +100,8 @@ <tr> <td><tt>RELENG_7_1</tt></td> <td>Frozen</td> - <td>&contact.re;</td> - <td>A branch for FreeBSD 7.1 release candidate - (to be the FreeBSD 7.1 supported errata fix branch).</td> + <td>&contact.so;</td> + <td>FreeBSD 7.1 supported errata fix branch.</td> </tr> <tr> ==== //depot/projects/docproj_nl/www/en/security/security.sgml#5 (text+ko) ==== @@ -1,12 +1,12 @@ <!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ <!ENTITY base CDATA ".."> -<!ENTITY date "$FreeBSD: www/en/security/security.sgml,v 1.204 2009/01/05 20:52:36 cperciva Exp $"> +<!ENTITY date "$FreeBSD: www/en/security/security.sgml,v 1.205 2009/01/06 01:22:08 cperciva Exp $"> <!ENTITY title "FreeBSD Security Information"> <!ENTITY % navinclude.support "INCLUDE"> <!ENTITY % developers SYSTEM "../developers.sgml"> %developers; <!ENTITY advisories.html.inc SYSTEM "advisories.html.inc"> ]> -<!-- $FreeBSD: www/en/security/security.sgml,v 1.204 2009/01/05 20:52:36 cperciva Exp $ --> +<!-- $FreeBSD: www/en/security/security.sgml,v 1.205 2009/01/06 01:22:08 cperciva Exp $ --> <html> &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. </dd> <dt>Extended</dt> <dd>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 @@ <events> <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> <cvs:keyword name="freebsd"> - $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 $ </cvs:keyword> </cvs:keywords> + <event id="fosdem-2009"> + <name>FOSDEM '09</name> + <url>http://fosdem.org/2009/</url>; + <startdate> + <year>2009</year> + <month>2</month> + <day>7</day> + </startdate> + <enddate> + <year>2009</year> + <month>2</month> + <day>8</day> + </enddate> + <location> + <country code="BE">Belgium</country> + <city>Brussels</city> + <site>ULB Campus Solbosh</site> + </location> + + <description>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.</description> + </event> + <event id="eurobsdcon-2009"> <name>EuroBSDCon 2009</name> <url>http://2009.eurobsdcon.org/</url>; @@ -63,6 +89,40 @@ from commercial vendors.</description> </event> + <event id="mckusick-adv-spring-2009"> + <name>FreeBSD Kernel Internals: Intensive Evening Course</name> + <url>http://www.mckusick.com/courses/adveveclass.html</url>; + <startdate> + <year>2009</year> + <month>3</month> + <day>18</day> + </startdate> + <enddate> + <year>2009</year> + <month>7</month> + <day>2</day> + </enddate> + <location> + <country code="US">USA</country> + <state>California</state> + <city>Berkeley</city> + </location> + + <description>The <a + href="https://www.mckusick.com/courses/advclassform.html">; + FreeBSD Kernel Internals: An Intensive Code Walkthrough</a> + 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 <a + href="http://www.hillsideclub.org/">; Hillside Club</a> 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.</description> + </event> + + <event id="asiabsdcon-2009"> <name>AsiaBSDCon 2009</name> <url>http://2009.asiabsdcon.org/</url>; ==== //depot/projects/docproj_nl/www/share/sgml/navibar.ent#3 (text+ko) ==== @@ -1,4 +1,4 @@ -<!-- $FreeBSD: www/share/sgml/navibar.ent,v 1.23 2008/11/24 11:22:27 miwi Exp $ --> +<!-- $FreeBSD: www/share/sgml/navibar.ent,v 1.24 2009/01/07 14:52:50 pav Exp $ --> <!ENTITY % navinclude.about "IGNORE"> <![ %navinclude.about; [ @@ -56,7 +56,7 @@ <li><a href="&base;/projects/index.html">Developers</a></li> <li><a href="&base;/doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a></li> <li><a href="&base;/doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a></li> - <li><a href="&base;/developers/cvs.html">CVS Repository</a></li> + <li><a href="&base;/developers/cvs.html">Source code repositories</a></li> <li><a href="&base;/releng/index.html">Release Engineering</a></li> <li><a href="&base;/platforms/">Platforms</a></li> <li><a href="&base;/projects/ideas/">Project Ideas</a></li>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200901071910.n07JA5bk057731>