On 06/13/16 11:37 PM, Douglas K. Rand wrote:
> I've encountered some FreeBSD specific things that could use
> representation in the documentation:
> 
> * chio works much better than mtx for changers
I think that is a known thing and that the port install the chio changer
script that was contributed to Bacula year ago.

> * /dev/xpt0 must be writable by the SD for encryption
> * SCSICRYPTO needs to be enabled in both the client and the server ports
Honestly the SCSI crypto support on FreeBSD is something I added based on the
documentation and manpages only. So it never got tested in any shape or form
by us internally. I myself run Solaris so that is a tested platform and we
run tests on Linux in our internal lab so that is also a tested platform.
The following document part of the source distribution explains how things
work with security on Solaris and Linux if you have input on extending that
with FreeBSD specific data that would probably help others looking for in
depth technical information on SCSI crypto support on FreeBSD.

https://github.com/bareos/bareos/blob/master/README.scsicrypto

> 
> If I could get some direction as to where in the documentation these
> items should be placed, I'd be happy to write them up. The only OS
> specific things I can find is Chapter 25 The Windows Version of Bareos.
> I'm not sure that a top-level chapter for FreeBSD is warranted.
> 
See above for the SCSI crypto stuff. For the bareos-docs I leave that
to our document gatekeeper.

-- 
Marco van Wieringen                   [email protected]
Bareos GmbH & Co. KG                  Phone: +49-221-63069389
http://www.bareos.com                     

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens,
                 P. Storz, M. v. Wieringen

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to