Got mt-daapd nightlies running on SlugOS/BE (aka OpenSlug)

FireFly Media Server (formerly mt-daapd) Firefly Media Server Forums Firefly Media Server Setup Issues Got mt-daapd nightlies running on SlugOS/BE (aka OpenSlug)

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #1898
    pedxing
    Participant

    FYI, I’ve been having more weird problems with Unslung and finally got fed up with its idiosyncrasies. Just not worth it since I’m not even using the web interface…

    So I’m trying out SlugOS/BE, the artist formerly known as OpenSlug. I thought Debian would be a bit heavy for this little machine (especially RAM-wise) so this looked like the best option.

    It was super easy to get it running. Almost TOO easy…

    First, I added the firefly nightlies to ipkg:

    echo "src firefly http://ipkg.fireflymediaserver.org/armeb" > /etc/ipkg/firefly.conf

    Then I added optware:

    echo "src optware http://ipkg.nslu2-linux.org/feeds/optware/nslu2/cross/stable" > /etc/ipkg/optware.conf

    Then I just did an ipkg update and ipkg install mt-daapd and Bob’s your uncle! All the dependencies just installed and everything’s working!

    So now I’m worried that something isn’t going to work long-run. But it’s working fine now.

    #14147
    rpedde
    Participant

    @pedxing wrote:

    FYI, I’ve been having more weird problems with Unslung and finally got fed up with its idiosyncrasies. Just not worth it since I’m not even using the web interface…

    So I’m trying out SlugOS/BE, the artist formerly known as OpenSlug. I thought Debian would be a bit heavy for this little machine (especially RAM-wise) so this looked like the best option.

    It was super easy to get it running. Almost TOO easy…

    First, I added the firefly nightlies to ipkg:

    echo "src firefly http://ipkg.fireflymediaserver.org/armeb" > /etc/ipkg/firefly.conf

    Then I added optware:

    echo "src optware http://ipkg.nslu2-linux.org/feeds/optware/nslu2/cross/stable" > /etc/ipkg/optware.conf

    Then I just did an ipkg update and ipkg install mt-daapd and Bob’s your uncle! All the dependencies just installed and everything’s working!

    So now I’m worried that something isn’t going to work long-run. But it’s working fine now.

    The only issue is that openslug seems to lag pretty far behind unslung.

    As far as debian, that’s what I’m running on two of my slugs. One be, one le. Works fine. Have dnsmask, a web server + php, samba, kernel-nfs-server, mt-daapd, and some other little stuff running on one. Seems to go okay. Not the fastest device in the world, but works great for what it is.

    #14148
    pedxing
    Participant

    FYI, Unslung expects init to start apps from /opt/etc/init.d, but SlugOS uses /etc/rcx.d instead. So simply create a symbolic link:

    ln -s /opt/etc/init.d/S60mt-daapd /etc/rc3.d/S60mt-daapd

    Also, it’s not a good idea to leave optware in the ipkg chain and do an ipkg upgrade – some are not compatible (busybox breaks SlugOS!). So once you get mt-daapd installed, remove optware.conf one from /etc/ipkg before doing an ipkg upgrade!

Viewing 3 posts - 1 through 3 (of 3 total)
  • The forum ‘Setup Issues’ is closed to new topics and replies.