Time-out for off-line files

[cstern]

I can see that the source code is available for download.

http://downloadcenter.intel.com/scripts-df-external/Detail_Desc.aspx?agr=N&ProductID=2366&DwnldID=13026&strOSs=All&OSFullName=All%20Operating%20Systems&lang=eng

[fizze]

Hm, looks like telnet was only active in some older firmwares.
There seems to be an SSH-daemon onboard though.

Rumors have it you can enable it by opening this page:

http://[IP-of-your-NAS]/ssh_controlF.cgi

in your browser.

Do you care to verify and post your results?;)

[rpedde]

@cstern wrote:

It seems doable, but being a complete imbecile with regard to Linux and hacking I think (for me) it is better left to those capable of doing such things. Also I am not really sure what to do – the kwaak project seems a bit preliminary at this point.

err, yeah. I guess I should have said “seems hackable if you don’t really care if you brick it”. Still, even without jtag, it looks safe to flash. USB looks to be the only thing not working on the kernels that are floating around. So using that and a debian “mkbootstrap”, you could probably be in business with etch.

Course, again, that’s only if you don’t mind potentially bricking it. 🙂

So for me it would be easier if Firefly could just ignore/wait/retry if the NAS is (temporarily) unavailable.

Thanks for the link anyway – it was interesting

np. I have been thinking about that issue, though, and I may figure something to do with it. It really is harder than it seems, though.

[cstern]

The ssh shell:

It’s a no-go. You just get to the normal admin interface… 😥

[cstern]

@fizze wrote:

Hm, looks like telnet was only active in some older firmwares.
There seems to be an SSH-daemon onboard though.

Rumors have it you can enable it by opening this page:

http://[IP-of-your-NAS]/ssh_controlF.cgi

in your browser.

Do you care to verify and post your results?;)

I just updated the firmware to 1.4 build 709 and the above hack seems to working (again?), or, at least the ssh daemon can be turned on from that page. I haven’t taken it further from there yet.

[cstern]

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?

[rpedde]

@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.

[cstern]

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

[cstern]

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

Claus

[rpedde]

@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

[Author]

Posts