Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
vms:freenas [2015/10/08 18:56] admin [FreeNAS Installation] |
vms:freenas [2017/03/31 15:13] admin ↷ Links adapted because of a move operation |
||
---|---|---|---|
Line 11: | Line 11: | ||
---- | ---- | ||
- | ++++| | + | |
===== Shortcut ===== | ===== Shortcut ===== | ||
---- | ---- | ||
- | OK, for the ones that do not want to take the deep dive into the gruesome details of building a FreeNAS development VM. Or if you simply don't have the time required to achieve the whole process, as it takes more than 3 hours to complete all described operations! Here is a download link to the .vdi file that is going to get build following the steps described in this article (you lucky ones!): | + | OK, for the ones that do not want to take the deep dive into the gruesome details of building a FreeNAS development VM. Or if you simply don't have the time required to achieve the whole process, as it takes more than 3 hours to complete all described operations! Here is a download link to the .vdi file that is going to get build following the steps described in this article +/- 663MB (you lucky ones!): |
- | DOWNLOAD LINK (not yet available sorry) | + | Note that you'll probably have to create extra virtual drives for the VM to create a "virtual pool". |
- | ++++ | + | |
+ | **{{:vms:freenas:freenas-dev-9.3.1.vdi|Download FreeNAS-Dev-9.3.1.vdi}}** | ||
---- | ---- | ||
===== Create a FreeBSD 9.3 Build Environment ===== | ===== Create a FreeBSD 9.3 Build Environment ===== | ||
Line 360: | Line 361: | ||
> Nameserver 2 : 8.8.4.4 | > Nameserver 2 : 8.8.4.4 | ||
+ | === VM Snapshot === | ||
+ | As our FreeNAS dev platform is now basicaly configured, it's time to make a snapshot of it (using VirtualBox GUI application for example). | ||
---- | ---- | ||
==== Additional Packages ==== | ==== Additional Packages ==== | ||
Line 426: | Line 429: | ||
---- | ---- | ||
==== Create a SAMBA Share to Ease FreeNAS GUI's Files Edition ==== | ==== Create a SAMBA Share to Ease FreeNAS GUI's Files Edition ==== | ||
- | |||
<WRAP center round tip> | <WRAP center round tip> | ||
Line 434: | Line 436: | ||
</WRAP> | </WRAP> | ||
- | Since we won't be able to use shared folders with FreeBSD (as described in this wiki's [[vms:django#using_a_shared_folder_to_host_your_projects|Python/Django Development Environment section]]) we'll have to create a SAMBA shared folder to easily manage and edit FreeNAS GUI's files from our host system. | + | ++++ CLICK HERE TO READ| |
+ | |||
+ | Since we won't be able to use shared folders with FreeBSD (as described in this wiki's [[vms:python:django#using_a_shared_folder_to_host_your_projects|Python/Django Development Environment section]]) we'll have to create a SAMBA shared folder to easily manage and edit FreeNAS GUI's files from our host system. | ||
As the intention is to analyze, and maybe modify, some code in the FreeNAS GUI and/or api, our main target directory location is //**/usr/local/www/freenasUI**//. We'll first duplicate it's content to the host's HD, then make this duplicate directory a SAMBA shared folder that we'll access from the FreeNAS development VM. Finally this SAMBA share will be mounted, with adequate ownership and permissions, as the ///usr/local/www/freenasUI// directory inside the FreeNAS development VM. | As the intention is to analyze, and maybe modify, some code in the FreeNAS GUI and/or api, our main target directory location is //**/usr/local/www/freenasUI**//. We'll first duplicate it's content to the host's HD, then make this duplicate directory a SAMBA shared folder that we'll access from the FreeNAS development VM. Finally this SAMBA share will be mounted, with adequate ownership and permissions, as the ///usr/local/www/freenasUI// directory inside the FreeNAS development VM. | ||
Line 586: | Line 590: | ||
Let's restart our VM to check everything goes as expected once we reboot the machine. | Let's restart our VM to check everything goes as expected once we reboot the machine. | ||
+ | ---- | ||
+ | ++++ | ||
---- | ---- |