From owner-p4-projects@FreeBSD.ORG Sun Aug 1 16:28:09 2010 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 94C0B106567A; Sun, 1 Aug 2010 16:28:09 +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 5833F106564A for ; Sun, 1 Aug 2010 16:28:09 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id 436868FC16 for ; Sun, 1 Aug 2010 16:28:09 +0000 (UTC) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.4/8.14.4) with ESMTP id o71GS9Hv010957 for ; Sun, 1 Aug 2010 16:28:09 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.4/8.14.4/Submit) id o71GS8UV010955 for perforce@freebsd.org; Sun, 1 Aug 2010 16:28:08 GMT (envelope-from rene@FreeBSD.org) Date: Sun, 1 Aug 2010 16:28:08 GMT Message-Id: <201008011628.o71GS8UV010955@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 181686 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: Sun, 01 Aug 2010 16:28:09 -0000 http://p4web.freebsd.org/@@181686?ac=10 Change 181686 by rene@rene_acer on 2010/08/01 16:27:47 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/casestudy-argentina.com/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#32 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#65 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#48 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/cups/article.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/euro/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/ldap-auth/article.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/linux-comparison/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/linux-emulation/article.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/linux-users/article.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#25 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/problem-reports/article.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/releng-packages/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/serial-uart/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/storage-devices/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#28 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#10 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml#11 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#7 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml#14 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#32 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#19 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#83 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#41 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/articles/solid-state/article.sgml#17 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#35 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.sgml#20 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/install/chapter.sgml#13 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mirrors/chapter.sgml#53 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/x11/chapter.sgml#28 integrate .. //depot/projects/docproj_nl/share/images/articles/releng/branches-releng8.pic#2 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/install/config-country.scr#2 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/install/dist-set.scr#2 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/install/dist-set2.scr#2 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/install/docmenu1.scr#2 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/install/main-doc.scr#2 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/install/main-keymap.scr#2 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/install/main-options.scr#2 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/install/main-std.scr#2 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/install/main1.scr#2 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/install/media.scr#2 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/install/options.scr#2 integrate .. //depot/projects/docproj_nl/share/images/books/handbook/install/sysinstall-exit.scr#2 integrate .. //depot/projects/docproj_nl/share/pgpkeys/andrew.key#1 branch .. //depot/projects/docproj_nl/share/pgpkeys/bapt.key#1 branch .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys-developers.sgml#42 integrate .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys.ent#39 integrate .. //depot/projects/docproj_nl/share/pgpkeys/tijl.key#1 branch .. //depot/projects/docproj_nl/share/sgml/freebsd.ent#17 integrate .. //depot/projects/docproj_nl/share/sgml/man-refs.ent#28 integrate .. //depot/projects/docproj_nl/share/sgml/mirrors.xml#20 integrate .. //depot/projects/docproj_nl/www/en/cgi/man.cgi#15 integrate .. //depot/projects/docproj_nl/www/en/cgi/monthly.cgi#2 integrate .. //depot/projects/docproj_nl/www/en/cgi/ports.cgi#4 integrate .. //depot/projects/docproj_nl/www/en/developers.sgml#39 integrate .. //depot/projects/docproj_nl/www/en/news/status/Makefile#10 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2010-04-2010-06.xml#1 branch .. //depot/projects/docproj_nl/www/en/news/status/status.sgml#11 integrate .. //depot/projects/docproj_nl/www/en/releases/8.1R/Makefile#2 integrate .. //depot/projects/docproj_nl/www/en/releases/8.1R/announce.sgml#1 branch .. //depot/projects/docproj_nl/www/en/releases/8.1R/docbook.css#2 integrate .. //depot/projects/docproj_nl/www/en/releases/8.1R/errata.html#1 branch .. //depot/projects/docproj_nl/www/en/releases/8.1R/hardware.html#1 branch .. //depot/projects/docproj_nl/www/en/releases/8.1R/readme.html#1 branch .. //depot/projects/docproj_nl/www/en/releases/8.1R/relnotes-detailed.html#1 branch .. //depot/projects/docproj_nl/www/en/releases/8.1R/relnotes.sgml#1 branch .. //depot/projects/docproj_nl/www/en/releases/8.1R/schedule.sgml#3 integrate .. //depot/projects/docproj_nl/www/en/releases/index.sgml#10 integrate .. //depot/projects/docproj_nl/www/en/releng/index.sgml#37 integrate .. //depot/projects/docproj_nl/www/en/search/web.atoz#4 integrate .. //depot/projects/docproj_nl/www/nl/administration.sgml#21 integrate .. //depot/projects/docproj_nl/www/share/sgml/commercial.consult.xml#24 integrate .. //depot/projects/docproj_nl/www/share/sgml/commercial.hardware.xml#6 integrate .. //depot/projects/docproj_nl/www/share/sgml/commercial.software.xml#5 integrate .. //depot/projects/docproj_nl/www/share/sgml/events.xml#28 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#85 integrate .. //depot/projects/docproj_nl/www/share/sgml/release.ent#28 integrate .. //depot/projects/docproj_nl/www/share/sgml/usergroups.xml#14 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/casestudy-argentina.com/article.sgml#2 (text+ko) ==== @@ -22,7 +22,7 @@ - $FreeBSD: doc/en_US.ISO8859-1/articles/casestudy-argentina.com/article.sgml,v 1.2 2005/09/04 22:03:59 joel Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/casestudy-argentina.com/article.sgml,v 1.3 2010/07/31 11:06:17 pgj Exp $ &tm-attrib.freebsd; @@ -296,7 +296,7 @@ With the adoption of FreeBSD, there was almost no additional effort necessary to setup a working Apache, PHP and MySQL environment in minutes. Even the upgrades from PHP4 to PHP5 were - painless. The ports system was again extemely useful in these + painless. The ports system was again extremely useful in these cases, and permitted us to do things like compress text and html contents in Apache with just a few lines of documentation. In addition, we have experienced excellent performance and ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#32 (text+ko) ==== @@ -9,7 +9,7 @@ The &os; Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.289 2010/06/06 09:34:40 romain Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.290 2010/07/31 10:39:08 pgj Exp $ 1999 @@ -1099,7 +1099,7 @@ and doc/share/pgpkeys/pgpkeys-developers.sgml. &a.des; has - written a shell script to make this extremely simple. See the + written a shell script (doc/share/pgpkeys/addkey.sh) to make this extremely simple. See the README file for more information. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#65 (text+ko) ==== @@ -1,4 +1,4 @@ - + + Dru Lavigne - $FreeBSD: doc/en_US.ISO8859-1/articles/linux-comparison/article.sgml,v 1.10 2006/08/08 19:35:13 jcamou Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/linux-comparison/article.sgml,v 1.11 2010/07/31 11:12:17 pgj Exp $ &tm-attrib.freebsd; @@ -546,6 +546,3 @@ - - - ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/linux-emulation/article.sgml#3 (text+ko) ==== @@ -1,4 +1,4 @@ - + &os; development happens in a central CVS repository where only - a selected team of so called commiters can write. This repository - posseses several branches; the most interesting are the HEAD branch, + a selected team of so called committers can write. This repository + possesses several branches; the most interesting are the HEAD branch, in &os; nomenclature called -CURRENT, and RELENG_X branches, where X stands for a number indicating a major version of &os;. As of December 2006, there are development branches for 6.X development @@ -799,7 +799,7 @@ Atomic operations and memory barriers Atomic operations are implemented through a set of functions - performing simple aritmetics on memory operands in an atomic way + performing simple arithmetics on memory operands in an atomic way with respect to external events (interrupts, preemption, etc.). Atomic operations can guarantee atomicity just on small data types (in the magnitude order of the .long. @@ -1083,7 +1083,7 @@ internal to VFS. The &man.namei.9; syscall can cope with symlinks, absolute and relative paths. When a path is looked up using &man.namei.9; it is inputed to the name cache. This behaviour can - be supressed. This routine is used all over the kernel and its + be suppressed. This routine is used all over the kernel and its performance is very critical. @@ -1735,7 +1735,7 @@ unused. Segments are either stored in a global GDT table or in a local LDT table. LDT is accessed via an entry in the GDT. The LDT can store more types of segments. LDT can be per process. - Both tables define upto 8191 entries. + Both tables define up to 8191 entries. @@ -1826,7 +1826,7 @@ fast (the condition variables will probably end up being implemented using signals, i.e. not fast) and simple. In 1:1 model, the situation is also quite clear - the threads must be synchronized - using kernel facilites (which is very slow because a syscall must be + using kernel facilities (which is very slow because a syscall must be performed). The mixed M:N scenario just combines the first and second approach or rely solely on kernel. Threads synchronization is a vital part of thread-enabled programming and its performance can @@ -2121,7 +2121,7 @@ performed, is. When the filename parameter is absolute dirfd is ignored but when the path to the file is relative, it comes to the play. The - dirfd paramtere is a directory relative to which + dirfd parameter is a directory relative to which the relative pathname is checked. The dirfd parameter is a file descriptor of some directory or AT_FDCWD. So for example the @@ -2236,7 +2236,7 @@ introduce a small infrastructure. We have the ldebug facility, which tells whether a given syscall should be debugged (settable via a sysctl). For printing we have LMSG and ARGS macros. Those are used - for altering a printable string for uniform debuging messages. + for altering a printable string for uniform debugging messages. @@ -2256,7 +2256,7 @@ the &linux; programs included in &os; Ports Collection with Fedora Core 4 at 2.6.16 and there are some rudimentary reports of success with Fedora Core 6 at 2.6.16. The - Fedora Core 6 linux_base was recently commited enabling + Fedora Core 6 linux_base was recently committed enabling some further testing of the emulation layer and giving us some more hints where we should put our effort in implementing missing stuff. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/linux-users/article.sgml#5 (text+ko) ==== @@ -19,7 +19,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/articles/linux-users/article.sgml,v 1.8 2009/07/04 20:07:29 blackend Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/linux-users/article.sgml,v 1.10 2010/07/31 11:12:17 pgj Exp $ &tm-attrib.freebsd; @@ -135,7 +135,7 @@ the &os; Handbook: Using the Packages System. - + Ports @@ -212,7 +212,7 @@ You can apply your own patches if you are so inclined. - + If you do not have any special requirements, packages will probably suit your situation just fine. If you may ever need to customize, ports are the way to go. (And remember, if you @@ -278,7 +278,7 @@ /etc/rc.conf. Also, when installing additional applications be sure to review the documentation to determine how to enable any associated services. - + The following snippet from /etc/rc.conf enables &man.sshd.8; and Apache 2.2. It also specifies that Apache should be started @@ -295,10 +295,10 @@ system): &prompt.root; /etc/rc.d/sshd start - + If a service has not been enabled it can be started from the command line using : - + &prompt.root; /etc/rc.d/sshd forcestart @@ -328,7 +328,7 @@ media: Ethernet autoselect (1000baseTX <full-duplex>) status: active - + IP Configuration @@ -355,7 +355,7 @@ Like IPTABLES in &linux;, &os; also offers a kernel level firewall; actually &os; offers three firewalls: - + IPFIREWALL IPFILTER @@ -584,7 +584,7 @@ Hopefully this document has provided you with enough to get started with &os;. Be sure to take a look at the &os; Handbook - for more indepth coverage of the topics touched on as well as + for more in depth coverage of the topics touched on as well as the many topics not covered in this document. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#25 (text+ko) ==== @@ -11,7 +11,7 @@ The &os; Ports Management Team - $FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.58 2010/06/01 01:30:13 linimon Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.59 2010/07/31 11:06:18 pgj Exp $ 2003 @@ -64,7 +64,7 @@ /usr/ports/Tools/portbuild/scripts/. Typically, incremental builds are done that use previous - packages as dependendencies; this takes less time, and puts less + packages as dependencies; this takes less time, and puts less load on the mirrors. Full builds are usually only done: ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/problem-reports/article.sgml#5 (text+ko) ==== @@ -7,7 +7,7 @@ Writing &os; Problem Reports - $FreeBSD: doc/en_US.ISO8859-1/articles/problem-reports/article.sgml,v 1.61 2008/12/30 08:24:54 remko Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/problem-reports/article.sgml,v 1.62 2010/07/31 11:06:18 pgj Exp $ &tm-attrib.freebsd; @@ -396,7 +396,7 @@ specific input then include an example of that input if possible, and include both the actual and the expected output. If this data is large or cannot be made public, - then do try to create a minimal file that exibits the + then do try to create a minimal file that exhibits the same issue and that can be included within the PR. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/releng-packages/article.sgml#2 (text+ko) ==== @@ -21,7 +21,7 @@ - $FreeBSD: doc/en_US.ISO8859-1/articles/releng-packages/article.sgml,v 1.19 2006/03/12 13:45:13 remko Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/releng-packages/article.sgml,v 1.20 2010/07/31 11:06:18 pgj Exp $ &tm-attrib.freebsd; @@ -209,7 +209,7 @@ On your first pass through a split it is best to fake the copying of packages and distfiles. This will save - both time and diskspace while you do a couple of trial runs to + both time and disk space while you do a couple of trial runs to make sure things fit, etc. In the oneshot.pl set the fake variable to 1 and instead of actually copying the files it will ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/serial-uart/article.sgml#2 (text+ko) ==== @@ -18,7 +18,7 @@ - $FreeBSD: doc/en_US.ISO8859-1/articles/serial-uart/article.sgml,v 1.13 2004/11/29 21:43:34 ceri Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/serial-uart/article.sgml,v 1.14 2010/07/31 11:06:18 pgj Exp $ &tm-attrib.freebsd; @@ -300,7 +300,7 @@ When two devices that are both DTE or both DCE must be connected together without a modem or a similar media - translater between them, a NULL modem must be used. The + translator between them, a NULL modem must be used. The NULL modem electrically re-arranges the cabling so that the transmitter output is connected to the receiver input on the other device, and vice versa. Similar translations ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/storage-devices/article.sgml#2 (text+ko) ==== @@ -18,7 +18,7 @@ - $FreeBSD: doc/en_US.ISO8859-1/articles/storage-devices/article.sgml,v 1.15 2004/11/29 21:43:34 ceri Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/storage-devices/article.sgml,v 1.16 2010/07/31 11:06:18 pgj Exp $ @@ -40,7 +40,7 @@ ESDI is an acronym that means Enhanced Small Device Interface. It is loosely based on the good old ST506/412 interface originally devised by Seagate Technology, the makers - of the first affordable 5.25" winchester disk. + of the first affordable 5.25" Winchester disk. The acronym says Enhanced, and rightly so. In the first place the speed of the interface is higher, 10 or 15 @@ -2099,7 +2099,7 @@ &prompt.root; mt -f /dev/st0ctl.0 blocksize 1024 Before using a mini cartridge for the first time, the - mini cartridge must be formated. FreeBSD 2.1.0-RELEASE and + mini cartridge must be formatted. FreeBSD 2.1.0-RELEASE and earlier: &prompt.root; /sbin/scsi -f /dev/rst0.ctl -s 600 -c "4 0 0 0 0 0" ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#28 (text+ko) ==== @@ -12,7 +12,7 @@ The &os; Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1121 2010/07/15 20:39:57 pgj Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1124 2010/07/30 21:34:30 pgj Exp $ 1995 @@ -2197,7 +2197,7 @@ must be used. PAE stands for Physical Address Extension and is a way for 32-bit x86 CPUs to address more than 4 GB of memory. It remaps the memory that would - otherwise be overlayed by address reservations for + otherwise be overlaid by address reservations for hardware devices above the 4 GB range and uses it as additional physical memory (see &man.pae.4;). Using PAE has some drawbacks; this mode of memory access is a little @@ -4085,7 +4085,7 @@ An answer for this question can be found in the &os; - Glosssary, see LOR. @@ -4528,7 +4528,7 @@ one should be able to refuse categories, but in practice there are too many ports that depend on ports in other categories. Until someone comes up with a solution for this - problem, the general rule is is that if you want to build + problem, the general rule is that if you want to build INDEX, you must have a complete copy of the Ports Collection. @@ -9069,7 +9069,7 @@ Care should be taken with this option. You should also use this command to limit the amount of time that - &man.ppp.8; waits for the peer to begin negotations: + &man.ppp.8; waits for the peer to begin negotiations: set stopped N @@ -9467,7 +9467,7 @@ special cases can be found in /usr/src/sys/netinet/libalias/alias_*.c (alias_ftp.c is a good prototype). - This usually involves reading certain recognised + This usually involves reading certain recognized outgoing packets, identifying the instruction that tells the outside machine to initiate a connection back to the internal machine on a specific (random) port and setting @@ -10145,10 +10145,10 @@ &prompt.user; chmod g-w bar - However, the permissions on foo + However, the permissions on bar will not have changed. - When changing modes of the file hiearchies rooted in the + When changing modes of the file hierarchies rooted in the files instead of the files themselves, you have to use either or together with the ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#10 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -2807,6 +2807,29 @@ do not expect the problem to be resolved since there are a lot of drivers/hardware that need more testing and work. + A common problem with suspend/resume is that many device + drivers do not save, restore, or reinitialize their firmware, + registers, or device memory properly. As a first attempt at + debugging the problem, try: + + &prompt.root; sysctl debug.bootverbose=1 +&prompt.root; sysctl debug.acpi.suspend_bounce=1 +&prompt.root; acpiconf -s 3 + + This test emulates suspend/resume cycle of all device + drivers without actually going into S3 state. + In some cases, you can easily catch problems with this method + (e.g., losing firmware state, device watchdog time out, and + retrying forever). Note that the system will not really enter + S3 state, which means devices may not lose + power, and many will work fine even if suspend/resume methods + are totally missing, unlike real S3 + state. + + Harder cases require additional hardware, i.e., serial + port/cable for serial console or Firewire port/cable for + &man.dcons.4;, and kernel debugging skills. + To help isolate the problem, remove as many drivers from your kernel as possible. If it works, you can narrow down which driver is the problem by loading drivers until it fails ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml#11 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -826,9 +826,9 @@ Syslogd uses its own special method for segregation of log data. It uses special groupings called facility and level. IPMON - in mode uses security + in mode uses local0 as the facility - name. All IPMON logged data goes to security + name by default. The following levels can be used to further segregate the logged data if desired: @@ -854,9 +854,9 @@ Add the following statement to /etc/syslog.conf: - security.* /var/log/ipfilter.log + local0.* /var/log/ipfilter.log - The security.* + The local0.* means to write all the logged messages to the coded file location. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#7 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -1211,12 +1211,12 @@ User Confirmation Requested Are you sure you wish to exit? The system will reboot - (be sure to remove any floppies/CDs/DVDs from the drives). [ Yes ] No - The install program will start again if the CDROM is left - in the drive and &gui.yes; is selected. + The install program will start again if the + &gui.yes; is selected and the CDROM is left in the drive during + the reboot. If you are booting from floppies it will be necessary to remove the boot.flp floppy before rebooting. @@ -1947,7 +1947,7 @@ Message Now, you need to create BSD partitions inside of the fdisk partition(s) just created. If you have a reasonable amount of disk - space (200MB or more) and don't have any special requirements, simply + space (1GB or more) and don't have any special requirements, simply use the (A)uto command to allocate space automatically. If you have more specific needs or just don't care for the layout chosen by (A)uto, press F1 for more information on manual layout. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml#14 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -660,7 +660,9 @@ The tree was branched again in August 2009, this time for RELENG_8. 8.0-RELEASE, the first release of the 8.X branch, was - released in &rel.current.date;. + released in November 2009. The most recent + &rel.current;-RELEASE came out in &rel.current.date;. There will + be additional releases from the RELENG_8 branch. For now, long-term development projects continue to take place in the 9.X-CURRENT (trunk) branch, and SNAPshot releases of 9.X on ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#32 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -2746,6 +2746,14 @@ + RELENG_8_1_0_RELEASE + + + &os; 8.1 + + + + RELENG_8_0_0_RELEASE ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#19 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -1709,13 +1709,14 @@ 21 * * * * root /usr/libexec/ypxfr passwd.byuid These two lines force the slave to sync its maps with - the maps on the master server. Although these entries are - not mandatory, since the master server attempts to ensure - any changes to its NIS maps are communicated to its slaves - and because password information is vital to systems - depending on the server, it is a good idea to force the - updates. This is more important on busy networks where map - updates might not always complete. + the maps on the master server. These entries are not + mandatory because the master server automatically attempts + to push any map changes to its slaves. However, due to the + importance of correct password information on other clients + depending on the slave server, it is recommended to + specifically force the password map updates frequently. This + is especially important on busy networks where map updates + might not always complete. Now, run the command /etc/netstart on the slave server as well, which again starts the NIS server. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#83 (text+ko) ==== @@ -1,7 +1,7 @@ DOs and DON'Ts section. Now that you are happy with your port, the only thing remaining - is to put it in the main FreeBSD ports tree and make everybody else + is to put it in the main &os; ports tree and make everybody else happy about it too. We do not need your work directory or the pkgname.tgz package, so delete - them now. Next, simply include the output of shar `find - port_dir` in a bug report and send it with the - &man.send-pr.1; program (see Bug + them now. Next, assuming your port is called oneko, + cd to the directory above where the + oneko directory is located, and then type the + following: shar `find oneko` > oneko.shar + + Include your oneko.shar file in a bug report + and send it with the &man.send-pr.1; program (see + Bug Reports and General Commentary for more information about &man.send-pr.1;). Be sure to classify the bug report as category ports and class @@ -382,7 +387,7 @@ confidential!). Also add a short description of the program you ported to the Description field of the PR and - the shar to the Fix field. + the shar file to the Fix field. You can make our work a lot easier, if you use a good @@ -402,10 +407,10 @@ After you have submitted your port, please be patient. Sometimes it can take a few months before a port is included - in FreeBSD, although it might only take a few days. You can + in &os;, although it might only take a few days. You can view the list of ports - waiting to be committed to FreeBSD. + waiting to be committed to &os;. Once we have looked at your port, we will get back to you if necessary, and put it in the tree. Your name will also appear in the list of @@ -616,7 +621,7 @@ 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 FreeBSD. Keep careful + 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 @@ -631,7 +636,7 @@ >>> TRUNCATED FOR MAIL (1000 lines) <<<