FreeNAS Code

Rework solution for r8298 (no resolv.conf -> avahi constantly complaining about it being missing in syslog).

The real solution should have been to make this an empty file at install, then cat the output to the file as necessary. 'Fixing' things in the prior fashion breaks DHCP installs until dhclient regenerates the file.

This fixes ticket # 1148 and will make the DHCP users happy again.

Unbeknownst to me in the prior commit, we have AD users in the FreeNAS community with large AD forests. Boost this up to 2g (the previous value was 1500m in 8.0.2).

Do-Not-Merge: this is already the default in TrueNAS.

Downgrade samba from 3.6 to 3.5 for test image. According to various sources on the forums and IRC there are throughput issues with the new version of samba (in particular with larger files).

Update ataidle to 2.72 based on the author's (bruce@...) recommendation as there are 'potential issues with some chipsets when using 2.60).

Promote the multimedia goo from 8.0.3-mm @ r9393 to 8.0.3.

Merge changes from 8.0.3-mm to 8.0.3
------------------------------------------------------------------------
r9411 | yaberauneya | 2012-01-04 04:58:43 -0800 (Wed, 04 Jan 2012) | 2 lines

Man, I bork-borked the patch. This is a prime example of why one should never, ever hand edit patches at 5am..

------------------------------------------------------------------------
r9410 | yaberauneya | 2012-01-04 04:52:37 -0800 (Wed, 04 Jan 2012) | 2 lines

*sigh* got the patch backwards.

------------------------------------------------------------------------
r9409 | yaberauneya | 2012-01-04 02:50:22 -0800 (Wed, 04 Jan 2012) | 2 lines

Doh. Forgot to remove the pathing in the diff used to produce the patch.

------------------------------------------------------------------------
r9407 | yaberauneya | 2012-01-04 01:12:54 -0800 (Wed, 04 Jan 2012) | 4 lines

Add hacks to help reduce the entry-level overhead in using minidlna, firefly, and transmission to a bare minimum by taking care of bits not properly handled by the ports infrastructure, hacking around checks that make sense on standalone PCs -- but not FreeNAS, and providing relevant examples of how to do things s.t. people can tune the settings to their liking without having to dive through either terse example files (daapd, minidlna), or have to read documentation (transmission) in order to produce a coherent settings file.

Will document the deltas required to get up and running on the forums/my LiveJournal blog.

------------------------------------------------------------------------
r9404 | yaberauneya | 2012-01-03 21:09:53 -0800 (Tue, 03 Jan 2012) | 3 lines

Bump xvid from 1.3.0 to 1.3.2. This fixes an issue with the build where building with a --prefix != /usr/local was replacing text in the build improperly (didn't change down the exact issue, but it appears to be resolved properly as evidenced on 8.0.3-mm and trunk on build.ix) a
nd a number of items related to MMX/SSE support. The full changelog can be found here: http://www.videohelp.com/tools/XviD-Codec/version-history#changelog

------------------------------------------------------------------------
r9403 | yaberauneya | 2012-01-03 10:06:26 -0800 (Tue, 03 Jan 2012) | 2 lines

Add the missing xvid ports patch so the port will build cleanly under amd64 100% of the time.

change to Volume Manager in tree menu as well

As requested:
Change the button that used to be called create volume, which is now called volume wizard to Volume Manager.
The field which is a dropbox underneath the Volume name should only be visible if there is an existing volume as a candidate to populate it. If there are no existing ZFS volumes it shouldn't be displayed.
This field should be named: Volume to extend

Auto-Commit of i18n data from Pootle for GUI

Clean up cornercase where a zvol, dataset, zpool in use when deleting a zvol would delete the zvol from the GUI/db, but wouldn't actually remove things from the backend in FreeBSD.

Introduce a few new notifier APIs to help ease this pain:

__get_mountpath - get the mountpath for a volume/dataset (name)
__rmdir_mountpoint - remove a mountpoint as a means to determine whether or not the

Split storage.models.Volumes.delete into two functions again to 'clean up' the database after storage.models.Volumes._delete has been run, in such a manner that the mountpoints aren't preemptively removed, even though some of the dataset / zvol objects might have been successfully removed, and instead are removed in the event that the directory, that previously was the mountpoint, is no longer present.

These APIs are coded relatively conservatively for now to avoid putting the user into situations where they need to do database surgery.. they can and should be cleaned up later to be more explicit and straightforward by tossing proper Exceptions up the stack.

This doesn't catch the following cases:

mount -f vol

zpool destroy -f tank

when I'm in /mnt/vol or /mnt/tank (this occurs on 8.0.3 as well and this is sort of by design as they're 'force' operations). This might be a noop, or something of concern.

This change -- along with r9317 and r9318 -- resolves the issue where one couldn't export volumes via the GUI, as explained in ticket # 1126.