From owner-p4-projects@FreeBSD.ORG Sun Feb 26 12:14:50 2012 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 73FEE106566C; Sun, 26 Feb 2012 12:14:50 +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 3620A106564A for ; Sun, 26 Feb 2012 12:14:50 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from skunkworks.freebsd.org (skunkworks.freebsd.org [IPv6:2001:4f8:fff6::2d]) by mx1.freebsd.org (Postfix) with ESMTP id 221858FC13 for ; Sun, 26 Feb 2012 12:14:50 +0000 (UTC) Received: from skunkworks.freebsd.org (localhost [127.0.0.1]) by skunkworks.freebsd.org (8.14.4/8.14.4) with ESMTP id q1QCEnQs068027 for ; Sun, 26 Feb 2012 12:14:49 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id q1QCEniV068024 for perforce@freebsd.org; Sun, 26 Feb 2012 12:14:49 GMT (envelope-from rene@FreeBSD.org) Date: Sun, 26 Feb 2012 12:14:49 GMT Message-Id: <201202261214.q1QCEniV068024@skunkworks.freebsd.org> X-Authentication-Warning: skunkworks.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 206912 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: Sun, 26 Feb 2012 12:14:50 -0000 http://p4web.freebsd.org/@@206912?ac=10 Change 206912 by rene@rene_acer on 2012/02/26 12:14:46 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#49 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#127 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml#6 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml#32 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/mailing-lists.ent#30 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/geom/chapter.sgml#23 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mail/chapter.sgml#23 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.sgml#33 integrate .. //depot/projects/docproj_nl/www/share/sgml/commercial.isp.xml#29 integrate .. //depot/projects/docproj_nl/www/share/sgml/events2012.xml#5 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#49 (text+ko) ==== @@ -9,7 +9,7 @@ The &os; Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.310 2012/02/17 22:34:05 gjb Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.311 2012/02/24 14:10:05 gjb Exp $ 1999 @@ -2945,7 +2945,7 @@ This list is not intended as a place for code reviews or a - replacement for the &a.arch; or the &a.audit;. In fact + replacement for the &a.arch;. In fact using it as such hurts the FreeBSD Project as it gives a sense of a closed list where general decisions affecting all of the FreeBSD using community are made without being open. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#127 (text+ko) ==== @@ -1,4 +1,4 @@ - + @@ -36,62 +36,58 @@ Preparation - Use a disk with sufficient free space. You may need anything from - 200 MB to over 500 MB, depending on the method you choose. - This space will hold the SGML tools, a subset of the - CVS tree, temporary build space and the - installed web pages. + Use a disk with sufficient free space. You may need + anything from 200 MB to over 500 MB, depending on the + method you choose. This space will hold the SGML tools, a + subset of the CVS tree, temporary + build space and the installed web pages. - Make sure your documentation ports are up to date! When in - doubt, remove the old ports using &man.pkg.delete.1; command before - installing the port. For example, we currently depend on - jade-1.2 and if you have installed jade-1.1, please do: + Make sure your documentation ports are up to date! When + in doubt, remove the old ports using &man.pkg.delete.1; + command before installing the port. For example, we currently + depend on jade-1.2 and if you have installed jade-1.1, please + do: &prompt.root; pkg_delete jade-1.1 - There are two methods to get the files required for the website - build: + There are two methods to get the files required for the + website build: - Use csup to get a local copy of the files - from a CVSup server. This is the - easiest method, and does not require installation of additional - software. The supfile presented in the next section will always - checkout the latest version of the required files. This is - sufficient if you are simply rebuilding the website and do not - intend to commit any changes. - - - &man.csup.1; became part of the base system in - &os; 6.2-RELEASE. If you are using an earlier version of &os; - you will need to install net/csup - from the Ports Collection. - + Use csup to get a local copy of the + files from a CVSup server. This + is the easiest method, and does not require installation of + additional software. The supfile presented in the next + section will always checkout the latest version of the + required files. This is sufficient if you are simply + rebuilding the website and do not intend to commit any + changes. - Use cvsup in cvs mode to - create and maintain a local CVS - repository with the required files. This will require you to - install a program like - net/cvsup-without-gui, but it is - a more flexible method if you need to have quick access to different - revisions of the doc/www files, revision histories, or if you - intend to commit changes to the central &os; - CVS repository. + Use cvsup in cvs mode + to create and maintain a local + CVS repository with the required + files. This will require you to install a program like + net/cvsup-without-gui, + but it is a more flexible method if you need to have quick + access to different revisions of the doc/www files, revision + histories, or if you intend to commit changes to the central + &os; CVS repository. Simple Method: Using <command>csup</command> - The csup command is part of the base system and + csup is part of the base system and already used extensively by most people for updating the - Ports Collection. The following sample supfile can be used to - obtain a checkout of the files required for the website build: + Ports Collection. The following sample supfile can be + used to obtain a checkout of the files required for the + website build: # # This file checks out all collections required to rebuild @@ -119,26 +115,25 @@ ports-base - You should, of course, change the default host - entry to a CVSup mirror near your - location, and the default prefix entry to the - location where you intend to store the checked out files. Save this - file as e.g. - doc-www-supfile, and - then execute the following command: + You should, of course, change the default + host entry to a CVSup + mirror near your location, and the default + prefix entry to the location where you intend to + store the checked out files. Save this file as e.g. + doc-www-supfile, + and then execute the following command: &prompt.root; csup doc-www-supfile When this command finishes, you will find the directories - doc/, - www/ and - ports/ under the directory you - specified in default prefix - (doc/, www/ and ports/ under the directory you + specified in default prefix (/usr/build - in our example). We will use this same directory for the build - process itself, so it would be better to use a filesystem with - sufficient free space. + in our example). We will use this same directory for the + build process itself, so it would be better to use a + filesystem with sufficient free space. That's it! You can now proceed with the website build. @@ -146,32 +141,36 @@ Advanced Method: Maintaining a Local - <application>CVS</application> doc/www Repository + CVS doc/www + Repository - This method will give you more advanced options, but will require - you to install the - net/cvsup-without-gui port or + This method will give you more advanced options, but will + require you to install the + net/cvsup-without-gui port or package. - The net/cvsup-without-gui - port has a build dependency on - lang/ezm3, a Modula 3 - compiler. This compiler takes quite some time to build, and since - most people will not need it for anything else, it is perhaps best - to use a package to install CVSup. + The net/cvsup-without-gui port has + a build dependency on lang/ezm3, a Modula 3 + compiler. This compiler takes quite some time to build, + and since most people will not need it for anything else, it + is perhaps best to use a package to install + CVSup. The CVSup utility has a special cvs mode that allows the retrieval of the - ,v files that make up a CVS - repository. This function is not currently available in - csup. For detailed information on - CVSup, please read the CVSup introduction in the &os; Handbook. + ,v files that make up a + CVS repository. This function is + not currently available in csup. + For detailed information on CVSup, + please read the CVSup + introduction in the &os; Handbook. - The supfile shown below will fetch the cvs collections required - for the website build, and create a local + The supfile shown below will fetch the cvs collections + required for the website build, and create a local CVS repository: # @@ -201,31 +200,32 @@ cvsroot-ports cvsroot-doc - You should, of course, change the default host - entry to a CVSup mirror near your - location, and the default prefix entry to the - location where you intend to store the repository files. Save this - file as e.g. - doc-www-cvsfile, and - then execute the following command: + You should, of course, change the default + host entry to a CVSup + mirror near your location, and the default + prefix entry to the location where you intend to + store the repository files. Save this file as e.g. + doc-www-cvsfile, + and then execute the following command: &prompt.root; cvsup doc-www-cvsfile - It is also advisable to set the CVSROOT environment - variable in your shell's startup files. For example, use - the following entry in your ~/.cshrc file: + It is also advisable to set the CVSROOT + environment variable in your shell's startup files. For + example, use the following entry in + ~/.cshrc: setenv CVSROOT /usr/dcvs - If you set this variable, you may omit the - argument (shown below) when performing repository operations using - the cvs command. + If you set this variable, you may omit the + argument (shown below) when performing + repository operations using cvs. - Currently, you will need more than 400 MB of free space to - host the repository files. An additional 200 MB will be needed - for the temporary build space. Once the cvsup - command completes, you are ready to check out the files to your build - directory: + Currently, you will need more than 400 MB of free + space to host the repository files. An additional 200 MB + will be needed for the temporary build space. Once + cvsup completes, you are ready to check out + the files to your build directory: &prompt.root; mkdir /usr/build &prompt.root; cd /usr/build @@ -233,24 +233,26 @@ The above command is consistent with the way csup checks out the files from the - CVSup servers. When it completes, you - will have a build directory with similar contents to the one used in - the simple csup method. + CVSup servers. When it completes, + you will have a build directory with similar contents to the + one used in the simple csup + method. - You can continue to use the cvsup command - shown above, to update your local CVS - repository on a regular basis. After the initial somewhat lengthy - download, regular updates will only take a few minutes. + You can continue to use cvsup as shown + above, to update your local CVS + repository on a regular basis. After the initial somewhat + lengthy download, regular updates will only take a few + minutes. Build the Web Pages from Scratch - Having completed either of the two methods, you will be ready to - start the website build. In our example, the build directory is - /usr/build + Having completed either of the two methods, you will be + ready to start the website build. In our example, the build + directory is /usr/build and all the required files are already in place. @@ -261,10 +263,10 @@ - The website build starts from the - www/en directory by executing - the &man.make.1; all target, to create - the web pages. + The website build starts from the www/en directory by executing + the &man.make.1; all target, to + create the web pages. &prompt.root; cd www/en &prompt.root; make all @@ -277,18 +279,19 @@ - If you have moved out of the - en directory, change back to + If you have moved out of the en directory, change back to it. &prompt.root; cd /usr/build/www/en - Run the &man.make.1; install target, - setting the DESTDIR variable to the name of the - directory you want to install the files to. The actual files are - installed under $DESTDIR/data + Run the &man.make.1; install + target, setting the DESTDIR variable to + the name of the directory you want to install the files to. + The actual files are installed under $DESTDIR/data which should be configured as your web server's document root. @@ -296,11 +299,12 @@ - If you have previously installed the web pages into the same - directory the install process will not have deleted any old or - outdated pages. For example, if you build and install a new copy - of the site every day, this command will find and delete all - files that have not been updated in three days. + If you have previously installed the web pages into the + same directory the install process will not have deleted any + old or outdated pages. For example, if you build and + install a new copy of the site every day, this command will + find and delete all files that have not been updated in + three days. &prompt.root; find /usr/local/www 3 | xargs rm @@ -321,11 +325,12 @@ &prompt.root; CVSROOT=/usr/dcvs; export CVSROOT - CVSROOT is an environment variable. You must - set it on the command line or in your dot files - (e.g., ~/.profile). The exact syntax will - differ depending on your shell (the above example is for - bash and bash-like shells). + CVSROOT is an environment variable. + You must set it on the command line or in your dot files + (e.g., ~/.profile). The exact syntax + will differ depending on your shell (the above example is + for bash and bash-like + shells). @@ -334,15 +339,15 @@ If set and not empty, the makefiles will build and - install only the English documents. All translations will be - ignored. E.g.: + install only the English documents. All translations will + be ignored. E.g.: &prompt.root; make ENGLISH_ONLY=YES all install If you want to unset the variable - ENGLISH_ONLY and build all pages, including - translations, set the variable ENGLISH_ONLY - to an empty value: + ENGLISH_ONLY and build all pages, + including translations, set the variable + ENGLISH_ONLY to an empty value: &prompt.root; make ENGLISH_ONLY="" all install clean @@ -352,10 +357,13 @@ WEB_ONLY - If set and not empty, the Makefiles will build and install - only the HTML pages from the www directory. All documents from - the doc directory (Handbook, - FAQ, Tutorials) will be ignored. E.g.: + If set and not empty, the Makefiles will build and + install only the HTML pages from the www directory. All + documents from the doc + directory (Handbook, FAQ, Tutorials) will be ignored. + E.g.: &prompt.root; make WEB_ONLY=YES all install @@ -368,7 +376,8 @@ If set, the Makefiles will build and install only for the languages specified by this variable inside the www directory. All - other languages except English will be ignored. E.g.: + other languages except English will be ignored. + E.g.: &prompt.root; make WEB_LANG="el es hu nl" all install @@ -378,19 +387,21 @@ NOPORTSCVS - If set, the Makefiles will not checkout files from the ports - CVS repository. Instead, it will copy the files from - /usr/ports (or where the - variable PORTSBASE points to). + If set, the Makefiles will not checkout files from the + ports CVS repository. Instead, it will copy the files + from /usr/ports (or + where the variable PORTSBASE points + to). - WEB_ONLY, WEB_LANG, ENGLISH_ONLY and - NOPORTSCVS are make variables. You can set the - variables in /etc/make.conf, - Makefile.inc, as environment variables on the - command line, or in your dot files. + WEB_ONLY, WEB_LANG, + ENGLISH_ONLY and + NOPORTSCVS are make variables. You can set + the variables in /etc/make.conf, + Makefile.inc, as environment variables on + the command line, or in your dot files. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml#32 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -217,11 +217,6 @@ - &a.audit.name; - Source code audit project - - - &a.binup.name; Design and development of the binary update system @@ -516,11 +511,6 @@ - &a.testing.name; - FreeBSD Performance and Stability Tests - - - &a.tilera.name; Porting FreeBSD to the Tilera family of CPUs @@ -949,29 +939,6 @@ - &a.audit.name; - - - Source code audit project - - This is the mailing list for the FreeBSD source code - audit project. Although this was originally intended for - security-related changes, its charter has been expanded to - review any code changes. - - This list is very heavy on patches, and is probably of no - interest to the average FreeBSD user. Security discussions - not related to a particular code change are held on - freebsd-security. Conversely, all developers are encouraged - to send their patches here for review, especially if they - touch a part of the system where a bug may adversely affect - the integrity of the system. - - - - - - &a.binup.name; ==== //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/mailing-lists.ent#30 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -48,10 +48,6 @@ FreeBSD ATM networking mailing list"> freebsd-atm"> - -FreeBSD source code audit mailing list"> -freebsd-audit"> - FreeBSD binary update system mailing list"> freebsd-binup"> @@ -483,10 +479,6 @@ FreeBSD test mailing list"> freebsd-test"> - -FreeBSD performance and stability testing mailing list"> -freebsd-testing"> - FreeBSD threads mailing list"> freebsd-threads"> ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/geom/chapter.sgml#23 (text+ko) ==== @@ -1,7 +1,7 @@ + - $FreeBSD: www/share/sgml/commercial.isp.xml,v 1.72 2012/02/12 14:12:00 jkois Exp $ + $FreeBSD: www/share/sgml/commercial.isp.xml,v 1.73 2012/02/23 17:21:22 jkois Exp $ @@ -474,6 +474,22 @@ + + Vellance B.V. + http://www.vellance.com/ + + Vellance B.V. is a Dutch managed hosting provider located in + Amsterdam. Our core-business is delivering advanced Managed hosting platforms. + Vellance primarily works with FreeBSD (since the 90's), so it is + not a surprise our managed hosting platforms and Virtual + Enterprise Cloud environment is completely based on a FreeBSD + infrastructure. Next to Virtual Dedicated Servers we offer many + products like Private Cloud infrastructures, Media hosting, + datacentre facilities and hosting consultancy. + + + Seiretto - UK FreeBSD Web Hosting http://www.s4servers.com/ ==== //depot/projects/docproj_nl/www/share/sgml/events2012.xml#5 (text+ko) ==== @@ -10,7 +10,7 @@ - $FreeBSD: www/share/sgml/events2012.xml,v 1.4 2012/01/30 19:36:16 brueffer Exp $ + $FreeBSD: www/share/sgml/events2012.xml,v 1.5 2012/02/24 10:21:40 jkois Exp $ @@ -41,6 +41,37 @@ + + BSDDay.eu/2012 + http://bsdday.eu/2012 + + 2012 + 5 + 5 + + + 2012 + 5 + 5 + + + Austria + Vienna + UAS Technikum Wien + + This year Beastie joins Tux on his tour in Vienna in + May: another "DanuBSDCon" is coming to gather Central-European BSD + people to meet! The event features several BSD developers and + enthusiasts to tell about their work, communicate with their fellows + and reach their potential future partners. As usual, there are no + formalities, papers, registration or participation fee, however the + invited folks are encouraged to give a brief talk about their + favorite BSD-related topic. The goal is to motivate everybody, + especially university students to work with BSD + systems. + + + BSDCan 2012 http://www.bsdcan.org/