From owner-p4-projects Fri Jul 12 15:50:16 2002 Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id D780937B873; Fri, 12 Jul 2002 15:45:10 -0700 (PDT) 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 313E137B4F4 for ; Fri, 12 Jul 2002 15:45:00 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30B6E4498E for ; Fri, 12 Jul 2002 15:35:05 -0700 (PDT) (envelope-from chris@FreeBSD.org) Received: from freefall.freebsd.org (perforce@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g6CLmYJU009637 for ; Fri, 12 Jul 2002 14:48:34 -0700 (PDT) (envelope-from chris@freebsd.org) Received: (from perforce@localhost) by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g6CLmWtZ009617 for perforce@freebsd.org; Fri, 12 Jul 2002 14:48:32 -0700 (PDT) Date: Fri, 12 Jul 2002 14:48:32 -0700 (PDT) Message-Id: <200207122148.g6CLmWtZ009617@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: perforce set sender to chris@freebsd.org using -f From: Chris Costello Subject: PERFORCE change 14158 for review To: Perforce Change Reviews Sender: owner-p4-projects@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG http://people.freebsd.org/~peter/p4db/chv.cgi?CH=14158 Change 14158 by chris@chris_holly on 2002/07/12 14:48:13 IFC Affected files ... .. //depot/projects/trustedbsd/doc/el_GR.ISO8859-7/articles/dialup-firewall/article.sgml#2 integrate .. //depot/projects/trustedbsd/doc/el_GR.ISO8859-7/articles/explaining-bsd/article.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/Makefile#4 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/committers-guide/article.sgml#4 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/console-server/article.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/contributing/article.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/contributors/article.sgml#4 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/cvsup-advanced/article.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/fonts/article.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/formatting-media/article.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/hats/Makefile#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/hats/article.sgml#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/hubs/article.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/java-tomcat/article.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/laptop/article.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/mh/article.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/new-users/article.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/pam/article.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/problem-reports/article.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/releng/article.sgml#4 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/releng/branches.ascii#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/storage-devices/article.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/vinum/article.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/vm-design/article.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/developers-handbook/driverbasics/chapter.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/developers-handbook/jail/chapter.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/developers-handbook/x86/chapter.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/faq/book.sgml#4 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/Makefile#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/contrib/Makefile#2 delete .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml#2 delete .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#4 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml#4 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/install/example-dir1.dot#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/install/example-dir1.eps#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/install/example-dir2.dot#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/install/example-dir2.eps#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/install/example-dir3.dot#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/install/example-dir3.eps#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/install/example-dir4.dot#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/install/example-dir4.eps#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/install/example-dir5.dot#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/install/example-dir5.eps#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#4 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/pgpkeys/ceri.key#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/pgpkeys/chapter.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/pgpkeys/dannyboy.key#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/pgpkeys/des.key#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/pgpkeys/jon.key#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/pgpkeys/perky.key#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/pgpkeys/pgpkeys.ent#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/pgpkeys/scop.key#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/pgpkeys/sheldonh.key#1 branch .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml#5 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml#4 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/handbook/sound/chapter.sgml#3 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml#4 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/ppp-primer/book.sgml#2 integrate .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/share/sgml/authors.ent#3 integrate .. //depot/projects/trustedbsd/doc/fr_FR.ISO8859-1/articles/Makefile#3 integrate .. //depot/projects/trustedbsd/doc/fr_FR.ISO8859-1/articles/contributing/Makefile#1 branch .. //depot/projects/trustedbsd/doc/fr_FR.ISO8859-1/articles/contributing/article.sgml#1 branch .. //depot/projects/trustedbsd/doc/fr_FR.ISO8859-1/articles/releng-packages/Makefile#1 branch .. //depot/projects/trustedbsd/doc/fr_FR.ISO8859-1/articles/releng-packages/article.sgml#1 branch .. //depot/projects/trustedbsd/doc/fr_FR.ISO8859-1/articles/releng-packages/extra.css#1 branch .. //depot/projects/trustedbsd/doc/fr_FR.ISO8859-1/share/sgml/catalog#2 integrate .. //depot/projects/trustedbsd/doc/fr_FR.ISO8859-1/share/sgml/freebsd.dsl#3 integrate .. //depot/projects/trustedbsd/doc/fr_FR.ISO8859-1/share/sgml/license.sgml#2 integrate .. //depot/projects/trustedbsd/doc/fr_FR.ISO8859-1/share/sgml/mailing-lists.ent#2 integrate .. //depot/projects/trustedbsd/doc/fr_FR.ISO8859-1/share/sgml/newsgroups.ent#2 integrate .. //depot/projects/trustedbsd/doc/fr_FR.ISO8859-1/share/sgml/teams.ent#2 integrate .. //depot/projects/trustedbsd/doc/it_IT.ISO8859-15/articles/filtering-bridges/article.sgml#3 integrate .. //depot/projects/trustedbsd/doc/ja_JP.eucJP/books/handbook/basics/chapter.sgml#2 integrate .. //depot/projects/trustedbsd/doc/ja_JP.eucJP/books/handbook/disks/chapter.sgml#2 integrate .. //depot/projects/trustedbsd/doc/ja_JP.eucJP/books/handbook/kernelconfig/chapter.sgml#2 integrate .. //depot/projects/trustedbsd/doc/ja_JP.eucJP/books/handbook/mirrors/chapter.sgml#2 integrate .. //depot/projects/trustedbsd/doc/ja_JP.eucJP/books/handbook/x11/chapter.sgml#2 integrate .. //depot/projects/trustedbsd/doc/ja_JP.eucJP/man/man1/cu.1#2 integrate .. //depot/projects/trustedbsd/doc/ja_JP.eucJP/man/man1/df.1#2 integrate .. //depot/projects/trustedbsd/doc/ja_JP.eucJP/man/man1/whois.1#2 integrate .. //depot/projects/trustedbsd/doc/ja_JP.eucJP/man/man1/window.1#2 integrate .. //depot/projects/trustedbsd/doc/ja_JP.eucJP/man/man8/init.8#2 integrate .. //depot/projects/trustedbsd/doc/no_NO.ISO8859-1/books/handbook/bibliography/chapter.sgml#1 branch .. //depot/projects/trustedbsd/doc/no_NO.ISO8859-1/books/handbook/install/chapter.sgml#1 branch .. //depot/projects/trustedbsd/doc/release/Makefile#2 integrate .. //depot/projects/trustedbsd/doc/release/texts/README#2 integrate .. //depot/projects/trustedbsd/doc/share/mk/doc.html.mk#2 integrate .. //depot/projects/trustedbsd/doc/share/sgml/man-refs.ent#4 integrate Differences ... ==== //depot/projects/trustedbsd/doc/el_GR.ISO8859-7/articles/dialup-firewall/article.sgml#2 (text+ko) ==== @@ -9,7 +9,7 @@ %man; ]> -
+
Σύνδεση μέσω τηλεφώνου και firewalling στο FreeBSD @@ -24,7 +24,7 @@ - $FreeBSD: doc/el_GR.ISO8859-7/articles/dialup-firewall/article.sgml,v 1.1 2002/02/15 00:35:06 keramida Exp $ + $FreeBSD: doc/el_GR.ISO8859-7/articles/dialup-firewall/article.sgml,v 1.2 2002/06/27 19:39:40 keramida Exp $ Αυτό το άρθρο περιγράφει πως μπορείτε να ρυθμίσετε ένα firewall ==== //depot/projects/trustedbsd/doc/el_GR.ISO8859-7/articles/explaining-bsd/article.sgml#2 (text+ko) ==== @@ -1,5 +1,5 @@ + @@ -273,7 +273,7 @@

The Stallion driver is not included in the default GENERIC kernel, so you will need to create a kernel config file with the appropriate entries. See the - stl(4) man page and the appropriate section of the + stl(4) manual page and the appropriate section of the FreeBSD Handbook.

@@ -283,12 +283,12 @@

After applying the patch you will certainly need to update the whole system, including all the user programs and the kernel. See the documentation in /usr/src/UPDATING and the - FreeBSD + FreeBSD Handbook.

Making The Devices

-

You will need to make the device notes for the Stallion card +

You will need to make the device nodes for the Stallion card (which are not made by default). A new version of /dev/MAKEDEV with Stallion support will have been created by the mergemaster run during the above @@ -305,7 +305,7 @@

to create dial-out devices for the first Stallion card. See the comments in MAKEDEV and the stl(4) - man page for more details.

+ manual page for more details.

Compiling conserver

@@ -416,10 +416,10 @@ carrier on these ports, perhaps by setting this using the ttyiEx device in the /etc/rc.serial file. See the comments in this file for more details. Also see the - sio(4) man page for information on the + sio(4) manual page for information on the initial-state and locked-state devices. (The Stallion driver also supports these conventions). And see the - stty(1) man page for details on setting device + stty(1) manual page for details on setting device modes.

The last section shows that any user logged into the server @@ -569,7 +569,7 @@ master server, and it will arrange to signal all the child processes. Yes, this will send a HUP to all clients whenever a single log file needs rotating, but that is quite cheap. See - the newsysylog(8) man page for details.

+ the newsysylog(8) manual page for details.

Cabling

@@ -966,7 +966,7 @@ key sequence <Return><Tilda><control-B> (within 5 seconds) will drop to the ROM. You can enable this permanently by editing the /etc/default/kbd file; - see the kbd(1) man page. Note that this alternate + see the kbd(1) manual page. Note that this alternate break sequence is only active once the kernel has started running multiuser and processed the default file. While the ROM is active (during power-on and during the boot process) and @@ -1192,9 +1192,9 @@
  • Grrr. Fixed the pinout for the Cisco - Stallion RJ-45 cable. The cable would have worked but was backwards. The new table now reflects the description. -
  • Noted that Catalyst cable is a 26xx cable plugged in the othyer +
  • Noted that Catalyst cable is a 26xx cable plugged in the other way around. -
  • Added notes about RJ-45 pin numberring and color coding +
  • Added notes about RJ-45 pin numbering and color coding conventions
  • Added notes about serial console on FreeBSD/i386 platforms.
  • Now in RCS. ==== //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/contributing/article.sgml#2 (text+ko) ==== @@ -14,7 +14,7 @@ Contributing to FreeBSD - $FreeBSD: doc/en_US.ISO8859-1/articles/contributing/article.sgml,v 1.486 2002/05/08 18:29:01 mwlucas Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/contributing/article.sgml,v 1.487 2002/07/11 19:07:49 trhodes Exp $ This article describes the different ways in which an @@ -329,7 +329,7 @@ &prompt.user; diff -c -r olddir newdir would generate such a set of context diffs for the given - source file or directory hierarchy. See the man page for + source file or directory hierarchy. See the manual page for &man.diff.1; for more details. Once you have a set of diffs (which you may test with the ==== //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/contributors/article.sgml#4 (text+ko) ==== @@ -18,7 +18,7 @@ Contributors to FreeBSD - $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/article.sgml,v 1.208 2002/06/19 23:13:30 mike Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/article.sgml,v 1.223 2002/07/12 02:59:19 mdodd Exp $ This article lists individuals and organizations who have @@ -334,7 +334,11 @@ - &a.dg; + &a.jhb; + + + + &a.kuriyama; @@ -346,7 +350,15 @@ - &a.dfr; + &a.markm; + + + + &a.wes; + + + + &a.murray; @@ -490,6 +502,10 @@ + &a.perky; + + + &a.dwcjr; @@ -698,15 +714,15 @@ - &a.petef; + &a.scrappy; - &a.scrappy; + &a.lars; - &a.lars; + &a.petef; @@ -914,11 +930,15 @@ - &a.joe; + &a.cokane; + + + + &a.johan; - &a.cokane; + &a.joe; @@ -974,11 +994,15 @@ + &a.reg; + + + &a.chern; - &a.reg; + &a.sam; @@ -1122,11 +1146,11 @@ - &a.markm; + &a.rich; - &a.rich; + &a.markm; @@ -1214,11 +1238,11 @@ - &a.alfred; + &a.roam; - &a.roam; + &a.alfred; @@ -1294,11 +1318,11 @@ - &a.luigi; + &a.paul; - &a.paul; + &a.luigi; @@ -1334,10 +1358,6 @@ - &a.asmodai; - - - &a.ps; @@ -1438,10 +1458,6 @@ - &a.nsouch; - - - &a.des; @@ -1458,6 +1474,10 @@ + &a.nsouch; + + + &a.mks; @@ -1891,6 +1911,15 @@ In rough chronological order: + + + &a.dg; (1992 - 2002) + + + + &a.dfr; (1999 - 2002) + + &a.msmith; (2000 - 2002) @@ -2005,6 +2034,9 @@ + &a.asmodai; (1999 - 2002) + + &a.uch; (2000 - 2002) @@ -3432,6 +3464,10 @@ + Filippo Natali filippo@widestore.net + + + Flemming Jacobsen fj@batmule.dk @@ -3513,6 +3549,10 @@ + Frerich Raabe frerich.raabe@gmx.de + + + FUJIMOTO Kensaku fujimoto@oscar.elec.waseda.ac.jp @@ -3859,10 +3899,6 @@ - Hye-Shik Chang perky@fallin.lv - - - Ian Holland ianh@tortuga.com.au @@ -4250,10 +4286,6 @@ - Johan Karlsson k@numeri.campus.luth.se - - - Johan Larsson johan@moon.campus.luth.se @@ -4701,6 +4733,10 @@ + Kyle Martin mkm@ieee.org + + + L. Jonas Olsson ljo@ljo-slip.DIALIN.CWRU.Edu @@ -4971,10 +5007,18 @@ + Matt Douhan matt@athame.co.uk + + + Matt Heckaman matt@LUCIDA.QC.CA + Matt Peterson matt@peterson.org + + + Matt Thomas matt@3am-software.com @@ -5055,6 +5099,10 @@ + Michael Handler handler@grendel.net + + + Michael Lyngbøl michael@lyngbol.dk @@ -5083,6 +5131,10 @@ + Michael Hostbaek mich@freebsdcluster.org + + + Michael Perlman canuck@caam.rice.edu @@ -5194,6 +5246,10 @@ + Mike Makonnen makonnen@pacbell.net + + + Mike McGaughey mmcg@cs.monash.edu.au @@ -7009,6 +7065,10 @@ + William Josephson wkj-freebsd@honk.eecs.harvard.edu + + + William Liao william@tale.net ==== //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/cvsup-advanced/article.sgml#3 (text+ko) ==== @@ -22,12 +22,12 @@ - $FreeBSD: doc/en_US.ISO8859-1/articles/cvsup-advanced/article.sgml,v 1.5 2002/05/26 21:45:41 keramida Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/cvsup-advanced/article.sgml,v 1.6 2002/06/30 20:39:47 blackend Exp $ - The present article assumes a basic understanding of CVSup + The present article assumes a basic understanding of CVSup operation. It documents several delicate issues connected with - source synchronization via CVSup, viz. effective solutions to + source synchronization via CVSup, viz. effective solutions to the problem of stale files as well as special source updating cases; which issues are likely to cause apparently inexplicable troubles. @@ -38,7 +38,7 @@ Preface This document is the fruit of the author's attempts to - fully understand the niceties of cvsup & source updating. :-) + fully understand the niceties of CVSup & source updating. :-) While the author has made every effort to make these pages as informative and correct as possible, he is only human and may have made all sorts of typos, mistakes, etc. He will be @@ -66,12 +66,12 @@ your base is /usr. A checkouts file contains information on the current status - of your sources -- in a way, a sort of "photograph". This - significant information enables cvsup to retrieve updates most - effectively. Further, and maybe more important, it enables cvsup + of your sources -- in a way, a sort of photograph. This + significant information enables cvsup to retrieve updates most + effectively. Further, and maybe more important, it enables cvsup to correctly manage your sources by locally deleting any files no longer present in the repository, thus leaving no stale files - on your system. In fact, without a checkouts file, cvsup would + on your system. In fact, without a checkouts file, cvsup would NOT know which files your collection was composed of (cf &man.cvsup.1; and the fallback method for details); as a result, it could NOT delete on your system those files no longer present @@ -82,15 +82,15 @@ have got(ten) your installation CDs. It is therefore recommended that you adopt the two-step procedure - outlined in the Cvsup FAQ (cf Q12, Q13); in subsequent sections, you + outlined in the CVSup FAQ (cf Q12, Q13); in subsequent sections, you will be given interesting and instructive concrete examples. - A useful python script: cvsupchk + A useful python script: <command>cvsupchk</command> Alternatively, in order to examine your sources for - inconsistencies, you may wish to utilize the cvsupchk python + inconsistencies, you may wish to utilize the cvsupchk python script; which script is currently found in /usr/ports/net/cvsup/work/cvsup-16.1/contrib/cvsupchk, together with a nice README. Prerequisites: @@ -121,7 +121,7 @@ &prompt.user; /path/to/cvsupchk -d /usr -c /usr/sup/src-all/checkouts.cvs:RELENG_4 | more - In each case, cvsupchk will inspect your sources for + In each case, cvsupchk will inspect your sources for inconsistencies by utilizing the information contained in the related checkouts file. Such anomalies as deleted files being present (aka stale files), missing checked-out files, extra RCS @@ -138,17 +138,17 @@ How to safely change tags when updating -<literal>src-all.</literal> +src-all - If you specify eg tag=A in your supfile, cvsup will create + If you specify eg tag=A in your supfile, cvsup will create a checkouts file called checkouts.cvs:A: - for instance, if tag=RELENG_4, a checkouts file called + for instance, if tag=RELENG_4, a checkouts file called checkouts.cvs:RELENG_4 is generated. This file will be used to retrieve and/or store information identifying your 4-STABLE sources. When tracking src-all, if you wish to - pass from tag=A to tag=B (A less/greater than B not making + pass from tag=A to tag=B (A less/greater than B not making any difference) and if your checkouts file is checkouts.cvs:A, the following actions should be performed: @@ -162,17 +162,17 @@ - write a supfile whose collection line reads: + write a supfile whose collection line reads: src-all tag=B - cvsup your sources using the new supfile. + cvsup your sources using the new supfile. - Cvsup will look for checkouts.cvs:B - -- in that the target is B; that is, cvsup will make use of + The cvsup utility will look for checkouts.cvs:B + -- in that the target is B; that is, cvsup will make use of the information contained therein to correctly manage your sources. @@ -185,15 +185,15 @@ - less load is placed on the server, in that cvsup + less load is placed on the server, in that cvsup operates in the most efficient way. - For example, A=RELENG_4, B=. The period in "B=." means + For example, A=RELENG_4, B=.. The period in B=. means -CURRENT. This is a rather typical update, from 4-STABLE - to -CURRENT. While it is straightforward to "downgrade" your + to -CURRENT. While it is straightforward to downgrade your sources (eg from -CURRENT to -STABLE), downgrading a system is quite another matter. You are STRONGLY advised not to attempt such an operation, unless you know exactly what you @@ -203,24 +203,24 @@ Updating to the same tag as of a different date - If you wish to switch from "tag=A" to "tag=A" as of a - different GMT date (say, "date=D"), you will execute the + If you wish to switch from tag=A to tag=A as of a + different GMT date (say, date=D), you will execute the following: - write a supfile whose collection line reads: + write a supfile whose collection line reads: src-all tag=A date=D - update your sources using the new supfile + update your sources using the new supfile Whether the new date precedes that of the last sync - operation with tag=A or not, it is immaterial. For example, - in order to specify the date "August 27, 2000, 10:00:00 GMT" + operation with tag=A or not, it is immaterial. For example, + in order to specify the date August 27, 2000, 10:00:00 GMT you write the line: @@ -237,19 +237,19 @@ is called checkouts.cvs:A (eg checkouts.cvs:RELENG_4). As a result, no particular action is needed in order to revert to the - previous state: you have to modify the date in the supfile, - and csvup again. + previous state: you have to modify the date in the supfile, + and run csvup again. Updating your ports collection for the first time - Since ports are tagged "." (ie -CURRENT), you can - correctly "sync" them for the first time by adding the date + Since ports are tagged . (ie -CURRENT), you can + correctly sync them for the first time by adding the date keyword (cf &man.cvsup.1; for the exact format): you should - specify a date as close as possible to that of "shipping" of - your ports tree. After cvsup has correctly created the ports + specify a date as close as possible to that of shipping of + your ports tree. After cvsup has correctly created the ports checkouts file, which is precisely the goal of this first special sync operation, the date field must be removed; all subsequent updates will be carried out smoothly. ==== //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/fonts/article.sgml#2 (text+ko) ==== @@ -1,4 +1,4 @@ - + @@ -7,7 +7,7 @@ +
    Formatting Media For Use With FreeBSD @@ -521,7 +521,7 @@ several identical disks as a single disk. Striping can result in increased disk performance by distributing reads and writes across the disks. See the &man.ccd.4; and &man.ccdconfig.8; - man pages or the CCD Homepage for further details. ==== //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/hubs/article.sgml#3 (text+ko) ==== @@ -11,7 +11,7 @@
    Mirroring FreeBSD - $FreeBSD: doc/en_US.ISO8859-1/articles/hubs/article.sgml,v 1.21 2002/05/21 20:11:19 logo Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/hubs/article.sgml,v 1.22 2002/06/28 23:44:36 keramida Exp $ Jun @@ -1005,7 +1005,7 @@ Then you can ask the &a.doc; or the &a.hubs; to add your mirror site to the mirror list in the - FreeBSD + FreeBSD Handbook. Make sure you tell them the email address, to list as the maintainer of the site. ==== //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/java-tomcat/article.sgml#2 (text+ko) ==== @@ -80,7 +80,7 @@ Hiten Pandya - $FreeBSD: doc/en_US.ISO8859-1/articles/java-tomcat/article.sgml,v 1.5 2002/04/27 00:12:03 znerd Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/java-tomcat/article.sgml,v 1.6 2002/07/03 23:19:11 jim Exp $ This document is presented in hopes of making it easier for @@ -118,7 +118,7 @@ The Tomcat portion of the install is very straight forward, but the difficulty I had was getting Java Development Kit up and - running for FreeBSD 4.x, as Sun Microsystems only supplies + running for FreeBSD 4.X, as Sun Microsystems only supplies Binaries for Linux, Solaris, and Windows NT. This means that I had to compile my own JDK for FreeBSD. I began by searching for documentation on the Internet. I quickly found that there is more ==== //depot/projects/trustedbsd/doc/en_US.ISO8859-1/articles/laptop/article.sgml#3 (text+ko) ==== >>> TRUNCATED FOR MAIL (1000 lines) <<< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe p4-projects" in the body of the message