From owner-svn-doc-all@FreeBSD.ORG Mon Apr 28 20:13:09 2014 Return-Path: Delivered-To: svn-doc-all@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 00CF6508; Mon, 28 Apr 2014 20:13: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 DEBFF1C42; Mon, 28 Apr 2014 20:13:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3SKD8GH019695; Mon, 28 Apr 2014 20:13:08 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3SKD7Wp019688; Mon, 28 Apr 2014 20:13:07 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201404282013.s3SKD7Wp019688@svn.freebsd.org> From: Warren Block Date: Mon, 28 Apr 2014 20:13:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44678 - in head/en_US.ISO8859-1/books/developers-handbook: kernelbuild kerneldebug l10n policies testing tools x86 X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2014 20:13:09 -0000 Author: wblock Date: Mon Apr 28 20:13:07 2014 New Revision: 44678 URL: http://svnweb.freebsd.org/changeset/doc/44678 Log: Restore lost tags. Modified: head/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml head/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml head/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.xml head/en_US.ISO8859-1/books/developers-handbook/policies/chapter.xml head/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml head/en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml head/en_US.ISO8859-1/books/developers-handbook/x86/chapter.xml Modified: head/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml Mon Apr 28 19:36:49 2014 (r44677) +++ head/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml Mon Apr 28 20:13:07 2014 (r44678) @@ -49,7 +49,7 @@ Run &man.config.8; to generate the kernel source code: - &prompt.root; /usr/sbin/config MYKERNEL + &prompt.root; /usr/sbin/config MYKERNEL @@ -57,7 +57,7 @@ print the name of this directory after being run as above. - &prompt.root; cd ../compile/MYKERNEL + &prompt.root; cd ../compile/MYKERNEL Modified: head/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml Mon Apr 28 19:36:49 2014 (r44677) +++ head/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml Mon Apr 28 20:13:07 2014 (r44678) @@ -153,8 +153,8 @@ the crash dump, locate the debug version of your kernel (normally called kernel.debug) and the path to the source files used to build your kernel (normally - /usr/obj/usr/src/sys/KERNCONF, - where KERNCONF + /usr/obj/usr/src/sys/KERNCONF, + where KERNCONF is the ident specified in a kernel &man.config.5;). With those two pieces of info, let the debugging commence! @@ -162,7 +162,7 @@ To enter into the debugger and begin getting information from the dump, the following steps are required at a minimum: - &prompt.root; cd /usr/obj/usr/src/sys/KERNCONF + &prompt.root; cd /usr/obj/usr/src/sys/KERNCONF &prompt.root; kgdb kernel.debug /var/crash/vmcore.0 You can debug the crash dump using the kernel sources just like @@ -180,7 +180,7 @@ your patch winds its way into the source tree via a problem report, mailing lists, or by being able to commit it! - 1:&prompt.root; cd /usr/obj/usr/src/sys/KERNCONF + 1:&prompt.root; cd /usr/obj/usr/src/sys/KERNCONF 2:&prompt.root; kgdb kernel.debug /var/crash/vmcore.0 3:GNU gdb 5.2.1 (FreeBSD) 4:Copyright 2002 Free Software Foundation, Inc. @@ -901,7 +901,7 @@ hw.firewire.dcons_crom.force_console=1Run &man.dconschat.8;, with: - &prompt.root; dconschat -e \# -br -G 12345 -t 00-11-22-33-44-55-66-77 + &prompt.root; dconschat -e \# -br -G 12345 -t 00-11-22-33-44-55-66-77 The following key combinations can be used once &man.dconschat.8; is running: Modified: head/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.xml Mon Apr 28 19:36:49 2014 (r44677) +++ head/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.xml Mon Apr 28 20:13:07 2014 (r44678) @@ -122,8 +122,8 @@ program is used, such as grep. This name will be used when looking for the compiled catalog file. The &man.catopen.3; call looks for this file - in /usr/share/nls/locale/catname - and in /usr/local/share/nls/locale/catname, + in /usr/share/nls/locale/catname + and in /usr/local/share/nls/locale/catname, where locale is the locale set and catname is the catalog name being discussed. The second parameter is a constant, which can have Modified: head/en_US.ISO8859-1/books/developers-handbook/policies/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/developers-handbook/policies/chapter.xml Mon Apr 28 19:36:49 2014 (r44677) +++ head/en_US.ISO8859-1/books/developers-handbook/policies/chapter.xml Mon Apr 28 20:13:07 2014 (r44678) @@ -167,13 +167,13 @@ SVN, vendor branches were imported with the same layout as the main tree. For example, the foo vendor sources ended up in - vendor/foo/dist/contrib/foo, + vendor/foo/dist/contrib/foo, but it is pointless and rather inconvenient. What we really want is to have the vendor source directly in - vendor/foo/dist, + vendor/foo/dist, like this: - &prompt.user; cd vendor/foo/dist/contrib/foo + &prompt.user; cd vendor/foo/dist/contrib/foo &prompt.user; svn move $(svn list) ../.. &prompt.user; cd ../.. &prompt.user; svn remove contrib @@ -207,8 +207,8 @@ that corresponds to the last change was made to the vendor tree prior to importing new sources is also needed: - &prompt.user; cd head/contrib/foo -&prompt.user; svn merge --record-only svn_base/vendor/foo/dist@12345678 . + &prompt.user; cd head/contrib/foo +&prompt.user; svn merge --record-only svn_base/vendor/foo/dist@12345678 . &prompt.user; svn commit where svn_base is the base @@ -231,30 +231,30 @@ sorted lists of the contents of the vendor tree and of the sources you are about to import: - &prompt.user; cd vendor/foo/dist -&prompt.user; svn list -R | grep -v '/$' | sort > ../old -&prompt.user; cd ../foo-9.9 -&prompt.user; find . -type f | cut -c 3- | sort > ../new + &prompt.user; cd vendor/foo/dist +&prompt.user; svn list -R | grep -v '/$' | sort > ../old +&prompt.user; cd ../foo-9.9 +&prompt.user; find . -type f | cut -c 3- | sort > ../new With these two files, the following command will list list removed files (files only in - old): + old): - &prompt.user; comm -23 ../old ../new + &prompt.user; comm -23 ../old ../new While the command below will list added files (files only in - new): + new): - &prompt.user; comm -13 ../old ../new + &prompt.user; comm -13 ../old ../new Let's put this together: - &prompt.user; cd vendor/foo/foo-9.9 + &prompt.user; cd vendor/foo/foo-9.9 &prompt.user; tar cf - . | tar xf - -C ../dist &prompt.user; cd ../dist -&prompt.user; comm -23 ../old ../new | xargs svn remove -&prompt.user; comm -13 ../old ../new | xargs svn add +&prompt.user; comm -23 ../old ../new | xargs svn remove +&prompt.user; comm -13 ../old ../new | xargs svn add If there are new directories in the new @@ -303,11 +303,11 @@ should tag it for future reference. The best and quickest way is to do it directly in the repository: - &prompt.user; svn copy svn_base/vendor/foo/dist svn_base/vendor/foo/9.9 + &prompt.user; svn copy svn_base/vendor/foo/dist svn_base/vendor/foo/9.9 To get the new tag, you can update your working copy of - vendor/foo. + vendor/foo. If you choose to do the copy in the checkout @@ -325,9 +325,9 @@ SVN not to handle merge conflicts yet, because they will be taken care of manually: - &prompt.user; cd head/contrib/foo + &prompt.user; cd head/contrib/foo &prompt.user; svn update -&prompt.user; svn merge --accept=postpone svn_base/vendor/foo/dist +&prompt.user; svn merge --accept=postpone svn_base/vendor/foo/dist Resolve any conflicts, and make sure that any files that were added or removed in the vendor tree have been @@ -335,7 +335,7 @@ a good idea to check differences against the vendor branch: - &prompt.user; svn diff --no-diff-deleted --old=svn_base/vendor/foo/dist --new=. + &prompt.user; svn diff --no-diff-deleted --old=svn_base/vendor/foo/dist --new=. The option tells SVN not to check files that are in the @@ -418,7 +418,7 @@ Object files are named - arch/filename.o.uu>. + arch/filename.o.uu>. Modified: head/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml Mon Apr 28 19:36:49 2014 (r44677) +++ head/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml Mon Apr 28 20:13:07 2014 (r44678) @@ -363,11 +363,11 @@ have rank 9999. - RELENG_x + RELENG_x has rank xx99. - RELENG_x_y + RELENG_x_y has rank xxyy. Modified: head/en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml Mon Apr 28 19:36:49 2014 (r44677) +++ head/en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml Mon Apr 28 20:13:07 2014 (r44678) @@ -600,7 +600,7 @@ compiler to add it. The rule is that if the library is called - libsomething.a, + libsomething.a, you give cc the argument . For example, the math library is @@ -996,7 +996,7 @@ free(foo); to find out the process ID of your program, and do - &prompt.user; kill -ABRT pid + &prompt.user; kill -ABRT pid where @@ -1147,7 +1147,7 @@ install: We can tell make which target we want to make by typing: - &prompt.user; make target + &prompt.user; make target make will then only look at that target and ignore any others. For example, if we type @@ -1376,12 +1376,12 @@ DISTFILES= scheme-microcode+dist-7. gdb (GNU debugger). You start it up by typing - &prompt.user; gdb progname + &prompt.user; gdb progname although many people prefer to run it inside Emacs. You can do this by: - M-x gdb RET progname RET + M-x gdb RET progname RET Using a debugger allows you to run the program under more controlled circumstances. Typically, you can step through the @@ -1543,7 +1543,7 @@ main() { listings of core files and sweat over machine code manuals, but now life is a bit easier. Incidentally, under FreeBSD and other 4.4BSD systems, a core file is called - progname.core instead of just + progname.core instead of just core, to make it clearer which program a core file belongs to. @@ -1551,7 +1551,7 @@ main() { the usual way. Instead of typing break or run, type - (gdb) core progname.core + (gdb) core progname.core If you are not in the same directory as the core file, you will have to do dir @@ -1609,7 +1609,7 @@ Cannot access memory at address 0x702079 use ps to find the process ID for the child, and do - (gdb) attach pid + (gdb) attach pid in gdb, and then debug as usual. @@ -1851,7 +1851,7 @@ else if (pid == 0) { /* child */ if you are doing something outside Emacs and you want to edit a file, you can just type in - &prompt.user; emacsclient filename + &prompt.user; emacsclient filename and then you can edit the file in your Modified: head/en_US.ISO8859-1/books/developers-handbook/x86/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/developers-handbook/x86/chapter.xml Mon Apr 28 19:36:49 2014 (r44677) +++ head/en_US.ISO8859-1/books/developers-handbook/x86/chapter.xml Mon Apr 28 20:13:07 2014 (r44678) @@ -249,7 +249,7 @@ the system know about it. After your pro linked, you need to brand the executable: -&prompt.user; brandelf -t Linux filename +&prompt.user; brandelf -t Linux filename @@ -870,7 +870,7 @@ If you do not have nasm &prompt.user; su -Password:your root password +Password:your root password &prompt.root; cd /usr/ports/devel/nasm &prompt.root; make install &prompt.root; exit @@ -2313,15 +2313,15 @@ to send the output to a different file. I end up using it like this: -&prompt.user; tuc myfile tempfile -&prompt.user; mv tempfile myfile +&prompt.user; tuc myfile tempfile +&prompt.user; mv tempfile myfile It would be nice to have a ftuc, i.e., fast tuc, and use it like this: -&prompt.user; ftuc myfile +&prompt.user; ftuc myfile In this chapter, then, we will write @@ -3343,7 +3343,7 @@ specified. To get the 11th field of each record, I can now do: -&prompt.user; csv '-t;' data.csv | awk '-F;' '{print $11}' +&prompt.user; csv '-t;' data.csv | awk '-F;' '{print $11}' The code stores the options (except for the file descriptors)