# Solaris modules

**URL:** <https://forum.ansible.com/t/solaris-modules/14050>\
**Category:** Ansible Project\
**Created:** [December 3, 2013, 7:43am UTC](https://forum.ansible.com/t/solaris-modules/14050 "2013-12-03T07:43:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul\_Markham](https://avatars.discourse-cdn.com/v4/letter/p/9d8465/32.png) [@Paul\_Markham](https://forum.ansible.com/u/Paul_Markham)\
**Post date:** [December 3, 2013, 7:43am UTC](https://forum.ansible.com/t/solaris-modules/14050/1 "2013-12-03T07:43:52Z")

</div>

Guys,

I’ve written two modules to make Ansible work better on Solaris.

1. A zone module to create and delete Solaris zones (pull request already submitted).
2. A filesystem mount module; the Ansible mount module doesn’t work on Solaris as it’s /etc/vfstab format is different to Linux’s /etc/fstab format. The question I have is about the best way to submit the mount changes for inclusion in Ansible. At the moment, I’ve got the Solaris mount module as a separate module. Ideally this would be incorporated in the core mount module, but that would make it quite messy. Other modules that handle different operating systems seem to have a base class and a subclass for each operating system. The mount module isn’t written as a class so this isn’t going to work. So, is it better to have a separate module, or put the code in the existing one and put up with the messiness?

Paul