diff options
| author | Lucas Ramage <oxr463@gmx.us> | 2020-05-04 23:16:41 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-05-04 23:16:41 +0200 |
| commit | c52121f4c92d711f6ba11472390fb2581a3ca6a5 (patch) | |
| tree | e5fe257a76f31936588626702ef500bd375f61e6 /docs/docsite | |
| parent | Add note in inventory guide saying group names follow variable name guideline... (diff) | |
| download | ansible-c52121f4c92d711f6ba11472390fb2581a3ca6a5.tar.xz ansible-c52121f4c92d711f6ba11472390fb2581a3ca6a5.zip | |
Clarification for Ansible and BSD Introduction (#69275)
Bug: https://github.com/ansible/ansible/issues/69274
Diffstat (limited to 'docs/docsite')
| -rw-r--r-- | docs/docsite/rst/user_guide/intro_bsd.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/docsite/rst/user_guide/intro_bsd.rst b/docs/docsite/rst/user_guide/intro_bsd.rst index 212e5e6c98..68a62f3197 100644 --- a/docs/docsite/rst/user_guide/intro_bsd.rst +++ b/docs/docsite/rst/user_guide/intro_bsd.rst @@ -3,7 +3,7 @@ Ansible and BSD =============== -Managing BSD machines is different from managing Linux/Unix machines. If you have managed nodes running BSD, review these topics. +Managing BSD machines is different from managing other Unix-like machines. If you have managed nodes running BSD, review these topics. .. contents:: :local: @@ -49,7 +49,7 @@ Once this is done you can now use other Ansible modules apart from the ``raw`` m Setting the Python interpreter ------------------------------ -To support a variety of Unix/Linux operating systems and distributions, Ansible cannot always rely on the existing environment or ``env`` variables to locate the correct Python binary. By default, modules point at ``/usr/bin/python`` as this is the most common location. On BSD variants, this path may differ, so it is advised to inform Ansible of the binary's location, through the ``ansible_python_interpreter`` inventory variable. For example: +To support a variety of Unix-like operating systems and distributions, Ansible cannot always rely on the existing environment or ``env`` variables to locate the correct Python binary. By default, modules point at ``/usr/bin/python`` as this is the most common location. On BSD variants, this path may differ, so it is advised to inform Ansible of the binary's location, through the ``ansible_python_interpreter`` inventory variable. For example: .. code-block:: text @@ -70,7 +70,7 @@ If you use additional plugins beyond those bundled with Ansible, you can set sim Which modules are available? ---------------------------- -The majority of the core Ansible modules are written for a combination of Linux/Unix machines and other generic services, so most should function well on the BSDs with the obvious exception of those that are aimed at Linux-only technologies (such as LVG). +The majority of the core Ansible modules are written for a combination of Unix-like machines and other generic services, so most should function well on the BSDs with the obvious exception of those that are aimed at Linux-only technologies (such as LVG). Using BSD as the control node ----------------------------- |