Bug 105256

Summary: [patch] nit-picking to Securing FreeBSD (14.3) chapter of handbook
Product: Documentation Reporter: Niclas Zeising <lothrandil>
Component: Books & ArticlesAssignee: Giorgos Keramidas <keramida>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description Niclas Zeising 2006-11-07 21:20:17 UTC 
I was reading through the "Securing FreeBSD" chapter of the handbook (section 14.3) and found some wording choices which I found wrong or hard to comprehend, along with some spelling mistakes.
The attached patch changes the wording and spelling in a way I find appropriate. Feel free to do whatever you like with the patch.

Fix: Apply the whole patch, or the parts you find good. (Note, I had to add the ".txt" extension to the patch so the browser would report it as text/*)

Patch attached with submission follows:
How-To-Repeat: Read Section 14.3 of the handbook
Comment 1 dfilter service freebsd_committer freebsd_triage 2006-11-12 00:13:14 UTC 
keramida    2006-11-12 00:13:05 UTC

  FreeBSD doc repository

  Modified files:
    en_US.ISO8859-1/books/handbook/security chapter.sgml 
  Log:
  Wording fixes and other minor nits to the 'Security' chapter.
  
  Submitted by:   Niclas Zeising <lothrandil@n00b.apagnu.se>
  PR:             docs/105256
  
  Revision  Changes    Path
  1.307     +26 -27    doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
Comment 2 Giorgos Keramidas freebsd_committer freebsd_triage 2006-11-12 00:13:20 UTC 
On 2006-11-07 21:13, Niclas Zeising <lothrandil@n00b.apagnu.se> wrote:
> >Number:         105256
> >Category:       docs

> I was reading through the "Securing FreeBSD" chapter of the handbook
> (section 14.3) and found some wording choices which I found wrong or
> hard to comprehend, along with some spelling mistakes.

Most of them are nice changes.  I only noticed one minor nit:

% diff -r 1d6db58d597b en_US.ISO8859-1/books/handbook/security/chapter.sgml
% --- a/en_US.ISO8859-1/books/handbook/security/chapter.sgml      Sun Nov 12 01:07:56 2006 +0100
% +++ b/en_US.ISO8859-1/books/handbook/security/chapter.sgml      Sun Nov 12 01:09:04 2006 +0100
% @@ -717,7 +717,7 @@
%         <literal>nosuid</literal> options (see &man.mount.8;) are what you
%         want to look into.  You should probably scan them anyway, at least
%         once a week, since the object of this layer is to detect a break-in
% -       attempt, whether or not the attempt succeds.</para>
% +       attempt, whether or not the attempt succeeds.</para>
% 
%        <para>Process accounting (see &man.accton.8;) is a relatively
%         low-overhead feature of the operating system which might help

which I fixed before committing this.  Thanks!
Comment 3 Giorgos Keramidas freebsd_committer freebsd_triage 2006-11-12 00:13:39 UTC 
State Changed
From-To: open->closed

Committed, thanks.
Comment 4 Giorgos Keramidas freebsd_committer freebsd_triage 2006-11-12 00:13:39 UTC 
Responsible Changed
From-To: freebsd-doc->keramida
Comment 5 Niclas Zeising 2006-11-12 09:35:35 UTC 
Giorgos Keramidas wrote:
> On 2006-11-07 21:13, Niclas Zeising <lothrandil@n00b.apagnu.se> wrote:
>>> Number:         105256
>>> Category:       docs
> 
>> I was reading through the "Securing FreeBSD" chapter of the handbook
>> (section 14.3) and found some wording choices which I found wrong or
>> hard to comprehend, along with some spelling mistakes.
> 
> Most of them are nice changes.  I only noticed one minor nit:
> 
> % diff -r 1d6db58d597b en_US.ISO8859-1/books/handbook/security/chapter.sgml
> % --- a/en_US.ISO8859-1/books/handbook/security/chapter.sgml      Sun Nov 12 01:07:56 2006 +0100
> % +++ b/en_US.ISO8859-1/books/handbook/security/chapter.sgml      Sun Nov 12 01:09:04 2006 +0100
> % @@ -717,7 +717,7 @@
> %         <literal>nosuid</literal> options (see &man.mount.8;) are what you
> %         want to look into.  You should probably scan them anyway, at least
> %         once a week, since the object of this layer is to detect a break-in
> % -       attempt, whether or not the attempt succeds.</para>
> % +       attempt, whether or not the attempt succeeds.</para>
> % 
> %        <para>Process accounting (see &man.accton.8;) is a relatively
> %         low-overhead feature of the operating system which might help
> 
> which I fixed before committing this.  Thanks!
> 

Great! My spelling isn't always that good ;)
Anyways, thanks!
Regards!
//Niclas