sorry for the late answer, but I am much engaged to debug the latest
release davfs2 1.1.1
This Howto is really out of date (it was out of date when I startet to
engage in davfs2). Please only use the documentation that is included in
the package. There is a README file, and after installation there is
also a manpage, but it is for 'mount.davfs' (man mount.davfs).
There is no more davfs module in the kernel. There is only the
mount.davfs program that communicates with the coda (or fuse) file
system in the kernel and the webdav-server.
version 0.2.8 and coda:
If the coda module really is running when you try to launch mount.davfs,
this message indicates, that another module uses the coda device, but
mount.davfs could not detect this. Do you run the real coda file system
(with venus) in parallel? In this case you might try without the coda
file system running.
Allthough this version is called beta (it needs some more testing by
real users), it has a lot of advantages over 0.2.8; and I consider it
just as stabel as 0.2.8.
As you can read and write, it is really curious that you can not delete
files. Some questions:
- what are the access permissions of the directory that contains the
file to delete?
- owner und group of this directory, who is the user that tries to
delete them? This user must have write and execute permissions for this
- access permissions, owner and group of the file. Has the user that
wants to delete it, write permission on that file?
-What is the exact error message you get when you try to delete the file?
- Are there any restrictions set on the server?
If everthing seems to be ok up to here, we are in trouble. In this case
it would be useful if you could access the server logs, to see what
requests davfs2 send to the server, and what was the answer.
Tracing the HTTP traffic, using Ethereal or tcpdump, would even be better.
If you install the package the standard way (./configure, make, su, make
install), the documentation should be in /usr/local/share/davfs2 (this
is a mistake, it really should be in /usr/local/share/doc/davfs2).
It is much preferable to add an entry into /etc/fstab and use the
standard mount program, instead of calling mount.davfs directly. Please
see the examples in the man page.
I just released version 1.1.1; at the moment we do some debugging and I
would not suggest to use this package. But the version in the CVS
repository seems fairly stable. And can use the fuse kernel file system,
if there are troubles with coda.
Nevertheless: I think it is easiest to stick with davfs2-1.0.2 and try
to solve the delete problem.
Waiting for answer to the above questions