# why didn't /etc/ansible get generated after my install on Mountain Lion?

**URL:** <https://forum.ansible.com/t/why-didnt-etc-ansible-get-generated-after-my-install-on-mountain-lion/14869>\
**Category:** Ansible Project\
**Created:** [March 26, 2014, 10:45pm UTC](https://forum.ansible.com/t/why-didnt-etc-ansible-get-generated-after-my-install-on-mountain-lion/14869 "2014-03-26T22:45:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gallagher\_Polyn](https://avatars.discourse-cdn.com/v4/letter/g/94ad74/32.png) [@Gallagher\_Polyn](https://forum.ansible.com/u/Gallagher_Polyn)\
**Post date:** [March 26, 2014, 10:45pm UTC](https://forum.ansible.com/t/why-didnt-etc-ansible-get-generated-after-my-install-on-mountain-lion/14869/1 "2014-03-26T22:45:34Z")

</div>

I installed Ansible on Mountain Lion with [pip](http://docs.ansible.com/intro_installation.html#latest-releases-via-pip), but /etc/ansible was not created. What gives?

G

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [March 26, 2014, 11:35pm UTC](https://forum.ansible.com/t/why-didnt-etc-ansible-get-generated-after-my-install-on-mountain-lion/14869/2 "2014-03-26T23:35:26Z")

</div>

The pip package doesn’t do everything the OS package managers do.

You can run mkdir yourself if you like.
