From owner-svn-doc-all@FreeBSD.ORG Wed Apr 1 05:40:25 2015 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 92310211; Wed, 1 Apr 2015 05:40:25 +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 733FE16A; Wed, 1 Apr 2015 05:40:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t315ePTg060951; Wed, 1 Apr 2015 05:40:25 GMT (envelope-from eadler@FreeBSD.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id t315ePtO060917; Wed, 1 Apr 2015 05:40:25 GMT (envelope-from eadler@FreeBSD.org) Message-Id: <201504010540.t315ePtO060917@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: eadler set sender to eadler@FreeBSD.org using -f From: Eitan Adler Date: Wed, 1 Apr 2015 05:40:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r46403 - 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-all@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 05:40:25 -0000 Author: eadler Date: Wed Apr 1 05:40:24 2015 New Revision: 46403 URL: https://svnweb.freebsd.org/changeset/doc/46403 Log: FAQ: multiple changes - don't point out bad IRC channels, just point to good ones - simplify password hashing question by presuming a modern version (and briefly mentioning 8) - combine memory limits questions into single question 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 Wed Apr 1 05:20:05 2015 (r46402) +++ head/en_US.ISO8859-1/books/faq/book.xml Wed Apr 1 05:40:24 2015 (r46403) @@ -971,9 +971,7 @@ Channel #FreeBSDhelp on EFNet - is a channel dedicated to helping &os; users. They - are much more sympathetic to questions than - #FreeBSD is. + is a channel dedicated to helping &os; users. @@ -1345,11 +1343,9 @@ - &os; 7 and 8 use MD5 password hashing by default. - Recent versions of &os; use SHA512 by - default. These are believed to be more secure than the - traditional &unix; password format, which used a scheme - based on the DES algorithm. DES + versions of &os; (past &os; 8) use + SHA512 by + default. DES passwords are still available for backwards compatibility with legacy operating systems which still use the less secure password format. &os; also supports @@ -1365,25 +1361,6 @@ - - What are the limits for memory? - - - - 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;. - - &os;/pc98 has a limit of 4 GB memory, and PAE can - not be used with it. Other architectures supported by - &os; have much higher theoretical limits on maximum memory - (many terabytes). - - - - What are the limits for FFS file systems? @@ -1440,11 +1417,8 @@ - Yes, &rel.head.releng; users can set - WITH_BSDCONFIG in - /etc/src.conf. Users of &rel.relx; - and higher may also install - sysutils/bsdconfig. + Yes. bsdconfig provides a + nice interface to configure &os; post-installation. @@ -1485,13 +1459,14 @@ - Does &os; support more than 4 GB of memory + What are the limits for memory? Does &os; support + more than 4 GB of memory (RAM)? More than 16 GB? More than 48 GB? - Yes. &os; as an operating system generally supports + &os; as an operating system generally supports as much physical memory (RAM) as the platform it is running on does. Keep in mind that different platforms have different limits for memory; for example &i386; @@ -1699,22 +1674,15 @@ - Which CD-ROM drives are supported by &os;? + Which CD-ROM and CD-RW drives are supported by + &os;? Any SCSI drive connected to a supported controller is supported. Most ATAPI compatible IDE CD-ROMs are supported. - - - - - Which CD-RW drives are supported by &os;? - - - &os; supports any ATAPI-compatible IDE CD-R or CD-RW drive. See &man.burncd.8; for details. @@ -1915,12 +1883,8 @@ bindkey ^[[3~ delete-char # for xterm

On a 32-bit version of &os;, the memory appears lost, since it will be remapped above 4 GB, which a 32-bit kernel is unable to access. In this case, the solution is - to build a PAE enabled kernel. See the entry on memory - limits and about different memory - limits on different platforms for more - information. + to build a PAE enabled kernel. See + the entry on memory limits for more information. On a 64-bit version of &os;, or when running a PAE-enabled kernel, &os; will correctly detect and remap