Commit | Date | |
---|---|---|
[r9422]
by
yaberauneya
Merge changes from 8.0.3-mm to 8.0.3 Man, I bork-borked the patch. This is a prime example of why one should never, ever hand edit patches at 5am.. ------------------------------------------------------------------------ *sigh* got the patch backwards. ------------------------------------------------------------------------ Doh. Forgot to remove the pathing in the diff used to produce the patch. ------------------------------------------------------------------------ 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. ------------------------------------------------------------------------ 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 ------------------------------------------------------------------------ Add the missing xvid ports patch so the port will build cleanly under amd64 100% of the time. |
2012-01-05 20:46:39 | Tree |
2012-01-05 17:53:44 | Tree | |
[r9420]
by
zippybr
As requested: |
2012-01-05 17:22:47 | Tree |
2012-01-05 10:00:47 | Tree | |
[r9418]
by
yaberauneya
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) 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. |
2012-01-05 06:07:24 | Tree |
2012-01-05 06:07:10 | Tree | |
2012-01-05 06:06:58 | Tree | |
2012-01-04 17:43:42 | Tree | |
2012-01-04 17:21:46 | Tree | |
2012-01-04 15:51:19 | Tree |