From owner-p4-projects@FreeBSD.ORG Sun Dec 18 17:35:53 2011 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id A8BA5106566B; Sun, 18 Dec 2011 17:35:53 +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 6A87D1065673 for ; Sun, 18 Dec 2011 17:35:53 +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 55FF78FC13 for ; Sun, 18 Dec 2011 17:35:53 +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 pBIHZrAH039105 for ; Sun, 18 Dec 2011 17:35:53 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id pBIHZpeg039102 for perforce@freebsd.org; Sun, 18 Dec 2011 17:35:51 GMT (envelope-from rene@FreeBSD.org) Date: Sun, 18 Dec 2011 17:35:51 GMT Message-Id: <201112181735.pBIHZpeg039102@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 203213 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, 18 Dec 2011 17:35:53 -0000 http://p4web.freebsd.org/@@203213?ac=10 Change 203213 by rene@rene_acer on 2011/12/18 17:35:08 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#115 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/hubs/article.sgml#6 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#42 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/Makefile#9 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.sgml#6 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#29 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#118 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/desktop/chapter.sgml#49 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/linuxemu/chapter.sgml#17 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.sgml#26 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/bsdinstall/bsdinstall-config-crashdump.png#1 branch .. //depot/projects/docproj_nl/share/images/books/handbook/bsdinstall/bsdinstall-final-modification-shell.png#1 branch .. //depot/projects/docproj_nl/share/images/books/handbook/bsdinstall/bsdinstall-finalconfiguration.png#3 integrate .. //depot/projects/docproj_nl/share/misc/docbook.css#6 integrate .. //depot/projects/docproj_nl/share/pgpkeys/marck.key#6 integrate .. //depot/projects/docproj_nl/share/sgml/freebsd-html.dsl#8 integrate .. //depot/projects/docproj_nl/share/sgml/freebsd41.dtd#2 integrate .. //depot/projects/docproj_nl/www/en/ipv6/index.sgml#3 integrate .. //depot/projects/docproj_nl/www/en/portmgr/qa.sgml#4 integrate .. //depot/projects/docproj_nl/www/nl/administration.sgml#36 integrate .. //depot/projects/docproj_nl/www/share/sgml/libcommon.xsl#10 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#115 (text+ko) ==== @@ -1,4 +1,4 @@ - + @@ -1900,6 +1900,27 @@ + + Enabling Crash Dumps + + bsdinstall will prompt if crash + dumps should be enabled on the target system. Enabling crash + dumps can be very useful in debugging issues with the system, so + users are encouraged to enable crash dumps whenever possible. + Select [ Yes ] to enable crash + dumps, or [ No ] to proceed + without crash dumps enabled. + +
+ Enabling Crash Dumps + + + + + +
+ + Add Users @@ -2100,16 +2121,28 @@ Handbook - Download and install the &os; Handbook (which is what you are reading now). - - - Shell - Open a shell to run commands - on the new system. - After any final configuration is complete, select Exit to leave the installation. +
+ Manual Configuration + + + + + + +
+ + bsdinstall will prompt if there + are any additional configuration that needs to be done before + rebooting into the new system. Select + [ Yes ] to exit to a shell + within the new system, or [ No ] + to proceed to the last step of the installation. +
Complete the Installation ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#29 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -2029,8 +2029,9 @@ (i.e. using boot -s from the loader prompt). Then run: - &prompt.root; adjkerntz -i + &prompt.root; mount -u / &prompt.root; mount -a -t ufs +&prompt.root; adjkerntz -i &prompt.root; mergemaster -p &prompt.root; cd /usr/src &prompt.root; make installworld ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#118 (text+ko) ==== @@ -1,7 +1,7 @@ - - Introduction + + Introduction - The FreeBSD ports collection is the way almost everyone - installs applications ("ports") on FreeBSD. Like everything - else about FreeBSD, it is primarily a volunteer effort. - It is important to keep this in mind when reading this - document. + The FreeBSD ports collection is the way almost everyone + installs applications ("ports") on FreeBSD. Like everything + else about FreeBSD, it is primarily a volunteer effort. + It is important to keep this in mind when reading this + document. - In FreeBSD, anyone may submit a new port, or volunteer - to maintain an existing port if it is unmaintained—you - do not need any special commit privileges to do so. + In FreeBSD, anyone may submit a new port, or volunteer + to maintain an existing port if it is unmaintained—you + do not need any special commit privileges to do so. - + - - Making a new port yourself + + Making a new port yourself - So, you are interested in making your own port or - upgrading an existing one? Great! + So, you are interested in making your own port or + upgrading an existing one? Great! - What follows are some guidelines for creating a new port for - FreeBSD. If you want to upgrade an existing port, you should - read this and then read . + What follows are some guidelines for creating a new port for + FreeBSD. If you want to upgrade an existing port, you should + read this and then read . - When this document is not sufficiently detailed, you should - refer to /usr/ports/Mk/bsd.port.mk, which - all port Makefiles include. Even if you do not hack Makefiles - daily, it is well commented, and you will still gain much - knowledge from it. Additionally, you may send specific questions - to the &a.ports;. + When this document is not sufficiently detailed, you should + refer to /usr/ports/Mk/bsd.port.mk, which + all port Makefiles include. Even if you do not hack Makefiles + daily, it is well commented, and you will still gain much + knowledge from it. Additionally, you may send specific questions + to the &a.ports;. - - Only a fraction of the variables - (VAR) that can be - overridden are mentioned in this document. Most (if not all) - are documented at the start of /usr/ports/Mk/bsd.port.mk; - the others probably ought to be. - Note that this file uses a non-standard tab setting: - Emacs and - Vim should recognize the setting on - loading the file. Both &man.vi.1; and - &man.ex.1; can be set to use the correct value by - typing :set tabstop=4 once the file has been - loaded. - + + Only a fraction of the variables + (VAR) that can be + overridden are mentioned in this document. Most (if not all) + are documented at the start of /usr/ports/Mk/bsd.port.mk; + the others probably ought to be. + Note that this file uses a non-standard tab setting: + Emacs and + Vim should recognize the setting on + loading the file. Both &man.vi.1; and + &man.ex.1; can be set to use the correct value by + typing :set tabstop=4 once the file has been + loaded. + - - Looking for something easy to start with? Take a look at the - list of - requested ports and see if you can work on one (or more). - - + + Looking for something easy to start with? Take a look at the + list of + requested ports and see if you can work on one (or more). + + - - Quick Porting + + Quick Porting - This section tells you how to quickly create a new port. In many cases, it - is not sufficient, so you will have to read further on into - the document. + This section tells you how to quickly create a new port. In many cases, it + is not sufficient, so you will have to read further on into + the document. - First, get the original tarball and put it into - DISTDIR, which defaults to - /usr/ports/distfiles. + First, get the original tarball and put it into + DISTDIR, which defaults to + /usr/ports/distfiles. - - The following assumes that the software compiled out-of-the-box, - i.e., there was absolutely no change required for the port to work - on your FreeBSD box. If you needed to change something, you will - have to refer to the next section too. - + + The following assumes that the software compiled out-of-the-box, + i.e., there was absolutely no change required for the port to work + on your FreeBSD box. If you needed to change something, you will + have to refer to the next section too. + - - Writing the <filename>Makefile</filename> + + Writing the <filename>Makefile</filename> - The minimal Makefile would look something - like this: + The minimal Makefile would look something + like this: - # New ports collection makefile for: oneko + # New ports collection makefile for: oneko # Date created: 5 December 1994 # Whom: asami # @@ -140,692 +140,692 @@ .include <bsd.port.mk> - See if you can figure it out. Do not worry about the contents - of the $FreeBSD$ line, it will be - filled in automatically by CVS when the port is imported to our main - ports tree. You can find a more detailed example in the sample Makefile section. - + See if you can figure it out. Do not worry about the contents + of the $FreeBSD$ line, it will be + filled in automatically by CVS when the port is imported to our main + ports tree. You can find a more detailed example in the sample Makefile section. + - - Writing the description files + + Writing the description files - There are two description files that are required for - any port, whether they actually package or not. They are - pkg-descr and - pkg-plist. Their - pkg- prefix distinguishes them from - other files. + There are two description files that are required for + any port, whether they actually package or not. They are + pkg-descr and + pkg-plist. Their + pkg- prefix distinguishes them from + other files. - - <filename>pkg-descr</filename> + + <filename>pkg-descr</filename> - This is a longer description of the port. One to a few - paragraphs concisely explaining what the port does is - sufficient. + This is a longer description of the port. One to a few + paragraphs concisely explaining what the port does is + sufficient. - - This is not a manual or an in-depth - description on how to use or compile the port! Please - be careful if you are copying from the - README or manpage; too often - they are not a concise description of the port or are in an - awkward format (e.g., manpages have justified spacing). If the - ported software has an official WWW homepage, you should list it - here. Prefix one of the websites with - WWW: so that automated tools will work - correctly. - + + This is not a manual or an in-depth + description on how to use or compile the port! Please + be careful if you are copying from the + README or manpage; too often + they are not a concise description of the port or are in an + awkward format (e.g., manpages have justified spacing). If the + ported software has an official WWW homepage, you should list it + here. Prefix one of the websites with + WWW: so that automated tools will work + correctly. + - The following example shows how your - pkg-descr should look: + The following example shows how your + pkg-descr should look: - This is a port of oneko, in which a cat chases a poor mouse all over + This is a port of oneko, in which a cat chases a poor mouse all over the screen. : (etc.) WWW: http://www.oneko.org/ - + - - <filename>pkg-plist</filename> + + <filename>pkg-plist</filename> - This file lists all the files installed by the port. It is - also called the packing list because the package is - generated by packing the files listed here. The pathnames are - relative to the installation prefix (usually - /usr/local or - /usr/X11R6). If you are using the - MANn variables (as - you should be), do not list any manpages here. If the port creates - directories during installation, make sure to add - @dirrm lines to remove them when the package is - deleted. + This file lists all the files installed by the port. It is + also called the packing list because the package is + generated by packing the files listed here. The pathnames are + relative to the installation prefix (usually + /usr/local or + /usr/X11R6). If you are using the + MANn variables (as + you should be), do not list any manpages here. If the port creates + directories during installation, make sure to add + @dirrm lines to remove them when the package is + deleted. - Here is a small example: + Here is a small example: - bin/oneko + bin/oneko lib/X11/app-defaults/Oneko lib/X11/oneko/cat1.xpm lib/X11/oneko/cat2.xpm lib/X11/oneko/mouse.xpm @dirrm lib/X11/oneko - Refer to the &man.pkg.create.1; manual page for details on the - packing list. + Refer to the &man.pkg.create.1; manual page for details on the + packing list. - - It is recommended that you keep all the filenames in this - file sorted alphabetically. It will make verifying the changes - when you upgrade the port much easier. - + + It is recommended that you keep all the filenames in this + file sorted alphabetically. It will make verifying the changes + when you upgrade the port much easier. + - - Creating a packing list manually can be a very tedious - task. If the port installs a large numbers of files, creating the packing list - automatically might save time. - + + Creating a packing list manually can be a very tedious + task. If the port installs a large numbers of files, creating the packing list + automatically might save time. + - There is only one case when pkg-plist - can be omitted from a port. If the port installs just a handful - of files, and perhaps directories, the files and directories may - be listed in the variables PLIST_FILES and - PLIST_DIRS, respectively, within the port's - Makefile. For instance, we could get along - without pkg-plist in the above - oneko port by adding the - following lines to the Makefile: + There is only one case when pkg-plist + can be omitted from a port. If the port installs just a handful + of files, and perhaps directories, the files and directories may + be listed in the variables PLIST_FILES and + PLIST_DIRS, respectively, within the port's + Makefile. For instance, we could get along + without pkg-plist in the above + oneko port by adding the + following lines to the Makefile: - PLIST_FILES= bin/oneko \ + PLIST_FILES= bin/oneko \ lib/X11/app-defaults/Oneko \ lib/X11/oneko/cat1.xpm \ lib/X11/oneko/cat2.xpm \ lib/X11/oneko/mouse.xpm PLIST_DIRS= lib/X11/oneko - Of course, PLIST_DIRS should be left - unset if a port installs no directories of its own. + Of course, PLIST_DIRS should be left + unset if a port installs no directories of its own. - The price for this way of listing port's files and - directories is that you cannot use command sequences - described in &man.pkg.create.1;. Therefore, it is suitable - only for simple ports and makes them even simpler. At the - same time, it has the advantage of reducing the number of files - in the ports collection. Please consider using this technique - before you resort to pkg-plist. + The price for this way of listing port's files and + directories is that you cannot use command sequences + described in &man.pkg.create.1;. Therefore, it is suitable + only for simple ports and makes them even simpler. At the + same time, it has the advantage of reducing the number of files + in the ports collection. Please consider using this technique + before you resort to pkg-plist. - Later we will see how pkg-plist - and PLIST_FILES can be used to fulfill - more sophisticated + Later we will see how pkg-plist + and PLIST_FILES can be used to fulfill + more sophisticated tasks. - - + + - - Creating the checksum file + + Creating the checksum file - Just type make makesum. The ports make rules - will automatically generate the file - distinfo. + Just type make makesum. The ports make rules + will automatically generate the file + distinfo. - If a file fetched has its checksum changed regularly and you are - certain the source is trusted (i.e. it comes from manufacturer CDs - or documentation generated daily), you should specify these files in - the IGNOREFILES variable. - Then the checksum is not calculated for that file when you run - make makesum, but set to - IGNORE. - + If a file fetched has its checksum changed regularly and you are + certain the source is trusted (i.e. it comes from manufacturer CDs + or documentation generated daily), you should specify these files in + the IGNOREFILES variable. + Then the checksum is not calculated for that file when you run + make makesum, but set to + IGNORE. + - - Testing the port + + Testing the port - You should make sure that the port rules do exactly what you - want them to do, including packaging up the port. These are the - important points you need to verify. + You should make sure that the port rules do exactly what you + want them to do, including packaging up the port. These are the + important points you need to verify. - - - pkg-plist does not contain anything not - installed by your port - + + + pkg-plist does not contain anything not + installed by your port + - - pkg-plist contains everything that is - installed by your port - + + pkg-plist contains everything that is + installed by your port + - - Your port can be installed multiple times using the - reinstall target - + + Your port can be installed multiple times using the + reinstall target + - - Your port cleans up - after itself upon deinstall - - + + Your port cleans up + after itself upon deinstall + + - - Recommended test ordering + + Recommended test ordering - - make install - + + make install + - - make package - + + make package + - - make deinstall - + + make deinstall + - - pkg_add package-name - - + + pkg_add package-name + + - - make deinstall - + + make deinstall + - - make reinstall - + + make reinstall + - - make package - - + + make package + + - Make sure that there are not any warnings issued in any of the - package and - deinstall stages. After step 3, check to - see if all the new directories are correctly deleted. Also, try - using the software after step 4, to ensure that it works correctly - when installed from a package. + Make sure that there are not any warnings issued in any of the + package and + deinstall stages. After step 3, check to + see if all the new directories are correctly deleted. Also, try + using the software after step 4, to ensure that it works correctly + when installed from a package. - The most thorough way to automate these steps is via - installing the ports tinderbox. - This maintains jails in which you can - test all of the above steps without changing the state of - your running system. Please see - ports/ports-mgmt/tinderbox for more - information. - + The most thorough way to automate these steps is via + installing the ports tinderbox. + This maintains jails in which you can + test all of the above steps without changing the state of + your running system. Please see + ports/ports-mgmt/tinderbox for more + information. + - - Checking your port with <command>portlint</command> + + Checking your port with <command>portlint</command> - Please use portlint to see if your port - conforms to our guidelines. The ports-mgmt/portlint - program is part of the ports collection. - In particular, you may want to check if the - Makefile is in the right - shape and the package is named - appropriately. - + Please use portlint to see if your port + conforms to our guidelines. The ports-mgmt/portlint + program is part of the ports collection. + In particular, you may want to check if the + Makefile is in the right + shape and the package is named + appropriately. + - - Submitting the new port + + Submitting the new port - Before you submit the new port, make sure you have read the DOs and DON'Ts section. + Before you submit the new port, make sure you have read the DOs and DON'Ts section. - Now that you are happy with your port, the only thing remaining - is to put it in the main &os; ports tree and make everybody else - happy about it too. We do not need your work - directory or the pkgname.tgz package, so delete - them now. Next, assuming your port is called oneko, - cd to the directory above where the - oneko directory is located, and then type the - following: shar `find oneko` > oneko.shar + Now that you are happy with your port, the only thing remaining + is to put it in the main &os; ports tree and make everybody else + happy about it too. We do not need your work + directory or the pkgname.tgz package, so delete + them now. Next, assuming your port is called oneko, + cd to the directory above where the + oneko directory is located, and then type the + following: shar `find oneko` > oneko.shar - Include your oneko.shar file in a bug report - and send it with the &man.send-pr.1; program (see - Bug - Reports and General Commentary for more information about - &man.send-pr.1;). Be sure to classify the bug report as category - ports and class - change-request (Do not mark the report - confidential!). - Also add a short description of the program you ported - to the Description field of the PR (e.g. - perhaps a short version of the COMMENT), and add - the shar file to the Fix field. + Include your oneko.shar file in a bug report + and send it with the &man.send-pr.1; program (see + Bug + Reports and General Commentary for more information about + &man.send-pr.1;). Be sure to classify the bug report as category + ports and class + change-request (Do not mark the report + confidential!). + Also add a short description of the program you ported + to the Description field of the PR (e.g. + perhaps a short version of the COMMENT), and add + the shar file to the Fix field. - - You can make our work a lot easier, if you use a good - description in the synopsis of the problem report. - We prefer something like - New port: <category>/<portname> - <short description of the port> for new ports. - If you stick to this scheme, the chance that someone will take a - look at your PR soon is much better. - + + You can make our work a lot easier, if you use a good + description in the synopsis of the problem report. + We prefer something like + New port: <category>/<portname> + <short description of the port> for new ports. + If you stick to this scheme, the chance that someone will take a + look at your PR soon is much better. + - One more time, do not include the original source - distfile, the work directory, or the package - you built with make package; - and, do use &man.shar.1; for new ports, not &man.diff.1;. - + One more time, do not include the original source + distfile, the work directory, or the package + you built with make package; + and, do use &man.shar.1; for new ports, not &man.diff.1;. + - After you have submitted your port, please be patient. - Sometimes it can take a few months before a port is included - in &os;, although it might only take a few days. You can - view the list of After you have submitted your port, please be patient. + Sometimes it can take a few months before a port is included + in &os;, although it might only take a few days. You can + view the list of ports PRs waiting to be committed to &os;. - Once we have looked at your port, we will get back to you if necessary, and put - it in the tree. Your name will also appear in the list of - Additional FreeBSD Contributors - and other files. Isn't that great?!? :-) - - + Once we have looked at your port, we will get back to you if necessary, and put + it in the tree. Your name will also appear in the list of + Additional FreeBSD Contributors + and other files. Isn't that great?!? :-) + + - - Slow Porting + + Slow Porting - Ok, so it was not that simple, and the port required some - modifications to get it to work. In this section, we will explain, - step by step, how to modify it to get it to work with the ports >>> TRUNCATED FOR MAIL (1000 lines) <<<