Attachment 108319 Details for Bug 149140 – file.diff

[patch] file.diff

file.diff (text/plain), 17.29 KB, created by Jimmy Olgeni on 2010-07-31 11:00:13 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Jimmy Olgeni

Created: 2010-07-31 11:00:13 UTC

Size: 17.29 KB

patch

obsolete

>Index: casestudy-argentina.com/article.sgml
>===================================================================
>RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/casestudy-argentina.com/article.sgml,v
>retrieving revision 1.2
>diff -u -r1.2 article.sgml
>--- casestudy-argentina.com/article.sgml	4 Sep 2005 22:03:59 -0000	1.2
>+++ casestudy-argentina.com/article.sgml	31 Jul 2010 09:44:33 -0000
>@@ -296,7 +296,7 @@
>     <para>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
>Index: cups/article.sgml
>===================================================================
>RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/cups/article.sgml,v
>retrieving revision 1.3
>diff -u -r1.3 article.sgml
>--- cups/article.sgml	24 Oct 2008 23:18:46 -0000	1.3
>+++ cups/article.sgml	31 Jul 2010 09:44:33 -0000
>@@ -141,7 +141,7 @@
>       entering <ulink url="http://localhost:631"></ulink> in the
>       browser's URL bar.  If the <application>CUPS</application> server
>       is on another machine on the network, substitute the server's
>-      local <acronym>IP</acronym> addresss for
>+      local <acronym>IP</acronym> address for
>       <hostid>localhost</hostid>.  The <application>CUPS</application>
>       web interface is fairly self-explanatory, as there are sections
>       for managing printers and print jobs, authorizing users, and more.
>@@ -263,7 +263,7 @@
>       listed below.  Please note that this sample
>       <filename>cupsd.conf</filename> file sacrifices security for
>       easier configuration; once the administrator successfully
>-      connnects to the <application>CUPS</application> server and
>+      connects to the <application>CUPS</application> server and
>       configures the clients, it is advisable to revisit this
>       configuration file and begin locking down access.</para>
> 
>Index: euro/article.sgml
>===================================================================
>RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/euro/article.sgml,v
>retrieving revision 1.11
>diff -u -r1.11 article.sgml
>--- euro/article.sgml	18 Aug 2005 07:53:23 -0000	1.11
>+++ euro/article.sgml	31 Jul 2010 09:44:34 -0000
>@@ -193,7 +193,7 @@
>       <para>Most keyboard maps should already be set up correctly. I.e: If you
> 	have a german keyboard and your Umlaut keys are working, you can
> 	safely skip this section since the keyboard already maps whatever key
>-	combination is necessary (e.g.: <keycombo action=simul><keycap>Alt
>+	combination is necessary (e.g.: <keycombo action="simul"><keycap>Alt
> 	    Gr</keycap><keycap>e</keycap></keycombo>) to decimal value 164.
> 	If running into problems, the best way to check is to take a look at
> 	<filename>/usr/share/syscons/keymaps/*.kbd</filename>. The format of 
>Index: ldap-auth/article.sgml
>===================================================================
>RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/ldap-auth/article.sgml,v
>retrieving revision 1.2
>diff -u -r1.2 article.sgml
>--- ldap-auth/article.sgml	17 Sep 2008 19:29:18 -0000	1.2
>+++ ldap-auth/article.sgml	31 Jul 2010 09:44:34 -0000
>@@ -31,7 +31,7 @@
>     </legalnotice>
> 
>     <abstract>
>-      <para>This document is indended as a guide for the configuration
>+      <para>This document is intended as a guide for the configuration
> 	of an LDAP server (principally an <application>OpenLDAP</application>
> 	server) for authentication on &os;.  This is useful for situations
> 	where many servers need the same user accounts, for example as a
>@@ -286,7 +286,7 @@
>       <title>Entries in the Database</title>
> 
>       <para>Authentication against an LDAP directory is generally
>-	accomplished by attempting to bind to the directory as the connectin user.
>+	accomplished by attempting to bind to the directory as the connecting user.
> 	This is done by establishing a <quote>simple</quote>
> 	bind on the directory with the user name supplied.  If there is an
> 	entry with the <literal>uid</literal> equal to the user name and
>@@ -344,7 +344,7 @@
> uid: tuser
> cn: tuser</programlisting>
> 
>-      <para>I start my LDAP users' UIDs at 10000 to avoid colisions with
>+      <para>I start my LDAP users' UIDs at 10000 to avoid collisions with
> 	system accounts; you can configure whatever number you wish here,
> 	as long as it's less than 65536.</para>
> 
>@@ -456,7 +456,7 @@
> 	<para>With this configuration you should be able to authenticate
> 	  a user against an LDAP directory.
> 	  <application>PAM</application> will perform a bind with your
>-	  credentails, and if successful will tell
>+	  credentials, and if successful will tell
> 	  <application>SSH</application> to allow access.</para>
> 
> 	<para>However it is not a good idea to allow
>@@ -890,7 +890,7 @@
>       <option>-signkey</option>:</para>
> 
>     <example id="ca-sign">
>-      <title>Signing as a certificate authorty</title>
>+      <title>Signing as a certificate authority</title>
> 
>       <screen>&prompt.user; <userinput>openssl x509 -req -days 1024 \
> -in ldap-server-one.csr -CA root.crt -CAkey root.key \
>Index: linux-comparison/article.sgml
>===================================================================
>RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/linux-comparison/article.sgml,v
>retrieving revision 1.10
>diff -u -r1.10 article.sgml
>--- linux-comparison/article.sgml	8 Aug 2006 19:35:13 -0000	1.10
>+++ linux-comparison/article.sgml	31 Jul 2010 09:44:34 -0000
>@@ -546,6 +546,3 @@
>     </orderedlist>
>   </sect1>
> </article>
>-
>-
>-
>Index: linux-emulation/article.sgml
>===================================================================
>RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/linux-emulation/article.sgml,v
>retrieving revision 1.3
>diff -u -r1.3 article.sgml
>--- linux-emulation/article.sgml	21 Jul 2009 15:19:50 -0000	1.3
>+++ linux-emulation/article.sgml	31 Jul 2010 09:44:35 -0000
>@@ -265,8 +265,8 @@
> 	be usable these days.</para>
> 
>       <para>&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&nbsp;2006, there are development branches for 6.X development
>@@ -799,7 +799,7 @@
> 	  <title>Atomic operations and memory barriers</title>
> 
> 	  <para>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 <literal>.long.</literal>
>@@ -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.</para>
> 	</sect4>
> 
>@@ -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.</para>
>+	  Both tables define up to 8191 entries.</para>
>       </sect3>
> 
>       <sect3 id="linux-i386">
>@@ -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 <varname>filename</varname> parameter is
> 	  absolute <varname>dirfd</varname> is ignored but when the path to
> 	  the file is relative, it comes to the play.  The
>-	  <varname>dirfd</varname> paramtere is a directory relative to which
>+	  <varname>dirfd</varname> parameter is a directory relative to which
> 	  the relative pathname is checked.  The <varname>dirfd</varname>
> 	  parameter is a file descriptor of some directory or
> 	  <literal>AT_FDCWD</literal>.  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.</para>
>+	  for altering a printable string for uniform debugging messages.</para>
>       </sect3>
>     </sect2>    
>   </sect1>
>@@ -2256,7 +2256,7 @@
> 	the &linux; programs included in &os; Ports&nbsp;Collection with
> 	Fedora&nbsp;Core&nbsp;4 at 2.6.16 and there are some rudimentary
> 	reports of success with Fedora&nbsp;Core&nbsp;6 at 2.6.16.  The
>-	Fedora&nbsp;Core&nbsp;6	linux_base was recently commited enabling
>+	Fedora&nbsp;Core&nbsp;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.</para>
>Index: linux-users/article.sgml
>===================================================================
>RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/linux-users/article.sgml,v
>retrieving revision 1.8
>diff -u -r1.8 article.sgml
>--- linux-users/article.sgml	4 Jul 2009 20:07:29 -0000	1.8
>+++ linux-users/article.sgml	31 Jul 2010 09:44:35 -0000
>@@ -135,7 +135,7 @@
> 	the &os; Handbook: <ulink
> 	  url="&url.base;/doc/en_US.ISO8859-1/books/handbook/packages-using.html">Using the Packages System</ulink>.</para>
>     </sect2>
>-      
>+
>     <sect2 id="ports">
>       <title>Ports</title>
> 
>@@ -212,7 +212,7 @@
> 	<listitem><simpara>You can apply your own patches if you are so
> 	  inclined.</simpara></listitem>
>       </itemizedlist>
>-        
>+
>       <para>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 @@
>       <filename>/etc/rc.conf</filename>.  Also, when installing additional
>       applications be sure to review the documentation to determine how to
>       enable any associated services.</para>
>-  
>+
>     <para>The following snippet from <filename>/etc/rc.conf</filename> enables
>       &man.sshd.8; and <application>Apache 2.2</application>.  It also
>       specifies that <application>Apache</application> should be started
>@@ -295,10 +295,10 @@
>       system):</para>
> 
>     <screen>&prompt.root; <userinput><replaceable>/etc/rc.d/sshd</replaceable> start</userinput></screen>
>-    
>+
>     <para>If a service has not been enabled it can be started from the
>       command line using <option>forcestart</option>:</para>
>-    
>+
>     <screen>&prompt.root; <userinput><replaceable>/etc/rc.d/sshd</replaceable> forcestart</userinput></screen>
>   </sect1>
> 
>@@ -328,7 +328,7 @@
>         media: Ethernet autoselect (1000baseTX &lt;full-duplex&gt;)
>         status: active</screen>
>     </sect2>
>-     
>+
>     <sect2 id="ipaddress">
>       <title>IP Configuration</title>
> 
>@@ -355,7 +355,7 @@
> 
>     <para>Like <application>IPTABLES</application> in &linux;, &os; also offers
>       a kernel level firewall; actually &os; offers three firewalls:</para>
>-    
>+
>     <itemizedlist>
>       <listitem><simpara><ulink url="&url.base;/doc/en_US.ISO8859-1/books/handbook/firewalls-ipfw.html">IPFIREWALL</ulink></simpara></listitem>
>       <listitem><simpara><ulink url="&url.base;/doc/en_US.ISO8859-1/books/handbook/firewalls-ipf.html">IPFILTER</ulink></simpara></listitem>
>@@ -584,7 +584,7 @@
>     <para>Hopefully this document has provided you with enough to get
>       started with &os;.   Be sure to take a look at the <ulink
> 	url="&url.base;/doc/en_US.ISO8859-1/books/handbook/index.html">&os;&nbsp;Handbook</ulink>
>-      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.</para>
>   </sect1>
> </article>
>Index: portbuild/article.sgml
>===================================================================
>RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v
>retrieving revision 1.58
>diff -u -r1.58 article.sgml
>--- portbuild/article.sgml	1 Jun 2010 01:30:13 -0000	1.58
>+++ portbuild/article.sgml	31 Jul 2010 09:44:36 -0000
>@@ -64,7 +64,7 @@
>       <filename>/usr/ports/Tools/portbuild/scripts/</filename>.</para>
> 
>     <para>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:</para>
> 
>     <itemizedlist>
>Index: problem-reports/article.sgml
>===================================================================
>RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/problem-reports/article.sgml,v
>retrieving revision 1.61
>diff -u -r1.61 article.sgml
>--- problem-reports/article.sgml	30 Dec 2008 08:24:54 -0000	1.61
>+++ problem-reports/article.sgml	31 Jul 2010 09:44:36 -0000
>@@ -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.</para>
> 	    </listitem>
> 
>Index: releng-packages/article.sgml
>===================================================================
>RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/releng-packages/article.sgml,v
>retrieving revision 1.19
>diff -u -r1.19 article.sgml
>--- releng-packages/article.sgml	12 Mar 2006 13:45:13 -0000	1.19
>+++ releng-packages/article.sgml	31 Jul 2010 09:44:36 -0000
>@@ -209,7 +209,7 @@
> 
>       <listitem><para>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
> 	<filename>oneshot.pl</filename> set the <varname>fake</varname>
> 	variable to 1 and instead of actually copying the files it will
>Index: serial-uart/article.sgml
>===================================================================
>RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/serial-uart/article.sgml,v
>retrieving revision 1.13
>diff -u -r1.13 article.sgml
>--- serial-uart/article.sgml	29 Nov 2004 21:43:34 -0000	1.13
>+++ serial-uart/article.sgml	31 Jul 2010 09:44:36 -0000
>@@ -300,7 +300,7 @@
> 		
> 	  <para>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
>Index: storage-devices/article.sgml
>===================================================================
>RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/storage-devices/article.sgml,v
>retrieving revision 1.15
>diff -u -r1.15 article.sgml
>--- storage-devices/article.sgml	29 Nov 2004 21:43:34 -0000	1.15
>+++ storage-devices/article.sgml	31 Jul 2010 09:44:37 -0000
>@@ -40,7 +40,7 @@
>     <para>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.</para>
>+      of the first affordable 5.25" Winchester disk.</para>
> 	  
>     <para>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 @@
> 	  <screen>&prompt.root; <userinput>mt -f /dev/st0ctl.0 blocksize 1024</userinput></screen>
> 	      
> 	  <para>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:</para>
> 	      
> 	  <screen>&prompt.root; <userinput>/sbin/scsi -f /dev/rst0.ctl -s 600 -c "4 0 0 0 0 0"</userinput></screen>

Actions: View | Diff

Attachments on bug 149140: 108319