Hi, I wanted to add some content to FAQ14 but I saw some errors there, so first I corrected them.
The problems are - No 14.13 - No 20.2 - 14.5.*, 14.17.* and 14.20.* are not linked in the "Table of Contents" Also what's the policy about giving numbers (like 14.5.1)? Because they are assigned to "h3" heading tags, but not all "h3" are numbered. If patches between the different problems are needed, I can give them. Cheers, Daniel Index: faq14.html =================================================================== RCS file: /cvs/www/faq/faq14.html,v retrieving revision 1.246 diff -u -p -u -p -r1.246 faq14.html --- faq14.html 8 Nov 2014 20:15:58 -0000 1.246 +++ faq14.html 16 Nov 2014 17:29:33 -0000 @@ -29,6 +29,11 @@ <li><a href="#disklabel" >14.3 - Using OpenBSD's disklabel(8)</a> <li><a href="#NewDisk" >14.4 - Adding extra disks in OpenBSD</a> <li><a href="#Swap" >14.5 - How is swap handled?</a> + <ul> + <li><a href="#SwapAbout">14.5.1 - About swap</a> + <li><a href="#SwapPartition">14.5.2 - Swapping to a partition</a> + <li><a href="#SwapFile">14.5.3 - Swapping to a file</a> + </ul> <li><a href="#SoftUpdates">14.6 - Soft Updates</a> <li><a href="#Boot386" >14.7 - How do OpenBSD/i386 and OpenBSD/amd64 boot?</a> <li><a href="#LargeDrive" >14.8 - What are the issues regarding large @@ -38,27 +43,37 @@ Restoring from tape.</a> <li><a href="#MountImage" >14.11 - Mounting disk images in OpenBSD</a> <li><a href="#pciideErr" >14.12 - Help! I'm getting errors with IDE DMA!</a> -<li><a href="#NegSpace" >14.14 - Why does <tt>df(1)</tt> tell me I +<li><a href="#NegSpace" >14.13 - Why does <tt>df(1)</tt> tell me I have over 100% of my disk used?</a> -<li><a href="#OhBugger" >14.15 - Recovering partitions after deleting +<li><a href="#OhBugger" >14.14 - Recovering partitions after deleting the disklabel</a> -<li><a href="#foreignfs" >14.16 - Can I access data on filesystems other than FFS?</a> +<li><a href="#foreignfs" >14.15 - Can I access data on filesystems other than FFS?</a> <ul> - <li><a href="#foreignfsafter">14.16.1 - The partitions are not in my + <li><a href="#foreignfsafter">14.15.1 - The partitions are not in my disklabel! What should I do?</a> </ul> -<li><a href="#flashmem" >14.17 - Can I use a flash memory device with OpenBSD?</a> +<li><a href="#flashmem" >14.16 - Can I use a flash memory device with OpenBSD?</a> <ul> - <li><a href="#flashmemPortable">14.17.1 - Flash memory as a portable storage + <li><a href="#flashmemPortable">14.16.1 - Flash memory as a portable storage device</a> - <li><a href="#flashmemBoot">14.17.2 - Flash memory as bootable storage</a> - <li><a href="#flashmemLive">14.17.3 - How can I make a "Live" bootable USB + <li><a href="#flashmemBoot">14.16.2 - Flash memory as bootable storage</a> + <li><a href="#flashmemLive">14.16.3 - How can I make a "Live" bootable USB device?</a> </ul> -<li><a href="#DiskOpt" >14.18 - Optimizing disk performance</a> -<li><a href="#Async" >14.19 - Why aren't we using async mounts?</a> -<li><a href="#altroot" >14.20 - Duplicating your root partition: altroot</a> -<li><a href="#softraid" >14.21 - How do I use softraid(4)?</a> +<li><a href="#DiskOpt" >14.17 - Optimizing disk performance</a> + <ul> + <li><a href="#Optsoftu">14.17.1 - Soft updates</a> + <li><a href="#Optmaxvnodes">14.17.2 - Size of the namei() cache</a> + </ul> +<li><a href="#Async" >14.18 - Why aren't we using async mounts?</a> +<li><a href="#altroot" >14.19 - Duplicating your root partition: altroot</a> +<li><a href="#softraid" >14.20 - How do I use softraid(4)?</a> + <ul> + <li><a href="#softraidDI">14.20.1 - Doing the install</a> + <li><a href="#softraidNotes">14.20.2 - Softraid notes</a> + <li><a href="#softraidDR">14.20.3 - Disaster recovery</a> + <li><a href="#softraidCrypto">14.20.4 - Softraid Crypto</a> + </ul> </ul> <hr> @@ -740,10 +755,9 @@ create an empty directory /usr/local. Th the files are there! <p> -<a name="SwapFile"></a> <a name="Swap"></a> <h2>14.5 - How is swap handled?</h2> - +<a name="SwapAbout"></a> <h3>14.5.1 - About swap</h3> Historically, all kinds of rules have been tossed about to guide administrators on how much swap to configure on their machines. @@ -784,7 +798,7 @@ In OpenBSD, swap is managed with the program, which adds, removes, lists and prioritizes swap devices and files. - +<a name="SwapPartition"></a> <h3>14.5.2 - Swapping to a partition</h3> <p> On OpenBSD, the 'b' partition of the boot drive is used by default and @@ -801,7 +815,7 @@ something like: /dev/sd3d none swap sw 0 0 </pre></blockquote> - +<a name="SwapFile"></a> <h3>14.5.3 - Swapping to a file</h3> (Note: if you are looking to swap to a file because you are getting @@ -1801,7 +1815,7 @@ device. <p> <a name="NegSpace"></a> -<h2>14.14 - Why does <tt>df(1)</tt> tell me I have over 100% of my disk +<h2>14.13 - Why does <tt>df(1)</tt> tell me I have over 100% of my disk used?</h2> People are sometimes surprised to find they have <i>negative</i> available disk space, or more than 100% of a filesystem in use, as shown @@ -1825,7 +1839,7 @@ command. <p> <a name="OhBugger"></a> -<h2>14.15 - Recovering partitions after deleting the disklabel</h2> +<h2>14.14 - Recovering partitions after deleting the disklabel</h2> <p> If you have a damaged partition table, there are various things @@ -1877,7 +1891,7 @@ it until the next reboot. <p> <a name="foreignfs"></a> -<h2>14.16 - Can I access data on filesystems other than FFS?</h2> +<h2>14.15 - Can I access data on filesystems other than FFS?</h2> <!-- This article written by Steven Mestdagh, ste...@openbsd.org, and released under the BSD license --> @@ -2031,7 +2045,7 @@ operating system associated with the fil <p> <a name="foreignfsafter"></a> -<h3>14.16.1 - The partitions are not in my disklabel! What should I do?</h3> +<h3>14.15.1 - The partitions are not in my disklabel! What should I do?</h3> If you install foreign filesystems on your system (often the result of adding a new operating system) after you have already installed OpenBSD, @@ -2106,9 +2120,9 @@ You can follow a very similar procedure <p> <a name="flashmem"></a> -<h2>14.17 - Can I use a flash memory device with OpenBSD?</h2> +<h2>14.16 - Can I use a flash memory device with OpenBSD?</h2> <a name="flashmemPortable"></a> -<h3>14.17.1 - Flash memory as a portable storage device</h3> +<h3>14.16.1 - Flash memory as a portable storage device</h3> <!-- This article written by Steven Mestdagh, ste...@openbsd.org, and released under the BSD license --> @@ -2244,7 +2258,7 @@ umass0 detached </pre></blockquote> <a name="flashmemBoot"></a> -<h3>14.17.2 - Flash memory as bootable storage</h3> +<h3>14.16.2 - Flash memory as bootable storage</h3> <!-- This article written by Nick Holland n...@openbsd.org, and released under the BSD license --> One can also use flash memory in various forms as bootable disk with @@ -2363,7 +2377,7 @@ which could be played when they booted f </ul> <a name="flashmemLive"></a> -<h3>14.17.3 - How do I create a bootable "Live" USB device?</h3> +<h3>14.16.3 - How do I create a bootable "Live" USB device?</h3> It is very easy to create a bootable USB flash (or other!) drive that can be used as a "live" OpenBSD system without installing OpenBSD on the local hard disk of a machine. @@ -2448,7 +2462,7 @@ to encrypt a data partition. <p> <a name= "DiskOpt"></a> -<h2>14.18 - Optimizing disk performance</h2> +<h2>14.17 - Optimizing disk performance</h2> <p> Disk performance is a significant factor in the overall speed of your @@ -2469,7 +2483,7 @@ operations. <p> <a name="Optsoftu"></a> -<h3>14.18.1 - Soft updates</h3> +<h3>14.17.1 - Soft updates</h3> An important tool that can be used to speed up your system is softupdates. One of the slowest operations in the traditional BSD file system is @@ -2484,7 +2498,7 @@ You can read more about softupdates in t <p> <a name="Optmaxvnodes"></a> -<h3>14.18.2 - Size of the namei() cache</h3> +<h3>14.17.2 - Size of the namei() cache</h3> The name-to-inode translation (a.k.a., <!-- need to write the manual page first... <a href="">namei(3)</a> --> namei()) cache controls @@ -2505,7 +2519,7 @@ set it at system startup time with <p> <a name= "Async"></a> -<h2>14.19 - Why aren't we using async mounts?</h2> +<h2>14.18 - Why aren't we using async mounts?</h2> <p> Question: "I simply do "mount -u -o async /" which makes one package I use @@ -2545,7 +2559,7 @@ they will get wiped and recreated on a r <a name="altroot"></a> -<h2>14.20 - Duplicating your root partition: altroot</h2> +<h2>14.19 - Duplicating your root partition: altroot</h2> OpenBSD provides an "altroot" facility in the <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=daily&sektion=8">daily</a> scripts. @@ -2603,7 +2617,7 @@ For this reason, you may want to specify <a name="softraid"></a> -<h2>14.21 - How do I use softraid(4)?</h2> +<h2>14.20 - How do I use softraid(4)?</h2> <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=softraid&sektion=4">Softraid(4)</a> works by emulating a <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=scsibus&sektion=4">scsibus(4)</a> @@ -2670,7 +2684,8 @@ In this case, adding RAID (either via ha added complication. </ul> -<h3>14.21.1 - Doing the install</h3> +<a name="softraidDI"></a> +<h3>14.20.1 - Doing the install</h3> Softraid disk space can be created using free (or added!) chunks of disk space after install, but that is just a special (and simple) case of adding softraid during install. @@ -2871,7 +2886,8 @@ Now you can reboot your system, and if y will automatically assemble your RAID set, and mount the appropriate partitions. -<h3>14.21.3 - Softraid notes</h3> +<a name="softraidNotes"></a> +<h3>14.20.2 - Softraid notes</h3> <h4>Complications when other sd(4) disks exist</h4> Softraid disks are assembled <i>after</i> all other IDE, SATA, SAS and SCSI disks are attached. @@ -2898,7 +2914,7 @@ In theory, a three disk RAID1 is slower though should be much faster on writes than a rebuilding two disk RAID1. <a name="softraidDR"></a> -<h3>14.21.4 - Disaster recovery</h3> +<h3>14.20.3 - Disaster recovery</h3> This is the section you want to skip over, but don't. This is the reason for RAID -- if disks never failed, you wouldn't add the complexity of RAID to your system! @@ -2992,7 +3008,8 @@ However, the boot disk in the machine ha just made changes in the root partition before doing this, you probably want to be sure you didn't boot from your altroot partition by mistake. -<h3>14.21.5 - Softraid Crypto</h3> +<a name="softraidCrypto"></a> +<h3>14.20.4 - Softraid Crypto</h3> Cryptographic softraid(4) volumes are set up rather simply: