TwonkyMedia? Server will at the time of writing not run on SlugOS/BE 5.3. This is because SlugOS/BE 5.3 comes with EABI compiled libraries, while TwonkyMedia? Server is compiled for OABI.

Similar issues exist with a program called CCcam? and in other distibutions with the EABI compilation target like an ARM version of Debian Lenny.

• TwonkyMedia? Server should be recompiled for EABI support. EABI is the successor of OABI, and probably more and more distributions will use it in future. Mail TwonkyMedia and ask them to include a build for the architecture 'ARM big endian EABI glibc' instead of the currently available 'ARM big endian OABI glibc' in the unsupported builds section.
• Create a sandbox/chroot, recompile libc and other required libraries for the OABI target and run twonkymedia server from this chrooted environment. Technically not for the faint-hearted, and requires support for OABI in the kernel (which SlugOS5.3 supposedly has?).
• Create a sandbox/chroot which can run the uclibc version of TwonkyMedia? Server. If for some reason the previous option is not possible, then this might be the only remaining option.

Not yet implemented in this HowTo

• Running multiple TwonkyMedia? Server instances on one server. Possible from two different user accounts (verified) or from one installation (but requires seperation of all config files, db and cache).

Other people have reported a similar issue with a program called CCcam? and in other distibutions like Debian Lenny. It's unclear to me why these ABIs? are missing from SlugOS/BE 5.3, as newer ABIs? do not appear to offer full backward compatibility (which is why older ABIs? are included normally). Is it related to the switchover to ARM's EABI with SlugOS 5.3? Can a SlugOS developer answer this?

At the end of the page a section with problems encountered when trying to install Twonkymedia Server on SlugOS/BE 5.3. A workaround to run Twonkymedia server on this version of SlugOS-BE is still needed.

TwonkyMedia? Server will at the time of writing not run on SlugOS/BE 5.3. This is because it needs the GLIBC ABIs? called 'GLIBC_2.0', 'GLIBC_2.1' and 'GLIBC_2.1.3'. These are not included with SlugOS/BE 5.3's libc libraries. The GLIBC ABIs? supported by SlugOS/BE 5.3 are found by performing the following command (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

strings libc.so.6 | grep GLIB
GLIBC_2.4
GLIBC_2.5
GLIBC_2.6
GLIBC_PRIVATE

(:tableend:)

The same command on SlugOS/BE 4.8 reveals (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

strings libc.so.6 | grep GLIB
GLIBC_2.0
GLIBC_2.1
GLIBC_2.1.1
GLIBC_2.1.2
GLIBC_2.1.3
GLIBC_2.2
GLIBC_2.2.1
GLIBC_2.2.2
GLIBC_2.2.3
GLIBC_2.2.4
GLIBC_2.2.6
GLIBC_2.3
GLIBC_2.3.2
GLIBC_2.3.3
GLIBC_2.3.4
GLIBC_2.4
GLIBC_2.5
GLIBC_PRIVATE

(:tableend:)

Other people have reported a similar issue with a program called CCcam? and in other distibutions like Debian Lenny. It's unclear to me why these ABIs? are missing from SlugOS/BE 5.3, as newer ABIs? do not appear to offer full backward compatibility (which is why older ABIs? are included normally). Can a SlugOS developer answer this?

• TwonkyMedia? Server builds that do not require these ABI's. Mail TwonkyMedia? about this issue (mention the use of the GLIBC_2.0, GLIBC_2.1 and GLIBC_2.1.3 ABIs?) if you would like them to do this (and tell them about the same issue in Debian Lenny)!
• Recompile (g?)libc in SLugOS?/BE 5.3 including these ABIs?. If this is possible, an explanation how to do this by a more technically inclined SlugOS user is needed!
• Install support for the uclibc in SlugOS/BE 5.3. Again, if this is possible, an explanation how to do this by a more technically inclined SlugOS user is needed!

Theoretic workarounds include:

Theoretic workarounds include

At the end of the page a section with problems encountered when trying to install Twonkymedia Server on SlugOS-BE 5.3. A workaround to run Twonkymedia server on this version of SlugOS-BE is still needed.

running="`ps ax --no-heading | grep -e twonkymedia | grep -v grep | grep -v twonkymedia.sh | grep -v twonkymediaserver | cut -d ' ' -f 2`"

running="`ps ax --no-heading | grep -e twonkymedia | grep -v grep | grep -v twonkymedia.sh | grep -v twonkymediaserver | cut -d ' ' -f 2`"

Edit the twonkymedia.sh file to make some necessary adaptations including for BusyBox? commands in SlugOS 4.8

Configure TwonkyMedia? Server by opening a browser on the same subnet as your Slug and to the address: http://IP_of_slug:9000/config

Now that twonkymedia server is properly configured, it's time to add an init.d script to automatically start/stop/restart the Twonkymedia server daemon

First, the 'sudo' package is needed to run twonkymedia server as user twonky. Root access is now needed again (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

su - root
ipkg install sudo sudo-doc

(:tableend:)

Create a file called twonkymediaserver in /etc/init.d containing (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

#!/bin/sh
case "$1" in
'start')
sudo -u twonky /home/twonky/twonkymedia-5.0.65/twonkymedia.sh start
;;
'stop')
sudo -u twonky /home/twonky/twonkymedia-5.0.65/twonkymedia.sh stop
;;
'restart')
sudo -u twonky /home/twonky/twonkymedia-5.0.65/twonkymedia.sh restart
;;
'status')
sudo -u twonky /home/twonky/twonkymedia-5.0.65/twonkymedia.sh status
;;
esac

(:tableend:)

Set the executable bits on this init.d file (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

chmod +x /etc/init.d/twonkymediaserver

(:tableend:)

Test the script's functioning by issueing the following command which should provide the server's PID (check with 'ps' !) (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

/etc/init.d/twonkymediaserver status

(:tableend:)

If all is working properly (if not, edit twonkymedia.sh and modify the running= parameters to properly obtain Twonky's PID), add the init.d script to automatic startup/shutdown (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

update-rc.d twonkymediaserver defaults 44 46

(:tableend:)

TwonkyMedia? Server on SlugOS/BE 5.3 issues

TwonkyMedia? Server will at the time of writing not run on SlugOS/BE 5.3. This is because it needs the GLIBC ABIs? called 'GLIBC_2.0', 'GLIBC_2.1' and 'GLIBC_2.1.3'. These are not included with SlugOS/BE 5.3's libc libraries. Other people have reported a similar issue with a program called CCcam? and in other distibutions like Debian Lenny.

Theoretic workarounds include: - TwonkyMedia? Server builds that do not require these ABI's. Mail TwonkyMedia? about this issue (mention the use of the GLIBC_2.0, GLIBC_2.1 and GLIBC_2.1.3 ABIs?) if you would like them to do this (and tell them about the same issue in Debian Lenny)!

- Recompile (g?)libc in SLugOS?/BE 5.3 including these ABIs?. If this is possible, an explanation how to do this by a more technically inclined SlugOS user is needed!

- Install support for the uclibc in SlugOS/BE 5.3. Again, if this is possible, an explanation how to do this by a more technically inclined SlugOS user is needed!

Prerequisites

Set the executable bit on some files in the Twonkymedia server directory

chmod +x twonkymediaserver chmod +x twonkymedia.sh chmod +x twonkymedia chmod +x cgi-bin chmod +x plugins chmod +x resources

Modify twonkymedia.sh script

Edit the twonkymedia.sh file to make some necessary changes for SlugOS

change the following variables at the start of the script

WORKDIR1?="/home/twonky/twonkymediaserver-5.0.65" PIDFILE="/home/twonky/twonkymediaserver-5.0.65/mediaserver.pid"

add the following lines in the start section directly after the "$TWONKYSRV" -D line

running="`ps ax --no-heading | grep -e twonkymedia | grep -v grep | grep -v twonkymedia.sh | grep -v twonkymediaserver | cut -d ' ' -f 2` echo $running > $PIDFILE

replace all occurrences of the -s TERM and -s HUP signal parameters for kill and killall with -SIGTERM and -SIGHUP respectively. e.g.

killall -SIGTERM twonkymedia

replace the line starting with 'running' in the status section with

running="`ps ax --no-heading | grep -e twonkymedia | grep -v grep | grep -v twonkymedia.sh | grep -v twonkymediaserver | cut -d ' ' -f 2`

and finally, in the same section replace the echo "TwonkyMedia? server IS running." with

echo "TwonkyMedia? server is running with PID $PID."

Test the installation

change the following variables at the start of the script

WORKDIR1?="/home/twonky/twonkymediaserver-5.0.65" PIDFILE="/home/twonky/twonkymediaserver-5.0.65/mediaserver.pid"

add the following lines in the start section directly after the "$TWONKYSRV" -D line

running="`ps ax --no-heading | grep -e twonkymedia | grep -v grep | grep -v twonkymedia.sh | grep -v twonkymediaserver | cut -d ' ' -f 2` echo $running > $PIDFILE

replace all occurances of the -s TERM and -s HUP signal parameters for kill and killall with -SIGTERM and -SIGHUP respectively. e.g. (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

killall -SIGTERM twonkymedia

(:tableend:)

replace the line starting with 'running' in the status section with (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

running="`ps ax --no-heading | grep -e twonkymedia | grep -v grep | grep -v twonkymedia.sh | grep -v twonkymediaserver | cut -d ' ' -f 2`

(:tableend:)

and finally, in the same section replace the echo "TwonkyMedia? server IS running." with (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

echo "TwonkyMedia server is running with PID $PID."

(:tableend:)

Set the executable bit on some files in the Twonkymedia server directory (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

chmod +x twonkymediaserver
chmod +x twonkymedia.sh
chmod +x twonkymedia
chmod +x cgi-bin
chmod +x plugins
chmod +x resources

(:tableend:)

Start TwonkyMedia? Server (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

/home/twonky/twonkymediaserver-5.0.65/twonkymedia.sh start

(:tableend:)

Check whether TwonkyMedia? Server is running properly (the ps command should produce a list which includes 'twonkymedia -D' and 'twonkymediaserver -D', the netstat command should show a line showing the Slug's IP address:9000 and LISTEN) (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

ps -fu twonky
netstat -an | grep 9000

(:tableend:)

(:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

- to be inserted: twonkymedia.sh -

(:tableend:)

Set the executable bit on some files in the Twonkymedia server directory (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

chmod +x twonkymediaserver
chmod +x twonkymedia.sh
chmod +x twonkymedia
chmod +x cgi-bin
chmod +x plugins
chmod +x resources

(:tableend:)

(:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

@] (:tableend:)

@] (:tableend:)

Twonkymedia server 5.0.65 for SlugOS/BE 4.8

Edit the twonkymedia.sh file to make some necessary changes for SlugOS

At the end of the page a section with problems encountered when trying to install Twonkymedia Server on SlugOS-BE 5.3. A workaround to run Twonkymedia server on this version of SlugOS-BE is still needed.

If not done already, create a user group in SlugOS that has read access to the directory tree containing the media files you would like to serve through Twonkymedia Server (the group name is called 'media' in this example) (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

addgroup media
adduser -G media twonky

(:tableend:)

Check whether glibc-dbg is installed, and install it if not present (:table border=0 width=80% bgcolor=#ddeedd:) (:cell:)

ipkg list_installed | grep -i glibc-dbg
ipkg install glibc-dbg

(:tableend:)

Download the preferred version of Twonkymedia Server from http://www.twonkyforum.com in the 'Beta/Unsupported Builds' forum (In this example it's Twonkymedia server v5.0.65). Make sure you download the binary for the "Linux ARM big endian glibc" architecture.

su - twonky
wget http://www.twonkyforum.com/unsupported/5.0.65/twonkymedia-armeb-glibc-2.2.5-5.0.65.zip
mkdir twonkymediaserver-5.0.65
cd twonkymediaserver
unzip ../twonkymedia-armeb-glibc-2.2.5-5.0.65.zip

(:tableend:)

(:table border=0 width=40% bgcolor=#ddeebb:) (:cell:) This article pertains to:

• SlugOS 4.8-beta

(:tableend:)

Twonkymedia server 5.0.65 unsupported for SlugOS/BE 4.8

Searching for a uPNP media server that is compatible with a wide variety of clients (e.g. Microsoft WMP11? & WMP12?, Philips NP1100?) soon leads to Twonkymedia Server. Although Twonkymedia stopped supporting DIY installations of Twonkymedia Server on NAS devices like NSLU2, they still provide the necessary binary to install and run it. This page will provide for a step-by step installation manual to run Twonkymedia Server in SlugOS/BE 4.8

At the end of the page a section with problems encountered when trying to install Twonkymedia Server on SlugOS-BE 5.3. A workaround to run Twonkymedia server on this version of SlugOS-BE is still needed.