From: Sean M A. <sea...@gr...> - 2002-04-03 19:30:22
|
Hi all, I just downloaded 0.2.4 and I must say things look good with it, although it seems slow to me. One note about compiling I noticed is that on my RH7.1 box w/ 2.4.9-21 kernel I had to use the --with-kernel option on the configure, otherwise I received errors about not finding net/scm.h and net/ip.h headers. I don't know if this is something with my system or just something that needs to perhaps be updated on the readme. Aside from that, I seem to not be having the proxying issues I ran into before. This is a good thing! Authentication seems to work with or with out the proxy. One question I have regards needing to be root to run mount.davfs. From my perspective it's no big deal, since I have local root on my machine, but for a person here who has a managed desktop (and wouldn't have root) this is an issue. When trying to run mount.davfs as a normal user, I get a mount: Operation not permitted. Our DAV server requires authentication to maintain integrity of documents in a KM system. When the filesystem is mounted as root, all the files/dirs under the mount point are owned by root and may not be readable by a nonroot user. I'm not sure what the logic is behind how linux permissions get assigned to dav files, but I noticed that all files were not world writable and some were not world readable. I'd envision a linux user being about to mount a dav server to a mount point in their home directory (or something like that). So is there a way I can accomplish this? For instance, I could have them put a mount command in their .profile or something like that. Thanks. -- Sean M. Alderman ITRACK Systems Analyst PACE/NCI - NASA Glenn Research Center (216) 433-2795 Calling a windowed operating system "Windows" is like naming an automobile "Wheels." |