From owner-svn-doc-projects@FreeBSD.ORG Thu Nov 15 13:37:21 2012 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6B72B7F9; Thu, 15 Nov 2012 13:37:21 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 4E3AC8FC12; Thu, 15 Nov 2012 13:37:21 +0000 (UTC) Received: from svn.freebsd.org (localhost [127.0.0.1]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id qAFDbL5X090413; Thu, 15 Nov 2012 13:37:21 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id qAFDbLYi090407; Thu, 15 Nov 2012 13:37:21 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201211151337.qAFDbLYi090407@svn.freebsd.org> From: Glen Barber Date: Thu, 15 Nov 2012 13:37:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r39997 - in projects/pkgng/en_US.ISO8859-1: articles/committers-guide articles/contributing articles/contributors books/faq books/handbook/basics books/handbook/eresources books/handboo... X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2012 13:37:21 -0000 Author: gjb Date: Thu Nov 15 13:37:20 2012 New Revision: 39997 URL: http://svnweb.freebsd.org/changeset/doc/39997 Log: Merge r39917 through r39993 from ^/head/en_US.ISO8859-1 to pkgng/ branch. Modified: projects/pkgng/en_US.ISO8859-1/articles/committers-guide/article.xml projects/pkgng/en_US.ISO8859-1/articles/contributing/article.xml projects/pkgng/en_US.ISO8859-1/articles/contributors/contrib.additional.xml projects/pkgng/en_US.ISO8859-1/articles/contributors/contrib.committers.xml projects/pkgng/en_US.ISO8859-1/books/faq/book.xml projects/pkgng/en_US.ISO8859-1/books/handbook/basics/chapter.xml projects/pkgng/en_US.ISO8859-1/books/handbook/eresources/chapter.xml projects/pkgng/en_US.ISO8859-1/books/handbook/geom/chapter.xml projects/pkgng/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml projects/pkgng/en_US.ISO8859-1/books/porters-handbook/book.xml projects/pkgng/en_US.ISO8859-1/htdocs/art.xml projects/pkgng/en_US.ISO8859-1/htdocs/cgi/man.cgi projects/pkgng/en_US.ISO8859-1/htdocs/internal/homepage.pl projects/pkgng/en_US.ISO8859-1/htdocs/search/sitemap.xml projects/pkgng/en_US.ISO8859-1/share/xml/mailing-lists.ent projects/pkgng/en_US.ISO8859-1/share/xml/release.l10n.ent Directory Properties: projects/pkgng/en_US.ISO8859-1/ (props changed) Modified: projects/pkgng/en_US.ISO8859-1/articles/committers-guide/article.xml ============================================================================== --- projects/pkgng/en_US.ISO8859-1/articles/committers-guide/article.xml Thu Nov 15 07:41:34 2012 (r39996) +++ projects/pkgng/en_US.ISO8859-1/articles/committers-guide/article.xml Thu Nov 15 13:37:20 2012 (r39997) @@ -370,7 +370,7 @@ Getting Started - There are three ways to obtain a working copy of the tree + There are a few ways to obtain a working copy of the tree from Subversion. This section will explain them. @@ -466,119 +466,6 @@ information on how to set one up. - - Checkout from a Local Mirror Using - <acronym>SVK</acronym> - - The third alternative is to use SVK - to maintain a local mirror. It is a version control system - build on top of Subversion's storage engine. It is - identical to Subversion in most respects, except that it - allows for setting up parts of repositories as mirrors of - other repositories, and keeping local branches for merging - back into the upstream repositories. There are extensions - that allow SVK to mirror - Perforce repositories in addition - to Subversion ones. - - Like everything, SVK has its - disadvantages, one being that local revision numbers will - not match upstream revision numbers. This makes it - difficult to svk log, svk - diff, or svk update to an - arbitrary upstream revision. - - To set up a mirror of the &os; repository, do: - - &prompt.user; svk mirror svn+ssh://svn.freebsd.org/base //freebsd/base - - The local SVK repository will be - stored in ~/.svk/local/, but can be - moved to an alternate location. If it is moved, - ~/.svk/config should be amended - manually to reflect the move. - - Any path can be used, not just the one in the example - above. A common pattern is to place mirrors under - //mirror, e.g., - //mirror/freebsd/base/, and - local branches under //local. - - To pull down the contents of the repository to the - mirror: - - &prompt.user; svk sync //freebsd/base - - - svk sync will take a very long - time, possibly several days over a slow network - connection. &a.peter; has a tarball that can be used to - jumpstart the mirror, but only if one does not exist - already. - - - To use the tarball referenced above: - - &prompt.user; cd ~ -&prompt.user; scp freefall:/home/peter/dot_svk_r179646.tbz2 . -&prompt.user; tar xf dot_svk_r179646.tbz2 - - Then edit ~/.svk/config and replace - /scratch/tmp/peter/.svk/local/ - with the equivalent of /home/jarjar/.svk/local/. - - You can check out files directly from your mirror, once - it has been created: - - &prompt.user; svk checkout //freebsd/base/head /usr/src - - Unlike SVN, SVK - does not store metadata or reference copies in the working - copy. All metadata is recorded in - ~/.svk/config; reference copies are not - used at all because SVK always operates - on a local repository. - - When committing from a working copy like the one above, - SVN will commit directly to the upstream - repository, then synchronise the mirror. - - However, the killer app for - SVK is the ability to work without a - network connection. To do that, a local branch must be set - up: - - &prompt.user; svk mkdir //local/freebsd -&prompt.user; svk copy //freebsd/base/head //local/freebsd/head - - Once again, any path can be used, it does not have to - specifically be the one in the example. - - Before use, the local branch has to be synchronized, - like so: - - &prompt.user; svk pull //local/freebsd/head - - Then check out from the newly created local - branch: - - &prompt.user; svk checkout //local/freebsd/head /usr/src - - The point of this exercise is showing that it is - possible to commit work-in-progress to a local branch, and - only push it to the upstream repository when work is - complete. The easy way to push is with svk - push, but there is a serious disadvantage to it: - it will push every single commit made to the local branch - incrementally instead of lumping them all into a single - commit. Therefore, using svk smerge is - preferable. - - <literal>RELENG_*</literal> Branches and General Layout Modified: projects/pkgng/en_US.ISO8859-1/articles/contributing/article.xml ============================================================================== --- projects/pkgng/en_US.ISO8859-1/articles/contributing/article.xml Thu Nov 15 07:41:34 2012 (r39996) +++ projects/pkgng/en_US.ISO8859-1/articles/contributing/article.xml Thu Nov 15 13:37:20 2012 (r39997) @@ -342,39 +342,22 @@ The preferred &man.diff.1; format for submitting patches is the unified output format generated by diff - -u. However, for patches that substantially - change a region of code, a context output format diff - generated by diff -c may be more readable - and thus preferable. + -u. diff - For example: - - &prompt.user; diff -c oldfile newfile - - or - - &prompt.user; diff -c -r olddir newdir - - would generate such a set of context diffs for the given - source file or directory hierarchy. - - Likewise, - &prompt.user; diff -u oldfile newfile or - &prompt.user; diff -u -r olddir newdir + &prompt.user; diff -u -r -N olddir newdir - would do the same, except in the unified diff - format. + would generate a set of unified diffs for the given source + file or directory hierarchy. - See the manual page for &man.diff.1; for more - details. + See &man.diff.1; for more information. Once you have a set of diffs (which you may test with the &man.patch.1; command), you should submit them for inclusion @@ -400,9 +383,8 @@ welcome. If your change is of a potentially sensitive nature, - e.g. you are unsure of copyright issues governing its further - distribution or you are simply not ready to release it without - a tighter review first, then you should send it to &a.core; + such as if you are unsure of copyright issues governing its further + distribution then you should send it to &a.core; directly rather than submitting it with &man.send-pr.1;. The &a.core; reaches a much smaller group of people who do much of the day-to-day work on FreeBSD. Note that this @@ -506,7 +488,7 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - $Id$ + $&os;$ For your convenience, a copy of this text can be found in /usr/share/examples/etc/bsd-style-copyright. @@ -565,16 +547,6 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE PO Donations Liaison Office. - - - Donating Internet Access - - We can always use new mirror sites for FTP, WWW or - cvsup. If you would like to be such a - mirror, please see the - Mirroring - FreeBSD article for more information. - Modified: projects/pkgng/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- projects/pkgng/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Thu Nov 15 07:41:34 2012 (r39996) +++ projects/pkgng/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Thu Nov 15 13:37:20 2012 (r39997) @@ -1722,6 +1722,11 @@ + Christian Heckendorf + heckend@bu.edu + + + Christian Lackas delta@lackas.net @@ -3595,11 +3600,6 @@ - Grzegorz Blach - magik@roorback.net - - - Guillaume Paquet amyfoub@videotron.ca Modified: projects/pkgng/en_US.ISO8859-1/articles/contributors/contrib.committers.xml ============================================================================== --- projects/pkgng/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Thu Nov 15 07:41:34 2012 (r39996) +++ projects/pkgng/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Thu Nov 15 13:37:20 2012 (r39997) @@ -116,6 +116,10 @@ + &a.gblach; + + + &a.mbr; @@ -1520,6 +1524,10 @@ + &a.bryanv; + + + &a.avilla; Modified: projects/pkgng/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- projects/pkgng/en_US.ISO8859-1/books/faq/book.xml Thu Nov 15 07:41:34 2012 (r39996) +++ projects/pkgng/en_US.ISO8859-1/books/faq/book.xml Thu Nov 15 13:37:20 2012 (r39997) @@ -143,8 +143,7 @@ For more detailed information on &os;, please see the &os; Handbook. - + url="&url.books.handbook;/index.html">&os; Handbook. @@ -154,32 +153,11 @@ - The goal of the &os; Project is to provide software that - may be used for any purpose and without strings attached. - Many of us have a significant investment in the code (and - project) and would certainly not mind a little financial - compensation now and then, but we definitely do not insist - on it. We believe that our first and foremost - mission is to provide code to any and all - comers, and for whatever purpose, so that the code gets the - widest possible use and provides the widest possible - benefit. This is, we believe, one of the most fundamental - goals of Free Software and one that we enthusiastically - support. - - That code in our source tree which falls under the - GNU General Public License (GPL) - or GNU Library General Public License (LGPL) - comes with slightly more strings attached, though at least - on the side of enforced access rather than the usual - opposite. Due to the additional complexities that can - evolve in the commercial use of GPL software, we do, - however, endeavor to replace such software with submissions - under the more relaxed &os; license - whenever possible. + The goal of the &os; Project is to provide a + stable and fast general purpose + operating system that may + be used for any purpose + without strings attached. @@ -205,6 +183,34 @@ Do not sue us if it breaks. + + Many of us have a significant investment in the + project + and would certainly not mind a little financial + compensation now and then, but we definitely do not insist + on it. We believe that our first and foremost + mission is to provide code to any and all + comers, and for whatever purpose, so that the code gets + the + widest possible use and provides the widest possible + benefit. This, we believe, is one of the most + fundamental + goals of Free Software and one that we enthusiastically + support. + + Code in our source tree which falls under the + GNU General Public License (GPL) + or GNU Library General Public License (LGPL) + comes with slightly more strings attached, though at least + on the side of enforced access rather than the usual + opposite. Due to the additional complexities that can + evolve in the commercial use of GPL software, we do, + however, endeavor to replace such software with submissions + under the more relaxed &os; license + whenever possible. @@ -226,8 +232,7 @@ network servers, and just about everything else you might want. Most of these applications can be managed through the Ports Collection. - + url="http://www.FreeBSD.org/ports/">Ports Collection. If you need to use an application that is only available on one operating system, you simply cannot replace that @@ -243,7 +248,7 @@ If you are migrating to &os; from some other &unix; environment, you already know most of what you need to. If your background is in graphic-driven operating systems such - as &windows; and older versions of &macos;, expect to invest + as &windows; and &macos;, expect to invest additional time learning the &unix; way of doing things. This FAQ and the &os; Handbook @@ -371,12 +376,12 @@ &os.current; + url="&url.books.handbook;/current-stable.html#current">&os.current; is the development version of the operating system, which will in due course become the new &os.stable; branch. As such, it is really only of interest to developers working on the system and die-hard hobbyists. See the relevant section + url="&url.books.handbook;/current-stable.html#current">relevant section in the Handbook for details on running -CURRENT. @@ -436,15 +441,13 @@ -STABLE snapshots. Snapshot releases are directly available from snapshot. - + url="&url.base;/snapshots/">snapshot. Official snapshots are generated each month on a regular basis for all actively developed branches. There are also daily snapshot builds of the popular &arch.i386; and &arch.amd64; branches, hosted on . - + url="http://snapshots.us.freebsd.org/">. @@ -457,9 +460,9 @@ Back when &os; 2.0.5 was released, &os; development branched in two. One branch was named -STABLE, + url="&url.books.handbook;/current-stable.html#stable">-STABLE, one -CURRENT. + url="&url.books.handbook;/current-stable.html#current">-CURRENT. &os;-STABLE is intended for Internet Service Providers and other commercial enterprises for whom sudden shifts or experimental features are quite @@ -472,8 +475,7 @@ url="&url.articles.releng;/release-proc.html#REL-BRANCH">&os; Release Engineering: Creating the Release Branch, the status of the branches and the upcoming release schedule can be found on the Release Engineering Information page. - + url="http://www.FreeBSD.org/releng">Release Engineering Information page. The 2.2-STABLE branch was retired with the release of 2.2.8. The 3-STABLE branch has ended with the release of @@ -542,7 +544,7 @@ url="&url.base;/administration.html#t-core">core team of 9 people. There is a much larger team of more than 350 committers + url="&url.articles.contributors;/article.html#staff-committers">committers who are authorized to make changes directly to the &os; source tree. @@ -561,15 +563,13 @@ Every significant release of &os; is available via anonymous FTP from the &os; FTP site: - + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/"> &os; FTP site: The latest &rel.stable; release, &rel.current;-RELEASE can be found in the &rel.current;-RELEASE directory. - + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/&rel.current;-RELEASE/">&rel.current;-RELEASE directory. @@ -584,22 +584,19 @@ The latest &rel2.stable; release, &rel2.current;-RELEASE can be found in the &rel2.current;-RELEASE directory. - + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;-RELEASE directory. The latest &rel3.stable; release, &rel3.current;-RELEASE can be found in the &rel3.current;-RELEASE directory. - + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel3.current;-RELEASE/">&rel3.current;-RELEASE directory. Information about obtaining &os; on CD, DVD, and other media can be found in the Handbook. - + url="&url.books.handbook;/mirrors.html">the Handbook. @@ -908,15 +905,14 @@ - The compression and packaging scheme. There are - three of these currently in use. + The compression and packaging scheme. Where the format is html-split, the files are bundled up using &man.tar.1;. The resulting - .tar file is then compressed + .tar is then compressed using the compression schemes detailed in the next point. @@ -927,42 +923,11 @@ (i.e., article.pdf, book.html, and so on). - These files are then compressed using two - compression schemes. - - - - - - Scheme - - Description - - - - - - zip - - The zip format. If you want to - uncompress this on &os; you will need to - install the archivers/unzip - port first. - - - - bz2 - - The bzip2 format. Less widespread than - zip, but generally gives smaller files. - Install the archivers/bzip2 - port to uncompress these files. - - - - + These files are then compressed using either + the zip or + bz2 compression schemes. + &man.tar.1; can be used to uncompress these + files. So the &postscript; version of the Handbook, compressed using bzip2 will be stored in a file @@ -979,14 +944,13 @@ appropriate documents into place. For example, the split HTML version of the FAQ, - compressed using &man.bzip2.1;, can be found in the + compressed using &man.bzip2.1;, can be found in doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2 - file. To download and uncompress that file you would have + To download and uncompress that file you would have to do this. &prompt.root; fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2 -&prompt.root; bzip2 -d book.html-split.tar.bz2 -&prompt.root; tar xvf book.html-split.tar +&prompt.root; tar xvf book.html-split.tar.bz2 You will be left with a collection of .html files. The main one is called @@ -1004,7 +968,7 @@ You can find full information in the Handbook entry on mailing-lists. + url="&url.books.handbook;/eresources.html#eresources-mail">Handbook entry on mailing-lists. @@ -1140,8 +1104,7 @@ BSD Certification Group, Inc. provides system administration certifications for DragonFly BSD, &os;, NetBSD, OpenBSD. If you are interested in them, visit their site. - + url="http://www.BSDCertification.org">their site. Any other organizations providing training and support should contact the Project in order to be listed here. @@ -1168,7 +1131,7 @@ Which platform should I download? I have a 64 - bit capable Intel CPU, + bit capable &intel; CPU, but I only see amd64. @@ -1245,8 +1208,7 @@ Full instructions on this procedure and a little bit more about installation issues in general can be found in the Handbook entry on installing &os;. - + url="&url.books.handbook;/install.html">Handbook entry on installing &os;. @@ -1295,8 +1257,7 @@ it to the floppy raw, using the low-level tools (e.g., fdimage or rawrite) described in the installation guide to &os;. - + url="&url.books.handbook;/install.html">installation guide to &os;. @@ -1309,8 +1270,7 @@ Installation instructions can be found in the Handbook entry on installing &os;. - + url="&url.books.handbook;/install.html">Handbook entry on installing &os;. @@ -1816,8 +1776,7 @@ Memory limits depend on the platform used. On a standard &i386; install, the limit is 4 GB but more memory can be supported through &man.pae.4;. See instructions for using 4 GB or more memory on &i386;. - + linkend="memory-i386-over-4gb">instructions for using 4 GB or more memory on &i386;. &os;/pc98 has a limit of 4 GB memory, and PAE can not be used with it. Other architectures supported by &os; @@ -2087,8 +2046,8 @@ - Yes. &os; currently runs on the Intel x86 and the - AMD64 architectures. The Intel EM64T, IA-64, &arm;, + Yes. &os; currently runs on the &intel; x86 and the + AMD64 architectures. The &intel; EM64T, IA-64, &arm;, &powerpc;, and &sparc64; architectures are also supported. Upcoming platforms are &mips; and &s390;, join the &a.mips; for more information about ongoing work on @@ -2138,6 +2097,7 @@ Install sysutils/devcpu-data, then add: microcode_update_enable="YES" + to /etc/rc.conf @@ -2172,8 +2132,7 @@ See the complete list in the Hardware Notes for &os; &rel.current; or &rel2.current;. - + url="&rel2.current.hardware;">&rel2.current;. @@ -2234,7 +2193,7 @@ drive. See &man.burncd.8; for details. &os; also supports any SCSI CD-R or CD-RW drives. - Install and use the cdrecord command + Install and use cdrecord from the ports or packages system, and make sure that you have the pass device compiled in your kernel. @@ -2440,8 +2399,7 @@ For the possible usage of wheels in the X Window environment, refer to that section. - + linkend="x-and-wheel">that section. @@ -2479,8 +2437,7 @@ bind ^[[3~ ed-delete-next-char # for xte bindkey ^[[3~ delete-char # for xterm For more information, see this page. - + url="http://www.ibb.net/~anne/keyboard.html">this page. @@ -2540,8 +2497,7 @@ bindkey ^[[3~ delete-char # for xterm

See this section of the handbook. - + url="&url.books.handbook;/serialconsole-setup.html">this section of the handbook. @@ -2722,8 +2678,7 @@ ARRE (Auto Read Reallocation Enbld): 1< address range clash :), by bumping the kernel option EISA_SLOTS to a value of 12. Configure and compile a kernel, as described in the Handbook entry on configuring the kernel. - + url="&url.books.handbook;/kernelconfig.html">Handbook entry on configuring the kernel. Of course, this does present you with a chicken-and-egg problem when installing on such a machine. In order to work @@ -2744,9 +2699,8 @@ quit You cannot use a dangerously - dedicated disk with an HP Netserver. See this note for more info. - + dedicated disk with an HP Netserver. See this note for more info. @@ -2759,8 +2713,8 @@ quit This is usually caused by an interrupt conflict (e.g., - two boards using the same IRQ). Boot with the - option and change the + two boards using the same IRQ). Boot with + and change the ed0/de0/... entry to match your board. @@ -2899,8 +2853,7 @@ quit instructions to send a problem report. There is an extensive FAQ on this at the SIG11 problem FAQ. - + url="http://www.bitwizard.nl/sig11/">the SIG11 problem FAQ. @@ -3017,7 +2970,7 @@ quit memory for network buffers (specifically, mbuf clusters). You can increase the amount of VM available for mbuf clusters by following the instructions in the Network Limits + url="&url.books.handbook;/configtuning-kernel-limits.html#nmbclusters">Network Limits section of the Handbook. @@ -3136,8 +3089,7 @@ quit You can find a detailed answer for this question in the Handbook. - + url="&url.books.handbook;/mail-trouble.html#Q26.5.2.">Handbook. @@ -3413,9 +3365,9 @@ chip1@pci0:31:5: class=0x040100 c /etc/resolv.conf. This will often cause a delay in SSH, as the option UseDNS is set to - yes by default in the - sshd_config file in - /etc/ssh. If this is causing the + yes by default in + /etc/ssh/sshd_config. + If this is causing the problem, you will either need to fill in the missing information in /etc/resolv.conf or set UseDNS to no in @@ -3448,7 +3400,7 @@ chip1@pci0:31:5: class=0x040100 c MAX_STRAY_LOG from 5 to 0 in your platform's (e.g., &i386;) - intr_machdep.c file and rebuild the + intr_machdep.c and rebuild the new kernel and all the warnings will be suppressed. @@ -3636,7 +3588,7 @@ kern.timecounter.hardware: TSC -> i82 Enter &man.sysinstall.8; and choose Configure, then Fdisk. Select the disk the Boot - Manager resided on with the Space key. + Manager resided on with Space. Press W to write changes to the drive. A prompt will appear asking which boot loader to install. Select this, and it will be restored. @@ -3706,8 +3658,7 @@ kern.timecounter.hardware: TSC -> i82 An answer for this question can be found in the &os; Glossary, see LOR. - + url="&url.books.handbook;/freebsd-glossary.html#LOR-GLOSSARY">LOR. @@ -3912,8 +3863,7 @@ kern.timecounter.hardware: TSC -> i82 url="http://www.xfce.org/">xfce. KDE and xfce are both in the ports system. - + url="&url.base;/ports/index.html">ports system. @@ -3996,8 +3946,7 @@ kern.timecounter.hardware: TSC -> i82 ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel3.packages; - + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel3.packages;/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel3.packages; @@ -4006,8 +3955,7 @@ kern.timecounter.hardware: TSC -> i82 ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel2.packages; - + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel2.packages;/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel2.packages; @@ -4016,8 +3964,7 @@ kern.timecounter.hardware: TSC -> i82 ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel.packages; - + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel.packages;/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel.packages; @@ -4084,8 +4031,7 @@ kern.timecounter.hardware: TSC -> i82 Yes. Please see http://www.FreeBSD.org/java/. - + url="&url.base;/java/index.html">http://www.FreeBSD.org/java/. @@ -4268,8 +4214,27 @@ kern.timecounter.hardware: TSC -> i82 The WAV files can then be converted to other formats or burned onto audio CDs, as described in the &os; Handbook. - + url="&url.books.handbook;/creating-cds.html">&os; Handbook. + + + + + + How can I convert from pkgng to the old package + tools? + + + + Short answer: it is not possible. + + Longer answer: if you have made any changes using + pkg converting back is non-trivial and + requires lots of manual editing of internal package + database files. However, if you have just run + pkg2ng then you may remove + /var/db/pkg/local.sqlite + and extract + /var/backups/pkgdb.bak.tbz. @@ -4287,8 +4252,7 @@ kern.timecounter.hardware: TSC -> i82 Not at all! Check out the kernel config section of the Handbook. - + url="&url.books.handbook;/kernelconfig.html">kernel config section of the Handbook. The new kernel will be installed @@ -4411,8 +4375,8 @@ device sio5 at isa? port 0x2b8 tty flags used to build the currently running system (e.g., you are compiling &rel.current;-RELEASE on a &rel2.current;-RELEASE system). If you are attempting - an upgrade, please read the - /usr/src/UPDATING file, paying + an upgrade, please read + /usr/src/UPDATING, paying particular attention to the COMMON ITEMS section at the end. @@ -4669,8 +4633,8 @@ kern.sched.name: ULE When you are slicing up your disk, check that the disk geometry displayed in the FDISK screen is correct (i.e., it - matches the BIOS numbers); if it is wrong, use the - G key to fix it. You may have to do this + matches the BIOS numbers); if it is wrong, use + G to fix it. You may have to do this if there is absolutely nothing on the disk, or if the disk has been moved from another system. Note that this is only an issue with the disk that you are going to boot from; &os; @@ -4937,7 +4901,7 @@ use "disklabel -r" to install initial la DOS/&windowsnt; partition. Assuming you name that file something like c:\bootsect.bsd (inspired by c:\bootsect.dos), you can - then edit the c:\boot.ini file to come + then edit c:\boot.ini to come up with something like this: [boot loader] @@ -5046,8 +5010,7 @@ C:\="DOS" title &os; 6.1 root (hd0,a) - kernel /boot/loader - + kernel /boot/loader Where hd0,a points to your root partition on the first disk. If you need to specify @@ -5097,69 +5060,38 @@ C:\="DOS" - Whether it is a removable drive like a &iomegazip; or an - EZ drive (or even a floppy, if you want to use it that way), - or a new hard disk, once it is installed and recognized by - the system, and you have your cartridge/floppy/whatever - slotted in, things are pretty much the same for all - devices. - - (this section is based on Mark Mayo's ZIP FAQ) - - - If it is a ZIP drive or a floppy, you have already got a - DOS file system on it, you can use a command like this: - - &prompt.root; mount -t msdosfs /dev/fd0c /floppy - - if it is a floppy, or this: - - &prompt.root; mount -t msdosfs /dev/da2s4 /zip - - for a ZIP disk with the factory configuration. - - For other disks, see how they are laid out using - &man.fdisk.8; or &man.sysinstall.8;. - - The rest of the examples will be for a ZIP drive on - da2, the third SCSI disk. - - Unless it is a floppy, or a removable you plan on - sharing with other people, it is probably a better idea to - stick a BSD file system on it. You will get long filename - support, at least a 2X improvement in performance, and a lot - more stability. First, you need to redo the DOS-level - partitions/file systems. You can either use &man.fdisk.8; - or &man.sysinstall.8;, or for a small drive that you do not - want to bother with multiple operating system support on, - just blow away the whole FAT partition table (slices) and - just use the BSD partitioning: - - &prompt.root; dd if=/dev/zero of=/dev/rda2 count=2 -&prompt.root; disklabel -Brw da2 auto - - You can use &man.disklabel.8; or &man.sysinstall.8; to - create multiple BSD partitions. You will certainly want to - do this if you are adding swap space on a fixed disk, but it - is probably irrelevant on a removable drive like a - ZIP. + If the drive already has a + file system on it, you can use a command like this: + + &prompt.root; mount /dev/da0s1 /mnt - Finally, create a new file system, this one is on our - ZIP drive using the whole disk: + If the drive will only be used with &os; + systems it is better idea to + stick a BSD file system on it, like UFS or ZFS. + You will get long filename + support, at least a 2X improvement in performance, + and a lot more stability. If the drive will be + used by other operating systems a more portable + choice, such as msdosfs, is better. + + &prompt.root; dd if=/dev/zero of=/dev/da0 count=2 *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***