mirror of
https://github.com/samba-team/samba.git
synced 2025-01-11 05:18:09 +03:00
15511f7c51
Based on <https://code.google.com/p/vfs-unityed-media/>. The existing VFS module media_harmony has some problems relative to Avid media sharing: Avid looks at the modification time of the ingest directory. Since media_harmony has everyone using the same directory, users (or client systems) have to somehow create "fake" directories with special names and then media_harmony returns the mod time of those fake directories for the different clients rather than the actual mod time of the communal ingest directory. To make matters worse, users then have to have a special utility or understand how to update the modtime on these specially named directories. Otherwise, their client system will never update the indexes to show new media. To make it even worse than that, Avid creates new directories on the fly, so you can't just set this up statically at the beginning. Avid will silently create a new directory and your reindexing problems will start all over until you create new fake directories. With unityed_media: * there are no reindexes between clients * clients don't need to know which directories have been created for them, it's automatic. * clients never have to reindex other systems directories. * unityed_media let's each client have their own directories. * unityed_media works much more like Avid's own ISIS servers work. A module option controls which name is appended to client specific paths: the username, the hostname (will not work with OS X) or the client's IP. Signed-off-by: Ralph Boehme <slow@samba.org> Reviewed-by: Jeremy Allison <jra@samba.org> Autobuild-User(master): Jeremy Allison <jra@samba.org> Autobuild-Date(master): Sat Jan 10 04:15:04 CET 2015 on sn-devel-104 |
||
|---|---|---|
| .. | ||
| archives | ||
| build | ||
| manpages | ||
| registry | ||
| Samba3-ByExample | ||
| Samba3-Developers-Guide | ||
| Samba3-HOWTO | ||
| scripts | ||
| smbdotconf | ||
| templates | ||
| test | ||
| using_samba | ||
| xslt | ||
| .gitignore | ||
| aclocal.m4 | ||
| configure.ac | ||
| gpl-3.0.xml | ||
| htmldocs.html | ||
| Makefile | ||
| Makefile.settings.in | ||
| README | ||
| Samba-EventLog-HOWTO.txt | ||
| Samba.desktop | ||
| structure.svg | ||
| wscript_build | ||
!== !== docbook.txt for Samba 3.0 !== !== Author: David Bannon, D.Bannon@latrobe.edu.au November, 2000 !== Updates: Gerald (Jerry) Carter, jerry@samba.org, Feb. 2001 !== Updates: Jelmer Vernooij, jelmer@samba.org, Aug, 2002 !== Updates: Jelmer Vernooij, jelmer@samba.org, Jun, 2003 !== Updates: Jelmer Vernooij, jelmer@samba.org, May, 2004 !== Updates: Jelmer Vernooij, jelmer@samba.org, May, 2005 Quick start ----------- Run: $ make all or to see what is possible: $ make help What are DocBook documents doing in the Samba Distribution ? ----------------------------------------------------------- We have converted all samba docs to XML/DocBook V4.2 in order to make them easier to maintain and produce a nicer looking product. This short note (strange isn't it how it always starts out as a short note and becomes a long one ?) will explain very briefly how and why we have done this. The format ---------- If you are new to xml, regard an xml file as 'source code'. You don't read it directly, but use it to create other formats (like the txt and html included in ../txtdocs and ../htmldocs). Docbook is a particular XML style, particularly suited to producing technical manuals. For more information on DocBook tags and format, see "DocBook: The Definitive Guide" by Walsh and Muellner, (c) O'Reilly Publishing. This book covers DocBook V4.2 and is available on-line at http://www.docbook.org/ The Output ---------- The current Samba Subversion tree contains the XML/DocBook source files. A regularly generated version can be found at http://samba.org/samba/docs/. The Tools --------- To generate the docs, you need to have the following packages installed: * GNU Make * GNU autoconf * xsltproc * inkscape For generating PDF and PostScript (thru LaTeX): * dblatex (from http://dblatex.sf.net/) For generating PDF (thru FO): * fop (http://xml.apache.org/fop/) For generating ASCII: * html2text For generating Palm-viewable docs: * plucker-build For generating texi files: * docbook2x-texi * makeinfo For validating: * xmllint This directory now contains a ./configure script and Makefile to support the automated building of man pages (including HTML versions), and the building of the Samba-HOWTO-Collection and the Samba Developers Guide (HTML,TeX,PDF,PS,Text versions). The configure script detects which of the required utilities are installed and builds as much docs as it can using these tools. Help! Building the docs generates a lot of HTTP traffic... ---------------------------------------------------------- To be able to build the docs without an internet connection (or faster with a slow internet connection), you need to set up "catalogs". For the Pearson DTD, add something like: <public publicId="-//Pearson//DTD Books//DE" uri="file:///home/jelmer/Xml_dtd_1.1/pearson.dtd"/> For the Samba DTD's, add something like: <rewriteURI uriStartString="http://www.samba.org/samba/DTD" rewritePrefix="file:///home/jelmer/samba-web/DTD"/> catalog entries for the other DTD's and XSL scripts should be present on your system already. Windows Help files ---------- http://htmlhelp.berlios.de/howto/mshh4wine.php