You are here: Home » Topic » Time-out for off-line filespage 2

Time-out for off-line files

This topic contains 25 replies, has 4 voices, and was last updated by  rpedde 10 years, 3 months ago.

Viewing 11 posts - 16 through 26 (of 26 total)
  • Author
    Posts
  • #10572

    cstern
    Participant

    ALLRIGHT! It works!
    Using SSH I now have a root login console. What/where should I look for the daapd binaries if they are there?

    #10573

    rpedde
    Participant

    @cstern wrote:

    ALLRIGHT! It works!
    Using SSH I now have a root login console. What/where should I look for the daapd binaries if they are there?

    Could be anywhere… maybe ‘find / -name “*daap*”‘ would be instructive.

    Course, you’ll need a build chain to be able to get new binaries working for it.

    #10574

    cstern
    Participant

    it’s not there.

    Anyway, regarding the issue of this thread: What if the songs.db and songs3.db could placed at the user’s choice. Then, if it was on an off-line storage it would not be cleared when it is off-line, and when it is on-line everything is fine. Would that be a possibility for a quick workaround?

    Sort of… although it wouldn’t start when the files were online. But then you could start it when the files came online without problems.

    The db path is in db_param in the config file, so that could work.

    — Ron

    #10575

    cstern
    Participant

    I didn’t see your reply as it was in the last post. Thanks I will try that

    Claus

    #10576

    rpedde
    Participant

    @cstern wrote:

    I didn’t see your reply as it was in the last post. Thanks I will try that

    Claus

    Ah, sorry. Must have hit edit, and not quote.

    Sorry about that.
    — Ron

    #10577

    ilikecl

    hey cstern,

    Found your post while looking for ss4000 info.

    I have what I believe is firmware 1.4 build 709 also.

    Current version : fs-bc – 1.4-b709

    I tried to get root access according to the link, but it doesn’t work for me…? Could you let me know how you did it? Thanks.

    #10578

    cstern
    Participant

    I used SSH2 via Bitwise Tunnelier (http://www.bitvise.com/tunnelier – free for private use) and logged using the username “root” and password whatever-you-selected (default is “storage”).

    The link is only good for enabling the SSH2 server on the SS4000. Don’t forget to replace [IP-of-your-NAS] with the actual IP address of you unit.

    #10579

    brad.chapin
    Participant

    I LOVE the Firefly product on my Windows Machine, but would much rather install it on my Intel SS4000-e which is running all of the time. If someone has created a cookbook, I’d love to give it a try too! If not, I’d be more than happy to try and collaborate with the other owners out there to figure out a way to get this installed. This NAS has been OEM’d by quite a few companies and is therefore somewhat widespread.

    #10580

    rpedde
    Participant

    @brad.chapin wrote:

    I LOVE the Firefly product on my Windows Machine, but would much rather install it on my Intel SS4000-e which is running all of the time. If someone has created a cookbook, I’d love to give it a try too! If not, I’d be more than happy to try and collaborate with the other owners out there to figure out a way to get this installed. This NAS has been OEM’d by quite a few companies and is therefore somewhat widespread.

    Any inexpensive ones out there? I’d take a whack at it if it weren’t too pricey.

    — Ron

    #10581

    brad.chapin
    Participant

    Ron,
    I still haven’t been able to get it to work on my SS4000-e, but have been learning a lot along the way. Currently I’m under the impression that based on the architecture, I need a little-endian / ARM version in order to install. From the factory, SS4000-e isn’t running debian so the .deb packges doesn’t work nor most of the others that I have tried. I saw a packages called mt-daapd_svn-1634-1_armeb.ipk, so it looks like you have complied for ARM, but would need a little endian version (e.g. Intel based). Is this something that could be easily compiled? Also if you want, I can open up access to my system remotely for you.

    #10582

    rpedde
    Participant

    @brad.chapin wrote:

    Ron,
    I still haven’t been able to get it to work on my SS4000-e, but have been learning a lot along the way. Currently I’m under the impression that based on the architecture, I need a little-endian / ARM version in order to install. From the factory, SS4000-e isn’t running debian so the .deb packges doesn’t work nor most of the others that I have tried. I saw a packages called mt-daapd_svn-1634-1_armeb.ipk, so it looks like you have complied for ARM, but would need a little endian version (e.g. Intel based). Is this something that could be easily compiled? Also if you want, I can open up access to my system remotely for you.

    I have both varieties of arm… the debian one might work, at least as far as the binary goes. The .deb format is really a tar.gz in disguise. You might try (just for grins) renaming the .deb to .tar.gz and extract it. You’ll find a data and a control tarball. Grab the data tarball and extract it. In there are the binaries. You might just for grins try the mt-daapd binary just to see if it runs.

    If it does, you might be able to shoehorn it in that way. Of course, it might have a ton of dependancies that might bite you, I’m not sure, as I don’t know what libraries are already installed on the device.

Viewing 11 posts - 16 through 26 (of 26 total)

You must be logged in to reply to this topic.