From owner-p4-projects@FreeBSD.ORG Thu Feb 17 20:59:35 2011 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 24B261065695; Thu, 17 Feb 2011 20:59:35 +0000 (UTC) Delivered-To: perforce@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2D6A1065670 for ; Thu, 17 Feb 2011 20:59:34 +0000 (UTC) (envelope-from remko@freebsd.org) Received: from skunkworks.freebsd.org (skunkworks.freebsd.org [IPv6:2001:4f8:fff6::2d]) by mx1.freebsd.org (Postfix) with ESMTP id AF1358FC33 for ; Thu, 17 Feb 2011 20:59:34 +0000 (UTC) Received: from skunkworks.freebsd.org (localhost [127.0.0.1]) by skunkworks.freebsd.org (8.14.4/8.14.4) with ESMTP id p1HKxYRZ079817 for ; Thu, 17 Feb 2011 20:59:34 GMT (envelope-from remko@freebsd.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id p1HKxYnB079814 for perforce@freebsd.org; Thu, 17 Feb 2011 20:59:34 GMT (envelope-from remko@freebsd.org) Date: Thu, 17 Feb 2011 20:59:34 GMT Message-Id: <201102172059.p1HKxYnB079814@skunkworks.freebsd.org> X-Authentication-Warning: skunkworks.freebsd.org: perforce set sender to remko@freebsd.org using -f From: Remko Lodder To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 188897 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2011 20:59:35 -0000 http://p4web.freebsd.org/@@188897?ac=10 Change 188897 by remko@remko_macosx on 2011/02/17 20:59:14 MFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#33 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#16 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/x11/chapter.sgml#20 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/x11/chapter.sgml#35 integrate .. //depot/projects/docproj_nl/www/en/gnome/news.xml#8 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#33 (text+ko) ==== @@ -9,7 +9,7 @@ The &os; Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.290 2010/07/31 10:39:08 pgj Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.291 2011/02/17 15:43:01 ryusuke Exp $ 1999 @@ -24,6 +24,7 @@ 2008 2009 2010 + 2011 The FreeBSD Documentation Project @@ -126,7 +127,6 @@ Noteworthy CVSup Tags - RELENG_6 (6.X-STABLE), RELENG_7 (7.X-STABLE), RELENG_8 (8.X-STABLE), HEAD (-CURRENT) @@ -137,7 +137,6 @@ Noteworthy SVN Branches - stable/6 (6.X-STABLE), stable/7 (7.X-STABLE), stable/8 (8.X-STABLE), head (-CURRENT) @@ -2071,7 +2070,7 @@ fixes, etc.) In other words, apply common sense. Changes to the security branches - (for example, RELENG_6_0) must be + (for example, RELENG_7_0) must be approved by a member of the &a.security-officer;, or in some cases, by a member of the &a.re;. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#16 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -631,35 +631,87 @@ - Prepare the Memory Stick + Write The Image File to the Memory Stick + + + Using FreeBSD To Write the Image + + + The example below + lists /dev/da0 as the + target device from which you will be booting. Be very careful + that you have the correct device as the output target, or you + may destroy your existing data. + + + Set the kern.geom.debugflags sysctl to be + able to write a master boot record to the target device. + + + The example below + lists /dev/da0 as the + target device where the image will be written. Be very careful + that you have the correct device as the output target, or you + may destroy your existing data. + + + + Writing the Image with &man.dd.1; + + Set the kern.geom.debugflags sysctl to + be able to write a master boot record to the target + device. + + &prompt.root; sysctl kern.geom.debugflags=16 + + The .img file + is not a regular file you copy to the + memory stick. It is an image of the complete contents of the + disk. This means that you cannot simply + copy files from one disk to another. Instead, you must use + &man.dd.1; to write the image directly to the disk: + + &prompt.root; dd if=&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k + + - - The example below lists - /dev/da0 as the target device from - which you will be booting. Be very careful that you - have the correct device as the output target, or you may - destroy your existing data. - + + Using &windows; To Write the Image - Set the kern.geom.debugflags sysctl - to be able to write a master boot record to the target - device. + + The example below + lists H: as the drive + letter of the device where the image will be written. Be very + careful that you have the correct device as the output target, + or you may destroy existing data. + - &prompt.root; sysctl kern.geom.debugflags=16 - + + Obtaining <application>Image Writer for Windows</application> - - Write the Image File to the Memory Stick + Image Writer for Windows is a + free application that can correctly write an image file to a + memory stick. Download it + from + and extract it into a folder. + - The .img file is - not a regular file you copy to the - memory stick. It is an image of the complete contents of - the disk. This means that you cannot - simply copy files from one disk to another. Instead, you - must use &man.dd.1; to write the image directly to the - disk: + + Writing The Image with Image Writer - &prompt.root; dd if=&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k + Double-click + the Win32DiskImager icon to start + the program. Verify that the drive letter shown + under Device is the drive + with the memory stick. Click the folder icon and select the + image to be written to the memory stick. + Click Save to accept the image file + name. Verify that everything is correct, and that no folders + on the memory stick are open in other windows. Finally, + click Write to write the image file to + the drive. + + ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/x11/chapter.sgml#20 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -1407,7 +1407,7 @@ proc /proc procfs rw 0 0 to /etc/fstab to mount - procfs automatically during + &man.procfs.5; automatically during startup. Once GNOME is installed, ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/x11/chapter.sgml#35 (text+ko) ==== @@ -1,9 +1,9 @@ @@ -1503,8 +1503,7 @@ proc /proc procfs rw 0 0 toe aan /etc/fstab om - procfs automatisch te koppelen - tijdens het opstarten. + &man.procfs.5; automatisch te koppelen tijdens het opstarten. Zodra GNOME geïnstalleerd is, moet de X server verteld worden dat in plaats van de ==== //depot/projects/docproj_nl/www/en/gnome/news.xml#8 (text+ko) ==== @@ -19,7 +19,7 @@ - $FreeBSD: www/en/gnome/news.xml,v 1.154 2010/11/20 23:23:37 ryusuke Exp $ + $FreeBSD: www/en/gnome/news.xml,v 1.155 2011/02/16 13:04:43 bland Exp $ @@ -34,7 +34,7 @@ Announcing GNOME 2.32.1 for FreeBSD! -

Presenting GNOME 2.32.1 for FreeBSD. The offical release +

Presenting GNOME 2.32.1 for FreeBSD. The official release notes for this release can be found at http://library.gnome.org/misc/release-notes/2.32/

@@ -82,7 +82,7 @@ Announcing GNOME 2.30.1. for FreeBSD! -

Presenting GNOME 2.30.1 for FreeBSD. The offical release +

Presenting GNOME 2.30.1 for FreeBSD. The official release notes for this release can be found at http://library.gnome.org/misc/release-notes/2.30/

@@ -107,7 +107,7 @@ and myself.

The FreeBSD GNOME Team would like to thank Anders F Bjorklund for - doing the initual packagekit porting.

+ doing the initial packagekit porting.

And the following contributors and testers for there help with this release:

@@ -548,7 +548,7 @@ and ports and packages - are available for everyone's faorite operating system. This + are available for everyone's favorite operating system. This release is a polishing of 2.18.0, so expect a more stable, nicer looking desktop experience. On top of that, some of our users have also submitted