Hi Jeremie and Filippo,

Jeremie Courreges-Anglas wrote on Sun, Oct 25, 2020 at 03:05:04PM +0100:
> On Sun, Oct 25 2020, "Filippo Valsorda" <fili...@ml.filippo.io> wrote:

>> Based on the text in faq14.html, but using the manpage language.

> Makes sense.  I'm not sure .Em is useful here, though.

Indeed.  We use .Em very sparingly in manual pages because too much
markup tends to look ugly, because manual pages tend to have quite a
bit of markup from semantical macros already, and because .Em can
sometimes be mistaken for semantical markup rather than stress
emphasis.  So i removed the .Em before i committed this, see the
commit below.

> ok jca@ if someone wants to pick this up, else I'll just commit it in
> a few hours.

Thanks to jca@ for checking.

Yours,
  Ingo


CVSROOT:        /cvs
Module name:    src
Changes by:     schwa...@cvs.openbsd.org        2020/10/25 09:33:20

Modified files:
        share/man/man4 : softraid.4 

Log message:
mention that stacking disciplines is not supported,
with wording similar to the FAQ;
suggested by Filippo Valsorda <filippo at ml dot filippo dot io>;
tweak and OK jca@


Index: softraid.4
===================================================================
RCS file: /cvs/src/share/man/man4/softraid.4,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- softraid.4  27 Jun 2017 16:02:05 -0000      1.42
+++ softraid.4  25 Oct 2020 15:33:19 -0000      1.43
@@ -1,4 +1,4 @@
-.\"    $OpenBSD: softraid.4,v 1.42 2017/06/27 16:02:05 tb Exp $
+.\"    $OpenBSD: softraid.4,v 1.43 2020/10/25 15:33:19 schwarze Exp $
 .\"
 .\" Copyright (c) 2007 Todd T. Fries   <t...@openbsd.org>
 .\" Copyright (c) 2007 Marco Peereboom <ma...@openbsd.org>
@@ -15,7 +15,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: June 27 2017 $
+.Dd $Mdocdate: October 25 2020 $
 .Dt SOFTRAID 4
 .Os
 .Sh NAME
@@ -200,6 +200,9 @@
 .Pp
 The RAID 5 discipline does not initialize parity upon creation, instead parity
 is only updated upon write.
+.Pp
+Stacking disciplines (CRYPTO on top of RAID 1, for example) is not
+supported at this time.
 .Pp
 Currently there is no automated mechanism to recover from failed disks.
 .Pp

Reply via email to