Beginn der weitergeleiteten Nachricht: Betreff: Re: AW: Minor typo in FAQ 14.21.5
You're so right, I misread the bug report. Didn't want to pollute @bugs with a correction. Honestly, I'm impressed the bug was noticed. Sorry On 06/05/2014 05:38 PM, Stefan Wollny wrote: > Hi James, > the error is NOT that the crypto volume attaches as 'sd1'! In the FAQ > the device '/dev/sd0m' becomes '/dev/sd1m' - and _this_ needs an > explanation or is a bug. (If I am wrong here please give me a clue, > thanks). Cheers, STEFAN > > Gesendet von meinem BlackBerry 10-Smartphone. > Originalnachricht > Von: James Smith > Gesendet: Freitag, 6. Juni 2014 00:27 > An: Stefan Wollny; [email protected] > Betreff: Re: Minor typo in FAQ 14.21.5 > >> softraid0: CRYPTO volume attached as sd1 >> fdisk(8), disklabel(8) and newfs(8) this new volume, sd1 as >> desired. > It's not a bug. > > > On 06/05/2014 04:58 PM, Stefan Wollny wrote: >> Hi there! >> >> As errors in the documentation are looked upon as being a bug I dare >> to report here: >> >> FAQ-Chapter 14.21.5 - Softraid Crypto >> http://www.openbsd.org/faq/faq14.html#softraid >> >> The example showing how to set up softraid(4) crypto states in bullet >> point 3: >> # bioctl -c C -l /dev/sd0m softraid0 >> >> Magically the device number changes from "0" to "1" a few lines below >> in the example to "unlock" the crypto volume: >> # bioctl -c C -l /dev/sd1m softraid0 >> >> My guess is this sneaked in as in this example the crypto volumes >> attaches as "sd1". >> >> THANK YOU for the fine documentation, btw! >> >> Cheers, >> STEFAN >> Just a reminder: Even thou this is not a big issue it should not be overlooked. Have a nice week, STEFAN
