Error with MacFusion uploading to FTP site

[B-Rand-Z]

I posted this over in MacFuse-Devel but thought maybe someone in
MacFusion would know...

I installed macfuse core 10.4-1.3.0 and then MacFusion 1.2 Beta3. I
logged on fine to my FTP site (using regular FTP) and the drive
appeared in Finder, no problem. I could create a new folder.
However, copying any files to that folder, or any folder, gave me the
Finder error that I don't have sufficient priveleges. The copy
operation actually starts, and seems to be uploading to the server,
and then at the very end it gets upset over perms and 'unrolls' the
upload. What could be going wrong?

i'm on a mac powerbook g4 on OS X 10.4.11.

Thanks.

[B-Rand-Z]

Hello I did some more research, and I think this is:

A). Limited to the Finder only
B). Possibly related to this issue regarding files that being with a
dot (??) such as .DS_STORE
http://code.google.com/p/macfusion/issues/detail?id=248&can=1

FWIW, I can copy files using terminal just fine, and this only happens
in Finder.

Does this narrow things down a bit? I seem to be getting the
impression that Finder is quirky in how it handles MacFuse mounted FTP
sites.

Thanks much.

[Michael Gorbach]

This is a tricky issue, and indeed it is a finder problem.
I would look at the various macfuse options for apple underscore
files.
Also, take a look at the solution suggested in the issue you
mentioned.

Michael

On Mar 21, 1:01 am, B-Rand-Z <brandz.feedb...@gmail.com> wrote:
> Hello I did some more research, and I think this is:
>
> A). Limited to the Finder only
> B). Possibly related to this issue regarding files that being with a

> dot (??) such as .DS_STOREhttp://code.google.com/p/macfusion/issues/detail?id=248&can=1

[B-Rand-Z]

Thanks for your reply.

I tried these options and none seemed to remedy the problem:
defer_permissions
default_permissions
noappledouble

The solution that is suggested in the issue below -- to stop Finder
from writing .DS_STORE files in network shares -- seems too heavy
handed, and it looks like Apple seems to recommend against doing that
(there's a link at the bottom of the article to an example of a side
effect of setting that switch). So, I guess I'm trying hard to make
it work with switches on MacFuse before resorting to changing the way
my OS works. :)

If I can find a way to make this work, I'm willing to update the FAQ
with details on what I ran into to help others who try to use
macfusion (since it is a really cool piece of software). I'd even be
willing to write a blog entry on it so searchers can find it (my few
searches brought up mostly folks with problems, and no real clear
solution). [http://search.yahoo.com/search?p=macfusion+insufficient
+permissions&ei=UTF-8&fr=moz2]

Any help/pointers would be appreciated.

Nice work on Macfusion, btw. Hope it spurs Apple to put ftp-write
capability in Finder in a future OS. :)

Thanks.

[Graham Perrin]

On Mar 21, 3:22 pm, B-Rand-Z <brandz.feedb...@gmail.com> wrote:

> Any help/pointers would be appreciated.

Finder is richer than most people realise. In my experience, Finder
(properly) requires things that some servers can't provide.

http://groups.google.com/group/macfuse-devel/msg/515eb00d2d1009f1

> Nice work on Macfusion, btw.  Hope it spurs Apple to put ftp-write
> capability in Finder in a future OS. :)

My suspicion is that such capability is possible, but that Apple
refrain from doing so because

* not all FTP servers are equal

* the FTP servers that don't fulfil requirements could give a false
impression that Finder is failing.

Good luck
Graham

[Graham Perrin]

On Mar 21, 3:22 pm, B-Rand-Z <brandz.feedb...@gmail.com> wrote:

> Any help/pointers would be appreciated.

Re .DS_Store
we find articles such as
Mac OS X 10.4: How to prevent .DS_Store file creation over network
connections
http://docs.info.apple.com/article.html?artnum=301711
and widespread discussion.

Re ._ (dot underscore) files
you'll find no preventative advice.
._ files should not be prevented.

----

Very broadly speaking, assume two things:

._foo.bar
may be written (possibly concurrently) whenever
foo.bar
is written

._foo.bar
may be removed after the write of
foo.bar
has completed, successfully.

----

Search for
brok MACS
to understand ._ files in this context.

Regards
Graham