MediaTomb release 0.12.1 is now available.
Take a look at the ChangeLog to find out what’s new in 0.12.1
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
- Latest development code
Download source code: mediatomb-0.12.1.tar.gz
MD5 = e927dd5dc52d3cfcebd8ca1af6f0d3c2
SHA1 = 86e880584cc9c8aaf3926d56048510d1d06e76b4
SHA256 = 31163c34a7b9d1c9735181737cb31306f29f1f2a0335fb4f53ecccf8f62f11cd
SIZE = 1240612
GPG signature: mediatomb-0.12.1.tar.gz.asc
GPG key (key id: A2DCDB57; fingerprint: F1A6 C581 6BC1 AD55 80E9 EEFE 48AD 7164 A2DC DB57)
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
Starting with version 0.11.0 there are three binary packages:
- 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.
- 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.
- 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.
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
If you want MediaTomb to be started at boot time, change the
NO_START option from
"" 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.
Andres Mejia did most work for the packages and is now the maintainer for the package in Debian.
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.
To install it you need to run:
The following USE flags are available:
Mediatomb can easily be installed using the package manager in Pardus. All you have to do is either:
- From the Pisi GUI: search for mediatomb, click to select, click “Install Package(s)” to install
- If you like working in command-line, it’s also easy, you just need to give the following command:
sudo pisi it mediatomb
After the installation is complete, you can use mediatomb through its command line interface, or better, use it as a system service as explained below:
- From TASMA, go to System and open Service Manager: Choose Mediatomb from the list and start it by clicking the button. If you want mediatomb to start at each boot, you can also configure that from the GUI.
- Again, if you’re a command line lover, you can issue
sudo service mediatomb start
to start it, and;
sudo service mediatomb on
to make it start at automatically at each system boot.
After the service is started, you can use the “Mediatomb” entry in your KDE Multimedia menu to perform any configuration necessary, such as adding your media files to the library.
Note that the configuration file (config.xml) of mediatomb is stored in /etc/
mediatomb directory, you can adjust it as you see necessary. The database and
other library files will be created in
/var/lib/mediatomb once you add your
media to it.
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
true after that start the daemon by issuing the following command:
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:
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
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 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.
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.
MD5 = 838bae6303e36b5ed0d7e536e76c3774
SHA256 = 741f23b8784b262fa06f75570c2a0a970c686c90b292dfafd8fe748f60b143e2
SIZE = 2333877
MD5 = 99310afc8f9428ec2fe3c61aba12ee9e
SHA256 = 87ff5eab84fd6cd57531edf9afaa64c8dfcc25cdd6d46e7b1c8a3c5e59469201
SIZE = 2519357
GPG signature: mediatomb-static-0.11.0-r2-linux-uclibc-mips32el.tar.gz.asc
MD5 = e735111df54ce0b44776007128e822a1
SHA256 = d031f987f5e7c074e7c399f77191544fdc2bb34ac130cbbcdc878b535d9e12d4
SIZE = 2526768
MD5 = b7e2fcbf8425f5c0846bc4b20fcf3fdb
SHA256 = de1594077941afb95d3805c412ced543b6040b17f455d8dffe4af7240dcecd18
SIZE = 2538388
GPG signature: mediatomb-static-0.11.0-r1-linux-uclibc-armv4.tar.gz.asc
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:
|i386||PC, Airlink WMU6500FS|
|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
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
Latest development code
To get the latest development code use:
git clone git://mediatomb.git.sourceforge.net/gitroot/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.