MediaTomb

Downloads

MediaTomb release 0.11.0 is now available.

Take a look at the ChangeLog to find out what’s new in 0.11.0

You can find older releases on our SourceForge download page.

Some of the packages below are not yet up to date and will be upgraded to the new release shortly.

Source code

Download source code: mediatomb-0.11.0.tar.gz
MD5 = 661f08933830d920de21436fe122fb15
SHA256 = 25e0b3d761e41fc6793c780eb7f638719867cdc6d3429ec24f72d1e9556ac1d2
SIZE = 1059429
GPG signature: mediatomb-0.11.0.tar.gz.asc
GPG key (key id: A2DCDB57; fingerprint: F1A6 C581 6BC1 AD55 80E9 EEFE 48AD 7164 A2DC DB57)

Binaries

Fedora core

Binaries for Fedora 7 and Fedora 8 are available directly from Fedora repositories! Just run the following command:

yum install mediatomb

If you want to run MediaTomb as a service, edit the /etc/mediatomb.conf file and choose a network interface. Afterwards start the server using the folowing command:

service mediatomb start

Use either the ntsysv or the graphical system-config-services utility to enable the mediatomb service startup at boot time.

Debian and Ubuntu

MediaTomb made it into Debian and Ubuntu recently and is currently in Debian unstable, Debian testing and Ubuntu hardy. But beware: There is a known problem if you upgrade directly from the old 0.10.0 packages provided by us to the official packages. Remove the old package first and install the new packages afterwards. You won’t run into this problem if you upgrade to the new packages provided by us. (If you want to know why: The “Conflicts” and “Replaces” lines are missing for the official packages. These lines are needed because most of the files in the “mediatomb” package moved to “mediatomb-common”.)

Starting with version 0.11.0 there are three binary packages:

  1. mediatomb-common: The main package consisting of the MediaTomb binary and all files necessary to run MediaTomb from the command line as a regular user. The other packages depend on this package, so it is needed in all cases.
  2. mediatomb-daemon: This package has additional files to allow MediaTomb to start as a daemon at startup. Use this package if you want to run MediaTomb at boot time.
  3. mediatomb: Additional files to add a menu entry that opens up a browser to show the MediaTomb UI. This package is separated from “mediatomb-daemon” to allow installation of MediaTomb on a headless system. Install this package only on systems with X installed.

The best way to install Debian or Ubuntu packages (if there aren’t any MediaTomb packages in your chosen distribution already) is via our APT repository. To use it properly, you will need our GPG key. To install it, issue the following command (probably as root, if you don’t have sudo; remove “sudo” in that case):
wget http://apt.mediatomb.cc/key.asc -O- -q | sudo apt-key add -
(key id: A2DCDB57; fingerprint: F1A6 C581 6BC1 AD55 80E9 EEFE 48AD 7164 A2DC DB57)

Below you will find the appropriate “deb” line to add to your /etc/apt/sources.list for all supported distributions and a direct download to the ”.deb” file in case you don’t want to use the APT repository. We also provide source packages for these distributions (add the same line, but with “deb-src” instead of “deb” at the beginning), so you should be able to build MediaTomb for platforms other than i386, AMD64 and ARM.

If you want APT to automatically install all dependencies on Ubuntu, you have to enable the “universe” component. (Spidermonkey isn’t part of the “main” component there.) This doesn’t apply to Debian.

There are basically two ways of starting MediaTomb: you can either start it directly as a normal user or run it as a deamon. For the latter you’ll need the “mediatomb-daemon” package. A “mediatomb” user and group will be added automatically. You’ll find the configuration under /etc/mediatomb/config.xml, the logfile under /var/log/mediatomb and the database under /var/lib/mediatomb/. If you want MediaTomb to be started at boot time, change the NO_START option from "yes" to "" in the file /etc/default/mediatomb. To access the UI of the MediaTomb daemon open the file /var/lib/mediatomb/mediatomb.html in your browser.

The binaries for ARM were built on hardware donated by eXcito.

Andres Mejia did most work for the packages and is now the maintainer for the package in Debian.

Debian 4.0 (“stable”/”etch”)

APT (i386, AMD64, ARM):
deb http://apt.mediatomb.cc/ etch main
all .deb: mediatomb_0.11.0-1etch1_all.deb mediatomb-daemon_0.11.0-1etch1_all.deb
i386 .deb: mediatomb-common_0.11.0-1etch1_i386.deb
AMD64 .deb: mediatomb-common_0.11.0-1etch1_amd64.deb
ARM .deb: mediatomb-common_0.11.0-1etch1_arm.deb

Debian “testing” (“lenny”)

The current MediaTomb version (0.11.0) is available directly from the official Debian repository, therefore we are currently not providing any packages for “lenny”. Nevertheless you can add a “deb” line to your sources.list to automatically receive updates to MediaTomb even if the packages are not (yet) updated in the official Debian repository.
APT (i386, AMD64, ARM):
deb http://apt.mediatomb.cc/ lenny main

Ubuntu 7.04 (“feisty”)

APT (i386, AMD64):
deb http://apt.mediatomb.cc/ feisty main
all .deb: mediatomb_0.11.0-1feisty1_all.deb mediatomb-daemon_0.11.0-1feisty1_all.deb
i386 .deb: mediatomb-common_0.11.0-1feisty1_i386.deb
AMD64 .deb: mediatomb-common_0.11.0-1feisty1_amd64.deb

Ubuntu 7.10 (“gutsy”)

APT (i386, AMD64):
deb http://apt.mediatomb.cc/ gutsy main
all .deb: mediatomb_0.11.0-1gutsy1_all.deb mediatomb-daemon_0.11.0-1gutsy1_all.deb
i386 .deb: mediatomb-common_0.11.0-1gutsy1_i386.deb
AMD64 .deb: mediatomb-common_0.11.0-1gutsy1_amd64.deb

Ubuntu 8.04 (“hardy”)

The current MediaTomb version (0.11.0) is available directly from the official Ubuntu repository (component “universal”), therefore we are currently not providing any packages for “hardy”. Nevertheless you can add a “deb” line to your sources.list to automatically receive updates to MediaTomb even if the packages are not (yet) updated in the official Ubuntu repository.
APT (i386, AMD64):
deb http://apt.mediatomb.cc/ hardy main

FreeBSD

MediaTomb is in the FreeBSD ports tree. Visit freshports.org for general information or portsmon.freebsd.org for information about binary packages.

There are basically two ways of running MediaTomb: you can either start it directly as a normal user or run it automatically as user “mediatomb” in daemon mode (only if MediaTomb was installed from the ports). For the latter way, you’ll have to add mediatomb_enable="YES" to your /etc/rc.conf. To access the UI, open /var/mediatomb/mediatomb.html in your browser.

Gentoo

An ebuild for MediaTomb is now available in Gentoo.

To install it you need to run: emerge mediatomb

The following USE flags are available:

USE="curl debug exif expat ffmpeg javascript libextractor mysql taglib"

Ångström

armv4t and armv5te MediaTomb packages are available here

Optware

MediaTomb packages for NSLU2 and other Optware targets are available here

If you are running Optware you can easily install MediaTomb using the following command:

ipkg install mediatomb

The current package provides an init script with some additional configuration. To enable automatic startup of the MediaTomb daemon edit /opt/etc/default/mediatomb and change the value of MT_ENABLE to true after that start the daemon by issuing the following command:

/opt/etc/init.d/S90mediatomb start

In this configuration MediaTomb will listen on port 50500, this behavior can be changed by editing /opt/etc/mediatomb.conf and restarting the server which can by done by:

/opt/etc/init.d/S90mediatomb restart

The config.xml and the database of the daemon configuration will be created in /opt/etc/mediatomb after the first launch.

If you encounter strange behavior or are not sure what is going on, have a look at the log output which will be located in /opt/var/log/mediatomb

There has been one more change in regard to the Optware package: the default settings make use of the database backup function, have a look at the storage settings in the documentation if you want to find out more about this.

Mac OS X

MediaTomb packages for Mac OS X are available via Fink

Mandriva

MediaTomb packages are available in the official Mandriva repositories. The latest version, 0.11.0, can be found in /contrib/release for the development distro (Cooker) and /contrib/backports for the two most recent stable releases (2008 and 2007 Spring). Instructions on using the /backports repositories are here.

openSUSE / SuSE

MediaTomb packages for openSUSE and SuSE are available in the PackMan repository.

Static Binaries

These packages can be used as an addon to the existing vendor firmware (no reflashing required) on various embedded devices. There are absolutely no dependencies on external packages, the binaries are statically linked and have no dependencies.

mediatomb-static-0.11.0-r2-linux-uclibc-mips32el.tar.gz
MD5 = 99310afc8f9428ec2fe3c61aba12ee9e
SHA256 = 87ff5eab84fd6cd57531edf9afaa64c8dfcc25cdd6d46e7b1c8a3c5e59469201
SIZE = 2519357
GPG signature: mediatomb-static-0.11.0-r2-linux-uclibc-mips32el.tar.gz.asc

mediatomb-static-0.11.0-r1-linux-uclibc-mips2el.tar.gz
MD5 = 88aa01d6891a453701a40f1a041c49b6
SHA256 = 2ec22368395c4be00f117ec33a63488a194a070c11a443c66fa2e10541be6f34
SIZE = 2529347
GPG signature: mediatomb-static-0.11.0-r1-linux-uclibc-mips2el.tar.gz.asc

mediatomb-static-0.11.0-r1-linux-uclibc-armv4.tar.gz
MD5 = b7e2fcbf8425f5c0846bc4b20fcf3fdb
SHA256 = de1594077941afb95d3805c412ced543b6040b17f455d8dffe4af7240dcecd18
SIZE = 2538388
GPG signature: mediatomb-static-0.11.0-r1-linux-uclibc-armv4.tar.gz.asc

mediatomb-static-0.11.0-r1-linux-uclibc-ppce300c2.tar.gz
MD5 = 967ae66c1286c35b6dbaac0750b153f1
SHA256 = 12f71372fd9b6cabbbb548d4c6b045c3fc8bfe9d06b2f9170dbb7f82edd1a313
SIZE = 2475111
GPG signature: mediatomb-static-0.11.0-r1-linux-uclibc-ppce300c2.tar.gz.asc

It is important to find out the architecture of your device and choose the correct package, otherwise it will simply not run.

So far the packages have been tested on the following devices:

ARCH TESTED DEVICES
mips2el Maxtor MSS-I, AVM FRITZ!Box Fon WLAN 7270
mips32el Asus WL500g, Syabas Popcorn Hour/A-100, Linksys WRT350N, Emtec Movie Cube R500
armv4 Raidsonic IB-NAS4200-B, Buffalo LinkStation Live, Thecus N4100Plus
ppce300c2 Promise NS4300N, Encore ENNHD-1GS, Conceptronic CH3WNAS

The installation is very easy, however there is one requirement: you need to have shell access (telnet/ssh/serial) to your NAS device. Download the package and unpack it on the mounted harddisk – do not install it in flash!

Here is a sample installation procedure:
tar -zxvf mediatomb-static-0.11.0-r1-linux-uclibc-mips32el.tar.gz
cd mediatomb
./mediatomb.sh

If you do not have tar on your device you can also mount the drive on your PC (NFS/Samba) and unpack the package from your PC. However, in this case you have to pay attention that the mediatomb/mediatomb.sh script and the mediatomb/usr/bin/mediatomb binary have the executable flag set. Linux software will probably take care of it, but if you unpack on Windows the executable flags will not be set. You can fix this by setting the permissions manually in the console:

chmod a+x mediatomb.sh usr/bin/mediatomb

It is important that you run the mediatomb.sh script from the mediatomb directory, otherwise it will not work.

After the first startup the server will create the default configuration in mediatomb/config/config.xml, it is a good idea to set your filesystem-charset in the configuration – since locale support will most likely not be available on your device we will not be able to determine the charset from the environment. If in doubt set <filesystem-charset>UTF-8</filesystem-charset> in the @ section, check chapter 6.2 of the documentation for more details.

WD MyBook

Here is a guide on how to install MediaTomb on a WD MyBook NAS device.

Latest development code

To get the latest development code use:
svn co https://svn.mediatomb.cc/svnroot/mediatomb/trunk/mediatomb mediatomb

Make sure you have autoconf (at least 2.61) and automake (at least 1.10) installed and run autoreconf -i in order to generate the configure script.