From owner-p4-projects@FreeBSD.ORG Sat Nov 1 21:17:05 2008 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 3306F1065679; Sat, 1 Nov 2008 21:17:05 +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 E97751065673 for ; Sat, 1 Nov 2008 21:17:04 +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 D56928FC12 for ; Sat, 1 Nov 2008 21:17:04 +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 mA1LH4xN032225 for ; Sat, 1 Nov 2008 21:17:04 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id mA1LH4F3032223 for perforce@freebsd.org; Sat, 1 Nov 2008 21:17:04 GMT (envelope-from rene@FreeBSD.org) Date: Sat, 1 Nov 2008 21:17:04 GMT Message-Id: <200811012117.mA1LH4F3032223@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 152329 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: Sat, 01 Nov 2008 21:17:05 -0000 http://perforce.freebsd.org/chv.cgi?CH=152329 Change 152329 by rene@rene_self on 2008/11/01 21:16:46 Oops, do two things at once: * IFC * Translate 'contributing' article up to 13% Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#11 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#10 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/articles/contributing/article.sgml#2 edit .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys-developers.sgml#8 integrate .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys.ent#8 integrate .. //depot/projects/docproj_nl/share/pgpkeys/versus.key#1 branch .. //depot/projects/docproj_nl/www/en/developers.sgml#8 integrate .. //depot/projects/docproj_nl/www/en/releases/6.4R/schedule.sgml#7 integrate .. //depot/projects/docproj_nl/www/en/releng/index.sgml#6 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#14 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#11 (text+ko) ==== @@ -1,4 +1,4 @@ - + @@ -65,8 +65,8 @@ like that, and our computers require some assistance before they can meaningfully process our text. - More precisely, they need help identifying what is what. You or I - can look at + More precisely, they need help identifying what is what. Let's + look at this text:
To remove /tmp/foo use &man.rm.1;. @@ -74,7 +74,7 @@ &prompt.user; rm /tmp/foo
- and easily see which parts are filenames, which are commands to be typed + It is easy to see which parts are filenames, which are commands to be typed in, which parts are references to manual pages, and so on. But the computer processing the document cannot. For this we need markup. @@ -204,15 +204,15 @@ For an element called element-name the start tag will normally look like - <element-name>. The + element-name. The corresponding closing tag for this element is - </element-name>. + /element-name. Using an element (start and end tags) HTML has an element for indicating that the content enclosed by - the element is a paragraph, called p. This + the element is a paragraph, called p. This element has both start and end tags. This is a paragraph. It starts with the start tag for @@ -231,7 +231,7 @@ Using an element (start tag only) HTML has an element for indicating a horizontal rule, called - hr. This element does not wrap content, so only + hr. This element does not wrap content, so only has a start tag. This is a paragraph.

@@ -266,10 +266,10 @@ end. When this document (or anyone else knowledgeable about SGML) refers - to the <p> tag they mean the literal text + to the p tag they mean the literal text consisting of the three characters <, p, and >. But the phrase - the <p> element refers to the whole + the p element refers to the whole element. This distinction is very subtle. But keep it @@ -287,7 +287,7 @@ attribute-name="attribute-value". In sufficiently recent versions of HTML, the p - element has an attribute called align, which suggests + element has an attribute called align, which suggests an alignment (justification) for the paragraph to the program displaying the HTML. @@ -494,7 +494,7 @@ 6 - The text of the error message. + The text of the message. @@ -519,7 +519,7 @@ - Put the title element back in. + Put the title element back in. @@ -781,7 +781,7 @@ Escaping back to SGML - Earlier in this primer I said that SGML is only used when writing a + As mentioned earlier, SGML is only used when writing a DTD. This is not strictly true. There is certain SGML syntax that you will want to be able to use within your documents. For example, comments can be included in your document, and will be ignored by the @@ -1379,7 +1379,7 @@ characters. RCDATA is for Entity references and - character data If the parser is in this content model then it + character data. If the parser is in this content model then it is expecting to see characters and entities. < loses its special status, but & will still be treated as @@ -1392,7 +1392,7 @@ < is converted to a &lt; and every & is converted to a &amp;, it can be - easier to mark the section as only containing CDATA. When the SGML + easier to mark the section as only containing CDATA. When the SGML parser encounters this it will ignore the < and & symbols embedded in the content. @@ -1534,7 +1534,7 @@ <body> <p>This paragraph <![ CDATA [contains many < characters (< < < < <) so it is easier - to wrap it in a CDATA marked section ]]></p> + to wrap it in a CDATA marked section.]]></p> <![ IGNORE [ <p>This paragraph will definitely not be included in the ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#5 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -623,7 +623,7 @@ - This is the basic set up for every + This is the basic setup for every crontab file, although there is one thing different about this one. Field number six, where we specified the username, only exists in the system ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#3 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -14,20 +14,24 @@ + Jordan Hubbard Original work by + Poul-Henning Kamp + John Polstra + Nik Clayton @@ -52,31 +56,48 @@ After reading this chapter, you will know: - The difference between the two development - branches: &os.stable; and &os.current;. + + The difference between the two development + branches: &os.stable; and &os.current;. - How to keep your system up to date with + + + How to keep your system up to date with CVSup, CVS, or CTM. - How to rebuild and reinstall the entire base - system with make buildworld (etc). + + + How to rebuild and reinstall the entire base + system with make buildworld (etc). - Before reading this chapter, you should: - Properly set up your network connection (). + + Properly set up your network connection (). + + + + Know how to install additional third-party + software (). - Know how to install additional third-party - software (). + + + Throughout this chapter, the cvsup command is + used to obtain and update &os; sources. To use it, you will need to + install a port or package like net/cvsup-without-gui. If you are using + &os; 6.2-RELEASE or later, you may wish to substitute this + with &man.csup.1;, which is now part of the base system. + - + &os.current; vs. &os.stable; -CURRENT @@ -95,7 +116,7 @@ &os.current; users are expected to have a high degree of technical skill, and should be capable of solving difficult system problems on their own. If you are new to &os;, think - twice before installing it. + twice before installing it. What Is &os.current;? @@ -184,31 +205,33 @@ Using &os.current; - + -CURRENT using - Join the &a.current.name; and the &a.cvsall.name; lists. This is not - just a good idea, it is essential. If - you are not on the &a.current.name; list, - you will not see the comments that people are - making about the current state of the system and thus will - probably end up stumbling over a lot of problems that others - have already found and solved. Even more importantly, you - will miss out on important bulletins which may be critical - to your system's continued health. + Join the &a.current.name; and the &a.svn-src-head.name; + lists. This is not just a good idea, it is + essential. If you are not on the + &a.current.name; list, you will not see + the comments that people are making about the current state of + the system and thus will probably end up stumbling over a lot + of problems that others have already found and solved. Even + more importantly, you will miss out on important bulletins + which may be critical to your system's continued health. - The &a.cvsall.name; list will allow you to see the - commit log entry for each change as it is made along with + The &a.svn-src-head.name; list will allow you to see the + commit log entry for each change as it is made, along with any pertinent information on possible side-effects. To join these lists, or one of the others available go to &a.mailman.lists.link; and click on the list that you wish to subscribe to. Instructions on the rest of - the procedure are available there. + the procedure are available there. If you are interested + in tracking changes for the whole source tree, we would + recommend subscribing to the &a.svn-src-all.name; list. @@ -216,47 +239,66 @@ site. You can do this in one of two ways: - - cvsup - - - cron - - - -CURRENT + + cvsup + + + cron + + + -CURRENT Syncing with CVSup Use the cvsup program - with the supfile named standard-supfile - available from /usr/share/examples/cvsup. - This is the most recommended - method, since it allows you to grab the entire - collection once and then only what has changed from then - on. Many people run cvsup from - cron and keep their - sources up-to-date automatically. You have to - customize the sample supfile above, and configure - cvsup for your environment. + with the supfile named + standard-supfile + available from + /usr/share/examples/cvsup. + This is the most recommended method, since it allows you to + grab the entire collection once and then only what has + changed from then on. Many people run + cvsup from cron and + keep their sources up-to-date automatically. You have to + customize the sample supfile above, + and configure cvsup for your environment. + + + The sample standard-supfile is + intended for tracking a specific security branch of + &os;, and not &os.current;. You will need to edit this + file and replace the following line: + + *default release=cvs tag=RELENG_X_Y + + With this one: + + *default release=cvs tag=. + + For a detailed explanation of usable tags, please + refer to the Handbook's CVS Tags section. + - - -CURRENT + + -CURRENT Syncing with CTM Use the CTM facility. If you + linkend="ctm">CTM facility. If you have very bad connectivity (high price connections or - only email access) CTM is an option. - However, it is a lot of hassle and can give you broken files. - This leads to it being rarely used, which again increases - the chance of it not working for fairly long periods of - time. We recommend using + only email access) CTM is an + option. However, it is a lot of hassle and can give you + broken files. This leads to it being rarely used, which + again increases the chance of it not working for fairly + long periods of time. We recommend using CVSup - for anybody with a 9600 bps modem or faster connection. - + for anybody with a 9600 bps modem or faster + connection. @@ -269,20 +311,21 @@ to compile just a subset is almost guaranteed to get you into trouble. - - -CURRENT - compiling - + + -CURRENT + compiling + Before compiling &os.current;, read the Makefile in /usr/src carefully. You should at least install a new kernel and rebuild the world the first time through + linkend="makeworld">install a new kernel and rebuild the + world the first time through as part of the upgrading process. Reading the &a.current; - and /usr/src/UPDATING will keep you up-to-date on other bootstrapping procedures - that sometimes become necessary as we move toward the next - release. + and /usr/src/UPDATING will keep you + up-to-date on other bootstrapping procedures that sometimes + become necessary as we move toward the next release. - + Be active! If you are running &os.current;, we want to know what you have to say about it, especially if you @@ -293,7 +336,7 @@ - + Staying Stable with &os; @@ -305,8 +348,8 @@ are made. Changes go into this branch at a different pace, and with the general assumption that they have first gone into &os.current; for testing. This is still - a development branch, however, and this means that at any given time, - the sources for &os.stable; may or may not be suitable for any + a development branch, however, and this means that at any given + time, the sources for &os.stable; may or may not be suitable for any particular purpose. It is simply another engineering development track, not a resource for end-users. @@ -315,23 +358,23 @@ Who Needs &os.stable;? If you are interested in tracking or contributing to the - FreeBSD development process, especially as it relates to the + FreeBSD development process, especially as it relates to the next point release of FreeBSD, then you should consider following &os.stable;. While it is true that security fixes also go into the &os.stable; branch, you do not need to - track &os.stable; to do this. Every security advisory for + track &os.stable; to do this. Every security advisory for FreeBSD explains how to fix the problem for the releases it affects That is not quite true. We can not continue to - support old releases of FreeBSD forever, although we do - support them for many years. For a complete description - of the current security policy for old releases of - FreeBSD, please see http://www.FreeBSD.org/security/. - - , and tracking an entire development branch just + support old releases of FreeBSD forever, although we do + support them for many years. For a complete description + of the current security policy for old releases of + FreeBSD, please see http://www.FreeBSD.org/security/. + , + and tracking an entire development branch just for security reasons is likely to bring in a lot of unwanted changes as well. @@ -355,38 +398,42 @@ Using &os.stable; - + -STABLE using - Join the &a.stable.name; list. This will keep you informed of - build-dependencies that may appear in &os.stable; - or any other issues requiring - special attention. Developers will also make announcements - in this mailing list when they are contemplating some - controversial fix or update, giving the users a chance to - respond if they have any issues to raise concerning the - proposed change. + Join the &a.stable.name; list. This will keep you informed + of build-dependencies that may appear in &os.stable; + or any other issues requiring special attention. Developers + will also make announcements in this mailing list when they are + contemplating some controversial fix or update, giving the + users a chance to respond if they have any issues to raise + concerning the proposed change. - The &a.cvsall.name; list will allow you to see the - commit log entry for each change as it is made along with - any pertinent information on possible side-effects. + Join the relevant SVN list for + the branch you are tracking. For example, if you are tracking + the 7-STABLE branch, join the &a.svn-src-stable-7.name; list. + This will allow you to view the commit log entry for each + change as it is made, along with any pertinent information on + possible side-effects. To join these lists, or one of the others available go to &a.mailman.lists.link; and click on the list that you wish to subscribe to. Instructions on the rest of - the procedure are available there. + the procedure are available there. If you are interested + in tracking changes for the whole source tree, we would + recommend subscribing to the &a.svn-src-all.name; list. If you are going to install a new system and want it to run monthly snapshot built from &os.stable;, please - check the - Snapshots web page for more information. - Alternatively, it is possible to + check the Snapshots web page for + more information. Alternatively, it is possible to install the most recent &os.stable; release from the mirror sites and follow the instructions below to upgrade your system to the @@ -405,39 +452,37 @@ cron - -STABLE + -STABLE syncing with CVSup Use the cvsup program - with the supfile named stable-supfile - from the directory - /usr/share/examples/cvsup. - This is the most recommended - method, since it allows you to grab the entire - collection once and then only what has changed from then - on. Many people run cvsup from - cron to keep their - sources up-to-date automatically. You have to + with the supfile named + stable-supfile from the directory + /usr/share/examples/cvsup. + This is the most recommended method, since it allows you to + grab the entire collection once and then only what has + changed from then on. Many people run + cvsup from cron to + keep their sources up-to-date automatically. You have to customize the sample supfile above, and configure cvsup for your environment. - -STABLE + -STABLE syncing with CTM Use the CTM facility. If + linkend="ctm">CTM facility. If you do not have a fast and inexpensive connection to the Internet, this is the method you should consider - using. - + using. - - + + Essentially, if you need rapid on-demand access to the @@ -454,11 +499,12 @@ Before compiling &os.stable;, read the Makefile in /usr/src carefully. You should at least install a new kernel and rebuild the world the first time through - as part of the upgrading process. Reading the &a.stable; and /usr/src/UPDATING will - keep you up-to-date on other bootstrapping procedures that - sometimes become necessary as we move toward the next - release. + linkend="makeworld">install a new kernel and rebuild the + world the first time through + as part of the upgrading process. Reading the &a.stable; and + /usr/src/UPDATING will keep you up-to-date + on other bootstrapping procedures that sometimes become + necessary as we move toward the next release. @@ -467,23 +513,23 @@ Synchronizing Your Source - + There are various ways of using an Internet (or email) connection to stay up-to-date with any given area of the &os; project sources, or all areas, depending on what interests you. The primary services we offer are Anonymous CVS, CVSup, and CTM. + linkend="ctm">CTM. While it is possible to update only parts of your source tree, - the only supported update procedure is to update the entire tree - and recompile both userland (i.e., all the programs that run in - user space, such as those in /bin and - /sbin) and kernel sources. Updating only part - of your source tree, only the kernel, or only userland will often - result in problems. These problems may range from compile errors - to kernel panics or data corruption. + the only supported update procedure is to update the entire tree + and recompile both userland (i.e., all the programs that run in + user space, such as those in /bin and + /sbin) and kernel sources. Updating only part + of your source tree, only the kernel, or only userland will often + result in problems. These problems may range from compile errors + to kernel panics or data corruption. @@ -494,7 +540,7 @@ Anonymous CVS and CVSup use the pull model of updating sources. In the case of - CVSup the user (or a + CVSup the user (or a cron script) invokes the cvsup program, and it interacts with a cvsupd server somewhere to bring your files @@ -504,12 +550,11 @@ of interest to you. Updates are generated on the fly by the server, according to what you have and what you want to have. Anonymous CVS is quite a bit more - simplistic than CVSup in that it is just an extension to - CVS which allows it to pull changes - directly from a remote CVS repository. + simplistic than CVSup in that it is just an + extension to CVS which allows it to pull + changes directly from a remote CVS repository. CVSup can do this far more efficiently, - but Anonymous CVS is easier to - use. + but Anonymous CVS is easier to use. CTM @@ -535,8 +580,10 @@ CTM will not do this, and if you wipe some portion of your source tree out (and do not have it backed up) then you will have to start from scratch (from the most recent CVS - base delta) and rebuild it all with CTM or, with - Anonymous CVS, simply delete the bad bits and resync. + base delta) and rebuild it all with + CTM or, with + Anonymous CVS, simply delete the bad bits + and resync. @@ -547,8 +594,7 @@ Once you have synchronized your local source tree against a particular version of &os; (&os.stable;, &os.current;, and so on) - you can then use the source - tree to rebuild the system. + you can then use the source tree to rebuild the system. Make a Backup @@ -561,9 +607,8 @@ source tree render your system unbootable. Make sure you have taken a backup. And have a fixit floppy or - bootable CD at - hand. You will probably never have to use it, but it is better to be - safe than sorry! + bootable CD at hand. You will probably never have to use it, but it + is better to be safe than sorry! @@ -581,15 +626,14 @@ file systems (or worse). If problems like these occur, a heads up is - posted to the appropriate mailing list, explaining the nature of + posted to the appropriate mailing list, explaining the nature of the problem and which systems it affects. And an all clear announcement is posted when the problem has been solved. If you try to track &os.stable; or &os.current; and do - not read the &a.stable; or the - &a.current; respectively, then you are - asking for trouble. + not read the &a.stable; or the &a.current; respectively, then you + are asking for trouble. @@ -611,10 +655,11 @@ necessary for your version of the sources and then use the following procedure: - &prompt.root; make buildworld + &prompt.root; cd /usr/src +&prompt.root; make buildworld &prompt.root; make buildkernel &prompt.root; make installkernel -&prompt.root; reboot +&prompt.root; shutdown -r now There are a few rare cases when an extra run of @@ -630,7 +675,9 @@ (i.e. using boot -s from the loader prompt). Then run: - &prompt.root; mergemaster -p + &prompt.root; mount -a -t ufs +&prompt.root; mergemaster -p +&prompt.root; cd /usr/src &prompt.root; make installworld &prompt.root; mergemaster &prompt.root; reboot @@ -658,8 +705,8 @@ Reading UPDATING is not an acceptable - substitute for subscribing to the correct mailing list, as described - previously. The two requirements are complementary, not + substitute for subscribing to the correct mailing list, as + described previously. The two requirements are complementary, not exclusive. @@ -667,12 +714,11 @@ Check <filename>/etc/make.conf</filename> - make.conf + make.conf Examine the files - /usr/share/examples/etc/make.conf - and + /usr/share/examples/etc/make.conf and /etc/make.conf. The first contains some default defines – most of which are commented out. To make use of them when you rebuild your system from source, add @@ -685,10 +731,9 @@ CFLAGS and NO_PROFILE lines found in /usr/share/examples/etc/make.conf - to - /etc/make.conf and uncomment them. + to /etc/make.conf and uncomment them. - Examine the other definitions (COPTFLAGS, + Examine the other definitions (COPTFLAGS, NOPORTDOCS and so on) and decide if they are relevant to you. @@ -706,15 +751,14 @@ /etc/group. There have been occasions when the installation part of - make installworld has expected certain usernames or groups - to exist. When performing an upgrade it is likely that these - users or groups did not exist. This caused problems when upgrading. - In some cases make buildworld will check to see if - these users or groups exist. + make installworld has expected certain usernames + or groups to exist. When performing an upgrade it is likely that + these users or groups did not exist. This caused problems when + upgrading. In some cases make buildworld will + check to see if these users or groups exist. - An example of this is when the - smmsp user was added. Users had the - installation process fail for them when + An example of this is when the smmsp user + was added. Users had the installation process fail for them when &man.mtree.8; was trying to create /var/spool/clientmqueue. @@ -757,9 +801,9 @@ multi-user mode Another method is to compile the system in multi-user mode, and - then drop into single user mode for the installation. If you would - like to do it this way, simply hold off on the following steps until - the build has completed. You can postpone dropping to single user + then drop into single user mode for the installation. If you would + like to do it this way, simply hold off on the following steps until + the build has completed. You can postpone dropping to single user mode until you have to installkernel or installworld. @@ -771,8 +815,8 @@ mode. Alternatively, reboot the system, and at the boot prompt, - select the single user option. The system will then boot - single user. At the shell prompt you should then run: + select the single user option. The system will then + boot single user. At the shell prompt you should then run: &prompt.root; fsck -p &prompt.root; mount -u / @@ -783,20 +827,18 @@ read/write, mounts all the other UFS file systems referenced in /etc/fstab and then turns swapping on. + + If your CMOS clock is set to local time and not to GMT + (this is true if the output of the &man.date.1; command + does not show the correct time and zone), + you may also need to run the following command: - - If your CMOS clock is set to local time and not to GMT - (this is true if the output of the &man.date.1; command - does not show the correct time and zone), - you may also need to run the following command: -&prompt.root; adjkerntz -i + &prompt.root; adjkerntz -i - This will make sure that your local time-zone settings - get set up correctly — without this, you may later run into some - problems. - - - + This will make sure that your local time-zone settings + get set up correctly — without this, you may later run + into some problems. + @@ -807,8 +849,8 @@ /usr/obj. The directories shadow those under /usr/src. - You can speed up the make buildworld process, and - possibly save yourself some dependency headaches by removing this + You can speed up the make buildworld process, + and possibly save yourself some dependency headaches by removing this directory as well. Some files below /usr/obj may have the @@ -839,9 +881,9 @@ when the process has finished. &prompt.root; script /var/tmp/mw.out -Script started, output file is /var/tmp/mw.out +Script started, output file is /var/tmp/mw.out &prompt.root; make TARGET -… compile, compile, compile … +… compile, compile, compile … &prompt.root; exit Script done, … @@ -865,9 +907,9 @@ make To rebuild the world you use the &man.make.1; command. This - command reads instructions from the Makefile, - which describes how the programs that comprise &os; should be - rebuilt, the order in which they should be built, and so on. + command reads instructions from the Makefile, + which describes how the programs that comprise &os; should be + rebuilt, the order in which they should be built, and so on. The general format of the command line you will type is as follows: @@ -891,7 +933,7 @@ is another way of specifying that profiled libraries should not be built, and corresponds with the - NO_PROFILE= true # Avoid compiling profiled libraries + NO_PROFILE= true # Avoid compiling profiled libraries line in /etc/make.conf. @@ -907,8 +949,8 @@ sub-steps. Most of the time you will not need to pass any parameters to - &man.make.1;, and so your command like will look like - this: + &man.make.1;, and so your command like will look like + this: &prompt.root; make target @@ -918,26 +960,27 @@ As the names imply, buildworld builds a complete new tree under /usr/obj, - and installworld, another target, installs this tree on - the current machine. + and installworld, another target, + installs this tree on the current machine. - Having separate options is very useful for two reasons. First, it allows you - to do the build safe in the knowledge that no components of - your running system will be affected. The build is + Having separate options is very useful for two reasons. First, + it allows you to do the build safe in the knowledge that no + components of your running system will be affected. The build is self hosted. Because of this, you can safely run buildworld on a machine running in multi-user mode with no fear of ill-effects. It is still - recommended that you run the - installworld part in single user - mode, though. + recommended that you run the installworld + part in single user mode, though. - Secondly, it allows you to use NFS mounts to upgrade + Secondly, it allows you to use NFS mounts to upgrade >>> TRUNCATED FOR MAIL (1000 lines) <<<