|
DISCLAIMER: The NMM software provided might be outdated. For newer releases, please visit the NMM homepage at www.motama.com.
Right now, we provide packages for Debian Sarge as well as RPM packages for SuSE Linux 9.3, Fedora Core and
RedHat Linux 9.0. To install these packages, different steps are required depending on what Linux distribution
you're running. Package installation is explained in detailed steps for the following distributions:
DEBIAN
The installation of NMM on Debian is quite easy when using apt-get.
Note that you need to do the following steps as root!
- Open /etc/apt/sources.list with your favorite text editor and add the following line:
deb ftp://graphics.cs.uni-sb.de/www/NMM/Packages/debian/sarge/current ./
- Update your local package metadata cache by running apt-get update.
- Install NMM by running apt-get install nmm.
- Continue with "Configuration and Tests"
After these steps have been performed one time, NMM will be updated with a regular
apt-get update
apt-get upgrade
along with the rest of the system.
SUSE LINUX 9.3
To install NMM on SuSE Linux, you need the XMLTV tools. Unfortunately, SuSE Linux doesn't provide these tools. For your
convenience, we have collected all the needed RPM packages from rpm.pbone.net.
The installation on SuSE is performed like this:
- Create a directory to store the RPM files in (In our example, we'll use /home/bob/nmm-install):
- Create the directory with mkdir /home/bob/nmm-install.
- CD into that directory with cd /home/bob/nmm-install.
- Download the needed files:
- Download our NMM RPM packages into your newly created directory.
- Also download xmltv-suse.tar.gz
into that directory.
This file contains the RPMs for XMLTV, which are made available to YaST by putting them into this directory, too.
- Untar it with tar -xzf xmltv-suse.tar.gz.
- Make NMM and XMLTV available to YaST for installation:
- The following steps need to be done as root!
- Start YaST2 (to be found in the SuSE menu under System -> YaST)
- Choose "Change Source of Installation".
- Select "Add" and choose "Local Directory ...".
- In the dialog that appears, enter your newly created directory, like /home/bob/nmm-install
and press "OK".
- A message will appear stating that there is no product information in the directory. You can safely press
"Continue".
- Close the window by clicking "Finish".
- Install NMM:
- The following steps need to be done as root!
- Choose "Install and Remove Software".
- In the search field, enter nmm and press Enter.
- In the list on the right side, the NMM package will appear. Select it for installation.
If you're updating from a previous version of NMM, the NMM package will have a "lock" symbol
indicating it will be kept if YaST is not instructed to do otherwise. You have to click on this symbol until
the "Update" symbol appears (looks like a "Z").
- Click on "Accept".
If you're updating from a previous version of NMM, YaST will most likely complain about unresolved
dependencies. This is because other packages you have installed along with NMM can have the "Keep"
state, too. In the window that pops up, select "Do not set <package name> to Protected"
for each package and click on "OK - Try again" to continue.
- Continue with "Configuration and Tests"
REDHAT LINUX 9.0
For installation on Red Hat Linux 9.0, you also need to install the XMLTV utilities. For convenience, we recommend using
the package manager yum to install XMLTV along with NMM. A version of yum suited for RedHat Linux 9.0 can be obtained on
the pages of the Fedora Legacy project.
Note that you need to do the following steps as root!
- If you haven't yum installed on your machine, download and install it:
- Download
yum
into a local directory, for example /home/bob.
- CD into that directory with cd /home/bob.
- Install yum with rpm -i yum-2.0.5-0.9.2.legacy.noarch.rpm
yum is pre-configured to download security updates for RH9 from the Fedora Legacy project FTP server.
We recommend you leave it at that.
- Add entries for the ATrpms YUM Repository (which contains RPMs for XMLTV on RedHat Linux 9) and the NMM repository:
- Install NMM with yum install nmm.
- Continue with "Configuration and Tests"
After these initial steps have been done, you can later update NMM simply with yum update.
If you want to only update NMM, you can do so with yum update nmm.
FEDORA CORE
Installation on Fedora Core is quite similar to installation in Red Hat 9, except that you'll have yum already installed
on your machine.
Note that you need to do the following steps as root!
- Add entries for the ATrpms YUM Repository (which contains RPMs for XMLTV on RedHat Linux 9) and the NMM repository:
- Install NMM with yum install nmm.
- Continue with "Configuration and Tests"
These packages have been tested with Fedora Core 3. They should work with other versions of Fedora, too. However, as we
have not tested that, there is no guarantee for that.
After these initial steps have been done, you can later update NMM simply with yum update.
If you want to only update NMM, you can do so with yum update nmm.
CONFIGURATION AND TESTS
You need to configure and test NMM. (If you have another NMM version installed that requires to set the NMM_DEV_DIR, please make sure that NMM_DEV_DIR is not set when running this version.)
- Setup NMM registry
-
Run 'serverregistry -s' and wait until all plug-in information is generated.
Notice: This step is also performed automatically when you start some NMM application or example for the first time.
- Test NMM
-
We recommend that you use 'clic' for testing NMM. clic is a very powerful tool.
-
Test audio: Run 'clic /usr/share/nmm/gd/playback/audio/mp3play.gd -i <some mp3 file>'
-
Test video: Run 'clic /usr/share/nmm/gd/playback/image/noise_yv12.gd'
(You should see a window showing some video 'white noise' using the Xv extension.)
-
If clic does not work as expected, try adding '-v' for getting all
error messages or '-vv' for all error and warning messages.
Most often, the NMM_DEV_DIR or LD_LIBRARY_PATH environment variables are not
set correctly. For the Debian/RPM release of NMM, NMM_DEV_DIR should not be
set at all. So check if NMM_DEV_DIR is set, and if it is, unset it.
LD_LIBRARY_PATH should not contain a path pointing to some external
NMM libraries other than /usr/lib/nmm. Normally, no reference at all should
be needed, as NMM finds the libraries in /usr/lib/nmm automatically.
Another possibility is that a plug-in required for the specific .gd file is not
available. Repeat 'serverregistry -s' and see, which plug-ins
are available. Then compare this information with the content of the
.gd file.
-
If everything works fine, you might want to read 'First steps with NMM'.
- Setup Multimedia-Box
-
Copy /usr/share/nmm/mmbox/mmboxrc_sample to your home as .mmboxrc and
edit to fit your setup (see comments in mmboxrc_sample). There are
only a few entries that you really have to edit; in many cases the
default values are just fine. Notice:
Since we frequently add new features to the Multimedia-Box, you
should create a new .mmboxrc file for every new NMM release.
- TV/EPG functionality: For all releases >= 0.9.0 you have to run
'channelReader' before you are running the Multimedia-Box for the
first time. This tool creates the global TV-Channel-Config-File
'$HOME/.nmm/tv_channels.xml'. For more information, read Setting
up LiveTV, TVGuide and TVTimer of the NMM Multimedia-Box [pdf]
-
Run 'mmbox' or 'mmbox --help'. In case the Multimedia-Box is not working as expected,
use 'mmbox -v' for getting all error messages or 'mmbox -vv' for all error and warning messages.
-
Due to a bug in mmbox (NMM-Version 0.9.1), grabbing DVDs does not work if the DVD drive is not
/dev/cdrom. The corresponding entry in .mmboxrc is not taken into account when trying to grab
from DVD. As a workaround, you can set a link from /dev/cdrom to your real DVD drive
if you want to use DVD grabbing. This bug will be fixed in a forthcoming release of NMM.
- Optional: Security
-
Copy /usr/share/nmm/nmmrc_sample to your home as .nmmrc and edit it.
-
By setting 'allowedreadpaths' you can restrict the paths from which plug-ins are allowed to read data, e.g. your MP3 files.
-
By setting 'allowedwritepaths' you can restrict the paths to which plug-ins are allowed to write data.
-
By setting a 'passwd' you can restrict access between NMM processes
(and therefore systems). Only processes using the same password are
allowed to interact. For example, if you start a serverregistry on
host A and another user at host B wants to connect to this
serverregistry, both of you need to agree on the same password.
-
Notice: If you are behind a firewall and only connected to
trusted hosts and users, you do not necessarily need these settings
at all.
-
Notice: If you want to access devices, e.g. /dev/dsp for
audio output, you need to add this to the 'allowed'
paths. Remember: the usual restrictions of your operating system
still apply, e.g. adding '/dev/' to 'allowedreadpaths' and
'allowedwritepaths' is not necessarily unsafe.
|