From owner-p4-projects@FreeBSD.ORG Sun Oct 29 21:37:20 2006 Return-Path: X-Original-To: p4-projects@freebsd.org Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id E4FC416A47C; Sun, 29 Oct 2006 21:37:19 +0000 (UTC) X-Original-To: perforce@freebsd.org Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DE7116A407 for ; Sun, 29 Oct 2006 21:37:19 +0000 (UTC) (envelope-from jb@freebsd.org) Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 304CF43D6D for ; Sun, 29 Oct 2006 21:37:19 +0000 (GMT) (envelope-from jb@freebsd.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.13.6/8.13.6) with ESMTP id k9TLbJtx029858 for ; Sun, 29 Oct 2006 21:37:19 GMT (envelope-from jb@freebsd.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.13.6/8.13.4/Submit) id k9TLbHcL029855 for perforce@freebsd.org; Sun, 29 Oct 2006 21:37:17 GMT (envelope-from jb@freebsd.org) Date: Sun, 29 Oct 2006 21:37:17 GMT Message-Id: <200610292137.k9TLbHcL029855@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to jb@freebsd.org using -f From: John Birrell To: Perforce Change Reviews Cc: Subject: PERFORCE change 108698 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2006 21:37:20 -0000 http://perforce.freebsd.org/chv.cgi?CH=108698 Change 108698 by jb@jb_freebsd8 on 2006/10/29 21:37:14 IFC Affected files ... .. //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/rc-scripting/article.sgml#3 integrate .. //depot/projects/dtrace/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml#29 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/advanced-networking/chapter.sgml#9 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/book.sgml#6 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/config/chapter.sgml#8 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/eresources/chapter.sgml#5 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/firewalls/chapter.sgml#8 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/geom/chapter.sgml#5 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/kernelconfig/chapter.sgml#7 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/l10n/chapter.sgml#5 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/multimedia/chapter.sgml#4 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/network-servers/chapter.sgml#7 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/ports/chapter.sgml#7 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/preface/preface.sgml#5 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/security/chapter.sgml#9 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/serialcomms/chapter.sgml#7 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/x11/chapter.sgml#9 integrate .. //depot/projects/dtrace/doc/zh_CN.GB2312/books/porters-handbook/book.sgml#12 integrate .. //depot/projects/dtrace/src/UPDATING#9 integrate .. //depot/projects/dtrace/src/bin/cp/cp.1#6 integrate .. //depot/projects/dtrace/src/etc/defaults/rc.conf#19 integrate .. //depot/projects/dtrace/src/etc/network.subr#9 integrate .. //depot/projects/dtrace/src/etc/rc.firewall#4 integrate .. //depot/projects/dtrace/src/lib/libc/gmon/Makefile.inc#4 integrate .. //depot/projects/dtrace/src/lib/libc/net/inet.3#4 integrate .. //depot/projects/dtrace/src/lib/libkvm/kvm_proc.c#6 integrate .. //depot/projects/dtrace/src/lib/libtacplus/libtacplus.3#4 integrate .. //depot/projects/dtrace/src/share/man/man4/sis.4#6 integrate .. //depot/projects/dtrace/src/share/man/man9/kobj.9#4 integrate .. //depot/projects/dtrace/src/sys/amd64/amd64/prof_machdep.c#4 integrate .. //depot/projects/dtrace/src/sys/amd64/include/asmacros.h#4 integrate .. //depot/projects/dtrace/src/sys/amd64/include/profile.h#4 integrate .. //depot/projects/dtrace/src/sys/amd64/linux32/linux.h#6 integrate .. //depot/projects/dtrace/src/sys/amd64/linux32/linux32_dummy.c#7 integrate .. //depot/projects/dtrace/src/sys/amd64/linux32/linux32_proto.h#11 integrate .. //depot/projects/dtrace/src/sys/amd64/linux32/linux32_syscall.h#11 integrate .. //depot/projects/dtrace/src/sys/amd64/linux32/linux32_sysent.c#11 integrate .. //depot/projects/dtrace/src/sys/amd64/linux32/syscalls.master#11 integrate .. //depot/projects/dtrace/src/sys/boot/common/load_elf.c#5 integrate .. //depot/projects/dtrace/src/sys/boot/i386/boot2/boot2.c#5 integrate .. //depot/projects/dtrace/src/sys/boot/i386/libi386/elf32_freebsd.c#5 integrate .. //depot/projects/dtrace/src/sys/boot/pc98/boot2/boot.c#4 integrate .. //depot/projects/dtrace/src/sys/compat/linprocfs/linprocfs.c#9 integrate .. //depot/projects/dtrace/src/sys/compat/linux/linux_aio.c#2 delete .. //depot/projects/dtrace/src/sys/compat/linux/linux_aio.h#2 delete .. //depot/projects/dtrace/src/sys/compat/linux/linux_emul.c#5 integrate .. //depot/projects/dtrace/src/sys/compat/linux/linux_emul.h#3 integrate .. //depot/projects/dtrace/src/sys/compat/linux/linux_misc.c#11 integrate .. //depot/projects/dtrace/src/sys/compat/linux/linux_misc.h#1 branch .. //depot/projects/dtrace/src/sys/conf/files.amd64#13 integrate .. //depot/projects/dtrace/src/sys/conf/files.i386#17 integrate .. //depot/projects/dtrace/src/sys/conf/files.pc98#11 integrate .. //depot/projects/dtrace/src/sys/dev/dc/if_dc.c#7 integrate .. //depot/projects/dtrace/src/sys/dev/sound/pcm/dsp.c#6 integrate .. //depot/projects/dtrace/src/sys/i386/include/asmacros.h#4 integrate .. //depot/projects/dtrace/src/sys/i386/include/profile.h#4 integrate .. //depot/projects/dtrace/src/sys/i386/isa/prof_machdep.c#4 integrate .. //depot/projects/dtrace/src/sys/i386/linux/linux.h#6 integrate .. //depot/projects/dtrace/src/sys/i386/linux/linux_dummy.c#7 integrate .. //depot/projects/dtrace/src/sys/i386/linux/linux_proto.h#13 integrate .. //depot/projects/dtrace/src/sys/i386/linux/linux_syscall.h#13 integrate .. //depot/projects/dtrace/src/sys/i386/linux/linux_sysent.c#13 integrate .. //depot/projects/dtrace/src/sys/i386/linux/syscalls.master#13 integrate .. //depot/projects/dtrace/src/sys/kern/kern_thread.c#8 integrate .. //depot/projects/dtrace/src/sys/kern/vfs_bio.c#8 integrate .. //depot/projects/dtrace/src/sys/modules/linux/Makefile#7 integrate .. //depot/projects/dtrace/src/sys/modules/powermac_nvram/Makefile#3 integrate .. //depot/projects/dtrace/src/sys/netinet/ip_dummynet.c#4 integrate .. //depot/projects/dtrace/src/sys/pci/if_sis.c#5 integrate .. //depot/projects/dtrace/src/sys/sys/param.h#13 integrate .. //depot/projects/dtrace/src/sys/sys/proc.h#16 integrate .. //depot/projects/dtrace/src/sys/sys/soundcard.h#5 integrate .. //depot/projects/dtrace/src/usr.sbin/fwcontrol/Makefile#4 integrate .. //depot/projects/dtrace/src/usr.sbin/fwcontrol/fwcontrol.8#4 integrate .. //depot/projects/dtrace/src/usr.sbin/fwcontrol/fwcontrol.c#4 integrate .. //depot/projects/dtrace/src/usr.sbin/fwcontrol/fwdv.c#4 integrate .. //depot/projects/dtrace/src/usr.sbin/fwcontrol/fwmethods.h#1 branch .. //depot/projects/dtrace/src/usr.sbin/fwcontrol/fwmpegts.c#1 branch .. //depot/projects/dtrace/www/en/docs/books.sgml#8 integrate .. //depot/projects/dtrace/www/en/donations/donors.sgml#17 integrate .. //depot/projects/dtrace/www/en/gnome/docs/bugging.sgml#5 integrate .. //depot/projects/dtrace/www/en/gnome/docs/develfaq.sgml#6 integrate .. //depot/projects/dtrace/www/en/gnome/docs/faq2.sgml#8 integrate .. //depot/projects/dtrace/www/en/gnome/docs/faq216.sgml#3 integrate .. //depot/projects/dtrace/www/en/gnome/news.xml#13 integrate .. //depot/projects/dtrace/www/share/sgml/events.xml#4 integrate .. //depot/projects/dtrace/www/share/sgml/press.xml#8 integrate .. //depot/projects/dtrace/www/zh_CN/about.sgml#5 integrate .. //depot/projects/dtrace/www/zh_CN/applications.sgml#4 integrate .. //depot/projects/dtrace/www/zh_CN/developers.sgml#3 integrate .. //depot/projects/dtrace/www/zh_CN/index.xsl#4 integrate .. //depot/projects/dtrace/www/zh_CN/internet.sgml#4 integrate .. //depot/projects/dtrace/www/zh_CN/security/security.sgml#4 integrate .. //depot/projects/dtrace/www/zh_CN/send-pr.sgml#4 integrate .. //depot/projects/dtrace/www/zh_CN/share/sgml/libcommon.xsl#4 integrate .. //depot/projects/dtrace/www/zh_CN/share/sgml/news.xml#4 integrate .. //depot/projects/dtrace/www/zh_CN/share/sgml/press.xml#3 integrate .. //depot/projects/dtrace/www/zh_CN/where.sgml#4 integrate Differences ... ==== //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/rc-scripting/article.sgml#3 (text+ko) ==== @@ -25,7 +25,7 @@ The FreeBSD Project - $FreeBSD: doc/en_US.ISO8859-1/articles/rc-scripting/article.sgml,v 1.6 2006/10/26 17:09:29 yar Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/rc-scripting/article.sgml,v 1.7 2006/10/27 10:30:52 yar Exp $ &tm-attrib.freebsd; @@ -240,13 +240,17 @@ (for the system) or /usr/local/sbin (for ports) and call it from a &man.sh.1; script in the appropriate rc.d directory. + - If you would like to know the details about why + + If you would like to learn the details of why rc.d scripts must be written in the &man.sh.1; language, see how /etc/rc - invokes them, then study the internals of - run_rc_script. - + invokes them by means of run_rc_script, + then study the implementation of + run_rc_script in + /etc/rc.subr. + @@ -284,6 +288,11 @@ set name before it calls &man.rc.subr.8; functions. + Now it is the right time to choose a unique name for + our script once and for all. We will use it in a number + of places while developing the script. For a start, let + us give the same name to the script file, too. + The current style of rc.d scripting is to enclose values assigned to variables @@ -331,6 +340,14 @@ The body of a sophisticated method can be implemented as a function. It is a good idea to make the function name meaningful. + + + It is strongly recommended to add the prefix + ${name} to the names of all functions + defined in our script so they never clash with the + functions from &man.rc.subr.8; or another common include + file. + @@ -463,10 +480,19 @@ This is a trivial example of how &man.rc.conf.5; variables can control an rc.d script. + + The names of all &man.rc.conf.5; variables used + exclusively by our script must + have the same prefix: ${name}. For + example: dummy_mode, + dummy_state_file, and so on. + + While it is possible to use a shorter name internally, - e.g., just msg, prepending a unique - prefix to global names will save us from possible + e.g., just msg, adding the unique prefix + ${name} to all global names introduced by + our script will save us from possible collisions with the &man.rc.subr.8; namespace. As long as an &man.rc.conf.5; variable and its @@ -980,7 +1006,7 @@ #!/bin/sh -# PROVIDE: mumble mumbled +# PROVIDE: mumbled oldmumble # REQUIRE: DAEMON cleanvar frotz # BEFORE: LOGIN # KEYWORD: nojail shutdown @@ -1019,27 +1045,9 @@ several conditions there, e.g., for compatibility reasons. - The best style is to use the same name for the - following entities: - - - - the script's file; - - - - its main PROVIDE: condition; - - - - its ${name}; - - - - the prefix of its &man.rc.conf.5; variables, - as well as of its private variables and functions. - - + In any case, the name of the main, or the only, + PROVIDE: condition should be the + same as ${name}. ==== //depot/projects/dtrace/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml#29 (text+ko) ==== @@ -1,7 +1,7 @@ + + Using <application>Lua</application> + + This section describes the status of the + Lua libraries in the ports tree and its + integration with the ports system. + + + Introduction + + There are many versions of the Lua + libraries and corresponding interpreters, which conflict between + them (install files under the same name). In the ports tree this + problem has been solved by installing each version under a different + name using version number suffixes. + + The obvious disadvantage of this is that each application has to + be modified to found the expected version. But it can be solved by + adding some additional flags to the compiler and linker. + + + + Version selection + + To make your port use a specific version of + Lua there are two variables available + for defining (if only one is defined the other will be set to a + default value): + + + Variables to select <application>Lua</application> + versions + + + + + Variable + + Description + + Default value + + + + + + USE_LUA + + List of versions the port can use + + All available versions + + + + USE_LUA_NOT + + List of versions the port can not use + + None + + + +
+ + The following is a list of available + Lua versions and the corresponding port + in the tree: + + + Available <application>Lua</application> versions + + + + + Version + + Port + + + + + + 4.0 + + lang/lua4 + + + + 5.0 + + lang/lua50 + + + + 5.1 + + lang/lua + + + +
+ + The variables in can be set + to one or more of the following combinations separated by + spaces: + + + <application>Lua</application> version specifications + + + + + Description + + Example + + + + + + Single version + + 4.0 + + + + Ascending range + + 5.0+ + + + + Descending range + + 5.0- + + + + Full range (must be ascending) + + 5.0-5.1 + + + +
+ + There are also some variables to select the preferred versions + from the available ones. They can be set to a list of versions, the + first ones will have higher priority. + + + Variables to select preferred <application>Lua</application> + versions + + + + + Name + + Designed for + + + + + + WANT_LUA_VER + + the port + + + + WITH_LUA_VER + + the user + + + +
+ + + Selecting the <application>Lua</application> version + + The following fragment is from a port which can use + Lua version 5.0 or + 5.1, and uses 5.0 by + default. It can be overriden by the user using + WITH_LUA_VER. + + USE_LUA= 5.0-5.1 +WANT_LUA_VER= 5.0 + + + + + Component selection + + There are other applications that, while not being + Lua libraries, are related to them. These + applications can be specified in the LUA_COMPS + variable. The following components are available: + + + Available <application>Lua</application> components + + + + + Name + + Description + + Version restriction + + + + + + lua + + main library + + none + + + + tolua + + Library for accesing C/C++ code + + 4.0-5.0 + + + + ruby + + Ruby bindings + + 4.0-5.0 + + + +
+ + + There are more components but they are modules for the + interpreter, not used by applications (only by other + modules). + + + The dependency type added when you select each component can be + manually specified by adding a suffix separated by a + :, or a default value will be used. The available + dependency types are: + + + Available <application>Lua</application> dependency + types + + + + + Name + + Description + + + + + + build + + Component is required for building, equivalent to + BUILD_DEPENDS + + + + run + + Component is required for running, equivalent to + RUN_DEPENDS + + + + lib + + Component is required for building and running, + equivalent to LIB_DEPENDS + + + +
+ + The default values for the components are detailed in the + following table: + + + Default <application>Lua</application> dependency + types + + + + + Name + + Value + + + + + + lua + + lib for 4.0-5.0 + (shared) and build for + 5.1 (static) + + + + tolua + + build (static) + + + + ruby + + lib (shared) + + + +
+ + + Selecting <application>Lua</application> components + + The following fragment corresponds to a port which uses + Lua version 4.0 and + its Ruby bindings. + + USE_LUA= 4.0 +LUA_COMPS= lua ruby + + + + + Detecting installed versions + + To detect an installed version you have to define + WANT_LUA. If you do not set it to a specific + version then the components will have a version suffix. The + HAVE_LUA variable will be filled after + detection. + + + Detecting installed <application>Lua</application> versions + and components + + The following fragment can be used in a port that uses + Lua if it is installed, or an option is + selected. + + WANT_LUA= yes + +.include <bsd.port.pre.mk> + +.if defined(WITH_LUA5) || ${HAVE_LUA:Mlua-5.[01]} != "" +USE_LUA= 5.0-5.1 +CONFIGURE_ARGS+=--enable-lua5 +.endif + + The following fragment can be used in a port that enables + tolua support if it is installed or if + an option is selected, in addition to + Lua, both version + 4.0. + + USE_LUA= 4.0 +LUA_COMPS= lua +WANT_LUA= 4.0 + +.include <bsd.port.pre.mk> + +.if defined(WITH_TOLUA) || ${HAVE_LUA:Mtolua} != "" +LUA_COMPS+= tolua +CONFIGURE_ARGS+=--enable-tolua +.endif + + + + + Defined variables + + The following variables are defined after defining one of the + variables from . + + + Variables defined for ports that use + <application>Lua</application> + + + + + Name + + Description + + + + + + LUA_VER + + The Lua version that is + going to be used (e.g., 5.1) + + + + LUA_VER_SH + The Lua shared library major + version (e.g., 1) + + + + LUA_VER_STR + + The Lua version without the + dots (e.g., 51) + + + + LUA_PREFIX + + The prefix where Lua (and + components) is installed + + + + LUA_SUBDIR + + The directory under ${PREFIX}/bin, + ${PREFIX}/share and + ${PREFIX}/lib where + Lua is installed + + + + LUA_INCDIR + + The directory where Lua and + tolua header files are + installed + + + + LUA_LIBDIR + + The directory where Lua and + tolua libraries are + installed + + + + LUA_MODLIBDIR + + The directory where Lua + module libraries (.so) are + installed + + + + LUA_MODSHAREDIR + + The directory where Lua + modules (.lua) are installed + + + + LUA_PKGNAMEPREFIX + + The package name prefix used by + Lua modules + + + +
+ + + Telling the port where to find + <application>Lua</application> + + The following fragment shows how to tell a port that uses a + configure script where the Lua header + files and libraries are. + + +USE_LUA= 4.0 +GNU_CONFIGURE= yes +CONFIGURE_ENV= CPPFLAGS="-I${LUA_INCDIR}" LDFLAGS="-L${LUA_LIBDIR}" + + + + + Processing in <filename>bsd.port.pre.mk</filename> + + If you need to use the variables for running commands right + after including bsd.port.pre.mk you need to + define LUA_PREMK. + + + If you define LUA_PREMK, then the version, + dependencies, components and defined variables will not change if + you modify the Lua port variables + after including + bsd.port.pre.mk. + + + + Using <application>Lua</application> variables in + commands + + The following fragment illustrates the use of + LUA_PREMK by running the + Lua interpreter to obtain the full + version string, assign it to a variable and pass it to the + program. + + USE_LUA= 5.0 +LUA_PREMK= yes + +.include <bsd.port.pre.mk> + +VER_STR!= lua${LUA_VER} -v + +CFLAGS+= -DLUA_VERSION_STRING="${VER_STR}" + + + + The Lua variables can be safely + used in commands when they are inside targets without the need of + LUA_PREMK. + + + + Starting and stopping services (rc scripts) ==== //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/advanced-networking/chapter.sgml#9 (text+ko) ==== @@ -2,8 +2,8 @@ The FreeBSD Documentation Project The FreeBSD Chinese Documentation Project - Original revision: 1.384 - $FreeBSD: doc/zh_CN.GB2312/books/handbook/advanced-networking/chapter.sgml,v 1.10 2006/09/15 04:28:30 delphij Exp $ + Original revision: 1.387 + $FreeBSD: doc/zh_CN.GB2312/books/handbook/advanced-networking/chapter.sgml,v 1.11 2006/10/27 06:37:47 delphij Exp $ --> @@ -2309,11 +2309,28 @@ 请参考 以了解关于将网桥配置为防火墙的其它信息。 - 如果允许非IP(non-IP)数据包 (比如 ARP) 穿过网桥， - 必须设置一个防火墙 (firewall) 选项。这个选项是 - IPFIREWALL_DEFAULT_TO_ACCEPT。 - 注意：这个选项改变了默认的规则使得防火墙接受任何的数据包。 - 在您设置这些规则前，请确认这些规则可能会产生什么后果。 + 如果需要允许非 IP 数据包 (例如 ARP) 穿过网桥， + 有三种方法可供选择。 第一种是在内核配置中加入下列选项， + 并重新联编： + + option IPFIREWALL_DEFAULT_TO_ACCEPT + + 第二种方法， 是在 + rc.conf 文件中将防火墙类型设置为 open： + + firewall_type="open" + + 注意， 这些选项会让防火墙看起来像透明的一样； + 默认情况下， 所有包或连接都会被允许。 + 如果选择这样做的话， 可能会需要对防火墙规则进行大幅调整。 + + 第三种方法是应用下述 &man.ipfw.8; + 规则： + + &prompt.root; ipfw add allow mac-type arp layer2 + + 或将其加入在用的防火墙规则集。 这个规则实际上是允许 &man.arp.8; 包通过， + 因此最好把它放在规则集前面， 以便能够尽早地应用此规则， 而避免由此带来的性能影响。 ==== //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/book.sgml#6 (text+ko) ==== @@ -2,8 +2,8 @@ The FreeBSD Documentation Project The FreeBSD Simplified Chinese Documentation Project - Original Revision: 1.166 - $FreeBSD: doc/zh_CN.GB2312/books/handbook/book.sgml,v 1.7 2006/08/14 02:26:09 delphij Exp $ + Original Revision: 1.168 + $FreeBSD: doc/zh_CN.GB2312/books/handbook/book.sgml,v 1.8 2006/10/27 06:37:47 delphij Exp $ --> 欢迎使用 FreeBSD！ 本手册适用于安装 FreeBSD &rel2.current;-RELEASE 和 FreeBSD &rel.current;-RELEASE 以及它们的日常使用。 - 这个手册目前由很多人 持续地 维护。其中的内容需要不断的添加和更新。 + 这个手册目前由很多人 持续地 维护。 其中的内容需要不断地更新。 如果您有兴趣参加这个项目，请发邮件到 &a.doc;。此文档最新的英文原始版本可以从 FreeBSD Web站点 上获得 (这本手册的较早期版本可以在 @@ -632,12 +632,11 @@ 中的 sshd_enable 设置成 的时候工作。不管是否在 /etc/rc.conf 中设置了，要 、 或者 - 一个服务，命令前可以加上一个force前缀。例如要不顾当前 + 一个服务，命令前可以加上一个one前缀。例如要不顾当前 /etc/rc.conf 的设置重新启动 - sshd，执行下面的命令： - + sshd，执行下面的命令： - &prompt.root; /etc/rc.d/sshd forcerestart + &prompt.root; /etc/rc.d/sshd onerestart 用选项 可以简单来的检查 /etc/rc.conf 中用适当的 rc.d @@ -703,7 +702,10 @@ &unix; 操作系统一样要用 runlevels 来控制。 更多关于 rc.d 系统的信息， 可以在 - &man.rc.8; 和 &man.rc.subr.8; 联机手册中找到。 + &man.rc.8; 和 &man.rc.subr.8; 联机手册中找到。 + 如果您有意撰写自己的 rc.d 脚本， + 或对现有的脚本进行一些改进， 也可以参考 + 这篇文章。 ==== //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/eresources/chapter.sgml#5 (text+ko) ==== @@ -2,8 +2,8 @@ The FreeBSD Documentation Project The FreeBSD Simplified Chinese Project - Original Revision: 1.178 - $FreeBSD: doc/zh_CN.GB2312/books/handbook/eresources/chapter.sgml,v 1.6 2006/10/08 16:13:05 delphij Exp $ + Original Revision: 1.181 + $FreeBSD: doc/zh_CN.GB2312/books/handbook/eresources/chapter.sgml,v 1.7 2006/10/27 06:37:47 delphij Exp $ --> @@ -241,6 +241,12 @@ + &a.eol.name; + 关于与 FreeBSD 有关， 但已不再为 FreeBSD Project + 所维护的软件的互助支持。 + + + &a.emulation.name; 在 FreeBSD 上模拟其它系统， 如 Linux/&ms-dos;/&windows; @@ -450,6 +456,11 @@ + &a.sun4v.name; + 将 FreeBSD 移植到基于 &ultrasparc; T1 的系统上 + + + &a.threads.name; 线程 @@ -881,6 +892,18 @@ + &a.eol.name; + + + 关于与 FreeBSD 有关， 但已不再为 FreeBSD Project + 所维护的软件的互助支持。 + + 这个邮件列表主要用于那些有兴趣提供或使用针对已不再为 FreeBSD Project + 官方所支持 (例如， 以安全更新或补丁的形式) 的 FreeBSD 相关软件的用户或公司讨论。 + + + + &a.firewire.name; ==== //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/firewalls/chapter.sgml#8 (text+ko) ==== @@ -2,8 +2,8 @@ The FreeBSD Documentation Project The FreeBSD Simplified Chinese Project - Original Revision: 1.72 - $FreeBSD: doc/zh_CN.GB2312/books/handbook/firewalls/chapter.sgml,v 1.9 2006/10/08 16:16:16 delphij Exp $ + Original Revision: 1.73 + $FreeBSD: doc/zh_CN.GB2312/books/handbook/firewalls/chapter.sgml,v 1.10 2006/10/27 06:37:47 delphij Exp $ --> @@ -1963,8 +1963,7 @@ <filename>/etc/rc.conf</filename> Options - 如果没有将 IPFW 编入内核， 则您需要在 - /etc/rc.conf 中加入下列语句来加载它： + 启用防火墙： firewall_enable="YES" ==== //depot/projects/dtrace/doc/zh_CN.GB2312/books/handbook/geom/chapter.sgml#5 (text+ko) ==== @@ -2,8 +2,8 @@ The FreeBSD Documentation Project The FreeBSD Simplified Chinese Project - Original Revision: 1.24 - $FreeBSD: doc/zh_CN.GB2312/books/handbook/geom/chapter.sgml,v 1.4 2006/07/20 10:59:28 delphij Exp $ + Original Revision: 1.25 + $FreeBSD: doc/zh_CN.GB2312/books/handbook/geom/chapter.sgml,v 1.5 2006/10/27 06:37:47 delphij Exp $ --> >>> TRUNCATED FOR MAIL (1000 lines) <<<