Kindle WebDAV cadaver

[knc1]

The Min-Kloud's clerk has been stirring things up with a big stick (again).

The directory name that had the path separator character in it, is gone bye, bye (causes too many troubles).

What was there, is now found in:
dav:/kpw2/Amazon/Sources/v5.4.0/
(Presuming that Amazon will post firmware updates in the future.)

With a corresponding:
dav:/kpw2/Amazon/Binaries/
(Presuming that Amazon will post binary update packages.)

- - - - -

The problems with the Linux davfs2 driver:
Current news: Don't use it. Author bugfixes it every two years or so.

There is also an (old, but working nicely) command line client: cadaver
Just use your package manager to install it. It should be in all distributions.
(File paths above are copies of the cadaver prompt.)

@twobob: We might consider this for porting to the Kindle, it doesn't take the huge amounts of ram the other clients need.

Documentation on cadaver is limited to the man page:
http://linux.die.net/man/1/cadaver

Note: There also is a PerlDAV and a PyDAV client - not played with here.

[brianinmaine]

Originally Posted by knc1

There is also an (old, but working nicely) command line client: cadaver
Just use your package manager to install it. It should be in all distributions.
(File paths above are copies of the cadaver prompt.)

@twobob: We might consider this for porting to the Kindle, it doesn't take the huge amounts of ram the other clients need.

Documentation on cadaver is limited to the man page:
http://linux.die.net/man/1/cadaver

compiled openssl from source:http://www.openssl.org/source/openssl-1.0.1e.tar.gz
installed to /usr/local/openssl

compiled from source: http://www.webdav.org/cadaver/cadaver-0.23.3.tar.gz
./configure --with-ssl --prefix=blah,blah --with-libs=/usr/local/openssl

seems to work, but I am behind a restrictive proxy now. Can someone test, please?

[knc1]

Originally Posted by brianinmaine

compiled openssl from source:http://www.openssl.org/source/openssl-1.0.1e.tar.gz
installed to /usr/local/openssl

compiled from source: http://www.webdav.org/cadaver/cadaver-0.23.3.tar.gz
./configure --with-ssl --prefix=blah,blah --with-libs=/usr/local/openssl

seems to work, but I am behind a restrictive proxy now. Can someone test, please?

There is a public 'Cloud Service' that provides (tiny) free Clouds.
See: http://box.com

Yes, they try real hard to sell you services and apts - you can ignore all of that if you wish.

This (and nearly any other) 'Cloud Service' is a super-set of the WebDAV protocol.

So yes, you can use WebDAV enabled applications,
See: https://support.box.com/entries/2035...upport-WebDAV-
(Yes, from a desktop also - ignore the hard sell marketing.)

If you are viewing your main account (files) page in a browser while using cadaver, it will post the most recent action it (you) preformed.
Yes, cadaver has a help command (and 'folders' are called 'collections').
Yes, you can set your account to share with others (either by blind, read-only links or with read/write collaboration).

No, I am not selling Box.com services - but it is there and a free place to use as a test target.

core2quad ~ $ cadaver
dav:/? open https://dav.box.com/dav
Authentication required for dav.box.com on server `dav.box.com':
Username: xxxxxxx@yyyyyyyy.org
Password: 
dav:/dav/> ls
Listing collection `/dav/': collection is empty.
dav:/dav/> mput part_notes.txt
Uploading part_notes.txt to `/dav/part_notes.txt':
Progress: [=============================>] 100.0% of 415 bytes succeeded.
dav:/dav/> mkcol Kindle
Creating `Kindle': succeeded.
dav:/dav/> move part_notes.txt Kindle
Moving `/dav/part_notes.txt' to `/dav/Kindle/part_notes.txt':  succeeded.
dav:/dav/> close
Connection to `dav.box.com' closed.
dav:!> quit
core2quad ~ $

https://app.box.com/s/e1ytx89948j3rrd1ny2r

With a little bit of source code diddling to make cadaver usable from scripting, this will allow us to provide a KUAL button to find and directly download Kindle add-ons.
While allowing application developers an easy place to publish their application bundles.
(the 'stock' cadaver does not read commands from stdin)

Disclaimer: WebDAV is not the only way to do the above, so my idea here may die due to a better one replacing it.

So, yes, there is a reason for a WebDAV client on a Kindle.
Someone please test Brian's build for us.

[knc1]

Originally Posted by brianinmaine

compiled openssl from source:http://www.openssl.org/source/openssl-1.0.1e.tar.gz
installed to /usr/local/openssl

compiled from source: http://www.webdav.org/cadaver/cadaver-0.23.3.tar.gz
./configure --with-ssl --prefix=blah,blah --with-libs=/usr/local/openssl

seems to work, but I am behind a restrictive proxy now. Can someone test, please?

Would someone please test this?
It should work on any K5 from kTerm.

@NiLuJe: It has an upload/download progress bar.

[brianinmaine]

Originally Posted by knc1

Would someone please test this?
It should work on any K5 from kTerm.

@NiLuJe: It has an upload/download progress bar.

So I can log into box.com and make directories and stuff. All seems well to me. This doesn't really belong in this thread, though. Maybe a moderator can move it somewhere better, please?

[knc1]

Originally Posted by brianinmaine

So I can log into box.com and make directories and stuff. All seems well to me. This doesn't really belong in this thread, though. Maybe a moderator can move it somewhere better, please?

thanks a lot
maybe twobob will move it for us

[twobob]

tis done.

gimme a clue on a good title.

[knc1]

Originally Posted by twobob

tis done.

gimme a clue on a good title.

prefix: K5
title: Kindle WebDAV cadaver

Since there are multiple contenders for Kindle Kode distribution system/site I think we should continue to look at this possibility (its small, light weight, can be adapted to read commands from stdin).

The mini-cloud(s) that I am providing do not have the file level access controls I think are required for a public distribution repository.

But that level of control is not needed for "development resource pools" used by the small groups of people using my mini-kloud(s).

And as testing shows, it will work with at least the box.com Cloud Service.
So this does give the basic functions that would be expected for a collection(s) of anything shared by Kindle users. With direct access from those Kindles.

Note: Time passes and the world moves on - I was out-of-date above about Cloud Services being generally a super-set of WebDAV. That was once the case but no longer.