From owner-svn-doc-head@FreeBSD.ORG Mon May 12 14:18:12 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 397A8969; Mon, 12 May 2014 14:18:12 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2450B2A50; Mon, 12 May 2014 14:18:12 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s4CEICUZ058839; Mon, 12 May 2014 14:18:12 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s4CEICAc058838; Mon, 12 May 2014 14:18:12 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405121418.s4CEICAc058838@svn.freebsd.org> From: Dru Lavigne Date: Mon, 12 May 2014 14:18:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44814 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2014 14:18:12 -0000 Author: dru Date: Mon May 12 14:18:11 2014 New Revision: 44814 URL: http://svnweb.freebsd.org/changeset/doc/44814 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Mon May 12 13:27:37 2014 (r44813) +++ head/en_US.ISO8859-1/books/faq/book.xml Mon May 12 14:18:11 2014 (r44814) @@ -21,8 +21,7 @@ ]> Frequently Asked Questions for &os; - &rel3.relx;, &rel2.relx; and &rel.relx; - + &rel3.relx;, &rel2.relx; and &rel.relx; The &os; Documentation Project @@ -70,16 +69,19 @@ $FreeBSD$ - This is the FAQ for &os; versions &rel3.relx;, &rel2.relx; and - &rel.relx;. Every effort has been made to make this FAQ as - informative as possible; if you have any suggestions as to how - it may be improved, please feel free to mail them to the + This is the FAQ for &os; versions &rel3.relx;, &rel2.relx; + and &rel.relx;. Every effort has been made to make this FAQ + as informative as possible; if you have any suggestions as to + how it may be improved, please feel free to mail them to the &a.doc;. - The latest version of - this document is always available from the &os; website. - It may also be downloaded as one large HTML file with HTTP or as a variety - of other formats from the &os; FTP + The latest version of this document is always available + from the &os; + website. It may also be downloaded as one large + HTML file with HTTP or as + a variety of other formats from the &os; FTP server. @@ -95,24 +97,26 @@ &os; is a modern operating system for desktops, - laptops, servers, and embedded systems with - support for a large number of platforms. - - It is based on U.C. - Berkeley's 4.4BSD-Lite release, with some - 4.4BSD-Lite2 enhancements. It is also based - indirectly on William Jolitz's port of U.C. Berkeley's - Net/2 to the &i386;, known as - 386BSD, though very little of the 386BSD code - remains. + laptops, servers, and embedded systems with support for a + large number of platforms. + + It is based on U.C. Berkeley's + 4.4BSD-Lite release, with some + 4.4BSD-Lite2 enhancements. It is also + based indirectly on William Jolitz's port of U.C. + Berkeley's Net/2 to the &i386;, known as + 386BSD, though very little of the 386BSD + code remains. &os; is used by companies, Internet Service Providers, - researchers, computer professionals, students and home users - all over the world in their work, education and + researchers, computer professionals, students and home + users all over the world in their work, education and recreation. For more detailed information on &os;, please see the - &os; Handbook. + &os; + Handbook. @@ -122,11 +126,9 @@ - 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. + 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. @@ -136,9 +138,11 @@ - Yes. Those restrictions do not control how you use the - code, merely how you treat the &os; Project itself. If you - have serious license concerns, read the actual license. + Yes. Those restrictions do not control how you use + the code, merely how you treat the &os; Project itself. + If you have serious license concerns, read the actual + license. For the simply curious, the license can be summarized like this. @@ -157,29 +161,29 @@ Many of us have a significant investment in the - project - and would certainly not mind a little financial + 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 + 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. + 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. @@ -193,36 +197,39 @@ that cut-and-dried. Most people do not actually use an operating system. - They use applications. The applications are what really use - the operating system. &os; is designed to provide a robust - and full-featured environment for applications. It supports - a wide variety of web browsers, office suites, email - readers, graphics programs, programming environments, - network servers, and just about everything else you might - want. Most of these applications can be managed through the - Ports Collection. - - If you need to use an application that is only available - on one operating system, you simply cannot replace that - operating system. Chances are there is a very similar - application on &os;, however. If you want a solid office or - Internet server, a reliable workstation, or just the ability - to do your job without interruptions, &os; will almost - certainly do everything you need. Many computer users - across the world, including both novices and experienced - &unix; administrators, use &os; as their only desktop - operating system. + They use applications. The applications are what really + use the operating system. &os; is designed to provide a + robust and full-featured environment for applications. It + supports a wide variety of web browsers, office suites, + email readers, graphics programs, programming + environments, network servers, and just about everything + else you might want. Most of these applications can be + managed through the Ports + Collection. + + If you need to use an application that is only + available on one operating system, you simply cannot + replace that operating system. Chances are there is a + very similar application on &os;, however. If you want a + solid office or Internet server, a reliable workstation, + or just the ability to do your job without interruptions, + &os; will almost certainly do everything you need. Many + computer users across the world, including both novices + and experienced &unix; administrators, use &os; as their + only desktop operating system. 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 &macos;, you may be interested in using - PC-BSD, a &os; based - distribution, instead. If you have not used &unix; before - expect to invest - additional time learning the &unix; way of doing things. - This FAQ and the &os; Handbook - are excellent places to start. + environment, you already know most of what you need to. + If your background is in graphic-driven operating systems + such as &windows; and &macos;, you may be interested in + using PC-BSD, a &os; + based distribution, instead. If you have not used &unix; + before expect to invest additional time learning the + &unix; way of doing things. This FAQ and the &os; + Handbook are excellent places to start. @@ -241,54 +248,59 @@ Full source for the operating system is freely available, and the minimum possible restrictions have - been placed upon its use, distribution and incorporation - into other work (commercial or non-commercial). + been placed upon its use, distribution and + incorporation into other work (commercial or + non-commercial). - Anyone who has an improvement or bug fix is free to - submit their code and have it added to the source tree - (subject to one or two obvious provisions). + Anyone who has an improvement or bug fix is free + to submit their code and have it added to the source + tree (subject to one or two obvious + provisions). It is worth pointing out that the word free is being used in two ways here, one meaning at no cost, the other meaning - you can do whatever you like. Apart from one - or two things you cannot do with the - &os; code, for example pretending you wrote it, you can - really do whatever you like with it. + you can do whatever you like. Apart from + one or two things you cannot do with + the &os; code, for example pretending you wrote it, you + can really do whatever you like with it. What are the differences between &os; and NetBSD, - OpenBSD, and other open source BSD operating systems? + OpenBSD, and other open source BSD operating + systems? - James Howard wrote a good explanation of the history and - differences between the various projects, - called The BSD Family Tree - which goes a fair way to answering this question. - Some of the information is out of date, but the history - portion in particular remains accurate. + James Howard wrote a good explanation of the history + and differences between the various projects, called The + BSD Family Tree which goes a fair way to + answering this question. Some of the information is out + of date, but the history portion in particular remains + accurate. Most of the BSDs share patches and code, even today. All of the BSDs have common ancestry. - The design goals of &os; are described in - , above. The design goals - of the other most popular BSDs may be summarized as + The design goals of &os; are described in , above. The design goals of + the other most popular BSDs may be summarized as follows: OpenBSD aims for operating system security above all else. The OpenBSD team wrote &man.ssh.1; and - &man.pf.4;, which have both been ported to &os;. + &man.pf.4;, which have both been ported to + &os;. @@ -297,9 +309,9 @@ - DragonFly BSD is a fork of &os; 4.8 that has - since developed many interesting features of its own, - including the HAMMER file system and support for + DragonFly BSD is a fork of &os; 4.8 that + has since developed many interesting features of its + own, including the HAMMER file system and support for user-mode vkernels. @@ -313,48 +325,51 @@ At any point in the development of &os;, there can be - multiple parallel branches. &rel.relx; releases are - made from the &rel.stable; branch, and &rel2.relx; - releases are made from the &rel2.stable; branch. - - Up until the release of 9.0, the - &rel2.relx; series was the one known as - -STABLE. However, as of - &rel.head.relx;, the - &rel2.relx; branch will be designated for - an extended support status and receive only - fixes for major problems, such as security-related fixes. + multiple parallel branches. &rel.relx; releases are made + from the &rel.stable; branch, and &rel2.relx; releases are + made from the &rel2.stable; branch. + + Up until the release of 9.0, the &rel2.relx; series + was the one known as -STABLE. + However, as of &rel.head.relx;, the &rel2.relx; branch + will be designated for an extended support + status and receive only fixes for major problems, such as + security-related fixes. - Version &rel.current; - is the latest release from the &rel.stable; - branch; it was released in &rel.current.date;. Version - &rel2.current; - is the latest release from the &rel2.stable; - branch; it was released in &rel2.current.date;. + Version &rel.current; + is the latest release from the &rel.stable; branch; it was + released in &rel.current.date;. Version &rel2.current; + is the latest release from the &rel2.stable; branch; it + was released in &rel2.current.date;. Briefly, -STABLE is aimed at the ISP, corporate user, or any user who wants stability and a - minimal number of changes compared to the new (and possibly - unstable) features of the latest + minimal number of changes compared to the new (and + possibly unstable) features of the latest -CURRENT snapshot. Releases can come - from either branch, but -CURRENT should - only be used if you are prepared for its increased + from either branch, but -CURRENT + should only be used if you are prepared for its increased volatility (relative to -STABLE, that is). - Releases are made every few months. While - many people stay more up-to-date with the &os; sources (see - the questions on &os.current; and &os.stable;) than that, doing so + Releases are made every + few months. While many people stay more + up-to-date with the &os; sources (see the questions on + &os.current; and &os.stable;) than that, doing so is more of a commitment, as the sources are a moving target. More information on &os; releases can be found on the - Release Engineering page - and in &man.release.7;. + Release + Engineering page and in &man.release.7;. @@ -364,22 +379,26 @@ - &os.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 - in the Handbook for - details on running -CURRENT. + such, it is really only of interest to developers working + on the system and die-hard hobbyists. See the relevant + section in the Handbook + for details on running + -CURRENT. - If you are not familiar with &os; - you should not use + If you are not familiar with &os; you should not use &os.current;. This branch sometimes evolves quite quickly - and due to mistake can be un-buildable at times. - People that use &os.current; are expected to be able to - analyze, debug, and report problems. + and due to mistake can be un-buildable at times. People + that use &os.current; are expected to be able to analyze, + debug, and report problems. - &os; snapshot + &os; snapshot releases are made based on the current state of the -CURRENT and -STABLE branches. The goals behind @@ -395,32 +414,34 @@ To give people who would like to run -CURRENT or -STABLE but who do not have the - time or bandwidth to follow it on a day-to-day basis an - easy way of bootstrapping it onto their systems. + time or bandwidth to follow it on a day-to-day basis + an easy way of bootstrapping it onto their + systems. - To preserve a fixed reference point for the code in - question, just in case we break something really badly - later. (Although Subversion normally prevents anything - horrible like this happening.) + To preserve a fixed reference point for the code + in question, just in case we break something really + badly later. (Although Subversion normally prevents + anything horrible like this happening.) - To ensure that all new features and fixes in need of - testing have the greatest possible number of potential - testers. + To ensure that all new features and fixes in need + of testing have the greatest possible number of + potential testers. No claims are made that any -CURRENT snapshot can be considered production quality for any purpose. If you - want to run a stable and fully tested system, you will have - to stick to full releases, or use the + want to run a stable and fully tested system, you will + have to stick to full releases, or use the -STABLE snapshots. - Snapshot releases are directly available from snapshot. + Snapshot releases are directly available from snapshot. Official snapshots are generated on a regular basis for all actively developed branches. @@ -434,30 +455,38 @@ - Back when &os; 2.0.5 was released, &os; development - branched in two. One branch was named -STABLE, - one -CURRENT. + Back when &os; 2.0.5 was released, &os; + development branched in two. One branch was named -STABLE, + one -CURRENT. &os;-STABLE is intended for Internet - Service Providers and other commercial enterprises for whom - sudden shifts or experimental features are quite + Service Providers and other commercial enterprises for + whom sudden shifts or experimental features are quite undesirable. It receives only well-tested bug fixes and other small incremental enhancements. &os;-CURRENT, on the other hand, has been one unbroken line since 2.0 was released, leading - towards &rel.current;-RELEASE and beyond. For more detailed - information on branches see &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. + towards &rel.current;-RELEASE and beyond. For more + detailed information on branches see &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. &rel.current;-STABLE is the actively developed - -STABLE branch. The latest release on - the &rel.current;-STABLE branch is &rel.current;-RELEASE, - which was released in &rel.current.date;. + -STABLE branch. The latest release + on the &rel.current;-STABLE branch is + &rel.current;-RELEASE, which was released in + &rel.current.date;. The &rel.head; branch is the actively developed -CURRENT branch toward the next - generation of &os;. See What is &os;-CURRENT? for more - information on this branch. + generation of &os;. See What is + &os;-CURRENT? for more information on this + branch. @@ -468,24 +497,26 @@ The &a.re; releases a new major version of &os; about - every 18 months and a new minor version about every 8 months, - on average. Release dates are announced well in advance, so - that the people working on the system know when their - projects need to be finished and tested. A testing period - precedes each release, to ensure that the addition - of new features does not compromise the stability of the - release. Many users regard this caution as one of the best - things about &os;, even though waiting for all the latest - goodies to reach -STABLE can be a - little frustrating. + every 18 months and a new minor version about every 8 + months, on average. Release dates are announced well in + advance, so that the people working on the system know + when their projects need to be finished and tested. A + testing period precedes each release, to ensure that the + addition of new features does not compromise the stability + of the release. Many users regard this caution as one of + the best things about &os;, even though waiting for all + the latest goodies to reach -STABLE + can be a little frustrating. More information on the release engineering process - (including a schedule of upcoming releases) can be found on - the release engineering - pages on the &os; Web site. + (including a schedule of upcoming releases) can be found + on the release + engineering pages on the &os; Web site. For people who need or want a little more excitement, - binary snapshots are made weekly as discussed above. + binary snapshots are made weekly as discussed + above. @@ -497,16 +528,18 @@ The key decisions concerning the &os; project, such as the overall direction of the project and who is allowed to - add code to the source tree, are made by a core team of - 9 people. There is a much larger team of more than 350 - committers + add code to the source tree, are made by a core + team of 9 people. There is a much larger team of + more than 350 committers who are authorized to make changes directly to the &os; source tree. However, most non-trivial changes are discussed in - advance in the mailing lists, - and there are no restrictions on who may take part in the - discussion. + advance in the mailing + lists, and there are no restrictions on who may + take part in the discussion. @@ -517,29 +550,40 @@ Every significant release of &os; is available via - anonymous FTP from the &os; FTP site: + anonymous FTP from the &os; + FTP site: - The latest &rel.stable; release, &rel.current;-RELEASE - can be found in the &rel.current;-RELEASE directory. + The latest &rel.stable; release, + &rel.current;-RELEASE can be found in the &rel.current;-RELEASE + directory. - Snapshot - releases are made monthly for the -CURRENT and -STABLE branch, these being of - service purely to bleeding-edge testers and + Snapshot + releases are made monthly for the -CURRENT and -STABLE branch, these being + of service purely to bleeding-edge testers and developers. - The latest &rel2.stable; release, &rel2.current;-RELEASE - can be found in the &rel2.current;-RELEASE directory. + The latest &rel2.stable; release, + &rel2.current;-RELEASE can be found in the &rel2.current;-RELEASE + directory. Information about obtaining &os; on CD, DVD, and other - media can be found in the Handbook. + media can be found in the + Handbook. @@ -549,18 +593,22 @@ - The Problem Report database of all user change requests - may be queried by using our web-based PR query + The Problem Report database of all user change + requests may be queried by using our web-based PR query interface. The &man.send-pr.1; command can be used to submit problem reports and change requests via electronic mail. - Alternatively, the web-based problem report submission interface - can be used to submit problem reports through a web - browser. - - Before submitting a problem report, please read Writing &os; Problem Reports, - an article on how to write good problem reports. + Alternatively, the web-based + problem report submission interface can be used + to submit problem reports through a web browser. + + Before submitting a problem report, please read Writing + &os; Problem Reports, an article on how to write + good problem reports. @@ -577,22 +625,28 @@ The project produces a wide range of documentation, - available online from this link: http://www.FreeBSD.org/docs.html. In addition, the Bibliography at the end of this - FAQ, and the one in the Handbook - reference other recommended books. + available online from this link: http://www.FreeBSD.org/docs.html. + In addition, the Bibliography at the + end of this FAQ, and the + one in the Handbook reference other recommended + books. - Is the documentation available in other formats, such as - plain text (ASCII), or &postscript;? + Is the documentation available in other formats, such + as plain text (ASCII), or &postscript;? Yes. The documentation is available in a number of different formats and compression schemes on the &os; FTP - site, in the /pub/FreeBSD/doc/ + site, in the /pub/FreeBSD/doc/ directory. The documentation is categorized in a number of @@ -600,8 +654,9 @@ - The document's name, such as faq, - or handbook. + The document's name, such as + faq, or + handbook. @@ -685,7 +740,8 @@ mn_MN.UTF-8 - Mongolian (Mongolia, UTF-8 encoding) + Mongolian (Mongolia, UTF-8 + encoding) @@ -740,7 +796,8 @@ zh_TW.Big5 - Traditional Chinese (Taiwan, Big5 encoding) + Traditional Chinese (Taiwan, Big5 + encoding) @@ -753,16 +810,17 @@ - The document's format. We produce the documentation - in a number of different output formats. Each format - has its own advantages and disadvantages. Some formats - are better suited for online reading, while others are - meant to be aesthetically pleasing when printed on - paper. Having the documentation available in any of - these formats ensures that our readers will be able to - read the parts they are interested in, either on their - monitor, or on paper after printing the documents. The - currently available formats are: + The document's format. We produce the + documentation in a number of different output formats. + Each format has its own advantages and disadvantages. + Some formats are better suited for online reading, + while others are meant to be aesthetically pleasing + when printed on paper. Having the documentation + available in any of these formats ensures that our + readers will be able to read the parts they are + interested in, either on their monitor, or on paper + after printing the documents. The currently available + formats are: @@ -818,8 +876,10 @@ Page numbers are not automatically updated when - loading Rich Text Format into Word. Press CtrlA, - CtrlEnd, + loading Rich Text Format into Word. Press CtrlA, + CtrlEnd, F9 after loading the document, to update the page numbers. @@ -831,17 +891,17 @@ Where the format is - html-split, the files are bundled - up using &man.tar.1;. The resulting + html-split, the files are + bundled up using &man.tar.1;. The resulting .tar file is then compressed using the compression schemes detailed in the next point. - All the other formats generate one file, called - type.format - (i.e., article.pdf, + All the other formats generate one file, + called type.format (i.e., + article.pdf, book.html, and so on). These files are then compressed using either @@ -851,24 +911,25 @@ files. So the &postscript; version of the Handbook, - compressed using bzip2 will be stored in a file - called book.ps.bz2 in the + compressed using bzip2 will be + stored in a file called + book.ps.bz2 in the handbook/ directory. - After choosing the format and compression mechanism that - you want to download, you will have to download the compressed - files yourself, uncompress them, and then copy the - appropriate documents into place. + After choosing the format and compression mechanism + that you want to download, you will have to download the + compressed files yourself, uncompress them, and then copy + the appropriate documents into place. For example, the split HTML version of the FAQ, compressed using &man.bzip2.1;, can be found in doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2 - To download and uncompress that file you would have - to do this: + 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; tar xvf book.html-split.tar.bz2 @@ -887,13 +948,16 @@ - Where do I find info on the &os; mailing lists? - What &os; news groups are available? + Where do I find info on the &os; mailing lists? What + &os; news groups are available? - You can find full information in the Handbook entry on mailing-lists - and the Handbook entry on newsgroups. + You can find full information in the Handbook + entry on mailing-lists and the Handbook + entry on newsgroups. @@ -909,70 +973,79 @@ - Channel #FreeBSDhelp on EFNet is - a channel dedicated to helping &os; users. They are - much more sympathetic to questions than + Channel #FreeBSDhelp on EFNet + is a channel dedicated to helping &os; users. They + are much more sympathetic to questions than #FreeBSD is. - Channel #FreeBSD on Freenode is a - general help channel with many users at any time. - The conversations have been known to run off-topic for a - while, but priority is given to users with &os; - questions. We are good about helping you understand the - basics, referring to the Handbook whenever possible, and - directing you where to learn more about the topic you - need help with. We are a primarily English speaking - channel, though we have users from all over the world. - If you would like to speak in your native language, try - to ask the question in English and then relocate to - another channel - ##freebsd-lang - as appropriate. + Channel #FreeBSD on Freenode is + a general help channel with many users at any time. + The conversations have been known to run off-topic for + a while, but priority is given to users with &os; + questions. We are good about helping you understand + the basics, referring to the Handbook whenever + possible, and directing you where to learn more about + the topic you need help with. We are a primarily + English speaking channel, though we have users from + all over the world. If you would like to speak in + your native language, try to ask the question in + English and then relocate to another channel + ##freebsd-lang as + appropriate. - Channel #FreeBSD on DALNET is available at - irc.dal.net in the US and - irc.eu.dal.net in Europe. + Channel #FreeBSD on DALNET is + available at irc.dal.net in + the US and irc.eu.dal.net in + Europe. - Channel #FreeBSD on UNDERNET is - available at us.undernet.org in the US - and eu.undernet.org in Europe. Since - it is a help channel, be prepared to read the documents - you are referred to. + Channel #FreeBSD on UNDERNET + is available at + us.undernet.org in the US and + eu.undernet.org in Europe. + Since it is a help channel, be prepared to read the + documents you are referred to. - Channel #FreeBSD on - RUSNET - is a russian-language oriented channel dedicated - to helping &os; users. This is also good place - for non-technical discussions. + Channel #FreeBSD on RUSNET + is a russian-language oriented channel dedicated to + helping &os; users. This is also good place for + non-technical discussions. - Channel #bsdchat on Freenode is a - Traditional-Chinese (UTF-8 encoding) language oriented - channel dedicated to helping &os; users. This is also - good place for non-technical discussions. + Channel #bsdchat on Freenode is + a Traditional-Chinese (UTF-8 encoding) language + oriented channel dedicated to helping &os; users. + This is also good place for non-technical + discussions. - The &os; wiki has a good list - of IRC channels. + The &os; wiki has a good + list of IRC channels. Each of these channels are distinct and are not - connected to each other. Their chat styles also differ, so - you may need to try each to find one suited to your chat - style. As with all types of IRC - traffic, if you are easily offended or cannot deal with lots - of young people (and more than a few older ones) doing the - verbal equivalent of jello wrestling, do not even bother - with it. + connected to each other. Their chat styles also differ, + so you may need to try each to find one suited to your + chat style. As with all types of IRC + traffic, if you are easily offended or cannot deal with + lots of young people (and more than a few older ones) + doing the verbal equivalent of jello wrestling, do not + even bother with it. @@ -981,7 +1054,8 @@ Are there any web based forums to discuss &os;? - The official &os; forums are located at http://forums.FreeBSD.org/. + The official &os; forums are located at http://forums.FreeBSD.org/. @@ -992,14 +1066,21 @@ *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***