Re: [diffs] faq/faq14.html, faq/index.html: punctuation, broken link, update.

Stuart Henderson <[email protected]>
Newsgroups gmane.os.openbsd.www
Message-ID <[email protected]>
On 2009-01-14, Alan R. S. Bueno <[email protected]> wrote:
> faq/faq14.html:
> . faq8.html#softdep doesn't exist. faq14.html#SoftUpdates is better.
>
> faq/index.html:
> . Update 14.8 ToC entry.

I've applied these.

> faq/faq14.html:
> . Punctuation fixes.

but not this yet; there's some inconsistency in the current page with
.) vs ). - I'd rather fix the lot in one go but don't have time right now.

thanks!


> Index: faq14.html
>===================================================================
> RCS file: /cvs/www/faq/faq14.html,v
> retrieving revision 1.181
> diff -u -r1.181 faq14.html
> --- faq14.html	30 Nov 2008 03:58:34 -0000	1.181
> +++ faq14.html	14 Jan 2009 05:25:35 -0000
> @@ -1801,10 +1801,9 @@
>
>  Depending on what happened, one or other of those may be preferable
>  (with dying discs you want the data first, with sloppy fingers you can
> -just have the label)
> +just have the label).
>
> <p>
> -
>  The first tool you need is
> <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=scan_ffs">scan_ffs(8)</a>
>  (note the underscore, it isn't called "scanffs").
> @@ -2204,10 +2203,10 @@
>  OpenBSD.
>  This can be done with both USB devices (assuming your computer can
>  boot from a USB flash device, not all can), or with a non-USB (i.e.,
> -CF) device with an IDE or SATA adapter.
> -(Non-USB devices attached with a USB adapter are treated as USB devices).
> +CF) device with an IDE or SATA adapter
> +(non-USB devices attached with a USB adapter are treated as USB devices).
>  In some cases, you may actually use a device in both ways (load the
> -media in a USB adapter, but run it in an IDE adapter)
> +media in a USB adapter, but run it in an IDE adapter).
>
> <p>
>  A flash device attached to a USB port will show up as a
> @@ -2240,7 +2239,7 @@
> <ul>
> <li><b>Speed:</b> In general, flash devices are much slower than hard disks,
>  especially when it comes to writing.
> -Using <a href="faq8.html#softdep">soft updates</a> will help this
> +Using <a href="faq14.html#SoftUpdates">soft updates</a> will help this
>  considerably, as will using the "noatime" mount option.
>
> <li><b>"Write fatigue":</b>
> @@ -2470,8 +2469,8 @@
>  cache misses be noticed with a tool such as
> <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=systat&amp;sektion=1">systat(1)</a>,
>  is to examine the system's current computed value with
> -<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sysctl&amp;sektion=8">sysctl(8)</a>,
> -(which calls this parameter "<tt>kern.maxvnodes</tt>") and to increase this
> +<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sysctl&amp;sektion=8">sysctl(8)</a>
> +(which calls this parameter "<tt>kern.maxvnodes</tt>"), and to increase this
>  value until either the namei() cache hit rate improves or it is determined that
>  the system does not benefit substantially from an increase in the size of the
>  namei() cache. After the value has been determined, you can
>
>
>
>
> Index: index.html
>===================================================================
> RCS file: /cvs/www/faq/index.html,v
> retrieving revision 1.298
> diff -u -r1.298 index.html
> --- index.html	7 Jan 2009 21:59:18 -0000	1.298
> +++ index.html	14 Jan 2009 05:30:47 -0000
> @@ -386,8 +386,8 @@
> <li><a href="faq14.html#Boot386"    >14.6 - How does OpenBSD/i386 boot?</a>
> <li><a href="faq14.html#LargeDrive" >14.7 - What are the issues regarding
>      large drives with OpenBSD?</a>
> -<li><a href="faq14.html#InstBoot"   >14.8 - Installing Bootblocks - i386
> -    specific</a>
> +<li><a href="faq14.html#InstBoot"   >14.8 - Installing Bootblocks -
> +    i386/amd64 specific</a>
> <li><a href="faq14.html#Backup"     >14.9 - Preparing for disaster:
>     Backing up and Restoring from tape.</a>
> <li><a href="faq14.html#MountImage" >14.10 - Mounting disk images in
>
>
> Thank you!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.