FreeBSD is a registered trademark of
the FreeBSD Foundation.
Intel, Celeron, EtherExpress, i386,
i486, Itanium, Pentium, and Xeon are trademarks or registered
@@ -13,7 +13,7 @@
as trademarks. Where those designations appear in this document,
and the FreeBSD Project was aware of the trademark claim, the
designations have been followed by the “™” or the
- “®” symbol.
Last modified on 2014-08-27 by gjb.
Abstract
This document lists errata items for FreeBSD 10.0-RELEASE,
+ “®” symbol.
Last modified on 2014-09-09 by gjb.
Abstract
This document lists errata items for FreeBSD 10.0-RELEASE,
containing significant information discovered after the
release or too late in the release cycle to be otherwise
included in the release documentation. This information
@@ -43,7 +43,7 @@
handling
FreeBSD/i386 10.0-RELEASE running as a guest
operating system on VirtualBox
can have a problem with disk I/O access. It depends on some
specific hardware configuration and does not depend on a
Modified: head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html
==============================================================================
--- head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html Tue Sep 9 15:51:33 2014 (r45579)
+++ head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html Tue Sep 9 17:53:48 2014 (r45580)
@@ -1,5 +1,5 @@
-
FreeBSD is a registered trademark of
the FreeBSD Foundation.
Intel, Celeron, EtherExpress, i386,
@@ -14,7 +14,7 @@
as trademarks. Where those designations appear in this document,
and the FreeBSD Project was aware of the trademark claim, the
designations have been followed by the “™” or the
- “®” symbol.
Last modified on 2014-07-08 by gjb.
Abstract
This document lists errata items for FreeBSD 9.3-RELEASE,
+ “®” symbol.
Last modified on 2014-09-09 by gjb.
Abstract
This document lists errata items for FreeBSD 9.3-RELEASE,
containing significant information discovered after the release
or too late in the release cycle to be otherwise included in the
release documentation.
@@ -38,7 +38,7 @@
the snapshot).
Problems described in the following security advisories have
been fixed in 9.3-RELEASE. For more information, consult
the individual advisories available from
- http://security.FreeBSD.org/.
All users of FreeBSD 9.3-STABLE should
From owner-svn-doc-head@FreeBSD.ORG Tue Sep 9 19:08:14 2014
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 5EE7A1F3;
Tue, 9 Sep 2014 19:08:14 +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 4A5EC8DF;
Tue, 9 Sep 2014 19:08:14 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s89J8Efh032328;
Tue, 9 Sep 2014 19:08:14 GMT (envelope-from gjb@FreeBSD.org)
Received: (from gjb@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id s89J8Eso032327;
Tue, 9 Sep 2014 19:08:14 GMT (envelope-from gjb@FreeBSD.org)
Message-Id: <201409091908.s89J8Eso032327@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: gjb set sender to gjb@FreeBSD.org
using -f
From: Glen Barber
Date: Tue, 9 Sep 2014 19:08:14 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r45581 - head/en_US.ISO8859-1/htdocs/snapshots
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-1
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: Tue, 09 Sep 2014 19:08:14 -0000
Author: gjb
Date: Tue Sep 9 19:08:13 2014
New Revision: 45581
URL: http://svnweb.freebsd.org/changeset/doc/45581
Log:
We no longer build boot floppies, so remove a reference
from the snapshots page.
Sponsored by: The FreeBSD Foundation
Modified:
head/en_US.ISO8859-1/htdocs/snapshots/index.xml
Modified: head/en_US.ISO8859-1/htdocs/snapshots/index.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/snapshots/index.xml Tue Sep 9 17:53:48 2014 (r45580)
+++ head/en_US.ISO8859-1/htdocs/snapshots/index.xml Tue Sep 9 19:08:13 2014 (r45581)
@@ -64,7 +64,7 @@
The major release number will not be changed in the
main distribution for each snapshot.
- It will only be changed on the boot floppies
+ It will only be changed on the installation medium
so that you know when the snapshot was made.
These are not releases, these are snapshots,
and it is important that this distinction be preserved.
From owner-svn-doc-head@FreeBSD.ORG Wed Sep 10 00:20:28 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 A28574F1;
Wed, 10 Sep 2014 00:20:28 +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 73A0DDF3;
Wed, 10 Sep 2014 00:20:28 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8A0KS3h082581;
Wed, 10 Sep 2014 00:20:28 GMT (envelope-from gjb@FreeBSD.org)
Received: (from gjb@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8A0KSQZ082580;
Wed, 10 Sep 2014 00:20:28 GMT (envelope-from gjb@FreeBSD.org)
Message-Id: <201409100020.s8A0KSQZ082580@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: gjb set sender to gjb@FreeBSD.org
using -f
From: Glen Barber
Date: Wed, 10 Sep 2014 00:20:28 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r45582 -
head/en_US.ISO8859-1/books/porters-handbook/versions
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-1
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: Wed, 10 Sep 2014 00:20:28 -0000
Author: gjb
Date: Wed Sep 10 00:20:27 2014
New Revision: 45582
URL: http://svnweb.freebsd.org/changeset/doc/45582
Log:
Update __FreeBSD_version values after r271341
Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation
Modified:
head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml
Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Tue Sep 9 19:08:13 2014 (r45581)
+++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Wed Sep 10 00:20:27 2014 (r45582)
@@ -3859,6 +3859,13 @@
+ 804504
+ September 9, 2014
+ 8.4-STABLE after FreeBSD-SA-14:18
+ (rev 271305).
+
+
+ 900000August 22, 20099.0-CURRENT.
@@ -4437,6 +4444,13 @@
+ 903503
+ September 9, 2014
+ 9-STABLE after FreeBSD-SA-14:18
+ (rev 269687).
+
+
+ 1000000September 26, 201110.0-CURRENT.
@@ -5098,6 +5112,13 @@
+ 1000715
+ September 9, 2014
+ 10-STABLE after FreeBSD-SA-14:18
+ (rev 269686).
+
+
+ 1100000October 10, 201311.0-CURRENT
@@ -5332,6 +5353,13 @@
11.0-CURRENT after SOCK_DGRAM
bug fix (rev 269489).
+
+
+ 1100031
+ September 9, 2014
+ 11.0-CURRENT after FreeBSD-SA-14:18.openssl
+ (rev 269686).
+
From owner-svn-doc-head@FreeBSD.ORG Wed Sep 10 08:48:59 2014
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 132958EE;
Wed, 10 Sep 2014 08:48:59 +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 E7AC6F70;
Wed, 10 Sep 2014 08:48:58 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8A8mwY4020719;
Wed, 10 Sep 2014 08:48:58 GMT (envelope-from ryusuke@FreeBSD.org)
Received: (from ryusuke@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8A8mw8A020718;
Wed, 10 Sep 2014 08:48:58 GMT (envelope-from ryusuke@FreeBSD.org)
Message-Id: <201409100848.s8A8mw8A020718@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: ryusuke set sender to
ryusuke@FreeBSD.org using -f
From: Ryusuke SUZUKI
Date: Wed, 10 Sep 2014 08:48:58 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r45583 - head/ja_JP.eucJP/books/handbook/preface
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-1
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: Wed, 10 Sep 2014 08:48:59 -0000
Author: ryusuke
Date: Wed Sep 10 08:48:58 2014
New Revision: 45583
URL: http://svnweb.freebsd.org/changeset/doc/45583
Log:
- Merge the following from the English version:
r40743 -> r42896 head/ja_JP.eucJP/books/handbook/preface/preface.xml
Modified:
head/ja_JP.eucJP/books/handbook/preface/preface.xml
Modified: head/ja_JP.eucJP/books/handbook/preface/preface.xml
==============================================================================
--- head/ja_JP.eucJP/books/handbook/preface/preface.xml Wed Sep 10 00:20:27 2014 (r45582)
+++ head/ja_JP.eucJP/books/handbook/preface/preface.xml Wed Sep 10 08:48:58 2014 (r45583)
@@ -3,7 +3,7 @@
The FreeBSD Documentation Project
The FreeBSD Japanese Documentation Project
- Original revision: r40743
+ Original revision: r42896
$FreeBSD$
-->
@@ -104,13 +104,6 @@
°Å¹æ²½¤µ¤ì¤¿¥Ç¥£¥¹¥¯¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë´Ø¤¹¤ë¾ðÊó¤¬Äɲ䵤ì¤Þ¤·¤¿¡£
-
-
¤Ë¡¢
@@ -285,6 +278,16 @@
+ ,
+ &os; 9.X
+ ¤Î¥¤¥ó¥¹¥È¡¼¥ë
+
+ bsdinstall ¤òÍѤ¤¤¿
+ &os; 9.x
+ °Ê¹ß¤Î¥·¥¹¥Æ¥à¤Î¥¤¥ó¥¹¥È¡¼¥ë²áÄø¤ò°ìÄ̤ê¥æ¡¼¥¶¤Ë°ÆÆ⤷¤Æ¤¤¤Þ¤¹¡£
+
+
+ ,
&os; 8.X
¤Î¥¤¥ó¥¹¥È¡¼¥ë
@@ -296,16 +299,6 @@
- ,
- &os; 9.X
- ¤Î¥¤¥ó¥¹¥È¡¼¥ë
-
- bsdinstall ¤òÍѤ¤¤¿
- &os; 9.x
- °Ê¹ß¤Î¥·¥¹¥Æ¥à¤Î¥¤¥ó¥¹¥È¡¼¥ë²áÄø¤ò°ìÄ̤ê¥æ¡¼¥¶¤Ë°ÆÆ⤷¤Æ¤¤¤Þ¤¹¡£
-
-
- , &unix;
¤Î´ðÁÃÃμ±
@@ -452,7 +445,7 @@
:-)
@@ -48,7 +48,7 @@
The extract target is run.
- It looks for your port's distribution file (typically a
+ It looks for the port's distribution file (typically a
gzipped tarball) in
DISTDIR and unpacks it into a temporary
subdirectory specified by WRKDIR
@@ -115,7 +115,7 @@
- The above are the default actions. In addition, you can
+ The above are the default actions. In addition,
define targets
pre-something
or
@@ -124,35 +124,35 @@
scripts subdirectory, and they will be
run before or after the default actions are done.
- For example, if you have a
- post-extract target defined in your
+ For example, if there is a
+ post-extract target defined in the
Makefile, and a file
pre-build in the
scripts subdirectory, the
post-extract target will be called
- after the regular extraction actions, and the
- pre-build script will be executed before
- the default build rules are done. It is recommended that you
+ after the regular extraction actions, and
+ pre-build will be executed before
+ the default build rules are done. It is recommended to
use Makefile targets if the actions are
simple enough, because it will be easier for someone to figure
out what kind of non-default action the port requires.The default actions are done by the
- bsd.port.mk targets
- do-something.
+ do-something
+ targets from bsd.port.mk.
For example, the commands to extract a port are in the target
- do-extract. If you are not happy
- with the default target, you can fix it by redefining the
+ do-extract. If
+ the default target does not do the job right, redefine the
do-something
- target in your Makefile.
+ target in the Makefile.
- The main targets (e.g.,
+ The main targets (for example,
extract,
configure, etc.) do nothing more
than make sure all the stages up to that one are completed and
call the real targets or scripts, and they are not intended to
- be changed. If you want to fix the extraction, fix
+ be changed. to fix the extraction, fix
do-extract, but never ever change
the way extract operates!
Additionally, the target
@@ -160,8 +160,8 @@
not run by the ports infrastructure.
- Now that you understand what goes on when the user types
- make install, let us go through the
+ Now that what goes on when the user types make
+ install is better understood, let us go through the
recommended steps to create the perfect port.
@@ -172,54 +172,55 @@
(foo.tar.gz or
foo.tar.bz2) and
copy it into DISTDIR. Always use
- mainstream sources when and where you
- can.
+ mainstream sources when and where
+ possible.
- You will need to set the variable
+ Set the variable
MASTER_SITES to reflect where the original
- tarball resides. You will find convenient shorthand definitions
+ tarball resides. Shorthand definitions exist
for most mainstream sites in bsd.sites.mk.
Please use these sites—and the associated
definitions—if at all possible, to help avoid the problem
of having the same information repeated over again many times in
the source base. As these sites tend to change over time, this
- becomes a maintenance nightmare for everyone involved.
+ becomes a maintenance nightmare for everyone involved. See
+ for details.
- If you cannot find a FTP/HTTP site that is well-connected to
+ If there is no FTP/HTTP site that is well-connected to
the net, or can only find sites that have irritatingly
- non-standard formats, you might want to put a copy on a reliable
- FTP or HTTP server that you control (e.g., your home
+ non-standard formats, put a copy on a reliable
+ FTP or HTTP server (for example, a home
page).
- If you cannot find somewhere convenient and reliable to put
- the distfile we can house it ourselves on
+ If a convenient and reliable place to put
+ the distfile cannot be found, we can house it ourselves on
ftp.FreeBSD.org; however, this is the
least-preferred solution. The distfile must be placed into
~/public_distfiles/ of someone's
freefall account. Ask the person who
- commits your port to do this. This person will also set
+ commits the port to do this. This person will also set
MASTER_SITES to
MASTER_SITE_LOCAL and
MASTER_SITE_SUBDIR to their
freefall username.
- If your port's distfile changes all the time without any
+ If the port's distfile changes all the time without any
kind of version update by the author, consider putting the
- distfile on your home page and listing it as the first
- MASTER_SITES. If you can, try to talk the
+ distfile on a home page and listing it as the first
+ MASTER_SITES. Try to talk the
port author out of doing this; it really does help to establish
- some kind of source code control. Hosting your own version will
+ some kind of source code control. Hosting a specific version will
prevent users from getting
checksum mismatch errors, and also reduce
the workload of maintainers of our FTP site. Also, if there is
- only one master site for the port, it is recommended that you
- house a backup at your site and list it as the second
+ only one master site for the port, it is recommended to
+ house a backup on a home page and list it as the second
MASTER_SITES.
- If your port requires some additional `patches' that are
+ If the port requires some additional `patches' that are
available on the Internet, fetch them too and put them in
DISTDIR. Do not worry if they come from a
- site other than where you got the main source tarball, we have a
+ site other than where the main source tarball comes, we have a
way to handle these situations (see the description of PATCHFILES below).
@@ -230,24 +231,24 @@
Unpack a copy of the tarball in a private directory and make
whatever changes are necessary to get the port to compile
properly under the current version of &os;. Keep
- careful track of everything you do, as you
- will be automating the process shortly. Everything, including
- the deletion, addition, or modification of files should be
- doable using an automated script or patch file when your port is
+ careful track of steps, as they will be
+ needed to automate the process shortly. Everything, including
+ the deletion, addition, or modification of files has to be
+ doable using an automated script or patch file when the port is
finished.
- If your port requires significant user
- interaction/customization to compile or install, you should take
+ If the port requires significant user
+ interaction/customization to compile or install, take
a look at one of Larry Wall's classic
Configure scripts and perhaps do
- something similar yourself. The goal of the new ports
+ something similar. The goal of the new ports
collection is to make each port as plug-and-play
as possible for the end-user while using a minimum of disk
space.Unless explicitly stated, patch files, scripts, and other
- files you have created and contributed to the &os; ports
+ files created and contributed to the &os; ports
collection are assumed to be covered by the standard BSD
copyright conditions.
@@ -385,7 +386,7 @@
junk in there. In particular, diffs between two backup files,
Makefiles when the port uses
Imake or GNU configure,
- etc., are unnecessary and should be deleted. If it was
+ etc., are unnecessary and have to be deleted. If it was
necessary to edit configure.in and run
autoconf to regenerate
configure, do not take the diffs of
@@ -444,10 +445,10 @@ DOS2UNIX_GLOB= *.c *.cpp *.h
Configuring
- Include any additional customization commands in your
+ Include any additional customization commands in the
configure script and save it in the
scripts subdirectory. As mentioned above,
- you can also do this with Makefile targets
+ it is also possible do this with Makefile targets
and/or scripts with the name pre-configure
or post-configure.
@@ -455,10 +456,10 @@ DOS2UNIX_GLOB= *.c *.cpp *.h
Handling User Input
- If your port requires user input to build, configure, or
- install, you must set IS_INTERACTIVE in your
+ If the port requires user input to build, configure, or
+ install, set IS_INTERACTIVE in the
Makefile. This will allow
- overnight builds to skip your port if the user
+ overnight builds to skip it. If the user
sets the variable BATCH in his environment (and
if the user sets the variable INTERACTIVE, then
only those ports requiring interaction are
@@ -466,8 +467,8 @@ DOS2UNIX_GLOB= *.c *.cpp *.h
It is also recommended that if there are reasonable default
- answers to the questions, you check the
- PACKAGE_BUILDING variable and turn off the
+ answers to the questions,
+ PACKAGE_BUILDING be used to turn off the
interactive script when it is set. This will allow us to build
the packages for CDROMs and FTP.
From owner-svn-doc-head@FreeBSD.ORG Wed Sep 10 13:14:00 2014
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 741DF3A3;
Wed, 10 Sep 2014 13:14:00 +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 5DE8710BA;
Wed, 10 Sep 2014 13:14:00 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8ADE0hX054062;
Wed, 10 Sep 2014 13:14:00 GMT (envelope-from mat@FreeBSD.org)
Received: (from mat@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8ADE0IJ054059;
Wed, 10 Sep 2014 13:14:00 GMT (envelope-from mat@FreeBSD.org)
Message-Id: <201409101314.s8ADE0IJ054059@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org
using -f
From: Mathieu Arnold
Date: Wed, 10 Sep 2014 13:14:00 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r45586 -
head/en_US.ISO8859-1/books/porters-handbook/quick-porting
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-1
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: Wed, 10 Sep 2014 13:14:00 -0000
Author: mat (ports committer)
Date: Wed Sep 10 13:13:59 2014
New Revision: 45586
URL: http://svnweb.freebsd.org/changeset/doc/45586
Log:
igor -Ry and some other rewording and fixes.
Differential Revision: https://reviews.freebsd.org/D650
Reviewed by: wblock
Sponsored by: Absolight
Modified:
head/en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml
Modified: head/en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml Wed Sep 10 12:56:21 2014 (r45585)
+++ head/en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml Wed Sep 10 13:13:59 2014 (r45586)
@@ -20,7 +20,7 @@
/usr/ports/distfiles.
- The following steps assume that the software compiled
+ These steps assume that the software compiled
out-of-the-box. In other words, absolutely no changes were
required for the application to work on a &os; system. If
anything had to be changed, refer to This is not a manual or an
in-depth description on how to use or compile the port!
Please be careful when copying from the
- README or manpage; too
+ README or manpage. Too
often they are not a concise description of the port or
- are in an awkward format (e.g., manpages have justified
- spacing, which looks particularly bad with monospaced
- fonts).
+ are in an awkward format. For example, manpages have
+ justified spacing, which looks particularly bad with
+ monospaced fonts.A well-written pkg-descr describes
@@ -116,7 +116,7 @@ COMMENT= Cat chasing a mouse all over th
one of the websites (pick the most
common one) with WWW: (followed by single
space) so that automated tools will work correctly. If the
- URI is the root of the website or directory, it should be
+ URI is the root of the website or directory, it must be
terminated with a slash.
@@ -125,8 +125,8 @@ COMMENT= Cat chasing a mouse all over th
moved, was renamed, or is hosted elsewhere.
- The following example shows how the
- pkg-descr should look:
+ This example shows how
+ pkg-descr looks:This is a port of oneko, in which a cat chases a poor mouse all over
the screen.
@@ -182,8 +182,8 @@ lib/X11/oneko/mouse.xpm
PLIST_DIRS, respectively, within the
port's Makefile. For instance, we
could get along without pkg-plist in
- the above oneko port by adding the
- following lines to the Makefile:
+ the above oneko port by adding these
+ lines to the Makefile:PLIST_FILES= bin/oneko \
man/man1/oneko.1.gz \
@@ -193,12 +193,12 @@ lib/X11/oneko/mouse.xpm
lib/X11/oneko/mouse.xpm
PLIST_DIRS= lib/X11/oneko
- Of course, PLIST_DIRS should be left
- unset if a port installs no directories of its own.
+ Of course, PLIST_DIRS does not need to
+ be set if a port installs no directories of its own.Several ports can share a common directory. In that
- case, PLIST_DIRS should be replaced by
+ case, PLIST_DIRS must be replaced by
PLIST_DIRSTRY so that the directory is
removed only if empty, otherwise it is silently ignored.
PLIST_DIRS and
@@ -351,26 +351,30 @@ PLIST_DIRS= lib/X11/onekoshar `find oneko` > oneko.shar
+
- Classify the bug report as Category
- ports and Class
- change-request. Do not
- mark the report confidential! Add a short
+ To submit oneko.shar, use the bug submit
+ form (category Ports Tree).
+ Add a short
description of the program to the Description field of the PR
- (perhaps a short version of the COMMENT), and
- add the .shar file to the Fix field.
+ (perhaps a short version of COMMENT), and
+ don't forget to add oneko.shar as an
+ attachment.
- Giving a good description in the synopsis of the problem
+ Giving a good description in the summary of the problem
report makes the work of port committers a lot easier. We
prefer something like New port:
- <category>/<portname> <short description of
- the port> for new ports. Using this
+ category/portnameshort description of
+ the port for new ports. Using this
scheme makes it easier and faster to begin the work of
committing the new port.
@@ -388,7 +392,7 @@ PLIST_DIRS= lib/X11/oneko.After looking at the new port, we will reply if necessary,
- and put it in the tree. Your name will also be added to the
+ and commit it to the tree. The submitter's name will also be added to the
list of Additional
&os; Contributors and other files.
From owner-svn-doc-head@FreeBSD.ORG Wed Sep 10 17:46:08 2014
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 6EADE5AC;
Wed, 10 Sep 2014 17:46:08 +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 4FF06603;
Wed, 10 Sep 2014 17:46:08 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8AHk8Ri089763;
Wed, 10 Sep 2014 17:46:08 GMT (envelope-from gavin@FreeBSD.org)
Received: (from gavin@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8AHk87r089762;
Wed, 10 Sep 2014 17:46:08 GMT (envelope-from gavin@FreeBSD.org)
Message-Id: <201409101746.s8AHk87r089762@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: gavin set sender to
gavin@FreeBSD.org using -f
From: Gavin Atkinson
Date: Wed, 10 Sep 2014 17:46:08 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r45587 - head/en_US.ISO8859-1/htdocs/platforms
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-1
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: Wed, 10 Sep 2014 17:46:08 -0000
Author: gavin
Date: Wed Sep 10 17:46:07 2014
New Revision: 45587
URL: http://svnweb.freebsd.org/changeset/doc/45587
Log:
Update the FreeBSD/arm lplatform page to reflect the last few years of
progress. Most of this information comes from the FreeBSD/arm wiki page.
Modified:
head/en_US.ISO8859-1/htdocs/platforms/arm.xml
Modified: head/en_US.ISO8859-1/htdocs/platforms/arm.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/platforms/arm.xml Wed Sep 10 13:13:59 2014 (r45586)
+++ head/en_US.ISO8859-1/htdocs/platforms/arm.xml Wed Sep 10 17:46:07 2014 (r45587)
@@ -45,35 +45,77 @@
FreeBSD should work on the i80321 based Intel XScale®
- devboards, which includes the IQ31244 and IQ80321 boards.
- Support is still minimal, covering only the CPU, PCI-X bus,
- em(4) Ethernet adapters, the UART and timer devices.
-
-
The i80219 XScale processor is supported, as is the EP80219
- devboard.
-
-
The IXP425 is supported, as is the Avila GW2348-4 devboard.
-
-
The Atmel AT91RM9200 CPU/Microcontroller range is supported.
- Support is provided for the Kwikbyte KB9202 devboard range, the
- BWCT board and the Hot-e HL200 thin client device.
-
-
Minimal support for the StrongARM 1100 CPU is provided, but
- only within the limits of what Simics emulate: CPU, UART and
- clock. It is theoretically possible to boot on the Assabet board,
- the one Simics emulates; no attempts, successful or unsuccessful,
- have been reported.
-
-
Additionally, support for the Technologic Systems TS-7200 devboard
- is in the works, as is support for the Atmel AT91SAM926x CPU and
- the Marvell Orion ARM SoC, the Samsung S3C2XX0 range, and Cirrus
- Logic EP93XX CPUs.
+
FreeBSD/arm supports or is working on support for a large range of
+ ARM CPUs and development boards. Not every peripheral is supported on
+ every CPU or board, though work continues towards this and contributions
+ are always welcome. Conversely, many CPUs and boards not listed may
+ work with only minimal changes needed.
+
+
Listing all supported devices on all CPUs and boards is impractical here,
+ however much information can be obtained from the mailing list and
+ archives, the FreeBSD/arm
+ Wiki pages, and also from the
+ Kernel
+ Configuration files
+
+
CPUs
+
+
+
Allwinner A10/A20
+
Atmel AT91RM92 and AT91SAM9 families
+
Broadcom BCM2835 (used in Raspberry Pi)
+
Cavium CNS11xx
+
Freescale i.MX51, i.MX53, i.MX6 and Vybrid Family
+
Intel XSCALE
+
Marvell Orion, Kirkwood and Discovery Innovation families of systems-on-chip
+
Marvell Armada 500 (ARMv6) and Armada XP (ARMv7)
+
NXP LPC32x0
+
Qualcomm Snapdragon
+
Rockchip RK3188
+
Samsung Exynos5 and S3C24xxx
+
Texas Instruments DaVinci Digital Media SoC
+
TI OMAP
+
Xilinx Zynq7 family
+
+
+
Note that not all peripherals are supported on all CPUs.
+
+
Boards
+
+
+
ArndaleBoard (Samsung Exynos5250)
+
Atmel AT91RM9200
+
BeagleBoard and BeagleBoard-xM (TI OMAP3)
+
BeagleBone
+
Colibri VF50 Evaluation Board
+
Cubieboard(1,2) (Allwinner A10/A20)
+
Device Solutions Quartz
+
Gateworks Avila GW2348 and Cambria GW2358
+
Genesi Efika MX Smarttop and Smartbook
+
Globalscale Technologies OpenRD platform
+
Google Chromebook
+
Kwikbyte KB9202B (as well as the older KB9202 and KB9202A)
With FreeBSD/ARM, you can enjoy the silence from running your
- (embedded) computer. There's even a song of that name, "Enjoy
- The Silence", by Depeche Mode:
-
-
All I ever wanted
-All I ever needed
-Is here in my ARMs
-Words are very unnecessary
-They can only do harm
At the moment, several MIPS32 development boards and
- SGI's MIPS64 computers are being targeted. Other MIPS platforms
- such as common embedded boards and non-exotic computers in
- a similar configuration are expected
- to be targeted later on.
FreeBSD/MIPS is a port of the FreeBSD operating system
- to platforms based around MIPS processors.
-
-
At the moment, several MIPS32 and MIPS64 development boards
+ to platforms based around MIPS processors.
+ At the moment, several MIPS32 and MIPS64 development boards
and embedded platforms are being targeted.
-
FreeBSD/MIPS is in the early stages of development, see the
- MIPS wiki page
- for information
- about currently ongoing work.
+
Listing all supported devices on all CPUs and boards is impractical here,
+ however much information can be obtained from the mailing list and
+ archives, the FreeBSD/MIPS
+ Wiki pages, and also from the
+ Kernel
+ Configuration files
+
+
CPUs
+
+
The following non-exhaustive list of CPUs and CPU families are
+ supported:
From owner-svn-doc-head@FreeBSD.ORG Sat Sep 13 02:08:35 2014
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id A0A6538C;
Sat, 13 Sep 2014 02:08:35 +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 8935B8F5;
Sat, 13 Sep 2014 02:08:35 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8D28Z0s001721;
Sat, 13 Sep 2014 02:08:35 GMT (envelope-from wblock@FreeBSD.org)
Received: (from wblock@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8D28Y7Y001710;
Sat, 13 Sep 2014 02:08:34 GMT (envelope-from wblock@FreeBSD.org)
Message-Id: <201409130208.s8D28Y7Y001710@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: wblock set sender to
wblock@FreeBSD.org using -f
From: Warren Block
Date: Sat, 13 Sep 2014 02:08:34 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r45602 - in head/en_US.ISO8859-1/books/handbook: .
bsdinstall disks filesystems zfs
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-1
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: Sat, 13 Sep 2014 02:08:35 -0000
Author: wblock
Date: Sat Sep 13 02:08:33 2014
New Revision: 45602
URL: http://svnweb.freebsd.org/changeset/doc/45602
Log:
Finally commit the rewritten ZFS section as a new chapter. This greatly
expands the original content, mostly due to the work of Allan Jude.
Added:
head/en_US.ISO8859-1/books/handbook/zfs/
head/en_US.ISO8859-1/books/handbook/zfs/chapter.xml (contents, props changed)
Modified:
head/en_US.ISO8859-1/books/handbook/Makefile
head/en_US.ISO8859-1/books/handbook/book.xml
head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
head/en_US.ISO8859-1/books/handbook/chapters.ent
head/en_US.ISO8859-1/books/handbook/disks/chapter.xml
head/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/Makefile
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/Makefile Fri Sep 12 23:42:14 2014 (r45601)
+++ head/en_US.ISO8859-1/books/handbook/Makefile Sat Sep 13 02:08:33 2014 (r45602)
@@ -245,6 +245,7 @@ SRCS+= desktop/chapter.xml
SRCS+= disks/chapter.xml
SRCS+= eresources/chapter.xml
SRCS+= firewalls/chapter.xml
+SRCS+= zfs/chapter.xml
SRCS+= filesystems/chapter.xml
SRCS+= geom/chapter.xml
SRCS+= install/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/book.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/book.xml Fri Sep 12 23:42:14 2014 (r45601)
+++ head/en_US.ISO8859-1/books/handbook/book.xml Sat Sep 13 02:08:33 2014 (r45602)
@@ -237,6 +237,7 @@
&chap.audit;
&chap.disks;
&chap.geom;
+ &chap.zfs;
&chap.filesystems;
&chap.virtualization;
&chap.l10n;
Modified: head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Fri Sep 12 23:42:14 2014 (r45601)
+++ head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Sat Sep 13 02:08:33 2014 (r45602)
@@ -1445,7 +1445,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID
Another partition type worth noting is
freebsd-zfs, used for partitions that will
contain a &os; ZFS file system (). Refer to &man.gpart.8; for
+ linkend="zfs"/>). Refer to &man.gpart.8; for
descriptions of the available GPT partition
types.
Modified: head/en_US.ISO8859-1/books/handbook/chapters.ent
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/chapters.ent Fri Sep 12 23:42:14 2014 (r45601)
+++ head/en_US.ISO8859-1/books/handbook/chapters.ent Sat Sep 13 02:08:33 2014 (r45602)
@@ -37,6 +37,7 @@
+
Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Fri Sep 12 23:42:14 2014 (r45601)
+++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Sat Sep 13 02:08:33 2014 (r45602)
@@ -2160,7 +2160,7 @@ Filesystem 1K-blocks Used Avail Capacity
This section describes how to configure disk quotas for the
UFS file system. To configure quotas on the
ZFS file system, refer to
+ linkend="zfs-zfs-quota"/>Enabling Disk Quotas
Modified: head/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml Fri Sep 12 23:42:14 2014 (r45601)
+++ head/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml Sat Sep 13 02:08:33 2014 (r45602)
@@ -5,7 +5,7 @@
-->
- File Systems Support
+ Other File SystemsTomRhodesWritten
@@ -29,8 +29,8 @@
native &os; file system has been the Unix File System
UFS which has been modernized as
UFS2. Since &os; 7.0, the Z File
- System ZFS is also available as a native file
- system.
+ System (ZFS) is also available as a native file
+ system. See for more information.
In addition to its native file systems, &os; supports a
multitude of other file systems so that data from other
@@ -91,642 +91,6 @@
-
- The Z File System (ZFS)
-
- The Z file system, originally developed by &sun;,
- is designed to use a pooled storage method in that space is only
- used as it is needed for data storage. It is also designed for
- maximum data integrity, supporting data snapshots, multiple
- copies, and data checksums. It uses a software data replication
- model, known as RAID-Z.
- RAID-Z provides redundancy similar to
- hardware RAID, but is designed to prevent
- data write corruption and to overcome some of the limitations
- of hardware RAID.
-
-
- ZFS Tuning
-
- Some of the features provided by ZFS
- are RAM-intensive, so some tuning may be required to provide
- maximum efficiency on systems with limited RAM.
-
-
- Memory
-
- At a bare minimum, the total system memory should be at
- least one gigabyte. The amount of recommended RAM depends
- upon the size of the pool and the ZFS features which are
- used. A general rule of thumb is 1GB of RAM for every 1TB
- of storage. If the deduplication feature is used, a general
- rule of thumb is 5GB of RAM per TB of storage to be
- deduplicated. While some users successfully use ZFS with
- less RAM, it is possible that when the system is under heavy
- load, it may panic due to memory exhaustion. Further tuning
- may be required for systems with less than the recommended
- RAM requirements.
-
-
-
- Kernel Configuration
-
- Due to the RAM limitations of the &i386; platform, users
- using ZFS on the &i386; architecture should add the
- following option to a custom kernel configuration file,
- rebuild the kernel, and reboot:
-
- options KVA_PAGES=512
-
- This option expands the kernel address space, allowing
- the vm.kvm_size tunable to be pushed
- beyond the currently imposed limit of 1 GB, or the
- limit of 2 GB for PAE. To find the
- most suitable value for this option, divide the desired
- address space in megabytes by four (4). In this example, it
- is 512 for 2 GB.
-
-
-
- Loader Tunables
-
- The kmem address space can
- be increased on all &os; architectures. On a test system
- with one gigabyte of physical memory, success was achieved
- with the following options added to
- /boot/loader.conf, and the system
- restarted:
-
- vm.kmem_size="330M"
-vm.kmem_size_max="330M"
-vfs.zfs.arc_max="40M"
-vfs.zfs.vdev.cache.size="5M"
-
- For a more detailed list of recommendations for
- ZFS-related tuning, see http://wiki.freebsd.org/ZFSTuningGuide.
-
-
-
-
- Using ZFS
-
- There is a start up mechanism that allows &os; to mount
- ZFS pools during system initialization. To
- set it, issue the following commands:
-
- &prompt.root; echo 'zfs_enable="YES"' >> /etc/rc.conf
-&prompt.root; service zfs start
-
- The examples in this section assume three
- SCSI disks with the device names
- da0,
- da1,
- and da2.
- Users of IDE hardware should instead use
- ad
- device names.
-
-
- Single Disk Pool
-
- To create a simple, non-redundant ZFS
- pool using a single disk device, use
- zpool:
-
- &prompt.root; zpool create example /dev/da0
-
- To view the new pool, review the output of
- df:
-
- &prompt.root; df
-Filesystem 1K-blocks Used Avail Capacity Mounted on
-/dev/ad0s1a 2026030 235230 1628718 13% /
-devfs 1 1 0 100% /dev
-/dev/ad0s1d 54098308 1032846 48737598 2% /usr
-example 17547136 0 17547136 0% /example
-
- This output shows that the example
- pool has been created and mounted. It
- is now accessible as a file system. Files may be created
- on it and users can browse it, as seen in the following
- example:
-
- &prompt.root; cd /example
-&prompt.root; ls
-&prompt.root; touch testfile
-&prompt.root; ls -al
-total 4
-drwxr-xr-x 2 root wheel 3 Aug 29 23:15 .
-drwxr-xr-x 21 root wheel 512 Aug 29 23:12 ..
--rw-r--r-- 1 root wheel 0 Aug 29 23:15 testfile
-
- However, this pool is not taking advantage of any
- ZFS features. To create a dataset on
- this pool with compression enabled:
-
- &prompt.root; zfs create example/compressed
-&prompt.root; zfs set compression=gzip example/compressed
-
- The example/compressed dataset is now
- a ZFS compressed file system. Try
- copying some large files to
- /example/compressed.
-
- Compression can be disabled with:
-
- &prompt.root; zfs set compression=off example/compressed
-
- To unmount a file system, issue the following command
- and then verify by using df:
-
- &prompt.root; zfs umount example/compressed
-&prompt.root; df
-Filesystem 1K-blocks Used Avail Capacity Mounted on
-/dev/ad0s1a 2026030 235232 1628716 13% /
-devfs 1 1 0 100% /dev
-/dev/ad0s1d 54098308 1032864 48737580 2% /usr
-example 17547008 0 17547008 0% /example
-
- To re-mount the file system to make it accessible
- again, and verify with df:
-
- &prompt.root; zfs mount example/compressed
-&prompt.root; df
-Filesystem 1K-blocks Used Avail Capacity Mounted on
-/dev/ad0s1a 2026030 235234 1628714 13% /
-devfs 1 1 0 100% /dev
-/dev/ad0s1d 54098308 1032864 48737580 2% /usr
-example 17547008 0 17547008 0% /example
-example/compressed 17547008 0 17547008 0% /example/compressed
-
- The pool and file system may also be observed by viewing
- the output from mount:
-
- &prompt.root; mount
-/dev/ad0s1a on / (ufs, local)
-devfs on /dev (devfs, local)
-/dev/ad0s1d on /usr (ufs, local, soft-updates)
-example on /example (zfs, local)
-example/data on /example/data (zfs, local)
-example/compressed on /example/compressed (zfs, local)
-
- ZFS datasets, after creation, may be
- used like any file systems. However, many other features
- are available which can be set on a per-dataset basis. In
- the following example, a new file system,
- data is created. Important files will be
- stored here, the file system is set to keep two copies of
- each data block:
-
- &prompt.root; zfs create example/data
-&prompt.root; zfs set copies=2 example/data
-
- It is now possible to see the data and space utilization
- by issuing df:
-
- &prompt.root; df
-Filesystem 1K-blocks Used Avail Capacity Mounted on
-/dev/ad0s1a 2026030 235234 1628714 13% /
-devfs 1 1 0 100% /dev
-/dev/ad0s1d 54098308 1032864 48737580 2% /usr
-example 17547008 0 17547008 0% /example
-example/compressed 17547008 0 17547008 0% /example/compressed
-example/data 17547008 0 17547008 0% /example/data
-
- Notice that each file system on the pool has the same
- amount of available space. This is the reason for using
- df in these examples, to show that the
- file systems use only the amount of space they need and all
- draw from the same pool. The ZFS file
- system does away with concepts such as volumes and
- partitions, and allows for several file systems to occupy
- the same pool.
-
- To destroy the file systems and then destroy the pool as
- they are no longer needed:
-
- &prompt.root; zfs destroy example/compressed
-&prompt.root; zfs destroy example/data
-&prompt.root; zpool destroy example
-
-
-
-
- ZFS RAID-Z
-
- There is no way to prevent a disk from failing. One
- method of avoiding data loss due to a failed hard disk is to
- implement RAID. ZFS
- supports this feature in its pool design.
-
- To create a RAID-Z pool, issue the
- following command and specify the disks to add to the
- pool:
-
- &prompt.root; zpool create storage raidz da0 da1 da2
-
-
- &sun; recommends that the amount of devices used in
- a RAID-Z configuration is between
- three and nine. For environments requiring a single pool
- consisting of 10 disks or more, consider breaking it up
- into smaller RAID-Z groups. If only
- two disks are available and redundancy is a requirement,
- consider using a ZFS mirror. Refer to
- &man.zpool.8; for more details.
-
-
- This command creates the storage
- zpool. This may be verified using &man.mount.8; and
- &man.df.1;. This command makes a new file system in the
- pool called home:
-
- &prompt.root; zfs create storage/home
-
- It is now possible to enable compression and keep extra
- copies of directories and files using the following
- commands:
-
- &prompt.root; zfs set copies=2 storage/home
-&prompt.root; zfs set compression=gzip storage/home
-
- To make this the new home directory for users, copy the
- user data to this directory, and create the appropriate
- symbolic links:
-
- &prompt.root; cp -rp /home/* /storage/home
-&prompt.root; rm -rf /home /usr/home
-&prompt.root; ln -s /storage/home /home
-&prompt.root; ln -s /storage/home /usr/home
-
- Users should now have their data stored on the freshly
- created /storage/home. Test by
- adding a new user and logging in as that user.
-
- Try creating a snapshot which may be rolled back
- later:
-
- &prompt.root; zfs snapshot storage/home@08-30-08
-
- Note that the snapshot option will only capture a real
- file system, not a home directory or a file. The
- @ character is a delimiter used between
- the file system name or the volume name. When a user's
- home directory gets trashed, restore it with:
-
- &prompt.root; zfs rollback storage/home@08-30-08
-
- To get a list of all available snapshots, run
- ls in the file system's
- .zfs/snapshot directory. For example,
- to see the previously taken snapshot:
-
- &prompt.root; ls /storage/home/.zfs/snapshot
-
- It is possible to write a script to perform regular
- snapshots on user data. However, over time, snapshots
- may consume a great deal of disk space. The previous
- snapshot may be removed using the following command:
-
- &prompt.root; zfs destroy storage/home@08-30-08
-
- After testing, /storage/home can be
- made the real /home using this
- command:
-
- &prompt.root; zfs set mountpoint=/home storage/home
-
- Run df and
- mount to confirm that the system now
- treats the file system as the real
- /home:
-
- &prompt.root; mount
-/dev/ad0s1a on / (ufs, local)
-devfs on /dev (devfs, local)
-/dev/ad0s1d on /usr (ufs, local, soft-updates)
-storage on /storage (zfs, local)
-storage/home on /home (zfs, local)
-&prompt.root; df
-Filesystem 1K-blocks Used Avail Capacity Mounted on
-/dev/ad0s1a 2026030 235240 1628708 13% /
-devfs 1 1 0 100% /dev
-/dev/ad0s1d 54098308 1032826 48737618 2% /usr
-storage 26320512 0 26320512 0% /storage
-storage/home 26320512 0 26320512 0% /home
-
- This completes the RAID-Z
- configuration. To get status updates about the file systems
- created during the nightly &man.periodic.8; runs, issue the
- following command:
-
- &prompt.root; echo 'daily_status_zfs_enable="YES"' >> /etc/periodic.conf
-
-
-
- Recovering RAID-Z
-
- Every software RAID has a method of
- monitoring its state. The status of
- RAID-Z devices may be viewed with the
- following command:
-
- &prompt.root; zpool status -x
-
- If all pools are healthy and everything is normal, the
- following message will be returned:
-
- all pools are healthy
-
- If there is an issue, perhaps a disk has gone offline,
- the pool state will look similar to:
-
- pool: storage
- state: DEGRADED
-status: One or more devices has been taken offline by the administrator.
- Sufficient replicas exist for the pool to continue functioning in a
- degraded state.
-action: Online the device using 'zpool online' or replace the device with
- 'zpool replace'.
- scrub: none requested
-config:
-
- NAME STATE READ WRITE CKSUM
- storage DEGRADED 0 0 0
- raidz1 DEGRADED 0 0 0
- da0 ONLINE 0 0 0
- da1 OFFLINE 0 0 0
- da2 ONLINE 0 0 0
-
-errors: No known data errors
-
- This indicates that the device was previously taken
- offline by the administrator using the following
- command:
-
- &prompt.root; zpool offline storage da1
-
- It is now possible to replace
- da1 after the system has been
- powered down. When the system is back online, the following
- command may issued to replace the disk:
-
- &prompt.root; zpool replace storage da1
-
- From here, the status may be checked again, this time
- without the flag to get state
- information:
-
- &prompt.root; zpool status storage
- pool: storage
- state: ONLINE
- scrub: resilver completed with 0 errors on Sat Aug 30 19:44:11 2008
-config:
-
- NAME STATE READ WRITE CKSUM
- storage ONLINE 0 0 0
- raidz1 ONLINE 0 0 0
- da0 ONLINE 0 0 0
- da1 ONLINE 0 0 0
- da2 ONLINE 0 0 0
-
-errors: No known data errors
-
- As shown from this example, everything appears to be
- normal.
-
-
-
- Data Verification
-
- ZFS uses checksums to verify the
- integrity of stored data. These are enabled automatically
- upon creation of file systems and may be disabled using the
- following command:
-
- &prompt.root; zfs set checksum=off storage/home
-
- Doing so is not recommended as
- checksums take very little storage space and are used to
- check data integrity using checksum verification in a
- process is known as scrubbing. To verify the
- data integrity of the storage pool, issue
- this command:
-
- &prompt.root; zpool scrub storage
-
- This process may take considerable time depending on
- the amount of data stored. It is also very
- I/O intensive, so much so that only one
- scrub may be run at any given time. After the scrub has
- completed, the status is updated and may be viewed by
- issuing a status request:
-
- &prompt.root; zpool status storage
- pool: storage
- state: ONLINE
- scrub: scrub completed with 0 errors on Sat Jan 26 19:57:37 2013
-config:
-
- NAME STATE READ WRITE CKSUM
- storage ONLINE 0 0 0
- raidz1 ONLINE 0 0 0
- da0 ONLINE 0 0 0
- da1 ONLINE 0 0 0
- da2 ONLINE 0 0 0
-
-errors: No known data errors
-
- The completion time is displayed and helps to ensure
- data integrity over a long period of time.
-
- Refer to &man.zfs.8; and &man.zpool.8; for other
- ZFS options.
-
-
-
- ZFS Quotas
-
- ZFS supports different types of quotas: the refquota,
- the general quota, the user quota, and the group quota.
- This section explains the basics of each type and includes
- some usage instructions.
-
- Quotas limit the amount of space that a dataset and its
- descendants can consume, and enforce a limit on the amount
- of space used by file systems and snapshots for the
- descendants. Quotas are useful to limit the amount of space
- a particular user can use.
-
-
- Quotas cannot be set on volumes, as the
- volsize property acts as an implicit
- quota.
-
-
- The
- refquota=size
- limits the amount of space a dataset can consume by
- enforcing a hard limit on the space used. However, this
- hard limit does not include space used by descendants, such
- as file systems or snapshots.
-
- To enforce a general quota of 10 GB for
- storage/home/bob, use the
- following:
-
- &prompt.root; zfs set quota=10G storage/home/bob
-
- User quotas limit the amount of space that can be used
- by the specified user. The general format is
- userquota@user=size,
- and the user's name must be in one of the following
- formats:
-
-
-
- POSIX compatible name such as
- joe.
-
-
-
- POSIX numeric ID such as
- 789.
-
-
-
- SID name
- such as
- joe.bloggs@example.com.
-
-
-
- SID
- numeric ID such as
- S-1-123-456-789.
-
-
-
- For example, to enforce a quota of 50 GB for a user
- named joe, use the
- following:
-
- &prompt.root; zfs set userquota@joe=50G
-
- To remove the quota or make sure that one is not set,
- instead use:
-
- &prompt.root; zfs set userquota@joe=none
-
- User quota properties are not displayed by
- zfs get all.
- Non-root users can
- only see their own quotas unless they have been granted the
- userquota privilege. Users with this
- privilege are able to view and set everyone's quota.
-
- The group quota limits the amount of space that a
- specified group can consume. The general format is
- groupquota@group=size.
-
- To set the quota for the group
- firstgroup to 50 GB,
- use:
-
- &prompt.root; zfs set groupquota@firstgroup=50G
-
- To remove the quota for the group
- firstgroup, or to make sure that
- one is not set, instead use:
-
- &prompt.root; zfs set groupquota@firstgroup=none
-
- As with the user quota property,
- non-root users can
- only see the quotas associated with the groups that they
- belong to. However, root or a user with the
- groupquota privilege can view and set all
- quotas for all groups.
-
- To display the amount of space consumed by each user on
- the specified file system or snapshot, along with any
- specified quotas, use zfs userspace.
- For group information, use zfs
- groupspace. For more information about
- supported options or how to display only specific options,
- refer to &man.zfs.1;.
-
- Users with sufficient privileges and root can list the quota for
- storage/home/bob using:
-
- &prompt.root; zfs get quota storage/home/bob
-
-
-
- ZFS Reservations
-
- ZFS supports two types of space reservations. This
- section explains the basics of each and includes some usage
- instructions.
-
- The reservation property makes it
- possible to reserve a minimum amount of space guaranteed
- for a dataset and its descendants. This means that if a
- 10 GB reservation is set on
- storage/home/bob, if disk
- space gets low, at least 10 GB of space is reserved
- for this dataset. The refreservation
- property sets or indicates the minimum amount of space
- guaranteed to a dataset excluding descendants, such as
- snapshots. As an example, if a snapshot was taken of
- storage/home/bob, enough disk space
- would have to exist outside of the
- refreservation amount for the operation
- to succeed because descendants of the main data set are
- not counted by the refreservation
- amount and so do not encroach on the space set.
-
- Reservations of any sort are useful in many situations,
- such as planning and testing the suitability of disk space
- allocation in a new system, or ensuring that enough space is
- available on file systems for system recovery procedures and
- files.
-
- The general format of the reservation
- property is
- reservation=size,
- so to set a reservation of 10 GB on
- storage/home/bob, use:
-
- &prompt.root; zfs set reservation=10G storage/home/bob
-
- To make sure that no reservation is set, or to remove a
- reservation, use:
-
- &prompt.root; zfs set reservation=none storage/home/bob
-
- The same principle can be applied to the
- refreservation property for setting a
- refreservation, with the general format
- refreservation=size.
-
- To check if any reservations or refreservations exist on
- storage/home/bob, execute one of the
- following commands:
-
- &prompt.root; zfs get reservation storage/home/bob
-&prompt.root; zfs get refreservation storage/home/bob
-
-
-
-
&linux; File Systems
Added: head/en_US.ISO8859-1/books/handbook/zfs/chapter.xml
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Sat Sep 13 02:08:33 2014 (r45602)
@@ -0,0 +1,4332 @@
+
+
+
+
+
+
+ The Z File System (ZFS)
+
+
+
+
+ Tom
+ Rhodes
+
+ Written by
+
+
+
+ Allan
+ Jude
+
+ Written by
+
+
+
+ Benedict
+ Reuschling
+
+ Written by
+
+
+
+ Warren
+ Block
+
+ Written by
+
+
+
+
+ The Z File System, or
+ ZFS, is an advanced file system designed to
+ overcome many of the major problems found in previous
+ designs.
+
+ Originally developed at &sun;, ongoing open source
+ ZFS development has moved to the OpenZFS Project.
+
+ ZFS has three major design goals:
+
+
+
+ Data integrity: All data includes a
+ checksum of the data.
+ When data is written, the checksum is calculated and written
+ along with it. When that data is later read back, the
+ checksum is calculated again. If the checksums do not match,
+ a data error has been detected. ZFS will
+ attempt to automatically correct errors when data redundancy
+ is available.
+
+
+
+ Pooled storage: physical storage devices are added to a
+ pool, and storage space is allocated from that shared pool.
+ Space is available to all file systems, and can be increased
+ by adding new storage devices to the pool.
+
+
+
+ Performance: multiple caching mechanisms provide increased
+ performance. ARC is an
+ advanced memory-based read cache. A second level of
+ disk-based read cache can be added with
+ L2ARC, and disk-based
+ synchronous write cache is available with
+ ZIL.
+
+
+
+ A complete list of features and terminology is shown in
+ .
+
+
+ What Makes ZFS Different
+
+ ZFS is significantly different from any
+ previous file system because it is more than just a file system.
+ Combining the traditionally separate roles of volume manager and
+ file system provides ZFS with unique
+ advantages. The file system is now aware of the underlying
+ structure of the disks. Traditional file systems could only be
+ created on a single disk at a time. If there were two disks
+ then two separate file systems would have to be created. In a
+ traditional hardware RAID configuration, this
+ problem was avoided by presenting the operating system with a
+ single logical disk made up of the space provided by a number of
+ physical disks, on top of which the operating system placed a
+ file system. Even in the case of software
+ RAID solutions like those provided by
+ GEOM, the UFS file system
+ living on top of the RAID transform believed
+ that it was dealing with a single device.
+ ZFS's combination of the volume manager and
+ the file system solves this and allows the creation of many file
+ systems all sharing a pool of available storage. One of the
+ biggest advantages to ZFS's awareness of the
+ physical layout of the disks is that existing file systems can
+ be grown automatically when additional disks are added to the
+ pool. This new space is then made available to all of the file
+ systems. ZFS also has a number of different
+ properties that can be applied to each file system, giving many
+ advantages to creating a number of different file systems and
+ datasets rather than a single monolithic file system.
+
+
+
+ Quick Start Guide
+
+ There is a startup mechanism that allows &os; to mount
+ ZFS pools during system initialization. To
+ enable it, add this line to
+ /etc/rc.conf:
+
+ zfs_enable="YES"
+
+ Then start the service:
+
+ &prompt.root; service zfs start
+
+ The examples in this section assume three
+ SCSI disks with the device names
+ da0,
+ da1, and
+ da2. Users
+ of SATA hardware should instead use
+ ada device
+ names.
+
+
+ Single Disk Pool
+
+ To create a simple, non-redundant pool using a single
+ disk device:
+
+ &prompt.root; zpool create example/dev/da0
+
+ To view the new pool, review the output of
+ df:
+
+ &prompt.root; df
+Filesystem 1K-blocks Used Avail Capacity Mounted on
+/dev/ad0s1a 2026030 235230 1628718 13% /
+devfs 1 1 0 100% /dev
+/dev/ad0s1d 54098308 1032846 48737598 2% /usr
+example 17547136 0 17547136 0% /example
+
+ This output shows that the example pool
+ has been created and mounted. It is now accessible as a file
+ system. Files can be created on it and users can browse
+ it:
+
+ &prompt.root; cd /example
+&prompt.root; ls
+&prompt.root; touch testfile
+&prompt.root; ls -al
+total 4
+drwxr-xr-x 2 root wheel 3 Aug 29 23:15 .
+drwxr-xr-x 21 root wheel 512 Aug 29 23:12 ..
+-rw-r--r-- 1 root wheel 0 Aug 29 23:15 testfile
+
+ However, this pool is not taking advantage of any
+ ZFS features. To create a dataset on this
+ pool with compression enabled:
+
+ &prompt.root; zfs create example/compressed
+&prompt.root; zfs set compression=gzip example/compressed
+
+ The example/compressed dataset is now a
+ ZFS compressed file system. Try copying
+ some large files to
+ /example/compressed.
+
+ Compression can be disabled with:
+
+ &prompt.root; zfs set compression=off example/compressed
+
+ To unmount a file system, use
+ zfs umount and then verify with
+ df:
+
+ &prompt.root; zfs umount example/compressed
+&prompt.root; df
+Filesystem 1K-blocks Used Avail Capacity Mounted on
+/dev/ad0s1a 2026030 235232 1628716 13% /
+devfs 1 1 0 100% /dev
+/dev/ad0s1d 54098308 1032864 48737580 2% /usr
+example 17547008 0 17547008 0% /example
+
+ To re-mount the file system to make it accessible again,
+ use zfs mount and verify with
+ df:
+
+ &prompt.root; zfs mount example/compressed
+&prompt.root; df
+Filesystem 1K-blocks Used Avail Capacity Mounted on
+/dev/ad0s1a 2026030 235234 1628714 13% /
+devfs 1 1 0 100% /dev
+/dev/ad0s1d 54098308 1032864 48737580 2% /usr
+example 17547008 0 17547008 0% /example
+example/compressed 17547008 0 17547008 0% /example/compressed
+
+ The pool and file system may also be observed by viewing
+ the output from mount:
+
+ &prompt.root; mount
+/dev/ad0s1a on / (ufs, local)
+devfs on /dev (devfs, local)
+/dev/ad0s1d on /usr (ufs, local, soft-updates)
+example on /example (zfs, local)
+example/data on /example/data (zfs, local)
+example/compressed on /example/compressed (zfs, local)
+
+ After creation, ZFS datasets can be
+ used like any file systems. However, many other features are
+ available which can be set on a per-dataset basis. In the
+ example below, a new file system called
+ data is created. Important files will be
+ stored here, so it is configured to keep two copies of each
+ data block:
+
+ &prompt.root; zfs create example/data
+&prompt.root; zfs set copies=2 example/data
+
+ It is now possible to see the data and space utilization
+ by issuing df:
+
+ &prompt.root; df
+Filesystem 1K-blocks Used Avail Capacity Mounted on
+/dev/ad0s1a 2026030 235234 1628714 13% /
+devfs 1 1 0 100% /dev
+/dev/ad0s1d 54098308 1032864 48737580 2% /usr
+example 17547008 0 17547008 0% /example
+example/compressed 17547008 0 17547008 0% /example/compressed
+example/data 17547008 0 17547008 0% /example/data
+
+ Notice that each file system on the pool has the same
+ amount of available space. This is the reason for using
+ df in these examples, to show that the file
+ systems use only the amount of space they need and all draw
+ from the same pool. ZFS eliminates
+ concepts such as volumes and partitions, and allows multiple
+ file systems to occupy the same pool.
+
+ To destroy the file systems and then destroy the pool as
+ it is no longer needed:
+
+ &prompt.root; zfs destroy example/compressed
+&prompt.root; zfs destroy example/data
+&prompt.root; zpool destroy example
+
+
+
+ RAID-Z
+
+ Disks fail. One method of avoiding data loss from disk
+ failure is to implement RAID.
+ ZFS supports this feature in its pool
+ design. RAID-Z pools require three or more
+ disks but provide more usable space than mirrored
+ pools.
+
+ This example creates a RAID-Z pool,
+ specifying the disks to add to the pool:
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
From owner-svn-doc-head@FreeBSD.ORG Sat Sep 13 07:10:21 2014
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id D50735D6;
Sat, 13 Sep 2014 07:10:21 +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 BFF12772;
Sat, 13 Sep 2014 07:10:21 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8D7AL0P043595;
Sat, 13 Sep 2014 07:10:21 GMT (envelope-from ryusuke@FreeBSD.org)
Received: (from ryusuke@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8D7ALxH043594;
Sat, 13 Sep 2014 07:10:21 GMT (envelope-from ryusuke@FreeBSD.org)
Message-Id: <201409130710.s8D7ALxH043594@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: ryusuke set sender to
ryusuke@FreeBSD.org using -f
From: Ryusuke SUZUKI
Date: Sat, 13 Sep 2014 07:10:21 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r45603 - head/ja_JP.eucJP/books/handbook/bsdinstall
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-1
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: Sat, 13 Sep 2014 07:10:22 -0000
Author: ryusuke
Date: Sat Sep 13 07:10:21 2014
New Revision: 45603
URL: http://svnweb.freebsd.org/changeset/doc/45603
Log:
- Merge the following from the English version:
r43689 -> r44241 head/ja_JP.eucJP/books/handbook/bsdinstall/chapter.xml
Modified:
head/ja_JP.eucJP/books/handbook/bsdinstall/chapter.xml
Modified: head/ja_JP.eucJP/books/handbook/bsdinstall/chapter.xml
==============================================================================
--- head/ja_JP.eucJP/books/handbook/bsdinstall/chapter.xml Sat Sep 13 02:08:33 2014 (r45602)
+++ head/ja_JP.eucJP/books/handbook/bsdinstall/chapter.xml Sat Sep 13 07:10:21 2014 (r45603)
@@ -482,7 +482,7 @@
¥á¥â¥ê¥¹¥Æ¥£¥Ã¥¯¤Î¥¤¥á¡¼¥¸¤Î¼èÆÀ&os; 9.0-RELEASE °Ê¹ß¤Î¥á¥â¥ê¥¹¥Æ¥£¥Ã¥¯¤Î¥¤¥á¡¼¥¸¤Ï¡¢
- ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/arch/arch/ISO-IMAGES/version/&os;-version-RELEASE-arch-memstick.img
+ ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/arch/arch/ISO-IMAGES/version/&os;-version-RELEASE-arch-memstick.img.
¤Î ISO-IMAGES/
¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¥À¥¦¥ó¥í¡¼¥É¤Ç¤¤Þ¤¹¡£
¤³¤³¤Ç¡¢arch ¤È
@@ -538,7 +538,7 @@
¤Ç¤¤Þ¤»¤ó¡£&man.dd.1;
¤ò»ÈÍѤ·¤ÆľÀÜ¥¿¡¼¥²¥Ã¥È¥Ç¥£¥¹¥¯¤Ë½ñ¤¹þ¤àɬÍפ¬¤¢¤ê¤Þ¤¹¡£
- &prompt.root; dd if=&os;-9.0-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k
+ &prompt.root; dd if=&os;-9.0-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k
@@ -1950,10 +1950,12 @@ Trying to mount root from cd9660:/dev/is
DNS)
¥ê¥¾¥ë¥Ð¤Ï¡¢¥Û¥¹¥È̾¤È¥Í¥Ã¥È¥ï¡¼¥¯¥¢¥É¥ì¥¹¤òÊÑ´¹¤·¤Þ¤¹¡£
¤¹¤Ç¤Ë DHCP ¤Þ¤¿¤Ï SLAAC
- ¤ò¥Í¥Ã¥È¥ï¡¼¥¯¤Î¼«Æ°ÀßÄê¤Ë»È¤Ã¤¿¤Î¤Ç¤¢¤ì¤Ð¡¢
- ¥ê¥¾¥ë¥Ð¤ÎÀßÄê¤Ï¤¹¤Ç¤Ë¹Ô¤ï¤ì¤Æ¤¤¤Þ¤¹¡£¤½¤¦¤Ç¤Ê¤±¤ì¤Ð¡¢Search
+ ¤ò»È¤Ã¤Æ¼«Æ°Åª¤Ë¥Í¥Ã¥È¥ï¡¼¥¯¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤òÀßÄꤷ¤¿¤Î¤Ç¤¢¤ì¤Ð¡¢
+ Resolver Configuration
+ ¤Ë¤ÏÃͤ¬¤¹¤Ç¤ËÆþ¤Ã¤Æ¤¤¤ë¤Ç¤·¤ç¤¦¡£
+ ¤½¤¦¤Ç¤Ê¤±¤ì¤Ð¡¢Search
¥Õ¥£¡¼¥ë¥É¤Ë¥í¡¼¥«¥ë¥Í¥Ã¥È¥ï¡¼¥¯¤Î¥É¥á¥¤¥ó̾¤òÆþÎϤ·¤Æ¤¯¤À¤µ¤¤¡£
- DNS #1 ¤ª¤è¤Ó DNS #2 ¤Ï¡¢
+ DNS #1 ¤ª¤è¤Ó DNS #2 ¤Ï¡¢
¥í¡¼¥«¥ë DNS ¥µ¡¼¥Ð¤Î IP ¥¢¥É¥ì¥¹¤Ç¤¹¡£
¾¯¤Ê¤¯¤È¤â¡¢1 ¤Ä¤Î DNS ¥µ¡¼¥Ð¤ÏɬÍפǤ¹¡£
@@ -2179,7 +2181,7 @@ Trying to mount root from cd9660:/dev/is
- Invite user into
+ Invite user into
other groups? -
¥æ¡¼¥¶¤òÊ̤Υ°¥ë¡¼¥×¤Î¥á¥ó¥Ð¡¼¤È¤·¤ÆÄɲ乤뤫¤É¤¦¤«¡£
@@ -2208,17 +2210,17 @@ Trying to mount root from cd9660:/dev/is
Use password-based authentication? -
- Ä̾ï¤Ï "yes" ¤Ç¤¹¡£
+ Ä̾ï¤Ï yes ¤Ç¤¹¡£
Use an empty password? -
- Ä̾ï¤Ï "no" ¤Ç¤¹¡£
+ Ä̾ï¤Ï no ¤Ç¤¹¡£
Use a random password? -
- Ä̾ï¤Ï "no" ¤Ç¤¹¡£
+ Ä̾ï¤Ï no ¤Ç¤¹¡£
@@ -2234,7 +2236,7 @@ Trying to mount root from cd9660:/dev/is
Lock out the account after creation?
- - Ä̾ï¤Ï "no" ¤Ç¤¹¡£
+ - Ä̾ï¤Ï no ¤Ç¤¹¡£
@@ -2256,7 +2258,7 @@ Trying to mount root from cd9660:/dev/is
¤µ¤é¤Ë¥æ¡¼¥¶¤òÄɲ乤ë¤Î¤Ç¤¢¤ì¤Ð¡¢
- "Add another user?" ¤Î¼ÁÌä¤ËÂФ·¡¢
+ Add another user? ¤Î¼ÁÌä¤ËÂФ·¡¢
yes ¤òÆþÎϤ·¤Æ¤¯¤À¤µ¤¤¡£
no ¤òÆþÎϤ¹¤ë¤È¡¢¥æ¡¼¥¶¤ÎÄɲ䬽ª¤ï¤ê¡¢¼¡¤Ë¿Ê¤ß¤Þ¤¹¡£
From owner-svn-doc-head@FreeBSD.ORG Sat Sep 13 07:17:02 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 F0AD9682;
Sat, 13 Sep 2014 07:17:01 +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 DBD04795;
Sat, 13 Sep 2014 07:17:01 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8D7H11v045779;
Sat, 13 Sep 2014 07:17:01 GMT (envelope-from ryusuke@FreeBSD.org)
Received: (from ryusuke@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8D7H1MH045778;
Sat, 13 Sep 2014 07:17:01 GMT (envelope-from ryusuke@FreeBSD.org)
Message-Id: <201409130717.s8D7H1MH045778@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: ryusuke set sender to
ryusuke@FreeBSD.org using -f
From: Ryusuke SUZUKI
Date: Sat, 13 Sep 2014 07:17:01 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r45604 - head/ja_JP.eucJP/htdocs
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-1
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: Sat, 13 Sep 2014 07:17:02 -0000
Author: ryusuke
Date: Sat Sep 13 07:17:01 2014
New Revision: 45604
URL: http://svnweb.freebsd.org/changeset/doc/45604
Log:
- Merge the following from the English version:
r45134 -> r45569 head/ja_JP.eucJP/htdocs/index.xsl
Modified:
head/ja_JP.eucJP/htdocs/index.xsl
Modified: head/ja_JP.eucJP/htdocs/index.xsl
==============================================================================
--- head/ja_JP.eucJP/htdocs/index.xsl Sat Sep 13 07:10:21 2014 (r45603)
+++ head/ja_JP.eucJP/htdocs/index.xsl Sat Sep 13 07:17:01 2014 (r45604)
@@ -5,7 +5,7 @@
]>
-
+
The
+ href="https://www.freebsdfoundation.org/documents/Guidelines.shtml">The
FreeBSD Foundation.
&header2.word.contact;
From owner-svn-doc-head@FreeBSD.ORG Sat Sep 13 17:56:40 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 E0133993;
Sat, 13 Sep 2014 17:56:40 +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 CADAD63C;
Sat, 13 Sep 2014 17:56:40 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8DHuehd051673;
Sat, 13 Sep 2014 17:56:40 GMT (envelope-from gavin@FreeBSD.org)
Received: (from gavin@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8DHues6051672;
Sat, 13 Sep 2014 17:56:40 GMT (envelope-from gavin@FreeBSD.org)
Message-Id: <201409131756.s8DHues6051672@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: gavin set sender to
gavin@FreeBSD.org using -f
From: Gavin Atkinson
Date: Sat, 13 Sep 2014 17:56:40 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r45605 - head/en_US.ISO8859-1/htdocs/platforms
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-1
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: Sat, 13 Sep 2014 17:56:41 -0000
Author: gavin
Date: Sat Sep 13 17:56:40 2014
New Revision: 45605
URL: http://svnweb.freebsd.org/changeset/doc/45605
Log:
Like ARM, note that not all available peripherals may be supported on mips.
Modified:
head/en_US.ISO8859-1/htdocs/platforms/mips.xml
Modified: head/en_US.ISO8859-1/htdocs/platforms/mips.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/platforms/mips.xml Sat Sep 13 07:17:01 2014 (r45604)
+++ head/en_US.ISO8859-1/htdocs/platforms/mips.xml Sat Sep 13 17:56:40 2014 (r45605)
@@ -65,6 +65,8 @@
NetLogic XLR/XLS CPU family
+
Note that not all peripherals are supported on all CPUs.
+
Boards
The following boards are supported:
@@ -92,6 +94,8 @@
Cavium development boards CN5860-EVB-NIC4, CN5650-EVB-NIC16, CN5200-EVB-MB4
+
Note that not all peripherals are supported on all boards.